Connection, Credentials & Host URLs

Retail Media uses connections created in the CDXP panel. Each connection carries the credentials a given integration point needs.

Steps

1. In the CDXP panel, go to Ads → Connections.
2. Create a connection of the type you need (see below).
3. Copy the credentials and host URLs it generates — you'll need them in code.

Web SDK connection

Your CDXP owner / retail-media manager creates a Web SDK connection for identity, event tracking, and (optionally) SDK ad rendering on your surface. It yields:

You need	What it is
API Key (apiKey)	Authenticates the Web SDK
Source Identifier (sourceIdentifier)	Identifies your source to the SDK
Ad Slot ID(s)	The numeric slot IDs from Define ad slots
Host URLs (rtbPath, apiPath, sdkPath)	The endpoints the SDK and your code call — see below

Host URLs

Host	Purpose
rtbPath	Ad requests (RTB)
apiPath	Tracking
sdkPath	Web SDK script & creatives

Their exact values are provided by your CDXP owner.

info

In device mode, the Web SDK's apiKey and sourceIdentifier are public — they run in the user's browser and are visible in dev tools. This is expected for a client-side SDK. See the Web SDK Quickstart.

Catalog connection

To send your catalog to the platform, create a catalog connection at the same path. It yields a sourceIdentifier and an API key:

• The sourceIdentifier goes into the Sync endpoint path (/api/tracker/catalog/{sourceIdentifier}/...).
• The API key is used as the Bearer token that authenticates your Sync calls.

Unlike the Web SDK credentials, the catalog connection is server-to-server — its Bearer token is a secret and must never be exposed in a browser. See Catalog API.

Ready

With the media property defined, the ad slots created, and these credentials in hand, you're ready to integrate — pick the ad family you're building:

• Display Ads · Sponsored Ads