Solution skill
CloudBees impressions with targeting=false are defaults, not exposures
Complete solution
When you consume CloudBees impression callbacks, always check impressionData.targeting first.
CloudBees impressions with targeting=false are defaults, not exposures
TL;DR
When you consume CloudBees impression callbacks, always check impressionData.targeting first. targeting=false means the user got the flag's default value because no targeting rule matched, not because they were bucketed into a variant. If your analytics treats default-served impressions as exposures, control and treatment counts inflate and experiment reads go wrong.
Use this when you run into the situation in the title.
When not to use this skill: unrelated tasks. It covers only the procedure above.
Compatibility
The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.
Details
Filter analytics to targeting=true impressions when you measure rule performance, and log default impressions separately as a config-coverage signal.
Context: Official docs (CloudBees, impression handler): documents the analytics gotcha: an impression with targeting=false means the flag served its default value with no active targeting rule, and treating it as a targeted exposure corrupts experiment analysis.
Evidence
Source: Official docs (CloudBees, impression handler): documents the analytics gotcha: an impression with targeting=false means the flag served its default value with no active targeting rule, and treating it as a targeted exposure corrupts experiment analysis.
Verified resolution: When you consume CloudBees impression callbacks, always check impressionData.targeting first. targeting=false means the user got the flag's default value because no targeting rule matched, not because they were bucketed into a variant. If your analytics treats default-served impressions as exposures, control and treatment counts inflate and experiment reads go wrong. Filter analytics to targeting=true impressions when you measure rule performance, and log default impressions separately as a config-coverage signal.
Source URL: https://docs.cloudbees.com/docs/cloudbees-rollout/latest/reporting/impression-handler
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_Occwn01VLTaeWHhGL5IUFQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">CloudBees impressions with targeting=false are defaults, not exposures <span>— Vectle</span></a>