Cross-campaign behavior lets you control how one survey campaign interacts with other survey campaigns. You can find this set of options in the Advanced Options tab of the survey editor.<\/p>\n\n\n\n
This is useful when you run multiple surveys at the same time and want to avoid overlapping survey experiences on different channels (web vs. mobile), poorly timed follow-up campaigns, or make sure a sequence of surveys is shown in specific order.<\/p>\n\n\n\n
Cross-campaign behavior helps you coordinate campaigns without having to build complex audience rules manually.<\/p>\n\n\n
\n<\/figure><\/div>\n\n\n
Sequence<\/h2>\n\n\n\n
Use Sequence<\/strong> when you want to show a survey only after users have seen selected survey campaigns.<\/p>\n\n\n\n
The survey becomes eligible only after the configured waiting period has passed since the previous survey was viewed. This allows you to create a controlled order between campaigns, such as showing a follow-up survey a few days after an initial feedback request.<\/p>\n\n\n
\n<\/figure><\/div>\n\n\n
You can configure the following options:<\/p>\n\n\n\n
\n
Selected surveys<\/strong>: Choose the survey campaigns that should be used as the prerequisite for this campaign.<\/li>\n\n\n\n
User must have seen<\/strong>: Define whether users need to have seen all<\/strong> selected surveys or any<\/strong> of the selected surveys before this campaign can become eligible.<\/li>\n\n\n\n
Wait period<\/strong>: Define how much time must pass after the previous survey was viewed before this campaign can be shown.<\/li>\n<\/ul>\n\n\n\n
For example, you can configure a campaign to become eligible only after a user has seen a Product Satisfaction survey and at least 7 days have passed.<\/p>\n\n\n\n
Optional: Combine with segments<\/h3>\n\n\n\n
The Sequence option controls when<\/strong> a campaign can be shown based on whether another campaign was viewed.<\/p>\n\n\n\n
If you also want to control who<\/strong> should see the campaign based on how they responded to a previous survey, use a user segment in the Target Audience<\/strong> section.<\/p>\n\n\n\n
For example, if you want to show a follow-up campaign only to users who gave a high NPS score, create a segment that includes users who responded with an NPS score above your chosen threshold. Then, use that segment as the target audience for the follow-up campaign.<\/p>\n\n\n\n
In other words, Sequence controls the timing<\/strong>, while segments control the audience<\/strong>.<\/p>\n\n\n\n
Prevent overlap<\/h2>\n\n\n\n
Use Prevent overlap<\/strong> when you want to exclude users who have already seen or responded to selected survey campaigns.<\/p>\n\n\n\n
This helps you avoid duplicate survey experiences across campaigns and channels. For example, if you run similar surveys in your web app and by email, you can prevent users from receiving both campaigns after they have already interacted with one of them.<\/p>\n\n\n
\n<\/figure><\/div>\n\n\n
You can configure the following options:<\/p>\n\n\n\n
\n
Seen surveys<\/strong>: Exclude users who have already seen one or more selected survey campaigns.<\/li>\n\n\n\n
Responded surveys<\/strong>: Exclude users who have already responded to one or more selected survey campaigns.<\/li>\n<\/ul>\n\n\n\n
For example, you can exclude users from an email survey if they have already responded to a similar in-app survey.<\/p>\n","protected":false},"excerpt":{"rendered":"
Cross-campaign behavior lets you control how one survey campaign interacts with other survey campaigns. You can find this set of options in the Advanced Options tab of the survey editor. This is useful when you run multiple surveys at the same time and want to avoid overlapping survey experiences on different channels (web vs. mobile), […]<\/p>\n
![\"\"](\"https:\/\/refiner.io\/docs\/wp-content\/uploads\/2026\/06\/Screenshot-2026-06-02-at-15.57.07-1024x347.png\")
<\/figure><\/div>\n\n\n![\"\"](\"https:\/\/refiner.io\/docs\/wp-content\/uploads\/2026\/06\/Screenshot-2026-06-02-at-15.59.10-1024x631.png\")
<\/figure><\/div>\n\n\n![\"\"](\"https:\/\/refiner.io\/docs\/wp-content\/uploads\/2026\/06\/Screenshot-2026-06-02-at-15.59.44-1024x524.png\")
<\/figure><\/div>\n\n\n