Banner - How to swap from Banner A to Banner B

sm

We are about to launch banners in our app but tight deadlines means we cannot get the right data onto the profile to do personalisation, which means we need 2 banners and swap between them.

I was thinking of having a canvas that displays Banner A for the "all app users" segment.

But now I have no idea how to remove banner A and display banner B.

Is this even possible?

I was thinking priority on B could be higher than priority on A, but we allow people to withdraw after accepting, which means we need to swap the banner back OR dismiss all together… if that is even possible?

Within a canvas, does a string of banner behaviour even work when there are no fixed delays and we're waiting on actions to change what is displayed?

Alternatively, can I use Liquid to pick up on the custom event or even a button click and personalise between 2 different messages that way?

any advice welcome.

dandoesmarketing

Hello SM, This is doable but I would take a different approach, not using a canvas. Run two banner campaigns on the same placement. Banner A targets everyone. Banner B targets people who've accepted and sits at a higher priority. When someone accepts in the app, set banner_accepted = true on their profile. That flips them into B's audience, so B beats A on the next refresh. When they withdraw, set it back to false. B drops off, A's still eligible for everyone, so it comes back on its own. I'd use a boolean custom attribute here ie. banner_accepted = true/false.

The only real requirement is that one bit of state, accepted true or false. If you can't write anything to the profile at all then you can't switch per user, but a single attribute update is usually easy to sneak in even on a tight timeline.

On your "dismiss altogether" question: add a second boolean like banner_dismissed = true and exclude dismissed users from both A and B. Once neither qualifies, the placement returns nothing and your app hides the container. So make sure you've got a clean empty state for that case.

For it to swap mid session, banners only update when the app asks for a refresh. That's session start, or you call the placement refresh method for your SDK. So after the accept, withdraw or dismiss fires, trigger a refresh. Just know there's a bit of ingestion lag before they qualify for the new one, so it won't feel instant.

Liquid won't save you here either. It can only pick between A and B using data that already exists when it renders, so it can't react to a click unless that click logs something and you refresh, which is what you're doing above anyway.

Hopefully that makes sense, please let me know if you have any questions.