Style size different from the ad unit
If the style is Fluid, the ad unit must also be Fluid. Google says the sizes must be the same.
Implementation guide
Native ads
An ad assembled from parts (title, image, text) and dressed in your site's look, always with the label that says it is an ad.
Understand it in 1 minute
A native ad arrives in loose pieces, not as a finished picture. The advertiser sends the pieces, such as the title, the image and a short text. Your site decides the clothes: color, font, size and place of each piece. It is like an assembly kit: the box brings the pieces, and you put them together in the way that fits your living room. That is why it looks like part of the page, like one more card in a list of articles.
In Ad Manager there are two ways to dress this ad. The first is native styles, created inside Ad Manager itself, with the guided design editor, which has ready-made templates, or with HTML and CSS, for those who know code. Google says the styles work for both web and apps. The second is the code for Android and iOS apps, where the app developer receives the pieces through the Google Mobile Ads SDK and draws everything in the app's code. For websites, the path is the native style.
Because native looks like content, Google is very firm on one thing: visitors must know it is an ad. The attribution label and the AdChoices icon mark the card as advertising. Nothing can hide, cover or disguise these labels, and the ad must be clearly separated from the content. It is like a promotional poster inside a store: it can be pretty and match the decor, but it has to make clear that it is advertising.
Google created this format so the same ad can show up with different looks in each part of the site, without changing what the advertiser sent. On the web, Google recommends the Fluid size, which takes the width of the column and adjusts the height on its own. It is worth using when you want ads that match the design of your pages, such as between the items of a list of posts, always with the ad label clearly visible.
Step by step
Implemented example
<!-- No <head> -->
<script async
src="https://securepubads.g.doubleclick.net/tag/js/gpt.js"
crossorigin="anonymous"></script>
<script>
window.googletag = window.googletag || { cmd: [] };
googletag.cmd.push(() => {
// Slot nativo com tamanho fluido.
googletag
.defineSlot("/1234567/exemplo", ["fluid"], "nativo-exemplo")
.addService(googletag.pubads());
googletag.enableServices();
});
</script>
<!-- No <body>, dentro de uma coluna com largura -->
<div id="nativo-exemplo"></div>
<script>
googletag.cmd.push(() => {
googletag.display("nativo-exemplo");
});
</script>What Google recommends
Tips
Watch out
If the style is Fluid, the ad unit must also be Fluid. Google says the sizes must be the same.
A custom native format does not receive programmatic ads. For programmatic, only standard formats work.
A fluid ad in a zero-width column, or inside a box with a fixed height smaller than the ad, may display wrongly.
Yes. The attribution label and AdChoices exist so nobody mistakes the ad for content, and they cannot be hidden or disguised.
No. Google describes this path for Android and iOS apps, using the Google Mobile Ads SDK. On websites, the path is the native style.
According to the GPT documentation, today the native ad is the only fluid type that Ad Manager supports.
Library
Everything on this page follows Google's official documentation. Read it straight from the source:
The audit reads the site as a visitor would, without clicking anything, and shows what to fix.