Skip to content
All field notes
Measurement
Published
Nov 4, 2026
Reading time
11 min read

CM360 YouTube Tracking: Audit Links, Formats and Reports

Reconcile missing CM360 YouTube reporting by checking advertiser links, creative sources, tracking-ad assignments, audio scope and report permissions.

AP
AdProof Research
Independent measurement desk
A video campaign record passes through advertiser linkage, tracking-ad assignment and report-access checks before reaching a client reporting folder.
The advertiser link, selected tracking ad, supported format and report configuration must agree before the client report can be interpreted. Conceptual illustration without campaign results.
In this guide (10 sections)

If DV360 reports YouTube delivery but the client's CM360 report is empty, identify the actual advertiser link, creative source and format-specific tracking workflow before looking for a place to paste a pixel. Then check the selected tracking object, report dimensions, permissions and data maturity. A tracking URL in a file does not establish that the client's reporting account receives the campaign's activity.

There are several supported architectures, and they have different boundaries. CM360-managed synced video creatives, an explicitly selected CM360 tracking ad and third-party verification-vendor measurement should not be assembled into one assumed integration. The practical output is a mapping from each bought population to its intended CM360 object and reporting contract.

Two historical questions expose the account boundary#

An older YouTube Audio tracking question asks how an agency can show DV360-bought impressions in a client's CM360 account. A separate programmatic question asks where to place client-provided impression tags when that CM360 account is not connected to DV360.

Both original bodies and their visible replies were checked on 4 November 2026. They are historical implementation questions, not evidence of a current outage. Replies propose account linking, support requests and manual tracking arrangements. Those suggestions do not establish what the current format supports or prove that the client's account is the linked reporting destination.

For your campaign

Verify the account link and tracking path

YouTube tracking depends on the advertiser relationship, creative format and selected tracking object. Discuss which workflow applies to your setup.

Discuss video measurement

A short inquiry to scope relevant options; no campaign access is needed.

1. Name the reporting outcome before choosing a tracking object#

Ask the client what needs to appear: impressions, clicks, completions, Active View measures, attributed conversions or cost. Keep those requests separate. A placement recording impressions does not establish availability of every metric or dimension the dashboard designer might select.

Create one mapping sheet:

LayerRecord to retain
Buying configurationDV360 partner, advertiser, campaign, line item, ad group and ad identifiers
Creative sourceYouTube-hosted ad with a selected tracking ad, or CM360-managed synced creative
CM360 relationshipAdvertiser, Floodlight configuration, site and association status
Measurement assignmentPlacement, ad, creative or selected tracking-ad identifiers
Format and marketActual line-item subtype, ad format, inventory and targeted country
Report contractMetric, dimensions, filters, dates, timezone, user access and extraction time

Retain identifiers privately and use names only as a reading aid. Similarly named advertisers in two products are not evidence of a link. A dashboard with the right client logo can still query a different CM360 advertiser or exclude the relevant placements.

2. Verify the advertiser relationship, not merely authorization#

Google's advertiser-linking documentation says a CM360 relationship is established while creating the DV360 advertiser, using a shared Floodlight configuration. It cannot be added to an already-created unlinked DV360 advertiser through that workflow, and the connection cannot later be unlinked. Only objects within the selected CM360 sites sync.

The separate Floodlight association reference distinguishes authorization from a completed link. “Authorized, not linked to Display & Video 360” is not the same status as “Linked.” Inspect the associated partner, advertiser and site details rather than interpreting a sharing permission as completed campaign reporting.

For an existing advertiser, collect the current relationship first. If the intended client account is not linked, ask the responsible account owner to establish the supported plan for that architecture. Do not recommend recreating or moving a live advertiser as an incidental troubleshooting step; the identifiers, shared objects and continuity of reporting need their own review.

When an object is missing from the selection interface, check its CM360 site and the last configuration or creative change. Google's link reference distinguishes initial synchronization from later creative synchronization. A source object existing in CM360 is not proof that the corresponding eligible creative is already available in DV360.

3. Determine which creative architecture is actually in use#

The current unified creative-trafficking guide describes CM360 placements syncing to DV360 as creatives for supported YouTube auction and instant-deal workflows. It lists supported reach, view and Demand Gen subtypes, while explicitly excluding YouTube Audio and ad-sequence line items.

For that synced architecture, inspect the CM360 placement and the DV360 creative/ad mapping. Do not add a manual tracking ad simply because an older tutorial assumes every YouTube ad begins as a separately uploaded video. The documented workflow removes that manual requirement for its supported configuration.

Also preserve the ad group's source setting. The guide warns that changing the ad source removes assigned creatives and associated ads. A reporting investigation should therefore begin with read-only evidence of the existing source, assignments and eligibility, followed by a clearly scoped change if one is needed.

For the separately selected tracking-ad architecture, Google's enhanced YouTube tracking reference documents selecting a CM360 tracking ad for listed in-stream, bumper and non-skippable ads. It also states that SDF cannot append impression or click trackers from non-linked CM360 sites or third-party ad servers. A bulk-upload field is not a documented way around the account boundary.

Do not generalize either workflow to every format. When the selected control is absent, record the actual subtype and source instead of treating the missing field as a product defect.

4. Check the tracking ad's own collection gates#

For a workflow that uses a CM360 tracking ad, open the actual object selected by the buying configuration. Google's tracking-ad setup guide distinguishes a tracking ad, which records activity on another ad, from a standalone click tracker. It documents required active status, creative assignments, rotation and applicable scheduling.

Inspect:

  • The tracking ad, assigned tracking creative and intended placement.
  • Active status and the relevant rotation settings.
  • Ad and creative dates, including the hard cut-off behavior.
  • The exact selected object in DV360, rather than the most recently exported attachment.
  • The date from which the intended assignment actually applied.

Keep the generated impression and click URLs identified by type. A working click destination does not validate impression collection, and replacing the impression URL with a click tracker changes the event being requested.

If an external event tag is involved, keep its application and serving checks in the ad-server impression investigation. Generic event-tag gates do not replace this YouTube format and account-mapping check.

5. Treat Audio as a current, separately documented branch#

The historical Audio discussion should not become a permanent manual-pixel recipe. Google's current YouTube Audio line-item instructions document an optional CM360 tracking-ad selection field. Inspect the current supported configuration and confirm the requested metrics; do not promise that every metric in a video-format table applies to Audio.

There is also a dated market boundary. Google's YouTube Audio change notice, checked on 4 November 2026, documents two phases for US targeting: new US campaigns and additions of US targeting blocked from 1 September; existing US-targeted campaigns continuing through 4 November; standard auction-based US Audio serving ceasing from 5 November. It says other-country targeting continues, including the non-US portion of mixed-country campaigns.

That is a documented schedule, not confirmation of an individual account's serving state or the cause of a report discrepancy. Separate a market where delivery is unavailable from a market where delivery occurs but the reporting assignment is wrong. Preserve the actual country and date scope before escalating a missing-impression case.

6. Simplify the report before declaring collection failed#

Start with a placement-based CM360 report for the verified mapping and interval. Add fields in small steps, retaining the base export so the team can identify which selection changed the result.

The enhanced tracking reference identifies a specific trap: adding DV360 dimensions to CM360 reports leaves click fields blank for YouTube & partners line items; CM360 placement dimensions are available. A blank in that configuration should not be silently converted to zero measured clicks.

Cost requires separate checks. That reference calls for the partner's DV360-cost reporting option and the CM360 user's View cost permission. Google's role-permission reference explains that report access depends on the user's role. An impression total being visible does not establish access to cost.

Record the exact cost field and currency rather than comparing any two columns labeled spend. The DV360 cost-field audit explains the separate commercial meanings of Media Cost, Total Media Cost, Billable Cost and configured Revenue.

Finally, preserve report maturity. Google's freshness documentation describes impression/click updates every three to four hours and later adjustments. Re-export the same completed interval with the same filters; changing the dates and dimensions while waiting makes the comparison harder to reproduce.

A hypothetical reconciliation with three populations#

Suppose a buying report contains 200,000 impressions for one completed interval. The team splits it using actual campaign mappings. These are invented figures, not measurements from either forum question.

Audit populationBought impressionsClient CM360 resultInterpretation
Verified format, account and tracking assignment100,00080,000Comparable population requiring further reconciliation
Client-account relationship not established60,000UnresolvedReporting destination or coverage remains unverified
Audio format/market/metric contract not confirmed40,000UnresolvedFollow the Audio-specific branch

Comparing 200,000 directly with 80,000 produces an apparent 60% difference: (200,000 − 80,000) ÷ 200,000. It combines an inspectable count gap with unresolved reporting scope.

Within the verified 100,000-impression population, the observed difference is 20,000, or 20% of that bought population. The 100,000 impressions mapped to a verified comparison represent 50% of the total buying-report impressions. These percentages answer different questions.

Do not label the remaining 100,000 impressions lost, invalid or unbilled. Do not inflate the 80,000 CM360 count to estimate what the unresolved rows would have shown. Finish the mapping and metric-support checks before expanding the comparison.

For the 20,000 difference, retain the same event definition, format, inventory, timezone, filtering and extraction time. Then investigate supported runtime and reporting evidence. A configuration repair affects a defined period going forward; it does not reconstruct missing historical events or establish a refund.

Keep external verification and the client report distinct#

Google's YouTube third-party measurement guide documents verified-vendor activation and says ordinary third-party tracking pixels are not accepted for YouTube measurement. That vendor route is different from establishing the client's CM360 tracking-ad or synced-creative reporting.

Use the viewability discrepancy guide for vendor enablement, inventory separation and measurable/viewable populations. Enabling a verification vendor does not prove that a particular CM360 client report has the expected object mapping, nor does a CM360 impression establish measured viewability.

The anonymized dairy video case illustrates why format-specific impression-quality scopes belong in their own reconciliation. It does not establish a CM360 or YouTube integration, a completion rate, a viewability benchmark or a customer outcome from this workflow.

For supported campaign evidence, discuss a scoped AdProof review using explicit campaign dates, timezone and metrics. Bring the platform mapping and comparable exports alongside the supported campaign-event or aggregate evidence. Confirm integration and observable-event coverage before requesting a cross-source conclusion; an AdProof export does not create the advertiser link or unlock a private YouTube measurement feed.

Frequently asked questions#

Can I link the client's CM360 account to an existing unlinked DV360 advertiser?

The documented linking workflow applies while creating the DV360 advertiser, not afterward, and the resulting connection cannot be unlinked. Inspect the existing architecture and ask the responsible account owner for the supported plan before changing live campaign structures.

Why can impressions appear while YouTube clicks or cost are blank?

Check report dimensions, the requested metric and access first. Google documents blank click fields when DV360 dimensions are added to these CM360 reports. Cost also needs its reporting option and user permission. Blank is not automatically a measured zero.

Does YouTube Audio require the manual pixel workaround from older discussions?

Current Audio instructions document a CM360 tracking-ad field. Use the current supported workflow for the actual market and account, and verify metric availability. The separate US availability schedule must also be considered; the historical reply is not a universal implementation contract.

Will adding a tracking ad repair the historical client report?

A supported configuration can be checked going forward. It does not by itself backfill historical impressions, fix every report dimension or prove a commercial adjustment. Keep the original reports and any platform-confirmed correction as separate evidence.

Your next step

Verify the account link and tracking path

YouTube tracking depends on the advertiser relationship, creative format and selected tracking object. Discuss which workflow applies to your setup.

Discuss video measurement

A short inquiry to scope relevant options; no campaign access is needed.

Back to all field notes