Supported file types for creative assets

To help protect user privacy, neither Studio nor Campaign Manager 360 accepts HTML5 assets that use local storage or session storage. If your upload is rejected for this reason, work with your developer to remove the forbidden APIs. Then try uploading the asset again. Specifically, you cannot upload HTML5 assets with the following JavaScript APIs:

• indexedDB
• localStorage
• openDatabase
• sessionStorage

If your advertising goals depend on these APIs, try using Campaign Manager 360 settings instead. For example, some advertisers use these APIs for ad targeting and frequency caps, but this isn't necessary: you can use Campaign Manager 360 to set up many kinds of targeting, and to set frequency caps. Ask your solutions consultant for help implementing workarounds. (Just keep in mind that regardless of how you set up your asset, you should only attempt to capture data that meets the privacy requirements in your contract with Google Marketing Platform.)

What is local storage and session storage? These are two kinds of HTML5 Web Storage. They are ways to store data on a browser. Local storage stores a file on the browser across browsing sessions. It remains on the browser permanently, unless the user clears the browser cache or deletes the file manually. Session storage only stores data on the browser during a particular browsing session. Once you close and restart the browser, all the session-stored data will be cleared.

Why isn't this type of storage allowed? The stored file can potentially include code designed to capture Personally Identifiable Information (PII), track cross-session browser activity, or send other data to third parties that may violate the terms of your Google Marketing Platform contract. This kind of data collection is certainly not the only use of local and session storage, but it's one possible use, because the file can include any type of code.