Attribution and Confirmed CTR
Arc XP Compass reports click-through rate (CTR) for recommendations as Confirmed CTR: a click counts toward CTR only when it can be tied back to the exposure that produced it. This page explains how that link is made, how clicks are classified, and why the number you see in analytics slightly undercounts.
Why attribution exists
A recommendation request returns a ranked list, but a list being returned is not the same as a reader seeing it, and a click on a story is not necessarily a click on a recommendation. Attribution closes that gap. It links each recommendation click back to the exposure that produced it, so the analytics pipeline can measure click-through against what the reader actually saw.
Confirmed CTR needs two signals from the client for a rendered recommendation set:
- a
recommendation_exposurewhen a rendered recommendation actually becomes visible, and - a
recommendation_clickwhen the reader clicks one,
each carrying the attribution identifiers the Recommender issued when it served the set.
Where the identifiers come from
Every recommendation response carries attribution so that clicks tie back to the exact set and slot. The response as a whole carries one identifier for the rendered set, and each item carries its own per-item identifier and its position in the set. These identifiers are opaque: the client’s job is to round-trip them verbatim, not to interpret or construct them.
The set-level identifier is what joins exposures and clicks from the same render. The per-item identifier is what lets a click match the exposure of that same story. Without the per-item identifier a click can never match its exposure, and without the set-level identifier an exposure can confirm nothing.
For the response fields, see
Compass API referenceand the attribution notes under Popular and Trending. For how the Compass Web SDK carries them on a host-rendered surface, see Compass Web SDK: Recommendation Attribution.
What counts as an impression
An impression is a recommendation exposure: a reader saw the story in a recommendation slot, qualified by the viewport. It is not a count of recommendation API requests or of lists rendered. A story rendered below the fold that the reader never scrolls to is not an impression. The exact visibility and dwell thresholds the Compass Web SDK applies are described in Exposure and click timing.
How clicks are attributed
Clicks fall into three classes:
| Click class | What it is | How to use it |
|---|---|---|
| Confirmed clicks | A click that carried valid attribution context and matched an exposure of that same story inside the attribution window. | The CTR numerator. This is the customer-facing click number. |
| Context-only attributed clicks | A click that carried valid attribution context but never matched an exposure. | Real evidence of recommendation-driven engagement. It does not raise CTR, and it must never be turned into a second CTR. |
| Unattributed clicks | A click with no usable attribution context. | Evidence that interaction happened, nothing more. Never derive a rate from it (see the following caution). |
Why confirmed CTR is a lower bound
Matching a click to its exposure is one-shot. Event files arrive out of order, which is normal with batched delivery, and if a click is processed before the exposure that produced it, the click is permanently classified as context-only. It is never promoted to confirmed when the exposure lands later.
So confirmed CTR slightly undercounts, and the size of the undercount moves with your delivery patterns. If you need to see how much is being missed, the context-only series in
Clicks by typeis that gap.
Related documentation
- Compass Web SDK: Recommendation Attribution: register rendered recommendations so the SDK emits exposures and clicks.
- Compass Analytics: Technical Reference: the Advanced view, event-stream readiness, and the analytics endpoints.
- Compass API Developer Guide: the Events endpoint and the recommendation endpoints.