Meridian Ads
Console

Show relevant ads from a script tag, or from the traits you already have.

A static page loads one script. An app sends a little context with each request. Paid fills pay you 60% of impression spend. Viewer ids never appear on an advertiser landing page.

Open console See how to integrate
60%
Of gross paid impression spend
$25
Minimum after a 7-day hold
$0
House ads do not create a payout

You keep the product. We pick the ad.

A static page is one script. An app is one request and a render. Payouts, review, and matching are not your problem to build.

  1. 01

    Name the slots

    A static site loads the browser tag and marks each placement. The tag stores a random first-party viewer id for 400 days. An app can send a user id and traits it already stores instead.

  2. 02

    Render what comes back

    One request can fill every slot on the page. If nothing can fill, that slot stays empty.

  3. 03

    Earn on paid views

    You receive 60% of paid impression spend. House ads from Yelle Software can fill gaps at $0. Transfers are USD through Stripe.

Publishers earn 60% of paid spend

Each paid view shares 60% of gross CPM spend with the publisher whose app served it. Accruals younger than 7 days are held. Cash-out and the monthly sweep both need $25 available and an active Stripe payout account. Yelle Software stays merchant of record.

60%
Of gross paid impression spend
$25
Minimum after a 7-day hold
$0
House ads do not create a payout

See pack math and the payout calculator on the pricing page .

Targeting without a tracking graph

Send the traits you already have. Meridian Ads does not build a cross-site identity graph to make the match.

You keep the relationship with your users

Advertisers buy reach in your product. They do not receive your user ids, and your app does not receive their raw landing URLs.

Your user id stays yours

You identify a person with an id you already use. That id never appears on the advertiser landing page.

Never on the landing URL

The app never sees the advertiser URL

Clicks pass through Meridian Ads, get recorded, then continue to the destination.

Recorded, then redirected

A first-party viewer id

On a static site, the tag stores a random id in a first-party cookie for 400 days, plus the browser language and a coarse device class. The id is not an account and is not added to advertiser links. Server SDKs do not set that cookie. You pass the user id.

No cross-site graph

Missing traits do not match

If a campaign needs a trait you did not send, it does not match. Empty rules match everyone. Missing data does not invent an audience.

Missing trait, no match

When nothing paid can fill

If no paid campaign can show, an approved house ad from Yelle Software can still occupy the placement. House ads do not spend advertiser credits and do not create a payout. If house cannot fill either, the slot stays empty.

Paid first. House second. Empty last.

Fill order

Paid campaigns compete on remaining budget, pacing, priority, and frequency caps. House ads only run when that paid set is empty. This is the order of the decision, not a fill-rate promise.

  1. 1

    A paid campaign that can fill

    Reviewed, in budget, matches the person, under its frequency cap.

    Fill
  2. 2

    A house ad from Yelle Software

    Same review as paid ads. Does not spend advertiser credits. Does not pay you.

    Fallback
  3. 3

    Nothing eligible

    The placement stays empty. Meridian Ads does not invent a creative to force a fill.

    Empty

House ads are first-party

House campaigns belong to Yelle Software / Meridian Ads. They do not compete with paid campaigns, and they do not take from an advertiser balance.

  • Advertiser spend$0.00
  • Your payout$0.00
  • If house cannot fillEmpty slot

Get started

Ready to show ads without standing up an exchange?

Open the console to add an app, or read how the request works before you integrate.

Console · Developers

Open console See how to integrate