Siden du har forespurt, er ikke tilgjengelig på språket ditt ennå. Du kan velge et annet språk nederst på siden. Eventuelt kan du bruke den innebygde oversettingsfunksjonen i Google Chrome til å oversette en hvilken som helst nettside til det språket du foretrekker.

Overview of native ads

Native ads match the look and feel of your site or app and provide a better user experience for your visitors. Native ads are different from standard ads in that they're designed to fit neatly inside the user's path through your site or app.

Native ads are element-based ads that are styled by the publisher instead of the advertiser. They're used for a broad range of use cases, from highly custom sponsored posts to scaled native backfill. In all cases, Google receives structured elements from the advertiser and inserts them into styles that the publisher defines.

Native ad elements

Ad attribution

The ad badge that clearly marks the ad as advertising. You render ad attribution in your own app code. You must clearly display the text "Ad", "Advertisement", or "Sponsored" (localized appropriately). The badge is required to be a minimum of 15px height and width. 

AdChoices

An AdChoices overlay is added automatically by the SDK in the corner you specify. It's important that the AdChoices overlay be easily seen, so choose background colors and images appropriately.

Icon

The small app icon or advertiser logo with square aspect ratio (1:1).

Call to action

Button or text field that encourages users to take action (for example, "Visit site" or "Install").

Media content

The large, primary image or video.

Title

The primary headline text.

Star rating

For app install ads, the rating from 0-5 that represents the average rating of the app in a store.

From advertiser-provided elements to publisher to user

  1. The advertiser provides the elements for a native creative (like the headline, image, destination URL, logo, and so forth) instead of a tag.
  2. The publisher uses Google Ad Manager to create a native style that matches their site or app. Ad Manager takes the elements and generates an ad with an appearance that is appropriate for the context of each impression. If some elements are missing, Ad Manager may generate them as needed.
  3. The user sees an ad that fits seamlessly into the surrounding content.

Example of native ad components

Compare to traditional banner ad elements

An example of banner ad components

As the above example shows, with traditional banner ads:

  1. The advertiser provides a completed ad (an image or tag) with a fixed size.
  2. Google Ad Manager hosts the ad, doesn’t change it, and serves it into the stated size.
  3. The user sees the ad exactly as the advertiser prepared it.

One creative, many layouts

Google Ad Manager can take the native ad elements that the advertiser provides and insert them into many different layouts, depending on the type of device where the ad will appear, how the content on the page appears, the amount of space available, and more.

Example of native ad components served to different layouts

For example:

  1. An advertiser provides the values for the variables (such as "Modern minimalist home goods" for the headline, additional text for the body, and a value for the clickthrough URL). These values are stored in a single native creative in Google Ad Manager.
  2. Google Ad Manager then applies different layouts for different inventory segments – one for mobile app and another for an ad unit on desktop web.

Both styles use the same variables, but they display the variables to users in different ways.

Next steps

Was this helpful?

How can we improve it?
Search
Clear search
Close search
Main menu
1499139633235008444
true
Search Help Center
true
true
true
true
true
148
false
false
false
false