As you already know, you can set up a wide variety of actions via the Dashboard - triggers, Cookie Wall with Alternative, scenarios... So, how does the Dashboard prioritize actions in the user journey when you have multiple set up? What's the logic behind it?

Well, you're in the right place to discover all!

🟠 The trigger feature is available for Enterprise plan only.

Priority of actions within the Dashboard

The order of action priority can be summarized very simply:

Trigger > Cookie Wall with alternative > Scenario

This works as a funnel, going from actions that reach a more global audience, to one that's more personalized to the user's profile or context.

Journey example

Let's illustrate this prioritization with an example:

In the Dashboard

Here's what is set in the Dashboard:

A trigger for users coming from Facebook

A Cookie Wall with Alternative set in the default context (this will be shown to users who don't consent to cookies)

A paywall scenario in the same context, targeting all users

From the user side

What does my reader see?

Let's imagine I am a reader coming from Facebook. Because of the trigger set up on your Dashboard, I get directed to an unlocked article that the publisher is offering me for free.

I then wish to read more articles, but, as I didn't give consent to cookies, I get shown a Cooke Wall with Alternative. I decide to give consent and visit another content before being shown the paywall.

Then, I want to read another content, but as I did not give my consent, I see a cookie wall with alternative. I finally decide to give my consent, I visit a new page, and see the subscription wall.

OK, got it! But what about inside scenarios themselves?

Priority of actions within the scenario

The same logic is applied inside the scenario as within the Dashboard.

Context > Group > Scenario actions

This order follows the usual flow that you're led to follow when setting up scenarios in the Dashboard.

These 3 steps can then be divided further into specific actions and, again, placed in order of priority:

For contexts:

1 - Custom value

2 - Location

3 - Device type

4 - Content type

5 - Default context

For groups:

1 - Custom group

2 - Native groups (all users, or volatiles/occasional/regular/fans groups)

For scenarios:

1 - Temporary scenario activated for the current date

2 - Classic scenario

For actions:

1 - Widget order as defined in the scenario

Voilà ✨ Now the order of priority of actions in the Poool Dashboard should be clear!

Keep this article on hand incase you wish to set up multiple types of journeys 😉

Need a refresh on some of the terms used in this article? Find them here: Triggers, Cookie wall with alternative, Context, Group, Scenario.

And for any questions you may have, our team is at your disposal to answer!

Did this answer your question?