What does this mean?
We successfully ingested a 3PAS impression report showing impressions on the affected date, but the Split Funnel tracking pixel did not track impressions for any of the adserver-reported placements/creatives on the indicated date.
What causes the issue and how to address it?
Determine the root cause by sequentially reviewing the possible causes below:
Case #1: The tracking pixel was deployed across live activity, but none of the active placements support third-party tracking [Uncommon]
- How to identify if this is the issue?
- Open the most recently ingested DCM impression report and locate an affected placement-creative row on the “Last Updated” date.
- Is the value of the “Placement Tag Type” field “Standard” or “Tracking ad impression (image)”?
- Is the case for all of the placement-creative row for the most recent date? If so, then this is likely the root cause.
Case #2: The tracking pixel was unsuccessfully deployed [Uncommon]
- How to identify if this is the issue? Find the “Applied Tags” under the Impressions Event Tag in DCM. Do you see your impression event tag in the “Applied Tags” table view? If not, then is your issue.
- Note: that you if you applied the Event Tag at the campaign-level, then you will need to individually review each Event Tag per campaign.
- How to address? You must add a new DCM Event Tag according to our instructions, which you can reopen via the Split Funnel “Settings” for your Advertiser.
Case #3: The tracking pixel was successfully deployed but only across activity that is not yet live [Rare]
- How to identify if this is the issue? If you applied the event tag at the advertiser “Advertiser” level, were none of the advertiser’s placements live on the indicated date? If so, then this is likely your issue.
- Note: if you applied the event tag at the “Campaign” level, were none of the placements of the selected campaigns live yesterday? If so, then this is likely your issue.
- How to address? The 3PAS report should contain only activity that you intend to track, so the client must adjust it to filter out the currently live activity they do not intend to track.
Case #4: The tracking pixel was successfully deployed across live activity but only within the last 8-12 hours [Common]
- How to identify if this is the issue? Did you deploy the tracking pixel within the last 8-12 hours? If so, this is likely the issue as it can take 8-12 hours to process impression data.
- How to address? Please allow one full day before reevaluating the status.
Case #5: The tracking pixel was correctly deployed but the tracking pixel’s macro(s) – used to collect the campaign IDs, placement IDs – were intentionally hardcoded, creating mismatching IDs between Split Funnel and adserver-reported data [Uncommon]
- How to identify if this is the issue? Are you able to locate the affected activity in the DCM Reporting UI (e.g. the partner, campaign, placement, creative IDs)? “No” indicates this is likely the root cause.
- How to address? You, as the advertiser deploying the tracking pixel, will typically be aware if/when the pixel’s macros have been hardcoded. The common use case is to separate activity of the same partner/campaign to report on each separately. Please ignore error messaging regarding these instances, as we work to release a more user friendly solution to addressing hardcoded macros.