Publisher: finance-easytips.com
MonetizeMore solution: PPS-PPID configuration that sends stronger first-party audience signals, including a PPID key
Method: cohort migration with staged traffic ramp and a PPID key update
Timeline: Aug 5 to Sep 2, 2025
Result: ~50 percent lift in both Session RPM and Page RPM after moving to 100 percent traffic on the PPS-PPID setup
The PPID key is a publisher-provided identifier used to pass first-party audience signals to demand partners in a privacy-safe way. When implemented correctly, PPID and PPS signals improve targeting accuracy, increase bid competitiveness, and compound yield gains from header bidding and price floor strategies. This case study documents a clear and repeatable uplift tied to a PPID key update and a full migration to PPS-PPID at scale.
What we changed
- Cohort migration: from
lightning-autoads-5
to lightning-tc-autoads-pps-ppid-5
- Identity enrichment: enabled PPS and passed a PPID key to demand partners
- Key update: refreshed the PPID key to improve match quality.
PPS-PPID Implementation Timeline
Date in 2025 |
Change |
Traffic allocation |
Observed outcome |
Aug 5 |
Onboarded to PPS-PPID cohort |
0 percent to start, then low test volume |
PPS-PPID outperformed legacy on early indicators |
Aug 12 |
PPID key updated |
Test traffic only |
Noticeably stronger results vs legacy after the key refresh |
Aug 22 |
Scaled to 50 percent of site traffic |
50 percent PPS-PPID, 50 percent legacy |
PPS-PPID continued to beat legacy across key metrics |
Sep 2 |
Scaled to 100 percent of traffic |
100 percent PPS-PPID |
Session RPM and Page RPM up by ~50 percent vs legacy baseline |
Notes:
- Baseline refers to performance on
lightning-autoads-5
prior to Aug 5.
- The lift figure reflects like-for-like comparisons during stable traffic slices after each change.
Results in plain numbers
Because absolute revenue is confidential, we index results to the legacy baseline.
Metric |
Legacy baseline |
PPS-PPID final after Sep 2 |
Uplift |
Session RPM |
100 |
~150 |
~+50 percent |
Page RPM |
100 |
~150 |
~+50 percent |
Supporting effects observed during ramp:
- Higher effective bid competitiveness
- Better audience match quality after the PPID key update
- More consistent RPM during peak hours.
Why the PPS-PPID setup worked

- Stronger first-party audience signals: The PPID key increased the probability that buyers could recognize returning users or high-intent cohorts in a privacy-safe way.
- Better auction eligibility: PPS-PPID made more impressions eligible for higher quality demand paths, raising bid density.
- Cleaner frequency and recency control: Passing a consistent PPID key improved pacing and frequency capping on the buyer side, reducing waste and increasing average price per mille.
- Compounding with existing yield tactics: The identity uplift stacked with header bidding and floor strategies already in place.
Implementation details publishers care about
- Signal format: The PPID key was implemented as a hashed, non-PII, first-party identifier that is stable within the publisher environment.
- Cohort testing: Changes were introduced via cohorts so legacy and PPS-PPID could be compared in parallel.
- Traffic ramp: 0 to low test volume, then 50 percent, then 100 percent after confirming outperformance.
- Key hygiene: A dedicated PPID key refresh on Aug 12 materially improved results, suggesting match quality and stability of the key are critical.
What this means for finance publishers
If you run a finance site with repeat readership, logged-in users, or newsletter traffic, a PPID key plus PPS can materially lift RPM in weeks, not months. The most important success factors are:
- high-quality first-party IDs that do not decay quickly
- correct mapping of the PPID key through your ad stack
- a measured ramp plan that proves lift on a holdout.
Reproducible rollout checklist
- Map first-party IDs to a stable PPID key and validate hashing, scope, and persistence policies.
- Enable PPS-PPID in your MonetizeMore stack and confirm the signal reaches all relevant demand partners.
- Run a cohort test with a clear holdout and shared KPIs.
- Refresh or optimize the PPID key if early performance plateaus.
- Scale traffic to 50 percent, then 100 percent once outperformance is statistically clear.
- Monitor Session RPM and Page RPM, bid density, and win rate as primary signals.
MonetizeMore is a full-stack monetization partner for publishers. Our PPS-PPID deployments combine first-party data best practices with advanced auction optimization so publishers can grow revenue while staying privacy-first.
Want the same result on your site? Get started here!
Join 1,500+ happy publishers who are having their ad revenue maximized
Take a tour of PubGuru and see how we can take your ad revenue to the next level.
Try MonetizeMore today