Native ads need an asset brief, not just a banner export

A polished banner is delivered for a native placement. The buyer uploads it as the image, adds the same headline again, and discovers that the publisher crops out the offer.

Native creative often consists of separate assets that the receiving environment assembles. That changes both the brief and the review process.

Google’s native-ad overview describes the advertiser supplying components such as an image, headline, URL, and logo. The specific asset requirements depend on the format and destination.

Separate the message into components

Ask for the required headline, body text, image, logo, brand name, call to action, and destination as distinct deliverables.

Confirm character limits and supported image proportions with the receiving platform. Do not assume the number of characters visible in one desktop preview will remain visible everywhere.

Write each text field so it retains meaning if another optional field is absent. An essential qualification placed only in a field that some placements omit can make the combined message misleading.

Test the crop, not just the image dimensions

An image may satisfy the upload dimensions but lose the subject when fitted into another aspect ratio.

Request a focal area that remains useful across the supported crops. Keep critical text out of an image if the placement can crop it unpredictably. Where text is necessary, verify each supported presentation rather than relying on the original design canvas.

The bulk creative asset checker can inventory image dimensions and file sizes. It cannot judge whether the crop preserves the message.

Review combinations as complete ads

A headline, image, and call to action can each be acceptable separately while making an awkward or inaccurate combination.

For example, an image of a premium product alongside a headline advertising the cheapest item may create an expectation the landing page does not satisfy. Review the assembled ad and destination together.

If several headlines or images can rotate, identify the permitted combinations and check that none introduces an unintended claim. Keep the approval record at the combination or rule level appropriate to the platform.

Inspect disclosure and accessibility

Confirm how the publisher identifies the placement as advertising. The disclosure should remain visible in the actual layout rather than appearing only in a mockup.

Ask how text, image alternatives, focus, and interaction are handled by the placement. Some details belong to the publisher template, others to the supplied assets. Assign the issue to the owner who can change it.

A screenshot is useful for visual approval, but it cannot establish keyboard behavior or how assistive technology reads the unit.

Preserve the approved asset mapping

Save the exact asset versions and text fields associated with each creative ID. Record any platform-side edits after upload.

Then use representative previews for the intended devices and inventory. The creative QA guide supplies the broader destination and measurement checks.

Native QA succeeds when the final combinations remain accurate and usable across the supported layouts. A single attractive preview is only one part of that evidence.