pakopress.dev — ID5 integration samples

Four ways to integrate the ID5 ID on this page, across two independent choices: where the ID5 calls go (first-party vs third-party base) and where the ID5 SDK file is loaded from (the edge vs jsDelivr). Each page shows the resolved ID5 ID and a live request panel.

first-partySDK from edge

First-party · SDK from edge

SDK and every ID5 call served first-party from edge.pakopress.dev (same registrable domain as the page). The variant that survives iOS 27.

Open sample →
third-partySDK from edge

Third-party · SDK from edge

SDK and calls served from the ID5-hosted edge edge.eu-2-id5-sync.com (third-party). Not on the iOS 27 block list; stop-gap for partners without the publisher's domain.

Open sample →
first-partySDK from jsDelivr

First-party · SDK from jsDelivr

SDK loaded from jsDelivr (neutral CDN); dynamic calls go first-party to edge.pakopress.dev. The edge handles only the calls.

Open sample →
third-partySDK from jsDelivr

Third-party · SDK from jsDelivr

SDK loaded from jsDelivr; dynamic calls go to the ID5-hosted edge edge.eu-2-id5-sync.com (third-party).

Open sample →

/a7q3 is the per-deployment proxy prefix. The first-party pages need an edge on edge.pakopress.dev/a7q3/*; the third-party pages need edge.eu-2-id5-sync.com/a7q3/*. partnerId: 173 is a placeholder; consent is static for the demo.