Google Ad Manager Query Authentication Guide
This is a step-by-step guide to creating an OAuth entry, acquiring credentials, and authorizing the Google Ad Manager Query connector for use in Matillion ETL.
- The Google Ad Manager Query connector uses an OAuth for third-party authentication.
- While connector properties may differ between Cloud Data Warehouses, the authentication process remains the same.
- The callback URL, and therefore the Matillion ETL instance, must be HTTPS, not HTTP.
- Please be aware, the use of some services with a Google Cloud Platform account may incur costs. For further information, please refer to Google Cloud Platform pricing.
Creating an OAuth Entry in Matillion ETL
1. In Matillion ETL, on the top left of the screen, click Project, then Manage OAuth.
If a Google Ad Manager Query connector has already been added to an Orchestration Job, the Manage OAuth window may also be accessed using the following method:
- Click the connector icon to open the Properties panel at the bottom of the screen.
- Click ... next to the Authentication input, and click Manage in the pop-up window.
2. Copy the Callback URL in the field at the top of the window as this will be required in Acquiring Third-Party Credentials.
3. Click in the bottom left of the window to open the Add OAuth Entry dialog.
4. Provide a name for the OAuth in the Name field, then use the Service drop-down menu to select Google Ad Manager. Click OK.
5. On returning to the Manage OAuth dialog, check the list of OAuths to ensure the new entry is listed.
This entry is Not Configured. Configuration of the OAuth entry will be discussed in Authorizing for use in Matillion ETL.
Acquiring Third-Party Credentials
1. Navigate to the Google Developers Console. The Google login screen will appear immediately. Enter valid login credentials to continue. The browser will then redirect to the API & Services dashboard. Click the project dropdown menu next to Google APIs in the top left of the screen.
The menu should display the name of the currently selected project, i.e. <Project Name>. If there is no current project, the menu will read Select a project.
2. The project window will pop up. Click NEW PROJECT in the top right of the window.
3. In the New Project dialog, provide details for the following fields:
- Project name – provide a name for the project.
- Organization – select an organization to be associated with the app.
- Location – select a folder where the project will be stored, then click Create.
4. The browser will return to the API & Services dashboard. Now click OAuth consent screen on the sidebar. In the OAuth consent screen, provide details for the following fields:
- Application name – provide a name for the app.
- Support email – provide an email address to be used to provide support for the app.
5. Next, scroll down ro the Authorized domains section, and provide details for the following fields:
- Authorized domains – provide all domain URLs associated with the app including the domain URL of the Callback URL (copied from the Manage OAuth window in Matillion ETL earlier).
- Application Homepage link – provide the homepage URL for the app (it must also be listed among the above Authorized domains), then click Save.
- IP Addresses unfortunately are not be accepted and will need to be mapped to a hostname. For further information, please refer to Google Cloud Platform Console Help.
6. The browser will return to the API & Services dashboard. Click Credentials on the sidebar. Then, in the Credentials dialog, click Create credentials, then OAuth client ID.
7. Now, in the Create OAuth client ID page, select Web Application under Application type to reveal further options. Then, provide details for the following fields:
- Name – provide a descriptive name for the client ID.
- Authorized redirect URLs – provide the Callback URL (earlier listed on the OAuth consent screen as one of the Authorized domains).
8. The browser will return to the API & Services dashboard once again, now with a pop-up window featuring the client ID and client secret. Copy both the client ID and client secret codes from the fields as they will be required in Authorising for use in Matillion ETL.
- Make sure to copy the client secret right away as it may appear only once.
- Additionally, when copying the codes, some browsers may add a space to the end of the code. Watch out for this as it will cause the credentials to fail.
9. A service API will now need to be enabled to work with the newly created credentials. Click Library on the sidebar, and in the API Library window, either type "Google Ads" into the search field at the top of the page, or click the Advertising filter category on the sidebar, then scroll down, and click the Google Ads API block.
10. Once selected, the Google Ads API window will open. To enable the API for use with the app, click Enable.
11. Lastly, navigate to the Google Ad Manager website. The Google login screen will appear immediately. Enter valid login credentials to continue. The browser will then redirect to the Ad Manager dashboard. Copy the code found either listed after
https://admanager.google.com/ in the website's URL, or in the top left of the screen underneath <Account name>.
Authorizing for Use in Matillion ETL
1. Return to the Manage OAuth dialog in Matillion ETL, and click next to the previously created OAuth entry. This will open the Configure OAuth window.
2. Using the codes copied from the Google Developers Console and the Google Ad Manager website earlier, provide details for the following fields:
- Client ID – enter the client ID.
- Client Secret – enter the client secret.
- Network Code – enter the Network Code, then click Next.
3. The next dialog will have an Authorization link. Click the link to authorise Matillion ETL to use the acquired credentials.
4. The browser will then redirect to a login screen to connect the Google account to the app. Click the associated account name to confirm the connection. A prompt will then ask permission to access each feature associated with the Google account. Either Allow or Deny to continue to the next prompt.
5. Once permission has been allowed or denied to each associated Google feature, a final window will confirm all the permissions together. Click Allow to confirm all is correct.
6. If all is successful, the browser will return to Matillion ETL stating, "Authorization Successful".