Understanding Dynamic Asset Requirements

Developing assets for dynamic creative may seem complicated - but it doesn’t have to be.  Innovid has a full staff of award-winning designers and producers here to help you every step of the way, from as early on in the personalization process as you need. Want your creative team to design everything in-house? Great! Simply provide us with your finalized files for dynamic creative versioning. Don’t have the time or resources? No problem - send us your brand guidelines and assets and we’ll take it from there. Either way, you’ll receive final approval on each and every version rendered.

With Innovid DCO, full creative control is in your hands.


Getting Started

Depending on the type of dynamic execution you are building, or the production route you go down, Innovid will always ask for a mix of the following files:

  • Any applicable brand guideline documents and key visuals.
  • Any applicable animations related to the overall product or campaign
  • Editable Photoshop (PSD), Google Web Designer (GWD) or After Effects (AE) files
  • Brand logos formats as vector files (.AI or .EPS or high resolution .PNG)
  • High quality images as (.JPG or .TIFF)
  • All applicable logos and fonts (windows compatible .OTF or .TTF) 
  • High quality videos (.MOV or .MP4, see additional specs below)

Specs for display assets can be found here.

Specs for video assets can be found here.


Data Feed Requirements

Customer Data Feeds: For all the internal information regarding dynamic values for the campaigns, the formats accepted are XML, CSV, Google Spreadsheets, JSON, API.

External Data Feeds: If the creative strategy requires integrating with an external data feed, Ex: Sports Data Sync, Custom API, etc. we will need to evaluate the development required per the feed type. Chat with your assigned Innovid Technical Project Manager for more information.


Dynamic File Prep Best Practices


All finalized designs should be provided as layered Photoshop (PSD) files. JPGs are fine for showing Innovid previews, but we will need to work from a layered PSD file when we start the build. Adobe Illustrator and InDesign files are not ideal, as additional work is required on our end to export optimized assets.

Each “frame” of your ad, should be grouped and clearly labelled. Clear labeling helps the developer building your ad understand your design and animation. 

Ensure the resolution of your document is 72 pixels/inch. 300 PPI is great for print, but digital content displays at 72 PPI. This helps us take accurate measurements from the PSD for font sizes and spacing, as well as positioning of elements within the ads. 

Ensure the color mode of your document is RGB. Digital content uses RGB, not CMYK. If you provide CMYK designs, we can’t guarantee that the final colors will be on brand.

Where available, all logos should be imported as vectors (smart objects). Using vector logos in your design will result in a much crisper final look across all devices.

All images should be imported into your PSD as Smart Objects. Smart Objects in photoshop can be resized repeatedly without losing their original quality and resolution. This will prevent any blurring and pixelation if we need to adjust any of the images. 



Make sure that the project is well organized. Layers and comps should have easy to understand names and master compositions should be highlighted. Note: External plugins are not supported.

Before sharing, reduce the project to include only the relevant assets. Share only the collected project to avoid missing assets. All relevant fonts should be included in an external folder next to the collected project.



Make sure that the project is well organized. Layers and Groups should have easy to understand names.

Select “Non-Google Ad” option in the environment drop down menu. The Tap-Area component should be on top of the layers and without any event / URL on it.

Use the image scaling options provided in the tool. For dynamic background images use the “Crop image to fill” scaling property. For dynamic product images use the “Resize image to fit” scaling property.

Before sharing, ensure you’re including only the relevant assets. All relevant fonts should be included in an external folder and shared with Innovid.



Dynamic Asset Considerations


LENGTH: Consider your longest and shortest sets of messaging to make sure your layout will accommodate them both. What is your longest word/name? Will it fit on a single line?

TREATMENT: Understand that font rendering web browsers will not be identical to your files. How will text be treated when it needs to scaled up/down? Should it resize dynamically? What are the font size limits?

ALIGNMENT: Is the text going to appear over an image or on a solid background color? Is it legible? How should it be aligned?

FONTS: What fonts are in your brand guidelines? Try to limit to 1-2 fonts where possible as embedding fonts in display creative is counted against file size.



NUMBER OF ASSETS: Consider the number of product shots or images you need to showcase and if animation or transitions are required.

FILE SIZE: Consider how the images will render differently across devices. Source images will be compressed for display creatives. Do the images need to be modified in any way to work across multiple devices? Can other elements be overlaid? How will compression affect the creative?

FILE TYPE: Consider what image file types will be needed for the various elements.



LENGTH: Consider the length of the video when deciding where to add dynamic messaging. Video length can also be extended using dynamic start, mid, or end cards. Do you have access to video content less than the allocated time slot? Then we can extend the time of the end frame to get more exposure to the user. If an end frame isn’t the right fit, consider adding the content in the middle of the video.

ELEMENTS: Remember that base videos can be recreated to support dynamic elements. Existing content on end frames such as offer messaging, logos, animations, etc can be recreated to include dynamic content.

AUDIO: When deploying an end card, decide whether to end audio early or provide custom dynamic audio for each version.

Was this article helpful?
0 out of 0 found this helpful