nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to trigger IAM right after the user clicks the push

Siva

Hey!

I have a question. I’m trying to send a push notification followed by an in-app message (IAM). The goal is for the IAM to appear immediately when the user taps the push and lands in the app. I’ve tried a few setups, but it’s not working as expected. Currently, I have two separate Canvases — one for the push and one for the IAM. In the IAM Canvas, I tested two entry criteria:

A custom attribute value change
A user action: "starts a session"

Neither approach worked. The IAM only triggers when I close and reopen the app — it seems the initial session after tapping the push isn’t being counted, likely because the app is already open in the background.

Any ideas on how to make the IAM trigger right after the user clicks the push and lands in the app? I don't want to use API or custom event, looking for a simple solution from whatever feature we have in Braze.

Thanks,

SIva

Find more posts tagged with

In-App Message

Comments

a_weaverling

@Siva, I'm not sure if you have any limitations that are preventing you from being able to combine both messages into a single canvas, but what I've done to accomplish what you're trying to do is have the messages in a single canvas. Depending on how your app is set up to send IAMs you'll have 2 options on setup.

Option 1: A very basic version of this canvas would have the push notification that feeds directly to an action path. The action path would have a path that users go down when they directly open the push notification with an evaluation period of maybe a day (most users won't have a push on their screen for longer than that), if they open the push they'll go down to the IAM which would be triggered immediately upon them opening the app.

Option 2: You would have the Push Notification send, then immediately send users to the IAM step, which would send the IAM when the user opens the app, this does get around users that did not interact directly with the push. They may have received it, swiped it away, but then opened the app for something else. It would still only go to users who were eligible for the push, but may not be a true metric of push engagement.

So I would think that if the IAM is directly related to the push notification and that you'd only want users who clicked the push to get it then Option 1 would be the better route to go.

If you need to have the 2 messages split into different campaigns, you could have an action-based entry criteria for the IAM campaign that requires entrants to have directly interacted with the push notification campaign. Unfortunately there's no direct method of checking if a user interacted with a canvas step as entry for another canvas so the messages would HAVE to be campaigns if they need to be split.

Hopefully this helps.

I did trying attaching images, but the platform was throwing errors unfortunately.

HariSirigiri1

There’s a catch when using Canvas for triggered IAM. I’d recommend using Campaigns instead. When IAMs are triggered via Canvas from a step, they typically appear in the second session, not instantly.

Here’s a better approach:

Create a Push Campaign first.
Then, set up a separate IAM campaign triggered by the action "Opened Push from specific campaign." This ensures the IAM is shown immediately in the same session.

If you're running a broader journey in Canvas, you can still use the API Triggered Campaign step to call the IAM campaign from within the flow.

TedScott

You are going to have a bit of a timing issue, so it is not going to be 100% reliable.

I have used a similar function do display a confirmation message after clicking a link (it worked, just not all the time).

IAM needs to be loaded before the page full loads so you are counting on the click to work all the way through the system into the campaign and trigger the IAM before the page finished loading