The below guide provides our specifications for native creative within the Quantcast Platform. A list of common errors associated with these assets can be found here.
Required Assets
| Asset | Requirements |
|---|---|
|
Image |
Minimum width: 200 pixels Aspect ratio: 4 : 3 preferred for optimal resizing File size: less than 2 MB |
| Logo |
Minimum size: 50 x 50 pixels Aspect ratio: 1 : 1 only File size: less than 1 MB |
| Title |
Recommended max: 60 characters including spaces Note: We recommend a title (headline) of 60 characters or as close as possible to take advantage of the ad space. |
| Description |
Recommended max: 140 characters including spaces Note: We recommend description (body) copy of 140 or as close as possible to take advantage of the ad space. |
| Advertiser Name | The advertiser name as you would like it to appear with the ad. 30 characters max including spaces. |
| Landing Page URL | The URL your ad will click out to. |
Optional Assets
| Asset | Requirements |
|---|---|
| 3rd Party Trackers | If using 3rd party ad server tracking, provide click and impression trackers (image pixels and JavaScript trackers are supported). They must be secure. |
Best Practices:
- Keep the focal point of the image toward the center for the optimal appearance after resizing.
- Use lifestyle images to match the appearance of other page content. Images where products are used in context are preferred to images of the product only.
- Avoid text on the image, as it may not be legible after resizing.
- Your image and copy should be relevant to the page your ad clicks out to.
- To make the most of the ad space, aim for your headline and body character lengths to be as close as possible to the recommended max.
Common Errors
In addition to following the creative specifications above, a validation error may surface in the UI that prevents you from saving the creative if there is an issue with a particular creative. Here are the most common errors related to Native creative and how to fix them.
The landing URL must not be empty, and must be valid according to these conditions:
- Each URL must look like a URL, in that it must have the standard RFC 3986 format:
scheme:[//authority]path[?query][#fragment].
- Each URL's scheme must be HTTP or HTTPS.
- The authority/domain, path, query-string, and fragment must be valid.
The landing URL must not contain any special characters. The allowed list of characters are:
- Any letter, upper or lower case
- Any number
- Full stops, underscores, tildes, colons, question marks, hashes, forward slashes, square brackets, @/at symbols, percentage symbols, exclamation marks, dollar signs, and symbols, single quotes, normal brackets, asterisks, plus signs, commas, semicolons, equals signs, curly braces
a-z A-Z 0-9 - . _ ~ : / [ ] @ % ! $ & ' ( ) * + , ; = { }
Each impression tracker URL, if provided, must not be empty, and must be valid according to these conditions:
- Each URL must look like a URL, in that it must have the standard RFC 3986 format:
scheme:[//authority]path[?query][#fragment].
- Each URL's scheme must be http or https.
- The authority/domain, path, query-string, and fragment must be valid.
Impression Tracker URLs must be secure