Announcement

Rich Text Style Guide

July 2026
·
3 min read
Dynamic Unit
Mobile
Native
Rich text content style guide

Heading 1

Heading 2

Heading 3

Heading 4

Heading 5
Heading 6

Sed posuere consectetur est at lobortis. Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Nullam quis risus eget urna mollis ornare vel eu leo. Donec ullamcorper nulla non metus auctor fringilla. Aenean eu leo quam. Pellentesque ornare sem lacinia quam venenatis vestibulum. Cras justo odio, dapibus ac facilisis in, egestas eget quam.

Vestibulum id ligula porta felis euismod semper. Nulla vitae elit libero, a pharetra augue. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Donec sed odio dui.

Vestibulum id ligula porta felis euismod semper. Praesent commodo cursus magna, vel scelerisque nisl consectetur et. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Maecenas sed diam eget risus varius blandit sit amet non magna. Donec ullamcorper nulla non metus auctor fringilla. Integer posuere erat a ante venenatis dapibus posuere velit aliquet. Donec id elit non mi porta gravida at eget metus.

Donec sed odio dui. Vestibulum id ligula porta felis euismod semper. Nulla vitae elit libero, a pharetra augue. Aenean lacinia bibendum nulla sed consectetur. Sed posuere consectetur est at lobortis. Sed posuere consectetur est at lobortis. Integer posuere erat a ante venenatis dapibus posuere velit aliquet.

Sed posuere consectetur est at lobortis. Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Nullam quis risus eget urna mollis ornare vel eu leo. Donec ullamcorper nulla non metus auctor fringilla. Aenean eu leo quam. Pellentesque ornare sem lacinia quam venenatis vestibulum. Cras justo odio, dapibus ac facilisis in, egestas eget quam.

Sed posuere consectetur est at lobortis. Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Nullam quis risus eget urna mollis ornare vel eu leo. Donec ullamcorper nulla non metus auctor fringilla. Aenean eu leo quam. Pellentesque ornare sem lacinia quam venenatis vestibulum. Cras justo odio, dapibus ac facilisis in, egestas eget quam.

  1. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Donec id elit non mi porta gravida at eget metus. Donec sed odio dui.
  2. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Donec id elit non mi porta gravida at eget metus. Donec sed odio dui.
  3. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Donec id elit non mi porta gravida at eget metus. Donec sed odio dui.
  4. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Donec id elit non mi porta gravida at eget metus. Donec sed odio dusds

  • Donec ullamcorper nulla non metus auctor fringilla.
  • Morbi leo risus, porta ac consectetur ac, vestibulum at eros.
  • Etiam porta sem malesuada magna mollis euismod.
  • Nullam quis risus eget urna mollis ornare vel eu leo.

Cras justo odio, dapibus ac facilisis in, egestas eget quam. Vestibulum id ligula porta felis euismod semper. Donec id elit non mi porta gravida at eget metus. Sed posuere consectetur est at lobortis. Vivamus sagittis lacus vel augue laoreet rutrum faucibus dolor auctor. Vivamus sagittis lacus vel augue laoreet rutrum faucibus dolor auctor.

Curabitur blandit tempus porttitor. Fusce dapibus, tellus ac cursus commodo, tortor mauris condimentum nibh, ut fermentum massa justo sit amet risus. Donec sed odio dui. Curabitur blandit tempus porttitor.

Curabitur blandit tempus porttitor. Fusce dapibus, tellus ac cursus commodo, tortor mauris condimentum nibh, ut fermentum massa justo sit amet risus. Donec sed odio dui. Curabitur blandit tempus porttitor.

Code Snippets

nimbus-init.ts
  1. import { Nimbus } from "@nimbus/sdk";
  2. // Initialize the SDK once at app startup
  3. const nimbus = Nimbus.init({
  4. apiKey: "pub_live_51H8x",
  5. timeout: 800,
  6. });
  7. // Request an ad for a placement
  8. const ad = await nimbus.request({
  9. format: "banner",
  10. slot: "home_feed",
  11. });

Layered integrations quietly tax every ad request. Collapsing them into one auction is where the eCPM lift actually comes from.

“Migrating to Nimbus full-stack mediation unified our auction and lifted eCPM — without adding operational overhead.”

Carolina Wagner Monetization Lead

+43% eCPM lift after migrating to Nimbus full-stack mediation.

List & Steps

What the migration unlocked

  • Single unified auction
  • 60+ demand sources, one connection
  • No added SDK weight
  • Transparent, advertiser-level reporting

FAQ

Frequently asked questions

Everything you need to know. Can't find an answer? Reach out to your Nimbus Account Manager.

What is full-stack mediation?

A single unified auction where every demand source bids in real time, replacing a sequential waterfall.

How long does migration take?

Most publishers complete migration in a few weeks, with white-glove support from the Nimbus team.

Will it add SDK weight?

No — the Nimbus SDK consolidates integrations, so you remove weight rather than add it.

How many demand sources does Nimbus support?

Over 60 demand partners compete in the core auction — more than any other open-marketplace partner.

Do I keep my existing direct deals?

Yes. Direct and programmatic demand run side by side with no extra setup.

Why the results held

Unified auction dynamics

  • Every demand source bids in one real-time auction
  • The highest bid wins, with no waterfall bias

Expanded demand access without friction

  • More buyers compete on each impression
  • No added integration overhead

Operational clarity

  • One source of truth for pricing and performance
  • Advertiser-level reporting out of the box

Media & Meta

Native Demand Ad Tech Case Study

Tumblr partnered with Nimbus to migrate its in-app monetization onto full-stack mediation, consolidating a fragmented waterfall into a single unified auction.

Metrics & Charts

Floored eCPM by geo

Floored eCPM across key markets.

eCPM trend, last 6 months

Blended eCPM by platform.

Avg eCPM lift

+31%

Fill rate

98%

Demand sources

60+

Ad render rate

99.9%

Floored vs. unfloored eCPM by geo

Impact of applying price floors on eCPM across key markets.

GeoUnfloored eCPMFloored eCPMLift
US$4.10$5.82+42%
UK$3.20$4.05+27%
DE$2.90$3.55+22%
JP$3.80$4.60+21%

Post-migration performance iOS + Android

Metric rCPM
+87%
Metric eCPM
+43%
Metric Revenue
+59%

Demand mix

Share of monetized impressions by source.

Nimbus vs. a legacy stack

Capability comparison at a glance.

Share this article

Found this useful? Pass it to a publisher who could put the same playbook to work.