Meta description: Guide to Viewst → Campaign Manager 360 integration: export CM360-ready HTML5 creatives, QA checklist, and high-volume workflows.

Table of contents

• Viewst Campaign Manager 360 integration: Overview & benefits

• How Campaign Manager 360 fits into the ad stack

• How Viewst works as your upstream HTML5 ad builder

• How to upload HTML5 creative to CM360 (ZIP/ADZ guide)

• Click tags: CM360 requirements and copy-paste examples

• CM360 creative group and tag setup

• Automated quality assurance for HTML5 banners (QA checklist)

• Dynamic creative optimization in CM360

• AI ad platforms, governance, and why upstream control matters

• Automating CM360 uploads via APIs

• DCM Campaign Manager HTML5 creatives (legacy naming)

• FAQ

Viewst Campaign Manager 360 integration: Overview & benefits

Ad builders at scale live upstream from your ad server. Google Campaign Manager 360 (CM360) is where trafficking, tracking, and reporting happen—not where production-heavy HTML5 creatives get built.

Viewst sits in that upstream layer as an AI-powered, HTML5-native production studio. It generates, resizes, animates, and packages banner sets so your team can upload HTML5 creative to CM360 as clean, compliant ZIP/ADZ bundles.

Why this upstream + downstream split matters

• CM360: trafficking, Floodlight, reporting, brand controls, creative rotation.

• Viewst: layout, animation, resizing, versioning, brand governance, QA-ready exports.

According to IAB, U.S. digital ad revenue reached $294.6B in 2025, up 13.9% year-over-year, with display at $81.6B (27.7% of digital) and programmatic at $162.4B (+20.5% YoY) [IAB Internet Advertising Revenue Report 2025, PR Newswire summary, 2026-04-18, https://www.prnewswire.com/news-releases/digital-ad-revenue-climbs-to-nearly-300b-as-iab-celebrates-30-year-anniversary-302743856.html]. That scale is impossible to support with manual production.

Viewst’s role is to eliminate banner-production bottlenecks so CM360 receives:

• Validated HTML5 bundles (ZIP/ADZ) that pass Google’s HTML5 Validator.

• Synchronized variant sets (sizes, markets, messages) governed by one master creative.

• Brand-consistent assets aligned with locked brandbooks.

How Campaign Manager 360 fits into the ad stack

Campaign Manager 360 is a web-based ad management system for advertisers and agencies [Google Campaign Manager 360 overview, accessed 2026-09-23, https://support.google.com/campaignmanager/answer/2709362]. It is best understood as the downstream trafficking and measurement layer.

Core CM360 responsibilities

• Trafficking display, video, and rich media creatives.

• Managing placements, rotations, and frequency.

• Implementing Floodlight tags and attribution.

• Providing reporting and verification.

• Enforcing brand controls and creative approvals.

CM360 supports HTML5 display creatives uploaded as ZIP or ADZ bundles. These bundles must conform to strict rules, which makes upstream QA essential.

Key CM360 HTML5 upload requirements (display creatives)

From Google’s HTML5 creative documentation for Campaign Manager 360 [HTML5 creatives in Campaign Manager 360, accessed 2026-09-23, https://support.google.com/campaignmanager/answer/4558694]:

• Archive format: ZIP or ADZ.

• Primary HTML file:

  • Must be at the root of the archive.

  • Must include at least one click tag variable.

• File-count limit: up to 100 files per HTML5 bundle.

• Total bundle size: up to 9.5 MB for the archive.

• References: the HTML must reference only files in the archive.

• Storage: no use of localStorage or sessionStorage for user data.

CM360 also supports polite-load behavior when total creative size is above certain thresholds [Polite load creatives, Campaign Manager 360, accessed 2026-09-23, https://support.google.com/campaignmanager/answer/4558923]:

• Initial load size threshold: around 150 KB.

• Polite-load image recommendation: under 40 KB.

These rules are specific to Campaign Manager 360’s HTML5 display creatives, and are distinct from:

• Google Ads: which has its own HTML5 ad specs and upload UI.

• Google Studio: the rich media authoring tool, which outputs Studio-compatible creatives for CM360 but with additional APIs and components.

Viewst focuses on generating bundles that comply with CM360’s HTML5 specs by default.

How Viewst works as your upstream HTML5 ad builder

Viewst is an HTML5-native ad production platform built for agencies, in-house teams, and enterprise brands producing high volumes of banner ads. It is not a general-purpose design app: instead, it acts as creative production infrastructure between tools like Figma/Adobe and downstream platforms like CM360.

Core Viewst capabilities for CM360 workflows

• AI Smart Resize: generate all required sizes from one master creative.

• AI Image Deflatening: turn flat assets into editable HTML5 layouts.

• AI Designer: generate structured HTML5 banners from prompts.

• AI Instant Animator: add motion across layers with one click.

• True WYSIWYG editor: what you see in the editor is what CM360 will serve.

• Figma / Adobe import: use your current design stack as the source.

• Brandbooks: locked typography, color systems, and components.

• Production-ready export: HTML5 ZIP/ADZ, GIF, MP4.

Because Viewst treats the master creative as a single source of truth, all sizes and variants remain structurally linked. This matches the “master creative → governed variants” model now common across creative automation platforms.

Benefits of using Viewst before CM360

• Speed: AI automates resizes, variant creation, and animations.

• Consistency: master-driven updates propagate across sets.

• Governance: brandbooks lock down fonts, colors, and layout rules.

• Stability: CM360 receives tested, compliant HTML5 bundles.

• Burnout prevention: senior designers don’t spend days on repetitive resizes.

Adobe’s 2024 survey found 83% of creative pros were already using generative AI; 62% said it reduced task time by about 20%, 66% reported better content, and 58% said they were producing more [Adobe, “Creative Pros and Generative AI,” 2024-02-02, https://blog.adobe.com/en/publish/2024/02/02/creative-pros-generative-ai-usage]. Viewst aligns with this: AI takes production work, humans retain creative judgment.

How to upload HTML5 creative to CM360 (ZIP/ADZ guide)

This section walks through the end-to-end path from Viewst to CM360. We’ll cover:

1. Exporting CM360-ready HTML5 from Viewst.

2. Understanding ZIP vs ADZ.

3. Creating a compliant folder/file structure.

4. Using CM360’s HTML5 Validator.

1. Export CM360-ready HTML5 from Viewst

In Viewst, once a master creative and its variants are ready:

1. Select the creative set or specific sizes you want to export.

2. Choose HTML5 export and select a CM360-compatible profile (if your team standardizes naming/size rules, this can be templated).

3. Ensure the click tag option is enabled so Viewst injects standard CM360 click variables (more on this in the click-tag section).

4. Download the resulting archive.

Each creative (size/variant) will be output as a separate ZIP or ADZ, depending on your export settings.

2. ZIP vs ADZ in CM360

Campaign Manager 360 accepts both ZIP and ADZ archives for HTML5 creatives [HTML5 creatives in Campaign Manager 360, accessed 2026-09-23, https://support.google.com/campaignmanager/answer/4558694].

• ZIP

  • Standard compressed archive.

  • Often used for individual or small sets of creatives.

• ADZ

  • Also a ZIP-format archive but typically used to package multiple related creatives or assets.

  • Historically associated with DoubleClick/Studio packaging.

In most modern workflows, especially when coming from an upstream ad builder like Viewst, standard ZIP files are sufficient. If your organization prefers ADZ:

• You can rename a ZIP to .adz if your tooling and CM360 workflow require it, since ADZ is effectively a ZIP container.

• Make sure your build pipeline or CI doesn’t alter internal paths when renaming.

There are no special naming conventions mandated by CM360 beyond typical file naming hygiene (no special characters that can break URLs, reasonable length, etc.).

3. Example HTML5 bundle structure

A compliant HTML5 ZIP/ADZ for CM360 might look like this:

300x250_promo_q4.zip
├── index.html
├── main.js
├── styles.css
├── images/
│   ├── logo.svg
│   ├── product.png
│   └── bg.jpg
└── polite.jpg

Key points:

• The primary HTML file (often index.html) is at the root.

• All references in index.html, main.js, and styles.css point only to files inside the archive.

• Optional polite-load asset (polite.jpg) is kept small (< 40 KB).

• Total file count ≤ 100 and ZIP size ≤ 9.5 MB.

Viewst structures exported HTML5 bundles to align with these expectations.

4. Using the CM360 HTML5 Validator

Google provides an HTML5 Validator inside Campaign Manager 360 to catch problems before trafficking [HTML5 creatives validator, accessed 2026-09-23, https://support.google.com/campaignmanager/answer/4558694].

To run the Validator:

1. In CM360, go to Creatives.

2. Click New → HTML5 (Display creative).

3. Upload your ZIP/ADZ.

4. CM360 automatically runs the HTML5 Validator on upload.

If there are issues, you’ll see warnings or errors such as:

• Missing or invalid primary HTML file.

• No click tag found.

• References to resources not in the bundle.

• Bundle exceeds file count or size limits.

At this stage, upstream control via Viewst is critical. Instead of manually editing HTML, you fix the master or export settings in Viewst and re-export.

Click tags: CM360 requirements and copy-paste examples

Click tags are mandatory for HTML5 creatives in CM360. They allow CM360 to assign and track destination URLs without hard-coding them into the creative.

CM360 click-tag requirements

According to Google’s HTML5 creative specs [HTML5 creatives in Campaign Manager 360, accessed 2026-09-23, https://support.google.com/campaignmanager/answer/4558694]:

• The primary HTML file must define at least one click tag variable.

• CM360 maps these variables to click-through URLs in the UI.

• For standard display, a global JavaScript variable and a click handler are typically used.

Basic click-tag pattern (copy-paste example)

In index.html (or your primary HTML file), place this inside a <script> block in the <head> or just before </body>:

<script>
  // Define the clickTag variable expected by CM360
  var clickTag = "https://example.com";

  function handleClick() {
    // Open the click-through URL in a new tab
    window.open(clickTag, "_blank");
  }
</script>

Then, in your HTML body, attach it to the clickable area:

<div id="clickArea" onclick="handleClick()">
  <!-- banner content -->
</div>

CM360 will override the clickTag value when you assign a destination URL in the UI. The hard-coded value is simply a fallback.

Multiple click tags example

If you have multiple clickable regions, use numbered variables:

<script>
  var clickTag = "https://example.com/main";
  var clickTag1 = "https://example.com/cta";

  function handleMainClick() {
    window.open(clickTag, "_blank");
  }

  function handleCtaClick() {
    window.open(clickTag1, "_blank");
  }
</script>

Attach them in the HTML:

<div id="mainArea" onclick="handleMainClick()"></div>
<button id="cta" onclick="handleCtaClick()">Shop now</button>

Mapping click tags to URLs in CM360

After uploading your HTML5 creative:

1. Open the creative in CM360.

2. Scroll to the Click-through URL section.

3. You’ll see fields for clickTag, clickTag1, etc.

4. Enter the destination URLs (or use macros for dynamic paths).

5. Save the creative.

Viewst can standardize click-tag naming across all exports so trafficking teams know exactly which fields to populate.

CM360 creative group and tag setup

Once your HTML5 creatives are validated, you need to structure them properly inside CM360.

Creative groups in CM360

Creative groups allow you to group multiple creatives for rotation, testing, or targeting [Creative basics, Campaign Manager 360, accessed 2026-09-23, https://support.google.com/campaignmanager/answer/2694149].

Common patterns:

• Size-based groups: one group per IAB size (e.g., 300×250, 728×90).

• Message-based groups: prospecting, remarketing, offer A/B.

• Market-based groups: US, UK, LATAM variants.

Using Viewst as the upstream builder:

• Produce the full matrix of sizes × messages × markets.

• Export each as CM360-ready HTML5 creatives.

• Group them in CM360 by your primary operational dimension (often size + market).

Tagging and placements

Once creatives and creative groups are defined:

1. Assign creatives to placements that map to your inventory (sites, apps, exchanges).

2. Configure rotation (even, weighted, sequenced) using CM360’s settings.

3. Attach Floodlight activities as needed for measurement.

Viewst doesn’t replace tagging or placements; it ensures every creative you attach is structurally sound and brand-safe.

Automated quality assurance for HTML5 banners (QA checklist)

Manual QA doesn’t scale when you’re shipping thousands of HTML5 variants. Viewst plus CM360’s HTML5 Validator provides a repeatable QA framework.

CM360 HTML5 QA checklist

Use this checklist before or during upload:

1. Bundle structure

   • Primary HTML file (e.g., index.html) at the root.

   • No nested HTML entry points.

   • All referenced assets exist in the archive.

2. Bundle limits

   • File count ≤ 100.

   • ZIP/ADZ size ≤ 9.5 MB.

3. Click tags

   • At least one clickTag variable defined.

   • Click area covers the intended interaction.

   • No hard-coded destination URLs required in code.

4. Polite load

   • Initial load assets around or below 150 KB when possible.

   • Polite-load image under 40 KB if used.

5. JavaScript health

   • No localStorage or sessionStorage used for user data.

   • No external network calls to unauthorized domains.

   • Console free of errors in major browsers.

6. Performance and animation

   • Animation duration and loops are reasonable (no infinite hyperactive loops that violate publisher policies).

   • CPU usage is tested on mid-range machines and mobile.

7. Accessibility and UX basics

   • Essential text remains legible at all sizes.

   • Focus order is sensible if there are interactive elements.

Viewst can be configured to enforce many of these rules at export. CM360’s HTML5 Validator catches the rest at upload time.

Dynamic creative optimization in CM360

Dynamic Creative Optimization (DCO) in CM360 allows you to serve different creative content based on user, context, or data feeds.

While CM360 supports dynamic creatives (often via Google Studio or custom setups), Viewst’s role is to provide ready-to-serve HTML5 templates and variant sets that slot into your DCO strategy.

Typical DCO scenarios

• Different messaging per audience segment.

• Customized pricing or product imagery per feed.

• Market/language rotations with shared layout.

In these cases:

• Viewst maintains the layout and animation system across variants.

• CM360 (with or without Studio) handles which variant shows to whom.

This division ensures dynamic optimization doesn’t turn into uncontrolled creative chaos.

AI ad platforms, governance, and why upstream control matters

Generative AI is now mainstream across planning and creative. IAB’s 2025 outlook found 80% of buyers using or exploring generative AI in media planning and activation; 42% were already using it and 36% were exploring [IAB, “Digital Advertising Growth: Retail Media, CTV, Social,” 2025-03-26, https://www.iab.com/news/report-digital-advertising-growth-retail-media-ctv-social/].

At the same time:

• More than 70% of marketers reported at least one AI-related incident.

• Fewer than 35% planned to increase governance/brand-integrity investment [IAB, “AI Adoption is Surging in Advertising—but is the Industry Prepared for Responsible AI?”, 2025-08-15, https://www.iab.com/insights/ai-adoption-is-surging-in-advertising-but-is-the-industry-prepared-for-responsible-ai/].

IAB’s 2025 AI Governance & Risk Management Playbook notes that 70% of agencies, brands, and publishers had not yet integrated AI across planning, activation, and analysis as of 2025, though it expects at least half to do so by 2026 [IAB, “AI Governance and Risk Management Playbook,” 2025-08-01, https://www.iab.com/wp-content/uploads/2025/08/IAB_AI_Governance_and_Risk_Management_Playbook_August_2025.pdf].

Adobe’s 2026 Creator’s Toolkit report similarly found 87% of creators say creative AI grew their business or audience, 75% say it’s integrated or essential, 85% believe final creative decisions should remain theirs, and they use AI on more than 40% of projects [Adobe, “Creators’ Toolkit Report 2026,” 2026-06-10, https://news.adobe.com/news/2026/06/creators-toolkit-report-2026]. A separate 2026 Adobe study found creatives save 17 hours per week with AI and 94% say they can produce content faster [Adobe, “Creatives say AI is helping them meet growing demand for content,” 2026-04-17, https://blog.adobe.com/en/publish/2026/04/17/creatives-say-ai-helping-them-meet-growing-demand-content-improving-their-work].

The takeaway: AI is no longer experimental, but governance lags.

Viewst’s viewpoint aligns with Adobe and IAB:

• AI should remove mechanical work—not human judgment.

• Brandbooks and approval flows must constrain AI output.

• CM360 should only see assets that have passed governed production.

Automating CM360 uploads via APIs

For very high-volume teams, even CM360’s UI becomes a bottleneck. Google’s APIs can help you connect upstream tools like Viewst directly into CM360 workflows.

Relevant Google APIs

• Campaign Manager 360 API

  • REST API for managing campaigns, placements, creatives, and reports.

  • Docs: https://developers.google.com/dcm

• Google Ad Manager API / Google Marketing Platform APIs

  • For coordinating with ad serving beyond CM360.

While the CM360 API does not directly accept a ZIP upload in the same way as the UI, it allows you to:

• Create and manage creative records.

• Associate creatives with placements and campaigns.

• Programmatically update fields like click-through URLs.

A common pattern is:

1. Automate HTML5 export from Viewst into a cloud bucket.

2. Use internal tooling or CI to:

   • Upload the ZIP to CM360 via UI scripting or headless browser flows.

   • Or leverage Google’s broader Marketing Platform APIs where available.

3. Use the CM360 API to attach creatives to placements and campaigns at scale.

Viewst is designed to plug into such CI/CD-style pipelines as the production engine that outputs CM360-compliant bundles.

DCM Campaign Manager HTML5 creatives (legacy naming)

Many teams still refer to CM360 as DCM (DoubleClick Campaign Manager). Google rebranded DCM as Campaign Manager and then Campaign Manager 360, but the functional model—HTML5 bundles uploaded into a trafficking system—remains consistent.

When you see references to:

• DCM HTML5 creatives

• DCM Campaign Manager HTML5 creatives

They map directly to the same HTML5 ZIP/ADZ bundles described in this guide. Viewst’s exports are compatible across that naming shift; what matters is adherence to current CM360 HTML5 specs.

FAQ

1. What is the best way to connect an AI ad builder like Viewst with Campaign Manager 360?

Use Viewst as your upstream production infrastructure and CM360 as your downstream trafficking layer. Build and govern all HTML5 variants in Viewst, export CM360-ready ZIP/ADZ bundles, validate them with CM360’s HTML5 Validator, then attach them to placements and campaigns in CM360.

2. How do I upload HTML5 creative to CM360 without errors?

Follow Google’s HTML5 specs: ensure one primary HTML file at the root, define at least one clickTag variable, keep file count ≤ 100 and ZIP size ≤ 9.5 MB, and avoid external references. Export from Viewst with CM360-compatible settings, then upload via CM360’s HTML5 creative workflow—the built-in Validator will highlight any remaining issues.

3. Can Viewst support dynamic creative optimization in CM360?

Yes.

Viewst creates the master layouts and governed variants that CM360 (often with Google Studio or feed-based setups) can use for Dynamic Creative Optimization.

Viewst focuses on consistent production; CM360 focuses on which variant is delivered to each user.

4. Are there differences between ZIP and ADZ for CM360 HTML5 creatives?

Functionally, both are compressed archives CM360 can ingest.

Most teams use standard ZIP files; ADZ is essentially a ZIP with a different extension historically used in DoubleClick/Studio workflows.

What matters are the internal structure and compliance with CM360’s HTML5 rules.

5. How does Viewst help with AI governance and brand safety?

Viewst anchors all AI-driven production in master creatives and brandbooks. AI handles resizes, animation, and derivative variants; brand rules, locked styles, and approval workflows ensure only compliant assets get exported to CM360, reducing the AI-related incidents and brand risks that IAB and Adobe highlight.