Campaign Priority

Overview

Campaign priority determines the execution order when multiple campaigns are set to trigger on the same event. The SDK processes the configuration from top to bottom, ensuring that higher-priority campaigns (those listed earlier) are executed first, while lower-priority ones are only considered if higher-priority campaigns do not meet all required conditions.

Properly configuring campaign priority ensures that:

✔ The most relevant campaigns are triggered first.

✔ Lower-priority campaigns serve as fallback options.

✔ Campaign execution follows a structured and predictable order.

Priority Value Range

Screenshot 2024-10-21 at 13.28.14-20241021-102842.png

1 – The lowest priority.
2,500,000 – The highest priority.

By setting campaign priorities correctly, you can optimize the delivery sequence and ensure that campaigns are executed based on their importance and relevance.

How Campaign Priority Works

Different Priorities with the Same Conditions

When multiple campaigns have the same targeting conditions but different priorities, the SDK selects the campaign with the highest priority and stops processing further.

Example:

You have three campaigns with no restrictions on impressions:

Campaign	Event	Priority
Campaign 1	Event 1	3
Campaign 2	Event 2	2
Campaign 3	Event 1	1

The configuration order in the SDK will be:

Campaign 1 (Event 1)
Campaign 3 (Event 2)
Campaign 2 (Event 1)

Execution Flow:

✅ Event 1 triggers → SDK processes the config:

Campaign 1 matches → It is served.
SDK stops searching for other campaigns (Campaign 2 is ignored).
Campaign 3 is skipped as it does not match Event 1.

✅ Event 2 triggers → SDK processes the config:

Campaign 1 does not match (wrong event).
Campaign 3 matches → It is served.
SDK stops searching further.

Same Priorities with the Same Conditions

If multiple campaigns have the same priority and conditions, they are positioned randomly in the configuration but will trigger equally over time.

Different Priorities with Different Conditions

When campaigns have both different priorities and different conditions, the SDK will evaluate conditions first and then prioritize execution accordingly.

Example:

You want Campaign 1 to be served on the first trigger of Event 1 but Campaign 2 to be served only on the 5th trigger of Event 1 globally.

Campaign	Event Condition	Priority
Campaign 1	Event 1 (1/1 global)	1
Campaign 2	Event 1 (5th occurrence globally)	2

Configuration Order:

Campaign 2
Campaign 1

Execution Flow:

✅ Event 3 triggers globally:

Campaign 2 is skipped (not the 5th trigger yet).
Campaign 1 matches → It is served.

✅ Event 5 triggers globally:

Campaign 2 matches (it was set for the 5th occurrence).
SDK stops searching, and Campaign 1 is ignored for this trigger.

Priority and Limits

The same logic applies to campaigns with limits.

If a limited campaign has a higher priority, it will be served until its limit is reached.
Once the limit is exhausted, the SDK will switch to lower-priority unlimited campaigns.

Priority Across Different Campaign Types

The campaign type does not affect priority.
If both an Interstitial Campaign and an In-App Campaign are set for the same trigger, the SDK will select the one with the highest priority.

LTO Campaigns and Priority Considerations

All LTO (Limited-Time Offers) campaigns triggered by a trigger (without display) rather than an event follow a separate logic. For more details, refer to the LTO Campaigns article.

Summary of Priority Execution in SDK

✔ Higher-priority campaigns execute first when multiple campaigns match the same conditions.

✔ Equal-priority campaigns execute randomly but evenly over time.

✔ Different conditions override priority — triggers must match first.

✔ Limits affect execution — higher-priority campaigns with limits will be served first until exhausted.

✔ Campaign type does not influence priority — only configuration order matters.

By properly setting campaign priorities, you ensure the correct campaigns are shown at the right time, improving user experience and campaign efficiency.