Incrementality
Part of CTV attribution and incrementality
Reviewing and comparing CTV attribution windows in reports
Audit CTV post-view and post-click windows, credit rules, event counting and data cut-offs before comparing attributed actions.
An attribution window is the period after an eligible ad impression or click in which a recorded action may receive credit. Post-view and post-click are separate clocks: each starts with its eligible exposure event, while the conversion event and credit model determine whether a later action qualifies and how credit is assigned.
Compare each CTV report’s effective windows alongside its event definition, credit model, counting method and cut-off. A different window can change credited totals without changing customer behaviour; eligibility for credit does not show how long an ad’s effect lasts or whether it caused an action.
Find the setting behind the number
Record effective post-view and post-click durations separately, along with the event that starts each clock, the conversion event counted, attribution model, counting method, report time zone, event-date convention and treatment of repeated actions. Compare those fields side by side before reading totals.
Check the effective configuration for the relevant campaign, placement or tracker rather than assuming a platform default applies everywhere. A label is not a universal duration, and providers may define labels differently.
A longer window cannot recover an impression or action the matching system never recorded.
Campaign Manager 360 Help names “Floodlight conversion windows”, “How Floodlight counts conversions” and “About attribution tracking”. Check the relevant window, counting and tracking rules separately, and compare reports using their effective configurations.
Key CTV Attribution Configuration Settings
- Report Time Zone
- UTC or local (Australia) – verify in platform settings
- Event-Date Convention
- Marketing touchpoint date (Accrual) vs. order date (Cash Snapshot)
- Eligibility for Credit
- Depends on configured window, not ad effect duration
- Repeat Actions Treatment
- Counted once or multiple times – check reporting rules
- Window Cut-off
- Full window must elapse before exposure is mature for credit
Check the credit and counting rules
Identify the attribution model used for each CTV report. Model names used in attribution guidance include last-touch, multi-touch and time-decay; if reports use different models, differences in credit cannot be attributed to windows alone.
A conversion can follow several ads, and different models can assign credit to different eligible interactions. Another channel can receive credit for the same event in a separate report.
Northbeam’s Clicks + Deterministic Views model assigns fractional conversion and revenue credit across channels. Click touchpoints receive their own share; impressions are grouped by ad platform and split within each pool regardless of ad type or funnel stage, with credit allocated proportionally by view count.
MNTN attributes conversions from a household following a Verified Visit using deterministic household-level matching. Northbeam’s model uses multi-touch fractional attribution across touchpoints, so the models’ credit rules differ as well as the windows reported for their setups.
Reports may use different event-counting methods, such as counting every event or limiting repeated events. A window comparison is incomplete if the event or counting method changed too.
Northbeam’s Accrual Performance dates revenue and transactional credit to the marketing touchpoint; Cash Snapshot dates them to the order. Keep the accounting mode and event-date convention consistent when comparing totals, because the date assigned to credit changes.
CTV Attribution Windows and Credit Rules Comparison
- Attribution ModelNorthbeam: Clicks + Deterministic Views (multi-touch fractional)
- Attribution ModelMNTN: Verified Visit (deterministic household-level matching)
- Credit AllocationFractional across touchpoints; impressions grouped by platform and split proportionally by view count
- Credit AllocationDeterministic household-level attribution; no fractional credit per touchpoint
- Event Counting MethodAccrual Performance: credits to marketing touchpoint date; Cash Snapshot: credits to order date
Compare like with like
Kochava describes 24 hours as a typical impression lookback for re-engagement trackers, adjustable for deterministic and probabilistic matches. Its guidance for OTT and CTV cross-screen conversions calls for appropriate partner and tracker configurations.
MNTN performance in Northbeam requires Clicks + Deterministic Views to be enabled and MNTN selected. The setup guidance calls for attribution and look-back windows of 30+ days; this is a different configuration context from Kochava’s typical 24-hour impression lookback, not a like-for-like post-view and post-click duration comparison.
Hold the event, eligible inventory, model, counting method and windows constant where possible. To isolate a window effect, compare reports with other fields matching and show each configured duration beside credited counts; flag other differences rather than attributing the whole change to the window.
If settings changed during the reporting period, check whether the change recalculates earlier events or applies only to new events. A report spanning such a change needs particular care.
For each post-view or post-click clock, an eligible impression or click is not mature until its full configured window has elapsed by the report cut-off. Compare cohorts only after that duration has elapsed; otherwise, the latest exposures have had less time to receive credit.
Describe the result as actions credited under the stated rules. Incremental sales require a suitable control or comparison.
How to Compare CTV Attribution Reports Accurately
- Identify the effective post-view and post-click windowsCheck report settings, not assumptions. Confirm duration, start event, and cut-off time.
- Verify the attribution modelEnsure models like last-touch, multi-touch, or time-decay are consistent across reports.
- Confirm event counting methodDetermine if every event is counted or repeated actions are limited.
- Align accounting mode and event-date conventionUse consistent dates—marketing touchpoint vs. order date—for accurate comparisons.
- Isolate window effects only when other settings matchHold all other variables constant to attribute differences solely to window changes.



