[Create connection] Setting Up a Service Account Connection for Google Ad Manager in ADvendio

The first requirement for this type of connection is a JSON key file containing the necessary credentials. The key’s content must be copied and pasted into the Extended Token field (where it will be automatically encrypted), and the API Access Connection option must be selected in the Connection Features field.

Hereby is a (redacted) example of how the JSON key file looks like:

{
  "type": "service_account",
  "project_id": "insert_project_id",
  "private_key_id": "insert_private_key_id",
  "private_key": "insert_private_key",
  "client_email": "insert_client_email",
  "client_id": "insert_client_id",
  "auth_uri": "https://accounts.google.com/o/oauth2/auth",
  "token_uri": "https://oauth2.googleapis.com/token",
  "auth_provider_x509_cert_url": "https://www.googleapis.com/oauth2/v1/certs",
  "client_x509_cert_url": "insert_url",
  "universe_domain": "googleapis.com"
}

To successfully set up a Service Account connection in ADvendio for Google Ad Manager, ensure that the following fields are present in the ADMANAGER connection:

Extended Token field
API Access Connection field in the Connection Features menu

If these fields are absent, follow the steps below to complete the configuration.

Step 1: Add the Extended Token Field

Navigate to Setup > Object Manager > Connection
In the Connection object, click on Page Layouts.
Select Ad Manager.
Under Fields, add the Extended Token field to the layout.
Click Save.
To ensure the layout is assigned to the correct record type:
- Click on Page Layout Assignment.
  Verify that the Ad Manager profile is assigned to the profile used to display the newly added fields.

Step 2: Add the API Access Connection Value to the Connection Features Menu

In the Connection object, navigate to Fields and Relationships.
Locate and click on Connection Feature.
Add a new field.
Name the new field API Access Connection.
Click Save.

Final Configuration Check

After completing these steps, your configured connection should look like this, with the fully encrypted JSON file once it’s pasted in the Extended token field.
Note that the Network ID field is still needed to point to the desired GAM profile, while on the other hand, the Additional Password field is not relevant in this process.