Campaign trafficking with CM360 and AdSync

Understand the objects before mapping

The advertiser provides the account context. A campaign groups the activity, placements describe delivery destinations, and creatives contain the advertising content. Ads connect those creatives to placements and serving settings.

Use platform identifiers alongside readable names. Two objects can have similar names; mapping by name alone can select the wrong record. Confirm the intended advertiser and campaign before applying updates.

Review the proposed campaign changes

• Import the trafficking instructions and inspect unresolved rows.
• Check proposed creative assignments against the campaign brief.
• Review QA findings and the scope of changes.
• Approve publication deliberately, then inspect the resulting CM360 records.

Confirm access and supported operations

AdSync uses the platform’s authorization flow and begins with validation before live changes. A connected Google account still needs the appropriate CM360 account access for the requested operation.

During early access, ask the team to demonstrate your creative formats, object types and account configuration. CM360 is the deepest AdSync integration, but this page does not promise support for every object or every API operation.

Keep platform workflows distinct

CM360’s object model should not be copied directly into Google Ads or Meta campaigns. Start with the common campaign instructions, then review the settings and limitations specific to each platform.