pakopress.dev — third-party · proxy on a blocked domain

SDK and every ID5 call go through proxy.eu-1-id5-sync.com/a7q3. Unlike eu-2-id5-sync.com, the registrable domain eu-1-id5-sync.com is subject to request blocking — so this is the control case showing the proxy host itself must be a non-blocked domain.

Expected result
Where this domain is blocked: the SDK and calls to proxy.eu-1-id5-sync.com are blocked → no ID5 ID.
Where it is not blocked: the proxy works → ID5 ID resolves (the block is browser-specific, not a proxy fault).
Waiting for ID5…

Integration

Host (SDK + calls): proxy.eu-1-id5-sync.com
Party: third-party — on a blocked registrable domain (eu-1-id5-sync.com)
Link: direct (ID5-owned subdomain)
<!-- 1. Load the ID5 SDK -->
<script src="https://proxy.eu-1-id5-sync.com/a7q3/api/1.0/id5-api.js"></script>  ← changed from cdn.id5-sync.com

<!-- 2. Initialise -->
ID5.init({
  partnerId: 173,
  apiBaseUrl: 'https://proxy.eu-1-id5-sync.com/a7q3',  ← new: routes every ID5 call to this base
  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 · amber = ID5 edge on a non-blocked domain · red = a blocked domain (id5-sync.com, eu-1-id5-sync.com)

typehostpath