Snapchat Attribution Window: The 28/1 Default and Tracker Discrepancies
Snapchat's attribution window is the pair of values Snap documents as the platform default: a 28-day click window and a 1-day view window - 28/1 - which Snap also recommends advertisers keep for the most complete measurement. Because the window decides how much credit a campaign collects, it is the first checkpoint whenever Snap's numbers and a tracker's disagree.
The 28/1 Default
Snap's attribution settings documentation states the recommendation directly: a 28-day click and 1-day view window (28/1) is the default on the platform, chosen to provide the most complete conversion measurement. The click window answers "did a conversion happen within 28 days of the click"; the view window adds credit for users who saw the ad and converted within a day without clicking. Compared with other networks - Reddit's 28/1 default, Meta's shorter modern defaults, Pinterest's 30-day click - Snap's default sits on the generous end, which matters whenever a tracker runs a shorter window.
Why Snap's Numbers Run Higher
| Difference | Snap | Typical tracker |
|---|---|---|
| Click window default | 28 days | Often 7 days |
| View-through credit | 1-day view included in the default type | Rarely counted |
| Attribution date | The day of the ad interaction | Often the conversion completion day |
None of these is an error: they are counting rules. The practical consequence is that a 7-day tracker against Snap's defaults will under-report relative to Ads Manager by design, and the gap is largest for view-driven campaigns where the 1-day view window collects credit the tracker never sees.
Reconciling Snap With a Tracker
The reconciliation checklist follows the counting rules:
- Align the tracker's click window with Snap's setting.
- Confirm whether the tracker counts view-through at all.
- Verify both systems attribute to comparable dates.
- Run both reports in UTC over the same closed period.
- Only then audit the delivery pipeline. One Snap-specific nuance: server events may carry timestamps up to 37 days old, so a flushed backlog can land conversions into old attribution periods - an apparent spike that is really delayed CAPI delivery. The payload mechanics behind it are in Snapchat conversion events, the delivery wiring in the Keitaro Snapchat integration, and the cluster map in the complete guide.
Frequently asked questions
Sources
Sources
- Manual testing and validation: Pixel Activator fires free test events while you tune parameters.
- Automated delivery: Most routes conversions from your tracker or CRM continuously, with deduplication and retries handled.