LogoLogo
PlatformsPricingRessources
  • Home
  • Onboarding
  • User documentation
  • Release Notes
  • Help Center
  • Help center
  • Troubleshooting
    • [Troubleshooting] Managing multiple currencies in the campaign reporting
    • [Troubleshooting] QA a campaign with a geolocation targeting
    • [Troubleshooting] Differences between the display frequency option and the scheduler
    • [Troubleshooting] Checking why you are not assigned to a campaign or variation
    • [Troubleshooting] Reasons for differences in data between Google Analytics and AB Tasty
    • [Troubleshooting] Checking if a page is assigned to a campaign
    • [Troubleshooting] I deactivated a variation in the traffic allocation step but still see it online
    • [Troubleshooting] I can’t log in to AB Tasty
    • [Troubleshooting] Traffic modulation doesn’t seem consistent with my settings
    • [Troubleshooting] The report indicated a statistical reliability yesterday, but today it doesn’t
    • [Troubleshooting] I see the original version very briefly before I see the variation (flickering)
    • [Troubleshooting] There are differences in data between AB Tasty and my analytics
    • [Troubleshooting] Scroll tracking data in report
    • [Troubleshooting] How to avoid being assigned to a test – the optout method
    • [Troubleshooting] My modifications are not displayed
    • [Troubleshooting] How to Force the Display of a Variation?
    • [Troubleshooting] Avoiding SEO mistakes in a redirection test
    • [Troubleshooting] Why is the editor not loading and how can I force it to open?
    • [Troubleshooting] QA Assistant doesn’t load on my website
  • FAQ
    • FAQ about custom widgets
    • FAQ Sequential Testing Alerts
    • FAQ traffic allocation
    • How to Check if the AB Tasty Tag Is Installed on My Website?
    • Why AB Tasty reporting data sometimes differs from Google Analytics data
    • FAQ About the Transaction Tag
    • FAQ Widgets
    • FAQ Campaign setup
    • FAQ about prioritization
  • Get help from our Copilots
Powered by GitBook
LogoLogo

AB Tasty Website

  • Home page AB Tasty
  • Blog
  • Sample size calculator
  • Release note

AB Tasty Plateform

  • Login

© Copyright 2025 AB Tasty, Inc, All rights reserved

On this page
  • Definitions
  • The scheduler
  • The display frequency option
  • Use cases

Was this helpful?

Edit on GitLab
Export as PDF
  1. Troubleshooting

[Troubleshooting] Differences between the display frequency option and the scheduler

Previous[Troubleshooting] QA a campaign with a geolocation targetingNext[Troubleshooting] Checking why you are not assigned to a campaign or variation

Was this helpful?

The more features we build inside our platform to bring you value, the more we need to accompany you on how to best use those. Moreover, we need to make sure that what we build answers your main needs and use cases.

We will dig-in that article on the differences that exist between the scheduler and the display frequency option inside the targeting. After going through this article, you’ll be able to clearly see in which cases you could use one of these two options.

Definitions

The scheduler

The scheduler has been built to allow you to play or pause one campaign at a precise date or timeframe that you’ll choose in the interface. The scheduler impacts that status of the campaign. It either plays or pauses it. Therefore, you do not need to manually activate it at the desired time, you can safely rely on our automatic scheduling feature to do so.

The display frequency option

This option has been built as a targeting criterion, which means it is at the same level of configuration as the segment or the trigger. While scheduler plays with the campaign’ global status, the display frequency will be a key element to define when the campaign will be triggered once put live by you or someone from your team. This will be defined on the user level (cookie).

Please be careful, the display frequency options are not totally similar to the recurrence options that you can find in the widgets forms. They apply at the user level (thus on the whole campaign targeting) and are not a display condition for the modification/widget per se. For example, if you want to display a message targeting all your URLs (or a wide ‘contains’) and having as frequency option ‘every 2 sessions’, the message will not only appear once on one page during the ongoing session as you may expect. Instead, the user will be affected on every targeted page ('Where' section) during the ongoing session. Same goes for 'every x days' and 'every x weeks' conditions. If you want to display the modifications made only one time per session, please use the frequency options 'Once per session'.

Use cases

Let’s play the “use-cases game” to know when to use what 😎 In the first column, you will find different use cases that you could face in your experiment journey (either when you want to test new ideas or personalize your visitor journey). In the second one, the option that we advise you to choose to configure well your experiment.

👉 Use cases
✅ Right option to choose

I want to launch my campaign during the launch of our special winter sales weekend.

Scheduler

I want my banner to be displayed only one time per user to avoid disturbing their navigation on my website.

Targeting display frequency option > 'Once' or 'Once per session'

OR see widget recurrence conditions

I want to strictly limit my campaign and launch it during weekends only for the coming year.

Scheduler

I want to promote my newsletter to every user each three sessions until they accept it.

Targeting display frequency option > 'Every 3 sessions'

Hope this article help you get a better idea about these two different features. If you still have a question or do not know which option to choose, do not hesitate to get back at your AB Tasty interlocutor, or ask our support 🚀