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

CM360 Creative Upload Fails? Audit the HTML5 Package and Request

Diagnose CM360 creative upload errors by separating file selection, HTML5 package validation, browser requests, saved creative state and click testing.

AP
AdProof Research
Independent measurement desk
A ZIP folder containing HTML, JavaScript and asset cards leads past separate file and upload receipts toward an abstract creative preview and click-check receipt.
Check archive contents, upload responses and creative behavior at separate boundaries. Conceptual illustration without validation or rendering results.
In this guide (11 sections)

When CM360 shows a generic upload error, first identify the creative format and the failed stage. A file that cannot be selected, a rejected HTML5 archive, a failed browser request and an uploaded creative that renders incorrectly need different fixes. Preserve the original asset and request evidence before rebuilding the creative or repeatedly trying the same upload.

For an HTML5 display asset, inspect the archive and its references, then verify the receiving request and saved creative separately. Do not treat a missing dimension tag, an unrecognized click exit or a browser console warning as the cause until the evidence connects it to the failed stage.

What the original question establishes#

An ad-operations question about CM360 upload errors reports a recurring generic error and a suspected network issue. The author does not identify the asset format or prove the cause. A reply suggests checking both the package and browser path. That is a useful diagnostic branch, not proof that the original asset was HTML5 or that CM360 had an outage.

An older HTML5 validation discussion describes the practical difficulty of handing creatives between developers, agencies and traffickers. Its changing deprecation claims and tool recommendations are historical context. This workflow depends on current format requirements and receiving evidence, rather than a promised replacement validator.

Related guide

Check the click path after the creative is accepted.

Compare the exported tag, saved configuration and actual navigation before interpreting the click count.

Audit CM360 click tracking

Opens a practical guide. No email required.

1. Separate the four acceptance states#

Start with one affected file and the exact workflow used. Record whether this is a single display-creative upload, a batch upload, a rich media route or an asset replacement. Instructions for one product or format should not silently become rules for every creative.

StageEvidence to preserveWhat it does not establish
File selectionActual extension, file identity and selection resultThe archive is valid
Upload requestRequest time, response, error details and request reference when availableA saved creative renders correctly
Saved asset and creativeAssigned asset, creative ID, version and propertiesThe final placement uses that version
Rendering and click pathAuthorized preview and placement observationsComplete campaign delivery or attribution

Give the incident a precise description, such as “the selected ZIP produces an application error before a saved asset appears.” “The banner is broken” leaves several owners guessing. Keep asset, browser and account observations in separate fields until a reproducible relationship is established.

Google's creative-assets overview also distinguishes the uploaded files from the creative they support. It specifies UTF-8 encoding. A file in an upload list and the final saved creative are different objects in the investigation.

2. Preserve an inspectable package inventory#

Keep an unchanged copy of the received asset and a digest or stable internal version reference. Record the compressed byte count, file count and paths. Inspect a copy rather than repeatedly modifying the only file supplied by the designer.

For an HTML5 package, identify the primary document and follow its relative references to scripts, styles, fonts and images. Look for missing files, spelling differences and references that resolve only in the developer's local environment. Record the exact broken reference and the document that contains it before proposing a repair.

This is an original diagnostic sequence, not a claim that a particular parser or upload has been executed. A text search can miss dynamically constructed paths or runtime errors. Conversely, finding a string in source does not prove the browser executes that code on the affected path.

Do not begin by renaming every file to index.html. Establish the actual entry document and references. The reviewed CM360 instructions do not justify treating that filename as a universal solution to a generic error. A successful local file opening is also weaker evidence than the supported platform workflow: paths and hosting conditions can differ.

3. Apply the current CM360 format rules#

Google's HTML5 preparation guide calls for a complete primary HTML document that works in an iframe and includes a click tag. Its package rules include:

  • Include referenced assets and exclude unrelated files.
  • Do not nest archives inside a single creative's archive.
  • Exclude local/session-storage APIs and filenames containing %.
  • Upload a backup image separately from the creative ZIP.
  • Check the supported file types and the 100-file limit.

Keep these checks scoped to the HTML5 display package. A valid image control does not prove the HTML5 package follows them. If source inspection finds a prohibited storage API in a bundled dependency, give the developer the dependency path and execution context. Do not merely hide the filename or delete code without checking the creative's intended behavior.

Resolve the published size discrepancy honestly

The preparation guide lists 10 MB, while the display-asset options page lists 9.5 MB for HTML5 assets. Both were checked for this guide. Do not invent an effective date, assume a rounding explanation or promise acceptance at either boundary.

Record the actual byte count and the documented requirement used by the receiving team. Where practical, keep the asset comfortably below the stricter stated size while confirming the applicable limit. The publisher or campaign can have additional requirements. A smaller archive can reduce one uncertainty; it does not diagnose a request failure unrelated to file size.

4. Distinguish one creative's ZIP from a batch container#

The phrase “no nested ZIPs” needs its workflow context. Google's batch-upload instructions describe one HTML5 ZIP per creative, with those creative ZIPs allowed inside an outer batch archive. That is different from nesting another archive inside a single creative package.

Write down which layer you are inspecting. For a batch, map each inner creative package and any separate assets to the intended creative. Save that mapping with the upload evidence. Removing every inner ZIP from a legitimate batch can damage the handoff rather than repair it.

The same instructions require lowercase file extensions for batch preparation and explain that uploaded items are not saved into CM360 until the workflow is finished. A row appearing in the batch interface is therefore not your completion receipt. Preserve the final saved creative identifiers, assignments and version after the authorized workflow completes.

5. Check dimensions, exits and secure resources separately#

The HTML5 preparation guide describes ad.size as optional, although useful for communicating dimensions. Its absence alone is not a verified cause of every rejected upload. The guide also requires a readable click-tag implementation used as the click destination; an unrelated hardcoded link does not establish that CM360 can manage the exit.

Google's display-creative setup reference explains dimension settings, including manually setting a single-size HTML5 creative and aligning supported sizes for responsive assets. Compare the asset's intended dimensions, saved creative properties and placement requirements. Keep that check separate from whether the archive was accepted.

Its secure-serving guidance makes another distinction: non-secure resource URLs affect SSL compatibility, while the landing-page URL does not determine that status and may use HTTP. A blanket search for every http: occurrence can therefore mix a rendering-resource problem with an exit destination. Classify the URL's role before changing it.

If a browser enforces a resource policy after upload, use the CSP tracking diagnostic to identify the actual blocked resource and policy. A console warning during a failed upload does not automatically explain a later creative-rendering failure, or vice versa.

6. Use controlled comparisons instead of repeated guesses#

When authorized, compare a known acceptable control asset and the affected package under recorded conditions. Use a test arrangement that avoids altering live campaign assignments. Keep the account, upload route and observation interval comparable where possible.

ObservationWhat it supportsNext check
Control image succeeds; HTML5 package failsThe attempts differ by more than account access aloneInspect package-specific validation and the failed request
Both fail with comparable request behaviorA shared upload-path issue is plausibleCompare authentication, browser and network evidence
Same unchanged package differs between authorized browser environmentsEnvironment dependence is plausibleIdentify the differing request or browser condition
Package uploads; preview exit is missingA later creative-behavior issue existsInspect saved properties and click-tag behavior

These are hypotheses to narrow, not automatic verdicts. An image success cannot prove every HTML5 rejection is a developer defect. Two failed files cannot prove a Google outage. Preserve status codes, sanitized errors and request references where exposed; a generic banner alone does not identify the responsible layer.

Use an approved clean browser profile where needed and record its conditions. Do not bypass organizational controls or disable protections globally to make an upload succeed. If a login or permission boundary prevents the test, retain the incomplete state and ask the appropriate account owner for help.

7. Verify the saved creative and the final click path#

Google's preview documentation warns that preview can reflect current creative properties even before the latest edits are saved. It also says landing pages can differ with the preview's starting location and directs readers to check final placement tags. Preserve both the saved state and the tested state.

For HTML5 assets, inspect the relevant HTML5 preview and its click-tag event log. Record which exit was triggered, the expected destination and the version tested. Do not substitute a successful click on a local developer page for the platform-managed exit. Once the question becomes redirect routing or missing counted clicks, continue with the CM360 click-path audit.

An upload acceptance receipt remains useful, but it is not a viewability result. If an accepted creative behaves differently inside its serving frame, the SafeFrame audit owns that later compatibility and measurement task.

A hypothetical handoff with different denominators#

Hypothetical example only: a team receives eight HTML5 packages for a controlled QA handoff. All eight can be selected. Two are rejected during upload, and six become saved creatives. Of those six, one has an exit mismatch in the authorized preview; five pass the stated preview checks.

The upload rejection share is 2 / 8 = 25% of submitted packages. The preview mismatch share is 1 / 6 ≈ 16.67% of saved creatives. Adding those percentages would combine different populations. Neither percentage describes ad-impression loss, invalid traffic or financial waste.

The team has two package/request investigations and one later exit investigation. It does not have proof that three creatives caused a campaign-delivery shortfall. Save the accepted versions and keep the failed packages available for comparison rather than overwriting them with similarly named replacements.

Close the incident with reproducible evidence#

The final packet should contain the original asset identity, format, byte/file inventory, exact upload route, browser conditions, sanitized request evidence, saved creative version and scoped preview results. State the first failed stage, the proposed repair and the remaining checks. Record who owns the package, account and serving configuration.

The current asset-options help page still links to an external validator endpoint that returned HTTP 404 during this research. That observation does not prove a global retirement date. Do not let an unverified standalone-tool recommendation replace the receiving platform's acceptance and preview checks.

For a supported delivery comparison after the creative is trafficked, discuss the evidence scope with AdProof. Bring the saved creative and placement identifiers, effective version, dates and campaign-delivery exports. AdProof's campaign-event and aggregate reporting workflow can support that delivery review; it is not described here as a CM360 creative-upload validator. The anonymized fashion-retail delivery case illustrates the separate delivery-evidence boundary.

Frequently asked questions#

Does the generic error prove CM360 is down?

No. Preserve the failed stage and request evidence, then compare authorized control conditions. Package validation, permissions, browser behavior and the receiving service can produce different failures behind a similar message. A successful or failed control narrows the investigation without identifying every cause.

Is a missing ad.size tag always an upload blocker?

No. The reviewed CM360 preparation guide calls it optional. Confirm the actual saved dimensions and receiving error. Do not turn an optional sizing aid into a universal rejection explanation.

Are ZIP files inside ZIP files always forbidden?

The single-creative package and batch container are different layers. CM360's batch workflow permits an outer archive containing a separate HTML5 ZIP for each creative. Follow the requirements for the layer you are preparing rather than applying a slogan to both.

Does a passing preview prove the saved placement will track clicks?

No. Preview can use unsaved properties, and the final landing page can depend on the ad or placement context. Preserve the saved creative version and test the supported final path separately. Preview evidence covers the tested behavior, not complete campaign measurement.

Your next step

Check the click path after the creative is accepted.

Compare the exported tag, saved configuration and actual navigation before interpreting the click count.

Audit CM360 click tracking

Opens a practical guide. No email required.

Back to all field notes