pakopress.dev — SDK from the alternate CDN

The ID5 SDK is loaded from cdn.delivrfy.cloud — an ID5-operated CDN on a registrable domain that carries no ID5 branding, serving the same bundle under the same paths as cdn.id5-sync.com. The dynamic ID5 calls still go first-party to edge.pakopress.dev: this page changes the SDK source only.

Waiting for ID5…

Which CDN served the SDK

SDK source
—
Build reported
—
id5cdn flag
—

Build is window.ID5.version and the id5cdn flag is window.ID5._isUsingCdn — both read from the loaded SDK, so the flag is the SDK’s own verdict rather than a re-derivation. If that field is ever gone, the page falls back to applying the rule below itself.

default (delivrfy primary) swap: id5-sync primary force primary to fail

Loader log

    What this tests

    Whether an ID5-operated CDN on an unrelated registrable domain is a drop-in for cdn.id5-sync.com. The two hosts serve byte-identical bundles under identical paths, so the swap is one string in the <script src>. What it does not change: the dynamic ID5 calls, which are driven by apiBaseUrl and still need the edge.

    // same path, same bundle, different registrable domain
<script src="https://cdn.delivrfy.cloud/api/1.0/id5-api.js"></script>

ID5.init({
  partnerId: 173,
  apiBaseUrl: 'https://edge.pakopress.dev/a7q3'  // unchanged — the CDN swap does not move the calls
});

    The id5cdn flag

    The SDK tells the ID5 backend whether it was served from the ID5 CDN. The test is a literal prefix match on one host, so a bundle served from cdn.delivrfy.cloud reports as self-hosted even though it is the same file from an ID5-operated CDN.

    // inside id5-api.js and id5PrebidModule.js (v1.0.99)
isUsingCdn = Boolean(document.currentScript && document.currentScript.src &&
  0 === document.currentScript.src.indexOf("https://cdn.id5-sync.com"));

// sent on every fetch as:  id5cdn: isUsingCdn

    Requests made by this page

    purple = cdn.delivrfy.cloud · amber = cdn.id5-sync.com · green = first-party pakopress.dev

    typehostpath