“Missing adserver reporting … ”

What does this mean?

It means the Split Funnel tracking pixel collected impressions for this specific creative* on the indicated date, but the most recent Sizmek impression report omitted reporting for this creative on the indicated date.

Before jumping in – a pro-tip for Sizmek advertisers who use “Tracking Only” placements

There are two inconvenient idiosyncrasies to applying third-party tracking on Sizmek “Tracking-Only” and “In-stream Video Tracking” placement types, which frequently impact Sizmek advertisers using third-party tracking:

• “Tracking Only” and “In-Stream Video Tracking” placements can only support one third-party impression tracking pixel. Therefore, advertisers cannot add Split Funnel tracking to the these placement types if they already are using an existing third-party tracking URL, unless they discard the existing tracking URL.

What causes the issue and how to address it?

After reviewing the pro-tip above, determine the root cause by sequentially reviewing the possible causes below:

Case #1: The Split Funnel impression pixel is working correctly, but the Sizmek report was configured in a way that filters out reporting for the affected activity. [Uncommon]

• How to identify if this is the issue?
1. Does the Sizmek reporting UI show impressions for the impacted creative on the specified date?
2. Did you intend to track the affected activity?
3. Answering “yes” to both questions indicates this is likely the root cause.
• How to address? Please adjust the filters on your Sizmek impression report to include the affected activity in your report.

Case #2 You did not intend to deploy the tracking pixel across the affected activity, but you mistakenly did. [Uncommon]

• How to identify if this is the issue?
1. Does DCM report impressions for the placement/creative in the DCM UI?
2. Did you intend to not track the impacted creative?
3. Answering “yes” the first and “no” the second indicates this is likely the root cause.
• The fix: adjust the existing tracking pixel to omit this activity and remove the tracking pixel from specific ads or campaigns.

Case #3: The Sizmek report was configured correctly, but the tracking pixel’s macros 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 impacted activity (e.g. the campaign, placement, ad IDs) in the Sizmek UI ? “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.