Campaign Manager 360 (CM360) Creative Specs, Formats & Upload Guide (2026)
Google Campaign Manager 360 (formerly DoubleClick CM) serves as the primary ad server for enterprise brands, programmatic trading desks, and media agencies worldwide. Trafficking rich media and standard HTML5 display creatives in CM360 demands strict adherence to file naming structures, asset boundaries, and click tracking APIs.
Validate Your CM360 ZIP Banners
Test your creative ZIP files against official Campaign Manager 360 and DV360 limits (9.5 MB compressed, 100 files, clickTag variables, ad.size tags) instantly in AdCheckLab.
1. CM360 Naming Conventions and Identifiers
In large enterprise campaigns involving hundreds of creative variations, accurate naming conventions and ID management ensure seamless delivery tracking and attribution reporting.
| CM360 Field | Definition and Format | Best Practice Standard |
|---|---|---|
| Creative Name | Descriptive name identifying client, campaign, concept, and banner dimensions | Brand_Product_Q1Promo_Awareness_300x250 |
| Creative Format | Display HTML5 banner, expandable rich media, interstitial, or native | Standard HTML5 Display Asset |
| Creative ID | Unique system-assigned numeric identifier generated upon upload | Automated 8 to 10 digit number in CM360 interface |
| Creative Version | Version increment tracked when updating assets without altering placement links | v1 initial, v2 revision |
| Site ID and Name | Identifier for publisher domains where placements are assigned | Assigned during media plan trafficking |
2. 2026 Technical Specifications
CM360 provides significantly higher asset boundaries than Google Ads, but still enforces strict packaging rules:
- Maximum ZIP File Weight: Up to 9.5 MB compressed bundle weight.
- Maximum File Count: Up to 100 files inside the root ZIP archive.
- Initial Polite Load: Recommended 150 KB initial payload before user interaction.
- Animation Duration: Recommended maximum 30 seconds, with loop limits observed.
- SSL Compliance: Every asset, external CDN font, and analytics pixel must call secure HTTPS protocols.
3. clickTag and Enabler exitApi Implementation
CM360 supports standard clickTag declarations as well as Google Studio Enabler exit APIs. For standard HTML5 display units, include this script tag inside your HTML head element:
<script type="text/javascript">
var clickTag = "https://www.example.com";
</script>Attach the click listener to your main interactive canvas container:
<div id="banner-container" onclick="window.open(window.clickTag)"></div>For rich media units utilizing Google Studio, initialize the Enabler library and call Enabler.exit('Background_Exit') instead.
4. Top 4 Upload Rejection Errors
1. "Primary asset index.html is missing"
Cause: The archive was created by zipping an enclosing folder rather than selecting the files directly. CM360 requires index.html directly in the archive root.
Solution: Select index.html and its companion asset folders together, right click, and select Compress.
2. "ClickTag parameter not found"
Cause: Case-sensitivity mismatches or missing window.open references. Ensure the variable name matches clickTag with capital T.
3. "SSL compliance warning"
Cause: An external stylesheet, font, or script calls an unencrypted http URL. Upgrade all asset URLs to https.
4. "Asset count exceeded"
Cause: Including loose sprite frames or uncompressed icon folders exceeding 100 individual files. Combine graphic assets into image sprites.
5. Agency Trafficking QA Flow
Before delivering creative batches to your client media planner:
- Drop all ZIP archives into the AdCheckLab Validator.
- Confirm all banners pass Google Ads and CM360 compliance rules with zero errors.
- Export the Client-Ready QA CSV report for delivery documentation.
- Traffick verified creatives directly into your CM360 advertiser account.