← Case studies Product Data Cortex · First-party data

First-Party Signal

Device, IP, and geo in every bid request. Richer signal, higher RPM.

up to +14%
RPM uplift, peak day
The point

The same impression, described better.

Most bid requests go out nearly blank: a URL, a placement, maybe a cookie. The first-party layer of Data Cortex adds device, IP, and geo to every request, so buyers can value the impression instead of guessing. It is the foundation tier, it ships free with Yield Cortex, and it adds no new ad slots. In a live A/B on the same inventory, requests carrying first-party signal earned more RPM in every measured window, up to +9% depending on the site.

+3%
Average RPM uplift

First-party signal in the bid request vs without, across the test window.

up to +9%
By site

Site-dependent, with peak days reaching +14%.

$0
Added cost

Ships with Yield Cortex as the Data Cortex foundation tier. No new ad slots, no creative changes.

What it is

What it is, in three lines.

01Data Cortex attaches first-party signal, device, IP, and geo, to every bid request.
02The foundation tier of Data Cortex for Publishers. Ships with Yield Cortex, no extra integration, no fee.
03The same inventory, described better to buyers. No new ad slots, no creative changes.
The daily data

Every day of the test, graphed.

Hover any day for the exact CPMs. No cherry-picked windows.

$0.55$0.47$0.38$0.29$0.21 3/13/43/73/103/133/163/193/223/253/283/31
With Data Cortex Control
From the working notes

What the team wrote next to the numbers.

We started passing first party data in the bid request

Data: device, IP, and geo signals

We are running an A/B test and seeing an uplift on RPM of up to 9%, depending on site