Ad management platforms and AI builders: how Campaign Manager 360 fits your creative workflow

Campaign Manager 360 (CM360) is an ad management and trafficking layer, not a design tool. AI ad builders like Viewst sit upstream, turning ideas and existing assets into finished HTML5 creatives that meet CM360 specs, then handing them off for serving, measurement, and reporting.

If you treat CM360 as your design environment, your workflow will stall. If you pair it with an AI production platform and clear QA rules, you get speed, control, and reliable delivery.

This article breaks down:

• Where CM360 belongs in a modern creative ops stack

• How AI ad builders fit upstream

• The specific CM360 HTML5 ad specs you need to build toward

• A practical production → QA → export workflow that keeps designers in a creative-first environment

Campaign Manager 360 vs AI ad builders: the core distinction

CM360 is an ad management platform, not a creative tool

Google describes Campaign Manager 360 as a web-based ad management system for advertisers and agencies.

Its core responsibilities are:

• Trafficking and serving display, video, and rich media

• Floodlight tagging and conversion tracking

• Brand controls and verification settings

• Reporting and attribution across channels

CM360 manages creatives as entities in the trafficking layer, but:

• It does not provide a full design canvas

• It does not automate layout, animation, or localization

• It assumes creatives arrive as production-ready files

That’s why creative teams still need a dedicated production environment upstream.

AI ad builders are production infrastructure

AI ad builders like Viewst sit before CM360 in the stack. Their job is to:

• Turn prompts or existing assets into structured, editable layouts

• Automate resizing across formats and placements

• Apply consistent, adjustable animation

• Localize and version creative for offers, markets, and languages

• Export campaign-ready HTML5 that passes CM360 and DV360 checks

Adobe’s 2026 survey found that 94% of creatives say AI helps them produce content faster and 81% save at least six hours per week. That productivity gain only translates into live campaigns if the output is packaged correctly for platforms like CM360.

Where CM360 belongs in your creative operations stack

Think in layers: creation, production, management, measurement

A modern creative ops stack works best when you separate concerns:

1. Creation & concept

   • Brand strategy, campaign ideas, visual direction, messaging

   • Tools: Adobe Creative Cloud, Figma, copy docs, concept decks

2. Production & automation (AI ad builder)

   • Translating ideas into reusable master creatives

   • Resizing, animating, adapting, and localizing at scale

   • Tools: Viewst and other creative automation platforms

3. Ad management & trafficking (CM360, DV360, other ad servers)

   • Uploading creatives, assigning placements, setting tags

   • Applying brand controls, frequency caps, and QA policies

   • Monitoring delivery and viewability

4. Measurement & optimization

   • Pulling CM360/DV360 reports, interpreting performance

   • Feeding learnings back into creative variants and testing

CM360 lives clearly in layers 3 and 4. AI ad builders live in layer 2.

Why that separation matters

Keeping CM360 and your AI ad builder in distinct layers:

• Prevents trafficking workflows from being blocked by design tasks

• Lets design teams iterate freely without touching live campaigns

• Ensures ad specs and QA live in one shared production checklist

• Makes it easier to scale production volume without overloading ops

McKinsey’s 2025 AI survey notes that nearly two-thirds of organizations haven’t scaled AI across the enterprise, and that workflow redesign is a key success factor. Clear boundaries between creation, production, and trafficking are part of that redesign.

Campaign Manager 360 HTML5 ad specs: what your builder must deliver

CM360 creative upload requirements in practice

For HTML5 display creatives, CM360 expects a very specific package. At a minimum, your AI ad builder must export ZIPs that meet these requirements:

• ZIP contents

  • Only files referenced by the HTML entry file

  • No nested ZIPs inside the main ZIP

  • Backup images stored outside the ZIP

• HTML entry file

  • One primary HTML file that CM360 can load

  • At least one click tag defined using Google’s approved pattern

  • UTF-8 encoding

• File limits

  • Up to 100 files per HTML5 creative in CM360

  • Total ZIP size up to 9.5 MB (hard upload cap)

• Behavior constraints

  • No local or session storage

  • No unauthorized calls that violate cookie/HTTP limits when served via DV360

If your export misses any of these points, CM360 can reject the creative, or it can pass upload but fail during QA and trafficking.

Downstream constraints from DV360

Many CM360 accounts integrate tightly with Display & Video 360 (DV360). That adds further constraints on "real-world" serving:

• Payload & performance

  • Total downloaded creative payload must be 5 MB or less

  • Up to 25 cookies and 100 HTTP calls per creative

• Animation & audio

  • Animation duration under 30 seconds

  • No autoplay audio

  • No popups or disruptive overlays

These specs should be treated as design constraints during production, not "clean-up items" at trafficking. The more you bake them into your AI builder workflow, the fewer roundtrips between design and ops.

Integrate creative tools with Campaign Manager 360: a practical stack

A typical mid-market/enterprise configuration

For the creative and performance teams Viewst serves, a pragmatic stack often looks like this:

• Creation

  • Adobe Photoshop/Illustrator for core brand assets

  • Figma or similar for layout exploration

• AI production

  • Viewst for AI-assisted layout, Smart Resize, Instant Animator, and HTML5 output

  • Brandbooks and controlled styles to enforce fonts, colors, and layout rules

• Ad management

  • CM360 to upload creatives, assign placements, manage Floodlight tags, and report

  • DV360 for programmatic buying and optimization

• Governance

  • AI content labeling settings in CM360/DV360

  • Review and approval workflows embedded in the production platform

Adobe’s research shows 91% of creatives use more than one AI model per asset, which aligns with this multi-tool reality: you’ll likely combine different AI systems for copy, image generation, layout, and QA.

How to structure an automated ad production workflow around CM360

Step 1: Build a master creative in a creative-first environment

Start with intent, not specs.

• Define the campaign concept, key messages, and visual system

• Approve one master creative direction that represents the core idea

• Build that master layout in your AI ad builder (e.g., Viewst), not in CM360

Focus on:

• Hierarchy (headline, CTA, brand mark, legal)

• Animation principles (entry, emphasis, exit)

• Reusable components (logo lockup, offer badge, CTA button)

Step 2: Use AI to generate formats and variants

Once the master is approved, let automation do the heavy lifting.

With an AI ad builder, you can:

• Use Smart Resize to generate standard display sizes (300x250, 728x90, 160x600, 300x600, 320x50, etc.) from one layout

• Apply Instant Animator to create consistent motion across all sizes

• Localize for markets and languages by swapping text layers while preserving layout

• Adjust offers and CTAs without rebuilding each banner

This "one master creative, many outputs" model is quickly becoming the norm. Adobe reports that 83% of marketers say content demand has at least doubled in the last two years, and 28% expect demand to increase 10x by 2028. Manual, one-by-one banner design won’t keep up.

Step 3: Apply brand systems and governance during production

To avoid chaos downstream:

• Use brandbooks and styles inside your AI builder to lock fonts, colors, spacing, logo usage

• Restrict who can change critical brand elements versus tactical fields like offer text

• Attach brand and legal guidelines to templates so new variants inherit the right rules

This is where "creative control" and "scale" meet. AI speeds up execution, but brand systems keep the output consistent enough to pass stakeholder review and CM360 brand controls.

Step 4: Run a structured QA checklist before export

Before anyone uploads to CM360, run a repeatable QA pass inside the production platform.

Include checks for:

• Technical specs

  • HTML5 entry file exists and loads correctly

  • Click tags are implemented per Google’s guidelines

  • Animation duration under 30 seconds

  • No autoplay audio or popups

• File constraints

  • Total ZIP size under 9.5 MB

  • Downloaded payload under 5 MB when served

  • Number of files in the package under 100

• Behavior & policies

  • No local/session storage

  • HTTP call and cookie usage within DV360 limits

  • AI content labeling rules respected, with human review where needed

• Visual consistency

  • Brand elements in the correct position

  • Legible typography at all sizes

  • CTA visible and readable

When these checks live in the production platform rather than CM360, your trafficking team receives creatives they can trust.

Step 5: Export HTML5 ads for ad servers like CM360

Once QA is complete, export.

A production-ready export flow should:

• Generate a clean ZIP per creative, with only referenced files

• Keep backup images separate for CM360’s upload rules

• Ensure UTF-8 encoding and valid click tag syntax

• Use naming conventions that align with CM360 placement and campaign structure

In Viewst’s case, the HTML5 output is native and editable:

• Every element remains a layer in the HTML5 structure

• Designers can revisit the creative later, adjust animation or layout, and re-export without starting from scratch

That matters when you receive performance data from CM360/DV360 and need quick creative changes for testing.

Step 6: Upload HTML5 ads to CM360 and connect downstream

With the ZIPs ready, the trafficking team can:

• Upload HTML5 creatives to CM360, validating size and behavior on preview

• Assign them to placements and campaigns, with Floodlight tags and brand controls configured

• Enable AI content labels in CM360 where required by policy or regulation

• Sync creatives into DV360 for programmatic buying and optimization

From here, CM360 and DV360 handle delivery, measurement, and reporting. When performance trends emerge, the loop closes by feeding insights back to the production environment.

Ethical AI tools for display ad design and governance

AI governance is now part of ad ops

Google’s recent updates added AI content labels across Google Ads, DV360, CM360, Merchant Center, and Ads Editor. The documentation clearly states that these labels do not guarantee legal compliance.

That puts responsibility on your workflow to:

• Track which creatives used AI-assisted content

• Include human review in every AI workflow

• Align labeling in CM360 with internal policies and regulatory needs

Keeping people in control of AI outputs

The most resilient workflows combine:

• AI for repetitive production work (resizing, layout, animation)

• Human judgment for concept, brand intent, and final approvals

Creative control is especially critical for regulated industries like financial services, consulting, SaaS, and fintech, where Viewst’s customers operate.

An AI ad builder should:

• Keep every creative editable after generation

• Support approvals, comments, and version tracking

• Make it impossible to accidentally ship unreviewed AI content into CM360

How Viewst HTML5 export fits CM360 specs reliably

For teams using Viewst as their AI ad builder, the CM360-friendly workflow looks like this:

• Design in Viewst, not CM360

  • Build and iterate master creatives on Viewst’s canvas

  • Use AI Designer, Smart Resize, and Instant Animator to scale variants

• Enforce brand and production rules in Viewst

  • Brandbooks and styles keep creative within guidelines

  • Permissions control who can edit what

• Run QA with CM360/DV360 specs in mind

  • Check file counts, payload size, animation length, click tags, and policy constraints before export

• Export native HTML5 with editable layers

  • Viewst packages creatives into CM360-ready ZIPs

  • Trafficking teams upload directly to CM360 without re-building assets

Designers stay in a creative-first environment. Ad ops teams stay in CM360. The integration point is clean, production-ready HTML5.

To see this workflow in action, teams often start by connecting Viewst to their existing CM360/DV360 stack at viewst.com.

FAQ: Campaign Manager 360, HTML5 specs, and AI ad builders

1. Is Campaign Manager 360 an ad design tool?

No. CM360 is an ad management and trafficking platform.

You can upload and preview creatives there, but it does not offer a full canvas for designing, animating, or localizing ads. Design and production should happen upstream in dedicated creative tools or AI ad builders.

2. What are the key CM360 HTML5 creative upload requirements?

For HTML5 display creatives, CM360 requires:

• A ZIP with only referenced files and no nested ZIPs

• A single HTML entry file encoded in UTF-8

• At least one properly implemented click tag

• Total package size under 9.5 MB and fewer than 100 files

Backup images should be stored outside the ZIP, and creatives must avoid local/session storage.

3. How do I ensure my HTML5 ads meet CM360 and DV360 specs?

Build a QA checklist in your production environment that covers:

• File limits (size, file count, payload)

• Behavior rules (no autoplay audio, popups, or local storage)

• Animation duration under 30 seconds

• Correct click tag implementation

• Compliance with cookie and HTTP call limits

Run this QA before export, then upload to CM360.

4. Where does an AI ad builder like Viewst fit alongside CM360?

Viewst sits upstream of CM360.

Teams use it to turn creative ideas into master layouts, automate resizing and animation, localize variants, and export HTML5 ZIPs that conform to CM360 specs. CM360 then handles trafficking, serving, and reporting.

5. Can I keep full creative control if I use AI in my ad production?

Yes—if you choose tools that keep outputs editable and embed human review.

In a well-structured workflow, AI handles repetitive production work while designers retain control over layout, animation, messaging, and approvals. CM360 receives only reviewed, production-ready creatives.