I want to create a flow of a customer clicking on a Content Card in our App which instantly triggers an IAM.
The logical solution is for the Content Card click to log an Event. Then a separate campaign triggers the IAM based on the Event being updated. Problem is in testing it works on some devices and not for others maybe due to Events being updated in the user profile is delayed. You could create a Canvas with an Action Path to look for "Click content card", but the IAM will trigger in the next session. Any ideas?
Thanks
Nick
Hey Nick, not sure how Content Cards are integrated in your app, but one option could be to handle the click within the app code and then fire a custom event via the Braze SDK to trigger the IAM. That way you’re not waiting for the server-side event ingestion and the trigger can happen immediately on the client-side.
If the goal is for the IAM to appear right after the card click, this might be a more reliable approach. Otherwise relying on the next session could feel a bit disjointed since it may rely on the customer having their next session soon after (depending what the message is)
Hey nickvdk, I think Jerome is on the right track with the custom event approach via the SDK.
The only way I can think of to make this work reliably is to have the Content Card click logged as a custom event via the SDK, with a standalone IAM campaign triggered off that custom event. The key thing is making sure users already meet the audience criteria for the IAM before they start the session where they see the Content Card.
At the start of a user's session, Braze delivers all eligible IAMs to their device upfront. So as long as your users meet the audience criteria when that session begins, the IAM payload will already be on the device and Braze will simply be waiting and listening for the trigger action, which in this case is your custom event firing when the Content Card is clicked.
This should give you that seamless trigger you're after without needing a Canvas.
Hi Nick,
That is not going to directly work, as in-app messages load at the start of the session.
While there is a refresh call for content cards, there is not an equivalent for in-app.
Even if you go the route of an event, you are looking for the content to appear right after the click, that would never be reliable due to the timing to back to braze, update the user, trigger the message.
A more reliable and direct approach would be to ad code to the content card to open a new screen when the link is clicked.
