Ads and revenue

Native ads
in your own style.

Zurla draws native ads in your fonts, colors and layout, on your website and in your app. Every one is labeled, and Zurla tests native against banners slot by slot.

One ad from Tovrin & Co., drawn three ways: in a news site’s serif type, a recipe site’s rounded cards and a forum’s compact rows. Each one says Sponsored and names the advertiser.Illustrative · fictional sites and brands

On your website

Tell Zurla your style.
It draws your native ads to match.

Zurla reads your site’s template and draws each native ad (a headline, an image, the advertiser’s name) in your fonts, colors and layout. Every one is labeled Sponsored, the banners beside it keep the standard sizes buyers bid on, and every slot holds its space.

Zurla · Pellbrook Media

We redesigned our recipe pages. Make the native ads match, and keep them labeled.

Ready. Your native ads now match your new recipe design. Go live?

  • Read your new recipe template: fonts, corners, image shape
  • Redrew the in-article card and the sponsored story
  • Kept the Sponsored label on both

Yes, go.

Live now, side by side with the old style, so I can compare the two.

  • New style on 50% of recipe pages · undo in one click

Native style matchedReport on Friday

Ask Zurla about your ads

Illustrative data

Preview

Illustration: a fictional recipe article on pellbrook.example. A 728×90 banner runs across the top, a native ad labeled “Sponsored · Tovrin & Co.” sits between the paragraphs, one story in the “More to read” row is labeled “Sponsored · Fernwick Travel”, and 300×250 and 300×600 banners fill the right-hand column. In the phone view, a 320×50 banner with a close button runs along the bottom of the screen and a 300×250 sits in the text.

pellbrook.example/food/weeknight-pasta

Ask for a new look and Zurla redraws the native ads in it; the banners keep their standard sizes.

Illustrative · fictional site and brands

  • In-feed native

    Sits between the cards on your home and section pages, drawn in your own card design.

  • In-article native

    One ad between paragraphs, sized to your text column. A good fit for long reads and recipes.

  • Sponsored stories

    Labeled sponsored stories in the row of reads at the end of an article, in your own card style.

In your app

Native ads in your app,
drawn in your own views.

The Zurla SDK delivers each native ad as parts: a headline, an image, an icon, a button and the advertiser’s name. You lay them out in your own views, or use a template you approve. Every one carries an Ad or Sponsored label and a small ⓘ that opens Why this ad and Report this ad.

Ask Zurla

Brindle Blocks: can a native ad sit on the results screen without getting in the way?

Yes. It sits below Next level, drawn in your game’s own card style, and the levels themselves stay ad-free.

  • Held the space below Next level
  • Drew it in your game’s card style, labeled Ad
  • Added the ⓘ: Why this ad and Report this ad

Native card live · undo in one clickResults screen

Ask Zurla about native ads
App
Phone

Illustration: one phone runs three fictional apps, Brindle Blocks (a puzzle game by Sorrelby Games), Fernhop Recipes and Trailmint (a fitness app), each with a native ad drawn in the app’s own style. Each native ad carries an Ad or Sponsored label and a small privacy icon that opens two choices, Why this ad and Report this ad.

Same SDK, three apps. Each native ad is drawn in the app’s own style, set apart from the app’s content and labeled Ad or Sponsored. Ads are chosen from the app and the screen, never from workout or health data.

Illustrative data · fictional apps and brands

How labels work

Native, never hidden.
Every ad says it’s an ad.

A native ad takes your look, never your voice. Three marks tell people what they’re seeing, and Zurla checks every new ad for its label before it runs.

  • Native on websites

    Sponsored, plus the advertiser’s name

    Every native ad on your site says Sponsored and names who paid for it, right above the headline, in your own type. Readers see the brand before they read a word.

  • Banners

    An Ad mark on every banner

    Each banner carries a small Ad mark in its corner, so it never passes for your content, whatever the creative looks like. Zurla checks for it before the banner runs.

  • In apps

    The ⓘ: why this ad, and a way to report it

    Native ads in apps carry an Ad or Sponsored label and a small ⓘ. One tap opens two choices: Why this ad, which says how it was chosen, and Report this ad.

Traffic and ad qualityEvery ad is checked before it runsThe label is one check. Zurla also scans each ad for malware, forced redirects and heavy files before it reaches your readers.

Native or banner

Native or banner?
Tested slot by slot.

Set each slot to native, banner or either. When it’s either, Zurla runs both on a share of traffic, compares them against your goals and keeps the one that does more, inside your rules. Any change can be undone in one click.

Zurla · Pellbrook Media

How did the sidebar test go?

Native won. It beat the 300×600 banner by 18% in your sidebar, with pages just as fast, so I kept it.

  • Ran native and the banner side by side on 20% of sidebar views
  • Compared revenue per 1,000 views, inside your speed budget
  • Kept native in the sidebar · undo in one click

Native kept+18% over the banner

Ask Zurla about your slots

Illustration: the slots on pellbrook.example, each set to native, banner or either. The sidebar slot was set to either; in a test on 20% of its views, native beat the 300×600 banner by 18%, so Zurla kept native. The top slot is set to either, with a test of native against the 728×90 banner on 10% of article views. The home page slots are set to banner, by the publisher’s rule.

Illustrative data · fictional site

For your developers

One tag on your site.
Parts in your app.

On a website, a native slot is one tag where the ad should appear, with its space held. In an app, the SDK hands you each ad as parts for your own views. Zurla writes the code for you; after that, a new native slot or a new look is a sentence to Zurla.

A native ad, as your app receives it

  1. 1Headline
  2. 2Image
  3. 3Icon
  4. 4Button
  5. 5Advertiser’s name

Lay the parts out in your own views, or use a template you approve. The Sponsored label and the ⓘ always come with them.

<!-- Once, in your page's <head>. It loads asynchronously, -->
<!-- so your content doesn't wait for it. -->
<script async src="https://sdk.zurla.com/v1/zurla.js"
        data-zurla-publisher="ZRL-000000"></script>
<!-- Exactly where the native ad should appear. The SDK sizes -->
<!-- it from your approved template; the space is held. -->
<div data-zurla-slot="home-feed-2" data-zurla-format="native"
     style="min-height:320px"></div>
// One call per native placement. The ad arrives as parts
// (headline, image, icon, button, advertiser name) for your
// own views, or for a template you approve.
let nativeAd = ZurlaNative(placement: "feed_native")
// One call per native placement. The ad arrives as parts
// (headline, image, icon, button, advertiser name) for your
// own views, or for a template you approve.
val nativeAd = ZurlaNative("feed_native")

Snippets are illustrative. Your real IDs come with your account.

  • Space heldThe slot keeps its height before the ad arrives, so your text never jumps.
  • Loads asynchronouslyYour page doesn’t wait for the script, and Zurla’s auctions finish in under 100 ms.
Works with PrebidAlready run Prebid? Keep it.Zurla works with your Prebid setup, native slots included, so you can start without changing how you run your ads today.

Questions

Good to know.

What publishers and app developers ask most about native ads on Zurla.

What will native ads look like on my site?

Like the rest of your pages. Zurla reads your template and draws each native ad in your fonts, colors and layout, labeled Sponsored with the advertiser’s name. You approve the style before it goes live, and banners keep their standard sizes in the spaces you choose.

How do readers know it’s an ad?

Three ways. Native ads on websites say Sponsored and name the advertiser, banners carry an Ad mark, and native ads in apps carry an Ad or Sponsored label with a small ⓘ that opens Why this ad and Report this ad. Zurla checks every new ad for its label before it runs.

Who draws the ads? Do we need a designer?

Zurla draws them. Zurla is a frontier model, built for advertising: it reads your template and builds native ads to match, and you approve the look. When you redesign, tell Zurla and it redraws them; no new code is needed.

Can we choose native or banner for each slot?

Yes. Set each slot to native, banner or either. With either, Zurla tests both on a share of traffic and keeps the one that does more for your goals, inside your rules, and you can undo any change in one click.

How do native ads work in an app?

The Zurla SDK delivers each native ad as parts: a headline, an image, an icon, a button and the advertiser’s name. You lay them out in your own views or use a template you approve, and Zurla runs the auction for every placement.

Will native ads slow our pages down?

No. The script loads asynchronously, so your content doesn’t wait for it, every slot holds its space so text never jumps, and Zurla’s auctions finish in under 100 ms.

See native ads drawn in your style.

Show us your site or app, and Zurla drafts native ads in your fonts, colors and layout, each one labeled, for you to approve before anything goes live.

Zurla
Ask Zurla
Book a demoZurla for publishers