Table of Contents
Before Beginning
This section contains information that is important to know before creating a Credential record.
Some external providers require additional setup before they can be connected to a OneStrata enterprise. These actions must be done directly within the external provider platform. For more information, see the Prerequisites section below.
Once a Credential record is created, the following values cannot be changed:
- The provider type of the record.
- The provider of the record.
- The entity level of the record (enterprise or non-enterprise).
Prerequisites
For some external providers, additional setup is required before the provider can be connected to OneStrata:
| Provider | Prerequisite Action(s) |
|---|---|
| Google integrations (CM360, DV360, Google Ads) | In Google Cloud API console, create and authorize a project for OneStrata:
|
Meta | In OneStrata version 25.4.22 (released May 7, 2022), the integration with Meta was upgraded to v22.0 of the Meta Marketing API. Enterprises with a Meta app using an earlier version of the Marketing API must upgrade their app to v22.0. Otherwise, the Meta integration will not work. For more information, see Upgrade to the Latest Graph API Version. For central login credentials:
|
| The Trade Desk | Request API access from The Trade Desk.
In The Trade Desk, create a report template.
|
Create a Credential Record
Start the Credential Record Creation Process
To start the Credential record creation process, do the following:
- Go to the Admin > External Integrations > Credentials tab.
- Click Create to open the Create External Integration widget.
Enter Application Level Details
On the Create External Integration > Application Level page, do the following:
- Enter general details:
Field Name
The value of any fields with a red background cannot be changed after the Credential record is created.
Step(s) Name Enter the name of the Credential record. Apply At The Enterprise Level
Select whether or not the Credential record is created at the enterprise level:
- Yes: The record is created at the enterprise level and can be used in campaigns for any client.
- No: The record is not created at the enterprise level can only be used in campaigns for the specified Agency, Business Unit, Client Group, or Client (see below).
Only available if Apply At The Enterprise Level is No
Agency / Business Unit
Client Group / Client
For non-enterprise-level Credential records, select the entity level and entity of the record.
- To create an Agency-level record: In the Agency / Business Unit field, select the desired Agency.
- To create a Business Unit-level record: In the Agency / Business Unit field, select the desired Business Unit.
- To create a Client Group-level record: In the Agency / Business Unit field, select the Business Unit that the Client Group belongs to. Then, in the Client Group / Client field, select the desired Client Group.
- To create a Client-level record: In the Agency / Business Unit field, select the Business Unit that the Client belongs to. Then, in the Client Group / Client field, select the desired Client.
Read-only
Media
The value of the Media field is automatically set to Digital and cannot be changed. - Yes: The record is created at the enterprise level and can be used in campaigns for any client.
Click Next to continue to the Create External Integration > Provider page.
Enter Provider Details
On the Create External Integration > Provider page, do the following:
- Enter provider details:
Field Name
The value of any fields with a red background cannot be changed after the Credential record is created.
Step(s) Provider Group Type Select the provider type of the Credential record.
- Ad Server
- DSP (Demand-Side Platform)
- Search Platform
- Social Platform
Provider Select the provider of the Credential record. Only providers that are available for the selected provider type are displayed.
Linked Suppliers Link one or more Suppliers to the Credential record.
For more information, see Supplier Linking and Mapping.
Click Next to continue to the Create External Integration > Credential page.
Enter Credential Details
On the Create External Integration > Credential page, do the following:
- Enter login details:
Field Name Step(s) Login Type Select the login type of the Credential record:
- Individual
- Central
- Depending on the provider of the Credential, additional information is required:
Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.
The table is being loaded. Please wait for a bit ...
Section Name Provider Note Application Details Meta
See Enter Application Details. Account Details Buyer Cloud (formerly known as FreeWheel DSP)
CM360,
DV360,
Innovid (formerly known as Flashtalking),
Google Ads,
Meta,
The Trade Desk
See Enter Account Details. API Credentials CM360,
DV360,
Google Ads
See Enter API Credentials. Token Details CM360,
DV360,
Google Ads,
Meta
Token details can be manually entered while creating the Credential record or generated after creating the record:
- For information on manually entering token details, see Optional: Enter Token Details.
- For information on generating token details (recommended), see Optional: Generate Token Details.
- For information on manually entering token details, see Optional: Enter Token Details.
Enter Application Details
- The Application Details section only applies to Meta integrations.
- A Meta app specifically for OneStrata must be created before the Credential record can be created. For more information, see Prerequisites.
In the Create External Integration > Credential > Application Details section, enter the following information:
| Provider | Field Name | Description |
|---|---|---|
| Meta | App ID | Enter the ID of the Meta app being linked to OneStrata. This value can be found on the Meta App Dashboard's App settings > Basic page, in the App ID field. |
| Meta | App Secret | Enter the App Secret of the Meta app being linked to OneStrata. This value can be found on the Meta App Dashboard's App settings > Basic page, in the App secret field. |
Enter Account Details
In the Create External Integration > Credential > Account Details section, enter the following information:
Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.
The table is being loaded. Please wait for a bit ...
| Provider | Field Name | Step(s) |
|---|---|---|
Buyer Cloud | Username | Enter the username of the Buyer Cloud account being linked to OneStrata. |
| Buyer Cloud | Password | Enter the corresponding password of the Buyer Cloud account being linked to OneStrata. |
| Buyer Cloud | Optional Account ID | Optional: If the user account has multi-account access, enter the ID of a specific Buyer Cloud account. The login credentials are then valid for that account only. |
| Buyer Cloud | Buzz Key | The buzz key provided if you have a specific environment. By default uses dsp. |
| CM360 | Profile ID | Enter the ID of the CM360 user profile/account being linked to OneStrata. This user profile must have access to the CM360 network being linked to OneStrata. This value can be found in the dropdown menu used to switch between networks within CM360. |
| CM360 | Network ID | Enter the ID of the CM360 network being linked to OneStrata. This network is used for data access and delivery data retrieval within OneStrata. This value can be found in the dropdown menu used to switch between networks within CM360. |
| CM360 | Optional Sub-Network ID | Optional: Enter the ID of the CM360 sub-network being linked to OneStrata. If a CM360 sub-network is linked to OneStrata, the access and permissions specified in the linked sub-network take precedence over the access and permissions specified in the linked CM360 network. |
| CM360 | Optional Report ID | Optional: Enter the ID of a specific CM360 report to retrieve delivery data from. If no specific CM360 report is linked to OneStrata, the default delivery data is retrieved instead. |
| DV360 | Partner ID | Enter the ID of the DV360 partner being linked to OneStrata. This value can be found on the DV360 Partners page. |
| DV360 | Reporting Currency | Select a reporting currency for DV360 campaigns linked to OneStrata:
The currency values are reported on the Actualization tab, in the Site Cost column of the Standard Actualization grid. |
| Innovid | Username | Enter the username of the Innovid account being linked to OneStrata. |
| Innovid | Password | Enter the corresponding password of the Innovid account being linked to OneStrata. |
| Innovid | Optional Use Sandbox | The Use Sandbox option should only be selected if Innovid has provided a UAT account and environment for testing purposes. Select the Use Sandbox option if the Innovid credentials entered above are for a testing account and environment. |
| Google Ads | Developer Token | Enter the Google Ads developer token used by Google Ads manager account being linked to OneStrata. This value can be found on Google Ad's Admin > API center page, in the Developer token field. |
| Google Ads | Login Customer ID | Enter the ID of the Google Ads manager account being linked to OneStrata. This value can be found in the dropdown menu used to switch between manager accounts within Google Ads. |
| Meta | Optional Business ID | Optional: Enter one or Meta business IDs to link to OneStrata. A Meta business ID is the identifier of a Meta business portfolio, and is also the same as Business Manager ID. If a Meta business portfolio is linked to OneStrata, the access and permissions specified in the linked business portfolio take precedence over the access and permissions specified in the linked Meta app configuration. |
| Meta | Config ID | Enter the ID of the Meta app configuration being linked to OneStrata. A Meta app configuration specifies the business assets and permissions required for and granted to the app, and is part of Facebook Login for Business. This value can be found on the Meta App Dashboard's Facebook Login for Business > Configurations page. |
The Trade Desk (TTD) | Username | API access must be requested from The Trade Desk before the Credential record can be created. For more information, see Prerequisites. Enter the username of the The Trade Desk API account being linked to OneStrata. |
| The Trade Desk | Password | Enter the corresponding password of the The Trade Desk API account being linked to OneStrata. |
| The Trade Desk | Partner ID | Each set of login credentials can only be linked to one The Trade Desk partner. To link multiple partners to OneStrata, create a new Credential record for each partner. The same API username and password can be used. Enter the ID of the The Trade Desk partner being linked to OneStrata. |
| The Trade Desk | Optional Use Sandbox | The Use Sandbox option should only be selected if The Trade Desk has provided a UAT account and environment for testing purposes. Select the Use Sandbox option if the The Trade Desk credentials entered above are for a testing account and environment. |
| The Trade Desk | Report Template ID | A report template must be created in The Trade Desk before the Credential record can be created. For more information, see Prerequisites. Enter the ID of the The Trade Desk report template being linked to OneStrata. This template is used for data access and delivery data retrieval within OneStrata. |
Enter API Credentials
- The API Credentials section only applies to Google integrations (CM360, DV360, Google Ads).
- A Google Cloud API Console project specifically for OneStrata must be created before the Credential record can be created. For more information, see Prerequisites.
In the Create External Integration > Credential > API Credentials section, enter the following information:
Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.
The table is being loaded. Please wait for a bit ...
| Provider | Field Name | Step(s) |
|---|---|---|
CM360, DV360, Google Ads | Client ID | Enter the ID of the OAuth client being linked to OneStrata. This value can be found on Google Cloud API Console's Credentials > Additional Information section, in the Client ID field. |
CM360, DV360, Google Ads | Client Secret | Enter the client secret of the OAuth client being linked to OneStrata. This value can be found on Google Cloud API Console's Credentials > Client secrets section, in the Client secret field. |
CM360, DV360, Google Ads | API Key | Enter the API key used to access the Google API. |
Optional: Enter Token Details
There are two ways to specify token details:
- Recommended: Generate token details using the provided API credentials, after the Credential record is created. For more information, see Optional (Recommended): Generate Token Details.
- Manually enter token details while creating the Credential record.
To manually enter token details, enter the following information in the Create External Integration > Credential > Token Details section:
Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.
The table is being loaded. Please wait for a bit ...
| Provider | Field Name | Step |
|---|---|---|
CM360, DV360, Google Ads, Meta | Access Token | Enter the token used to access the external provider's API. |
CM360, DV360, Google Ads | Refresh Token | Enter an access token. Access tokens have limited lifetimes, and refresh tokens are used to automatically obtain new access tokens and ensure continuous API access. |
CM360, DV360, Google Ads, Meta | Read-only Access Token Expiration UTC | Read-only The expiration date and time of the entered access token, in Coordinated Universal Time (UTC). |
CM360, DV360, Google Ads | Read-only Access Token Issue Date UTC | Read-only The issue date and time of the entered access token, in Coordinated Universal Time (UTC). |
Finish the Credential Record Creation Process
Remember: After a Credential record is created, the record's entity level (enterprise or non-enterprise) and Provider Group Type and Provider values cannot be changed.
To change any of these values, click Previous to return to an earlier step and make any desired changes.
To finish the Credential record creation process, do the following:
- Click the Create button.
By default, the page redirects to the Credential tab of the newly created record. If the record requires token details and the token details were not manually entered, follow the steps in Optional (Recommended): Generate Token Details to generate the token details.
Optional (Recommended): Generate Token Details
There are two ways to enter token details:
- Recommended: Generate token details using the provided API credentials, after the Credential record is created. For more information, see the steps below.
- Manually enter token details while creating the Credential record.
To generate token details, do the following:
- Open the desired Credential record and go to its Credential tab.
- In the Integration Test section, click the Run Integration Test button.
If the login credentials are correct, the integration test succeeds and the Token Details section is automatically populated with the appropriate token details. Otherwise, the integration test fails.