Member Avatar for keepbusy

So I ran some reports and found that I'm losing about 10-12% of my ad impressions from Tier to Tier down the Daisy-Chain. For example if my top-tier network reports that it could not fill 500,000 ad impressions, my tier 2 should see 500,000 impressions but instead is only seeing 450,000. This trend continues from tier 2 to tier 3 and tier 3 to tier 4 etc. Does everyone else see this Trend? If so, are there any recommendations to improve this?

Thanks!!

  • 4 Contributors
  • 3 Replies
  • 126 Views
  • 4 Months Discussion Span
  • Latest Post Latest Post by bobchrist

Dani AI

Generated

— seeing fewer impressions as a request cascades down a daisy‑chain is a real and diagnosable symptom. It usually comes from differences in what each system counts, timing and timeout behavior, or tag/logic failures in the passback chain. Below is a concise troubleshooting checklist and practical fixes to narrow the loss and prevent recurrence.

  • Confirm metric definitions first: ask each network whether they are reporting “ad requests”, “served ads”, or “impressions (pixel fired)”. Mismatched definitions explain many gaps.
  • Align clocks and reporting windows: ensure timezones and aggregation buckets match across reports before comparing numbers.
  • Match request IDs/timestamps: enable or pass a unique request macro so you can correlate a single page request across publisher ad server and downstream networks.
  • Use a waterfall test in the browser: load pages with devtools open and watch the chain of tag calls, errors (4xx/5xx), and round‑trip times. Note tags that never get called.
  • Check timeouts and latencies: if a top-tier tag times out or swallows errors instead of issuing a passback, downstream tiers never see the request.
  • Look for filtering: frequency caps, targeting rules, geo/campaign blocks, invalid traffic filters, and ad blockers can drop some requests before downstream tiers see them.

Practical fixes and longer-term changes:

  • Make passbacks explicit and asynchronous so “no-fill” paths reliably call the next tier (and fire an impression pixel if served).
  • Reduce sequential hops: consolidate demand via header bidding or server‑to‑server connections to avoid round‑trip losses.
  • Instrument logging for matched IDs and ask networks for matched log exports when discrepancies persist.
  • Test changes in staging with synthetic traffic, then roll out gradually.

For and : placement is less likely the root cause than how the tags/counting are implemented. For : audience/targeting can contribute, but confirm tag and reporting alignment before changing targeting.

Recommended Answers

All 3 Replies

Member Avatar for Techie08

Not sure i understand what you mean, where are you placing the ads?

Member Avatar for IdeaAlex

Yes, I am a bit confused too. can you please clarify? May be reporting system is buggy?

Member Avatar for bobchrist

Can you specify what problem you're facing? Are you targeting the right audience?

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.