✨ Taboola amp privacy fallback - #40537
Conversation
If the primary loader (cdn.taboola.com/.../loader.js) is blocked by private browsing / tracking protection treating taboola.com as a tracker, fall back to the privacy loader served from the clean domain (static.tblcontent.com/.../loader.privacy.js). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Fire an unconditional GET to static.qovani.com (clean domain) on every page view, independent of whether the primary loader or the privacy loader fallback succeeds. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
|
|
Hi @calebcordry / @ampproject/wg-ads-reviewers This is a small change that adds a fallback so ads keep serving when the primary cdn.taboola.com loader is blocked/unavailable, plus a lightweight telemetry pixel to confirm the adapter ran. This is currently impacting live publisher pages on our side, so we'd really appreciate a review (or a pointer to the right owner) whenever you get a chance. happy to make any changes needed 🙏 |
|
Hi @erwinmombay / @powerivq, |
|
Thanks for merging this, @powerivq 🙏 It's not in a served build yet, any chance of cutting a new release from main so it can go live? |
|
@Michalkals https://amp.dev/documentation/guides-and-tutorials/learn/spec/release-schedule It will follow release schedule and should go live within 2wk. |
5 participants
The Taboola AMP adapter has a single point of failure: it loads its runtime from
cdn.taboola.com. When that CDN loader is blocked or unavailable, Taboola servesnothing on the page. This PR adds a privacy-loader fallback so ads keep serving,
plus a lightweight telemetry pixel on a clean domain to get a reliable per-page-view
signal that the adapter ran.