ID5 ID inside the auction
Read from the bidRequest.userIdAsEids seen by a pbjs auction event.
Which host served the module
externalModuleUrl- —
- Build reported
- —
id5cdnflag- —
Build is window.id5Prebid.version and the id5cdn flag is window.id5Prebid.integration._isUsingCdn — both read from the loaded module, so the flag is the module’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) swap: cdn.id5-sync.com swap: edge.pakopress.dev
Integration
externalModuleUrl → https://cdn.delivrfy.cloud/api/1.0/id5PrebidModule.js (alternate CDN, third-party to the page)pbjs.setConfig — no enablerconfigUrl → https://edge.pakopress.dev/a7q3/config/prebid — the alternate CDN mirrors static bundles and has no /config/prebid endpoint, so the submodule's dynamic-config fetch stays on the edge. id5ApiBaseUrl stays unset.<!-- 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, externalModuleUrl: 'https://cdn.delivrfy.cloud/api/1.0/id5PrebidModule.js', configUrl: 'https://edge.pakopress.dev/a7q3/config/prebid' },
storage: { type: 'html5', name: 'id5id', expires: 90 }
}] }
});
The id5cdn flag
The module tells the ID5 backend whether it was served from the ID5 CDN. The test is a literal prefix match on one host, so a module served from cdn.delivrfy.cloud reports as self-hosted even though it is the same file from an ID5-operated CDN.
// inside id5PrebidModule.js and id5-api.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 · green = first-party · amber = ID5 edge · red = direct id5-sync.com
| type | host | path |
|---|