Waiting for ID5…
Diagnostics
…
The SDK decides once at init whether to publish: Math.random() < publishingSampleRatio. It then posts to apiBaseUrl + /diag/measurements after publishAfterLoadInMsec and again on page unload.
Integration
SDK host:
cdn.delivrfy.cloud — serves the same bundle as cdn.id5-sync.com under the same path, byte for byte. Floating build, max-age=3600.Calls host:
delegated.pakopress.devParty: first-party calls — same registrable domain as the page (
pakopress.dev)Link: whole subdomain NS-delegated → AWS Route 53 (authoritative DNS) →
A records to the ID5 edge on OVH. No CNAME.Endpoints: served at the root of the host —
/gm/v3, /bounce, /event, /diag/measurements. No path prefix.<!-- 1. Load the ID5 SDK from the alternate CDN --> <script src="https://cdn.delivrfy.cloud/api/1.0/id5-api.js"></script> ← changed from cdn.id5-sync.com, same path <!-- 2. Initialise --> ID5.init({ partnerId: 173, apiBaseUrl: 'https://delegated.pakopress.dev', ← routes every ID5 call to the delegated base diagnostics: { publishingSampleRatio: 1, publishAfterLoadInMsec: 3000 }, ← added only with ?sampling= cmpApi: 'static', consentData: { /* static TCF v2.2: vendor 131, purposes 1-11 */ } }).onAvailable(id5 => console.log(id5.getUserId()));
Requests made by this page
green = first-party (same site as the page) · amber = ID5 edge (third-party domain) · red = direct call to id5-sync.com (should never appear) · violet row = diagnostics publish
| type | host | path |
|---|