Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Creating a Google Ads account and credentials

Updated on September 6, 2023

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.

  1. Sign in to Google with a Google account that is not already linked to a Google Ads account.
  2. Go to Google Ads Manager Accounts.
  3. Click Create a Manager Account and fill out the registration form.
  4. In Google Ads, click Tools & SettingsSetupAPI Center.
    Google Ads API Center access
    Google Ads API Center access
  5. In the API Center, fill out the access form.
    Note: In the Company type section, select Advertiser.
  6. Click Create Token.
    Make a note of the token. You will need it to configure the connection between Paid Media Manager and Google Ads later. For more information, see Configuring Google Ads destinations in Paid Media Manager.
  7. Go to the Google Ads overview, and then click Accounts.
  8. Click + to create a new account or link an existing account.
    Google Ads API Center access
    Google Ads API Center access
    You can use either a Google Ads account or an AdWords Express account, depending on your requirements. For more information, see Compare Smart campaigns with other Google Ads campaign types.
  9. Create the OAuth credentials. For more information, see Creating a Google Ads account and credentials.
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.
  1. Sign in to Google with a Google account that is not already linked to a Google Ads account.
  2. Go to Create a Google Ads Test Account.
  3. Fill out the registration form and click Save and continue.
  4. Create the OAuth credentials for use with the test account.

Creating the OAuth credentials in Google Ads

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.

  1. 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.
  2. Log in to the Google API Interface console.
  3. Create a new project by clicking Create.
  4. Select the project which you created.
    Sample project
    Sample project
  5. 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.
  6. Click Save.
  7. Click CredentialsCreate credentialsOAuth client ID.
  8. Under Application type, select Web application.
  9. 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.
  10. 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.
To continue setting up the Paid Media Manager connection to the Google Ads destination, see Configuring Google Ads destinations in Paid Media Manager.
  • Previous topic Configuring Google Ads destinations
  • Next topic Configuring Google Ads destinations in Paid Media Manager

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us