Skip to content
Help Center/For Publishers/Rendering Native Ad Formats
Back to Help Center

Rendering Native Ad Formats

Display the JSON response from /api/v1/serve as a native-feeling placement.

What's in the Response

Each matched ad includes a headline, body text, an image or logo URL, and a click-tracking URL. There's no iframe or third-party script — you render the creative using your own markup and styling.

Native Rendering Principles

  • Match the ad's typography and spacing to your surrounding content so it reads as native, not bolted-on
  • Label sponsored content clearly (e.g. "Sponsored" or "Ad") — this is required and keeps trust with your audience
  • Use the exact click-tracking URL provided — don't construct your own link to the destination

Common Placements

  • In-feed cards between content items
  • Sidebar or end-of-article native units
  • In-app native cards between content cards in mobile apps

Handling No-Fill

When the serve endpoint returns no matched ad, don't render an empty slot — collapse it or show fallback content so your layout doesn't break.