Dev guideAPI ReferenceUser Guide
Dev guideAPI Reference
Dev guideAPI ReferenceUser GuideGitHubNuGetDev CommunityDoc feedbackLog In
GitHubNuGetDev CommunityDoc feedback

Impressions and decisions

Describes when Optimizely Feature Experimentation sends impressions and decision data.

Suggest Edits

Optimizely Experimentation records an impression when a user is exposed to a flag variation. Specifically, Optimizely logs an impression through the following sequence:

  1. The Feature Experimentation SDK makes a decision for a user in an experiment through a Decide method.
  2. As a result, the SDK sends an SDK decision even* asynchronously to the Optimizely Event API. If the decision event indicates that the user is bucketed into an experiment, then Optimizely logs an impression, even if the user buckets into a disabled (or "off") variation, and therefore does not see the feature flag.

Impressions generate the visitor counts shown on the Results page. They also serve as the denominator for measuring conversion rates.

A decision event is one of the few SDK actions that trigger a network request. To avoid the request, you can disable dispatching decision events for the Decide method.

For more information, see the Decide method for your SDK language:

See the event dispatcher for your SDK language for more information on managing network requests:

How the SDK triggers impressions

Impressions are sent

  • When the user is bucketed into an A/B test, regardless of whether the flag is enabled or disabled in the variation.

Optimizely logs the impression when it receives the decision event indicating the user was bucketed into the experiment.

Examples:

  • A new visitor lands on a page and is exposed to an experiment.
  • A visitor refreshes a page and is exposed to the experiment again.
  • A return visitor is exposed to the experiment again.

Impressions are not sent

  • If the user is only bucketed into a targeted delivery rule, not into an experiment rule.
  • If no flag rule is running.

📘

Note

You must make sure that your local datafile has been updated after pausing or archiving a test to ensure you no longer send impressions to Optimizely.

Impressions deduplication

Depending on your application logic, your users may trigger rapid bursts of impressions. To avoid overcounting these bursts on your Reports page, Optimizely uses fixed-interval impressions deduplication. All impressions received within fixed 5-second intervals count as one impression for each user in an experiment—Optimizely buckets events into the fixed time windows based on when Optimizely received the event.

📘

Note

For more information on how impressions are triggered specifically, see Impression in Optimizely Experimentation.

deduplication example

Updated 18 days ago