Skip to content

Commit 53688da

Browse files
authored
Merge pull request #862 from IABTechLab/gwh-APIDOCS-3078-clarify-re-integ-keys
make info re getting integ credentials more accessible
2 parents fd0328c + 46b1e8d commit 53688da

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/guides/integration-prebid-client-side.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -49,7 +49,7 @@ You'll need to complete the following steps:
4949

5050
To integrate with UID2, you'll need to have a UID2 account. If you haven't yet created an account, first follow the steps described on the [Account Setup](../getting-started/gs-account-setup.md) page.
5151

52-
When initial account setup is complete, you'll receive instructions and a link to access the [UID2 Portal](../portal/portal-overview.md), where you can create your [credentials](../getting-started/gs-credentials.md) for the production environment and configure additional values that you'll need to provide. For details, see [Getting Started with the UID2 Portal](../portal/portal-getting-started.md).
52+
When initial account setup is complete, you'll receive instructions and a link to access the [UID2 Portal](../portal/portal-overview.md), where you can create your [credentials](../getting-started/gs-credentials.md) for the production [environment](../getting-started/gs-environments.md) and configure additional values that you'll need to provide. For details, see [Getting Started with the UID2 Portal](../portal/portal-getting-started.md).
5353

5454
For a client-side integration you'll need to set up these values, in the UID2 Portal on the [Client-Side Integration](../portal/client-side-integration.md) page:
5555

@@ -118,7 +118,7 @@ const baseConfig = {
118118
```
119119

120120
:::note
121-
This example assumes that you're using the UID2 production environment. During integration testing, use the UID2 integration environment (for credentials, see [Getting Your Credentials](../getting-started/gs-credentials.md#getting-your-credentials)) by setting `params.uid2ApiBase` to `'https://operator-integ.uidapi.com'`. Tokens from the UID2 integration environment are not valid for passing to the bidstream. For the integration environment, you will have different **Subscription ID** and **public key** values.
121+
This example assumes that you're using the UID2 production environment. During integration testing, use the UID2 integration environment by setting `params.uid2ApiBase` to `'https://operator-integ.uidapi.com'`. Tokens from the UID2 integration environment are not valid for passing to the bidstream. For the integration environment, you will need to request separate **Subscription ID** and **public key** values; you cannot create those in the UID2 Portal. For details, see [Getting Your Credentials](../getting-started/gs-credentials.md#getting-your-credentials).
122122
:::
123123

124124
## Storing the UID2 Token in the Browser
@@ -171,7 +171,7 @@ If there are problems with the integration, here are some steps you can take:
171171
- Check the browser console logs.
172172
- Check the values for **Subscription ID** (**subscriptionId** value) and **public key** (**serverPublicKey** value):
173173
- Make sure they are exactly the same values that you received from the UID2 team.
174-
- Check that you have the correct values for the environment you're using. You'll have different **Subscription ID** and **public key** values for each [environment](../getting-started/gs-environments.md).
174+
- Check that you have the correct values for the environment you're using. You'll have different **Subscription ID** and **public key** values for each environment: see [Getting Your Credentials](../getting-started/gs-credentials.md#getting-your-credentials).
175175
- Check that you provided the domain name of the site to the UID2 team during account setup. If needed, to confirm, ask your UID2 contact.
176176
- Use the browser developer tools to inspect the API calls to the UID2 service.
177177

0 commit comments

Comments
 (0)