Connection Setup

This workflow covers the initial connection between your Progrid instance and Google Ads, including OAuth2 authorization, credential configuration, and connection verification.

Important

You need a Google Ads account, a Google Cloud project with the Google Ads API enabled, and a developer token from the Google Ads API Center before proceeding.

Prerequisites

Before configuring the connection, gather the following credentials:

  • Developer token – Obtained from the Google Ads API Center in your Google Ads account

  • OAuth2 Client ID – Created in the Google Cloud Console under APIs & Services –> Credentials

  • OAuth2 Client Secret – Generated alongside the Client ID

  • Customer ID – Your Google Ads account number (10 digits, no dashes)

  • Login Customer ID (optional) – Required only if accessing through a Manager (MCC) account

Step 1: Open the configuration

  1. Navigate to Google Ads ‣ Configuration ‣ Settings.

  2. The configuration form opens. If this is the first time, a default record is created automatically.

Step 2: Enter API credentials

  1. In the Connection tab, fill in:

    • Developer Token – Your Google Ads API developer token

    • Client ID – The OAuth2 client ID from Google Cloud Console

    • Client Secret – The OAuth2 client secret

    • Customer ID – Your 10-digit Google Ads customer ID (no dashes)

  2. If you access Google Ads through a Manager (MCC) account, enter the MCC account ID in the Login Customer ID field.

Step 3: Authorize with Google

  1. Click the Connect to Google Ads button.

  2. A new browser window opens with the Google OAuth2 consent screen.

  3. Sign in with the Google account that has access to the Google Ads account.

  4. Grant the requested permissions.

  5. After authorization, you are redirected back to Progrid. The Refresh Token field is populated automatically.

Step 4: Test the connection

  1. Click Test Connection.

  2. If successful, the Account Name field populates with your Google Ads account name, and the Last Connection Test timestamp updates.

  3. The connection status indicator turns green.

Note

If the test fails, verify that your developer token is approved (not in test mode), the customer ID is correct, and the authorized Google account has access to the specified Google Ads account.

Step 5: Configure defaults

Switch to the Settings tab and configure:

  • Default Consent Status – Set to granted if your users have consented to ad tracking under GDPR

  • Default Ad Personalization Consent – Set to granted if users have consented to personalized ads (required for audience uploads)

  • Default Currency – The fallback currency for conversions (default: USD)

  • Batch Size – Number of conversions per upload batch (default: 500, max: 2000)

Step 6: Enable optional features

Switch to the Features tab:

  • Ad Performance Reporting – Check to pull campaign, ad group, and keyword metrics daily

  • Lead Form Import – Check to import lead form submissions hourly

    • Set the Default Stage where imported leads start

    • Set the Default Sales Team for lead assignment

    • Optionally set a UTM Source for tracking

  1. Click Save.

Next steps

See also

Troubleshooting