As part of the process of connecting Paid Media Manager to a Google Ads destination,
you must have a manager account in Google Ads and use the credentials for that account to
configure a destination in Paid Media Manager.
Pega Customer Decision Hub Paid Media Manager User Guide
Pega Customer Decision Hub Paid Media Manager User Guide
Pega Customer Decision Hub Paid Media Manager User Guide
Pega Customer Decision Hub Paid Media Manager User Guide
Creating a Google Manager Account to call the Google Ads APIs for production
accounts
If you do not already have a Google Manager Account, create it, and then apply for
access to the AdWords API.
Sign in to Google with a Google account that is not already linked to a Google
Ads account.
What to do next: Before you can use the Google Ads Manager Account in
production, your API token must first be approved by Google. To start testing
immediately without waiting for the token to be approved, create a test manager account.
Creating a test manager account in Google Ads
Create a test manager account to test new API implementations or account
configurations before implementing the changes in your production environment. Test accounts
do not require an approved developer token, so you can start working with the API
immediately.
Note: Test accounts cannot be used in production, since they do not actually serve ads
to customers.
Sign in to Google with a Google account that is not already linked to a Google
Ads account.
Create the OAuth credentials to obtain the client ID and client secret required to
configure the connection to a Google Ads destination in Paid Media Manager. You can create
these credentials for both the production and test manager accounts.
Log in to Pega Customer Decision Hub.
Note: Make sure that the link you use to log in includes the
prweb root domain and the Pega Customer Decision Hub instance domain, that is,
https://host.domain:port/prweb.
If you log in using a link without either the root domain or the instance
domain, the redirect URL for OAuth will not be valid and authentication will
not succeed.
Click OAuth consent screen and fill out the required
information. Details of some of the critical fields are provided below.
Under User type, select
External.
On the first screen, under Authorized domains,
enter the root domain of your Pega Customer Decision Hub
instance.
On the second screen, click Add users and add an
email ID that will be used for the OAuth process. This is required while
the app has the Testing status. When you start
using the app for production systems, move it to the In
Production status.
Caution: If you do not update the app to the In
Production Publishing status and leave it at the
Testing Publishing status, the refresh
token generated when you saved the Google Ads destination in the
paid destination will expire in a few days. This will lead to Sync
Job failures. To prevent the refresh token from expiring too soon,
transition your app to the In Production
Publishing status.
Note: Domain verification is an optional step for Paid Media Manager
integration.
Under Authorized redirect URLs, click
Add and enter the redirect URL for your instance,
that is,
https://host.domain:port/prweb/PRRestService/oauth2/v1/redirect.
Click Create and note the client ID and client secret
that are displayed.
What to do next:
Important: Your Google Ads account must able
to access the following APIs:
CrmBasedUserList - Mandatory. Paid Media Manager uses
this API to manage the audiences in the Google Ads network.
OfflineDataUploadService - Optional. This API is required
if you want to use Paid Media Manager to upload data about historical
offline conversions into Google Ads.
Contact your Google Ads account representative for information about enabling
the APIs for your account.
