Where the config response points
Waiting for the
configUrl response…Captured from the response Prebid.js actually received. id5ApiBaseUrl is deliberately unset here — the built-in path ignores it.
Config host
Resolving the ID5 ID through Prebid…
ID5 ID inside the auction
Waiting for the first auction…
Read from the bidRequest.userIdAsEids seen by a pbjs auction event.
Integration
Knob exercised:
configUrl → …Not set:
externalModuleUrl (keeps Prebid.js on its built-in path) and id5ApiBaseUrl (that param is read only by the external module)What decides the next hop:
fetchCall.url from the config response. The ID5 backend rewrites it to the first-party base only when the proxy sends X-Id5-Proxy-Base-Url.<!-- 1. Prebid.js (with the ID5 User ID module) -->
<script src="https://pakopress.dev/prebid.js"></script>
<!-- 2. Configure the ID5 User ID module -->
pbjs.setConfig({
userSync: { auctionDelay: 5000, userIds: [{
name: 'id5Id',
params: { partner: 173, configUrl: '…' },
storage: { type: 'html5', name: 'id5id', expires: 90 }
}] }
});
Requests made by this page
green = first-party · amber = ID5 edge · red = direct id5-sync.com
| type | host | path |
|---|