PROVIDER - Publisher revenue optimization
AdPushup
AdPushup is a publisher revenue optimization platform founded in 2014 and based in the United States, adding Google AdX and multiple SSPs through header bidding on top of AdSense, with automatic placement optimization, layout A/B tests, and lazy loading under an incremental revenue share.
3.8pts
Detailed Notes
Pros 5 items
Cons 4 items
Service Overview
AdPushup is a publisher revenue optimization platform founded in 2014 and headquartered in the United States, aimed at sites that already have steady content traffic but earn too little from AdSense alone. The approach is not to replace the existing network but to add a header bidding layer: Google AdX and multiple SSPs bid on the same placement at once, so the same traffic clears at a higher price.
Within the Ad Monetization category it plays the revenue-optimization role. The site keeps AdSense as floor demand while AdPushup raises competition, and running both in parallel means page RPM differences show up directly in reporting instead of forcing an either-or choice.
Integration touches the ad script and placement rendering logic, and the vendor offers both a WordPress plugin and a generic JavaScript path. The real work sits in placement naming and template changes: sites with messy naming will struggle to break reporting down by placement later, so fix the naming rules and per-template unit counts during onboarding.
Key Strengths
- Stacked demand, not replacement: AdSense, Google AdX, and multiple SSPs compete on one placement through header bidding, so 2 or more bid rounds run without discarding existing demand
- Data-driven placement advice: the console proposes additional or relocated units from the last 30 days of RPM and page structure, so layout changes can be previewed before shipping
- Layout A/B testing: pages split into control and variant groups and are compared over a 30-day window, avoiding a single all-site change
- Lazy loading: below-the-fold units request after first paint through 1 async entry point, keeping the impact on LCP and CLS within a smaller range
- Breakdown reporting: revenue splits across 4 dimensions (page, country, device, placement), which points straight at the unit or region dragging average price down
Product Ecosystem
Platform capabilities
The core is the header bidding wrapper: the platform hosts the Prebid configuration, timeouts, and floor strategy so the site does not maintain a bidding chain. Smart placements, A/B tests, and lazy loading run from one console, and reporting returns RPM, fill rate, and viewability per placement for unit-level tuning.
Integrations
Running alongside AdSense is the most common setup, with AdX and third-party SSPs connected through the shared wrapper. Deployment supports a WordPress plugin or manual installation into a custom template via plain JavaScript, and data is read from the console rather than a self-hosted warehouse.
Typical scenarios
Sites that have proven content monetization but trail peers on RPM; multi-site operators that need one placement strategy across domains; publishers in transition from pure AdSense to a mixed bidding stack. In all three, traffic is not the problem — price competition on the same traffic is.
Limitations
- Incremental share: billing is a share of incremental revenue rather than a flat percentage, so monthly checks require an independently calculated baseline
- Density bias: suggestions default toward raising ad density to raise revenue, and experience-sensitive sites must cap it themselves
- Integration effort: templates and script order change, and sites with many legacy pages also have to retire old units and duplicate tags
- Regional ceiling: Chinese and emerging-market inventory has limited upside, with gains concentrated in high-value English categories
Use Cases
- Content sites with steady traffic (★★★★☆): the bidding layer only pays off once the traffic base is there
- Sites running AdSense only (★★★★☆): one more demand path effectively raises the price of existing units
- Multi-site operators (★★★☆☆): a shared placement strategy helps, though each domain still needs its own validation
- Chinese-only low-CPM traffic (★★☆☆☆): the price ceiling is low and the incremental share may not justify the effort
- Brand-new sites (★☆☆☆☆): traffic is too small for A/B samples, leaving the optimization layer with nothing to tune
Pricing
| Item | Price | Notes |
|---|---|---|
| Onboarding and deployment | No upfront fee | WordPress plugin or generic JavaScript |
| Revenue share | Share of incremental revenue | Percentage per official quote, tied to traffic scale |
| Settlement | Monthly after threshold | Currency and payment method per contract |
| Extra capabilities | Included in the share | A/B tests, lazy loading, and placement reporting are not billed separately |
Share percentages, thresholds, and settlement currencies follow the official quote and contract, and terms vary meaningfully with traffic scale. Budget with page RPM uplift multiplied by monetizable pages rather than total pageviews times one blended price, otherwise the incremental gain is easily overstated.
FAQ
Does it conflict with AdSense?
No. AdSense stays as floor demand and AdPushup adds a bidding layer above it, as long as the same placement never renders the same network's ads twice.
How much traffic is needed?
No hard threshold is published, but small traffic leaves too few samples for split tests, so wait until page volume can support a controlled comparison.
Does it slow the page down?
Script count rises, and lazy loading offsets the below-the-fold part. Above-the-fold units still consume request budget, so compare real user metrics before and after.
Is it worth it for Chinese sites?
It can be connected, but uplift on Chinese and emerging-market traffic is limited; model the net gain after the share against template rework cost first.
Code Examples
<!-- Placement container generated per site id; both variables are injected by the build -->
<div id="ap-slot-incontent" data-ap-slot="$ADPUSHUP_SLOT_ID"></div>
<script async src="https://cdn.adpushup.com/adpushup.js" data-site="$ADPUSHUP_SITE_ID"></script>
// Inject site credentials at build time instead of hardcoding ids in the page
const fs = require('fs');
const path = require('path');
const SITE_ID = process.env.ADPUSHUP_SITE_ID; // provided by the CI environment
const SLOT_ID = process.env.ADPUSHUP_SLOT_ID;
if (!SITE_ID || !SLOT_ID) {
throw new Error('missing ADPUSHUP_SITE_ID or ADPUSHUP_SLOT_ID');
}
const tpl = fs.readFileSync(path.join(__dirname, 'slot.tpl.html'), 'utf8');
const out = tpl.replaceAll('$ADPUSHUP_SITE_ID', SITE_ID)
.replaceAll('$ADPUSHUP_SLOT_ID', SLOT_ID);
fs.writeFileSync(path.join(__dirname, 'dist', 'slot.html'), out);
console.log('injected slot for', SITE_ID.length, 'chars of site id');
Community & Resources
- Official site: https://www.adpushup.com/
- Publisher solutions: https://www.adpushup.com/publishers/
- Help documentation: https://help.adpushup.com/
- Official blog: https://www.adpushup.com/blog/