Skip to main content

Prerequisites

Before setting up the Google Ads integration, ensure you have:

Getting Your Google Ads Credentials

1. Customer ID

1

Access Google Ads

Log in to your Google Ads account
2

Find Customer ID

Your Customer ID is displayed in the top right corner of Google Ads. It’s a 10-digit number without dashes (e.g., 1234567890)
3

Copy Customer ID

Copy this value for the integration configuration

2. Developer Token

1

Access API Center

In Google Ads, go to Tools & Settings → API Center
2

Request Access

If you don’t have a developer token, request access to the Google Ads API
3

Get Developer Token

Once approved, your developer token will be displayed in the API Center
4

Copy Token

Copy the developer token securely - you’ll need it for the integration
Developer token approval can take several days. Make sure to request access well in advance.

3. OAuth 2.0 Credentials

1

Access Google Cloud Console

Go to Google Cloud Console and select or create a project
2

Enable Google Ads API

Navigate to APIs & Services → Library and enable the Google Ads API
3

Create OAuth Consent Screen

Configure the OAuth consent screen with your app information
4

Create OAuth Credentials

Go to APIs & Services → Credentials and create OAuth 2.0 Client ID
5

Get Client ID and Secret

Copy the Client ID and Client Secret for the integration

4. Refresh Token

1

Authorize Application

Use the OAuth 2.0 flow to authorize your application to access Google Ads
2

Get Refresh Token

After authorization, you’ll receive a refresh token. Save this securely
3

Verify Access

Ensure the refresh token has access to the Google Ads account you want to track conversions for

5. Conversion Action ID

1

Access Conversions

In Google Ads, go to Tools & Settings → Conversions
2

Create or Select Conversion

Create a new conversion action or select an existing one
3

Get Conversion Action ID

The Conversion Action ID is displayed in the conversion action details. Copy this value

Configuration Steps

Step 1: Access Integration Settings

1

Navigate to CDP

Go to your Masivo dashboard and select the CDP section
2

Open Integrations

Click on “Integrations” in the CDP menu
3

Add New Integration

Click “Add Integration” and select “Google Ads” from the catalog

Step 2: Configure Basic Settings

Required Fields

Enter your Google Ads Customer ID (10 digits, no dashes). This identifies your Google Ads account.
Enter your Google Ads API Developer Token from the API Center.
Enter your OAuth 2.0 Client ID from Google Cloud Console (format: xxxxxx.apps.googleusercontent.com).
Enter your OAuth 2.0 Client Secret from Google Cloud Console (format: GOCSPX-…).
Enter your OAuth 2.0 Refresh Token obtained after authorizing the application.
Enter the Conversion Action ID from Google Ads where conversions will be tracked.

Step 3: Configure Conversion Tracking Options

Conversion Tracking

Enable this option to send custom events to Google Ads for conversion tracking. Events will be mapped to your conversion action.
Enable this option to send purchase events with revenue data to Google Ads for ROAS (Return on Ad Spend) tracking.

Required API Permissions

Google Ads API Permissions

Your Google Ads account must have API access enabled. This is typically enabled by default for most accounts.
The OAuth credentials must have permission to upload conversions to the specified conversion action.
Ensure the OAuth refresh token has access to the Google Ads account specified by the Customer ID.

Conversion Tracking Process

1

Event Collection

Customer conversions and purchases are collected in Masivo through various touchpoints
2

Conversion Mapping

Events are mapped to your Google Ads conversion action and enhanced with customer data
3

Data Processing

Customer data is processed and formatted for Google Ads Conversion Upload API
4

Conversion Upload

Conversions are sent to Google Ads via Conversion Upload API for campaign optimization

Enhanced Conversions

Enhanced Conversion Data

Masivo automatically includes hashed customer data (email, phone, address) for improved conversion matching accuracy
All PII data is automatically hashed before sending to Google Ads to maintain privacy compliance
Enhanced conversions improve conversion matching accuracy, especially for cross-device conversions

Monitoring and Troubleshooting

Health Monitoring

1

Conversion Upload

Monitor conversion upload success rates in Google Ads conversion reports
2

Data Quality

Check for data validation errors and missing fields in Google Ads
3

API Errors

Review error logs and failed API requests in Masivo integration logs
4

Token Refresh

Monitor OAuth token expiration and refresh as needed

Common Issues

1

Check Token Validity

Verify the refresh token is still valid and hasn’t been revoked
2

Verify Permissions

Ensure the OAuth credentials have the required permissions
3

Token Refresh

If the token has expired, re-authorize the application to get a new refresh token
1

Verify Format

Ensure the Customer ID is exactly 10 digits without dashes
2

Check Account Access

Verify the OAuth token has access to the specified Customer ID
3

Account Status

Ensure the Google Ads account is active and not suspended
1

Verify Conversion Action

Ensure the Conversion Action ID exists and is active in Google Ads
2

Check Permissions

Verify the OAuth token has permission to upload conversions to this action
3

Conversion Type

Ensure the conversion action is configured to accept API uploads
1

Check Approval Status

Verify your developer token is approved in Google Ads API Center
2

Token Format

Ensure the developer token is entered correctly without extra spaces
3

API Access

Verify API access is enabled for your Google Ads account