Goal Duration Settings

Goal Durations help configure:

• Assignment Period – how long a user remains assigned to a variant of a campaign.
• Conversion Logging Window – for how long conversions are tracked for that campaign.
• Visibility Period – when a user will continue to see a campaign after joining or closing it.

These settings apply to templates integrated on the respective page. Importantly, the user will continue to see the campaign even if they close and refresh the page. The main objective is to maintain consistent visibility of the assigned variant. For example, you can keep a campaign visible to promote free shipping, discounts, or other promotional offers.

Re-eligibility Duration

The Re-eligibility Duration determines the time span for which an impression log remains valid for a user. This controls when subsequent impressions of the same campaign are counted.

For example, the re-eligibility duration is set to 14 days:

• If the user viewed the campaign 2 days ago → Total impressions = 1
• If the user viewed the campaign again yesterday → Still total impressions = 1 (second view is not counted)
• If the user viewed the campaign after 16 days → Total impressions = 2 (re-eligibility period has elapsed)

Goal Conversion Duration

The Goal Conversion Duration defines the time window between the first display of a campaign to a user and the first goal completion (e.g., purchase) that is counted. After this window, subsequent conversions will not be attributed to the campaign.

For example, the Goal Conversion Duration is set to 5 days:

• Day 0: User views the campaign → Impressions = 1
• Day 2: User makes a purchase → Conversions = 1
• Day 10: User makes another purchase → Conversions still = 1 (the 5-day window has elapsed)

Re-eligibility Duration After Click

The Re-eligibility Duration After Click setting controls when a user becomes eligible again to see the same variant of a campaign after clicking on a link or button inside it.

During the re-eligibility period:

• The clicked variant is hidden.
• Other variants or the control group may still be shown to the user.

For example, the Re-eligibility Duration After Click duration is set to 5 days:

• Day 0: User views Variant A → Impressions = 1
• If the user does not interact, they may see Variant A or other variants in the next session.
• If the user clicks on Variant A → they won’t see Variant A for 5 days, but they may see Variant B or the control group.
• After 5 days → the user can be re-randomized into Variant A, Variant B, or the control group (based on traffic allocation).

Key Rules

• Cross-variant logic:
  • If Variant A is clicked → it is hidden for 5 days.
  • Variant B can still be shown during that period.
  • After clicking Variant B, it too will be hidden for 5 days (independent of Variant A).
• Impression counting:
  • If Variant A becomes visible again after the re-eligibility duration, its second impression is only counted if the re-eligibility duration since the first impression has elapsed.
• Non-interaction scenario:
  • If the user neither clicks nor closes Variant A, they may still see It in the next session.
  • Insider cannot fully guarantee variant suppression without a click or close event.

Together, these settings ensure controlled exposure to campaign variants, prevent over-counting impressions or conversions, and balance user experience with campaign fairness.

Re-eligibility Duration After Close

The Re-eligibility Duration After Close defines how long a user must wait before they can see the same campaign variant again after dismissing (closing) it.

During this re-eligibility period:

• The closed variant is suppressed.
• Other variants or the control group may still be displayed to the user.

For example, the Re-eligibility Duration After Close duration is set to 5 days:

• Day 0: User views Variant A → Impressions = 1
• If the user does not interact, they may still see Variant A (or another variant) in the next session.
• If the user closes Variant A, they will not see Variant A again for 5 days, but may see Variant B or the control group.
• After 5 days → the user can be re-randomized into Variant A, Variant B, or the control group.

Key Rules

• Variant suppression logic:
  • Closing Variant A hides it for 5 days.
  • Variant B can still be shown during that period.
  • If Variant B is then closed, it too is hidden for 5 days (independently of Variant A).
• Impression counting:
  • If Variant A becomes visible again after the re-eligibility duration, a new impression is only counted if the re-eligibility period since the first impression has elapsed.
• Non-interaction scenario:
  • If the user neither clicks nor closes a variant, they might still see the same variant in the next session.
  • Insider cannot guarantee suppression of a variant unless the user actively closes (or clicks) it.

This ensures users are not repeatedly exposed to a campaign variant they have already dismissed, while still allowing exposure to other variants and maintaining fair campaign distribution.

Session-Based Setting

The Session-Based Setting determines how campaign visibility and conversion tracking behave within the boundaries of a user session.

A session begins when a user visits the website and remains active until one of the following occurs:

• The user closes the browser or tab.
• The user is inactive (no mouse movement, clicks, or scrolls) for more than 30 minutes.

Campaign Visibility

If a user does not interact with a campaign (neither closes it nor clicks on it), they can still view the campaign during the same session. The campaign will remain visible until the session ends, even if the user refreshes the page.

Metrics & Conversions

Metrics tied to sessions only consider events that occur within the same session.

For example:

• If the Goal Conversion Duration is session-based:
• The user must view the campaign and complete the conversion (e.g., purchase) within the same session.
• If the conversion happens in a later session, it will not be counted.

This setting ensures campaign tracking and conversion attribution remain tightly aligned with a single user session, preventing cross-session carryover.