Prerequisites
Before setting up the Google Ads integration, ensure you have:Getting Your Google Ads Credentials
1. Customer ID
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)
2. Developer Token
3. OAuth 2.0 Credentials
4. Refresh Token
5. Conversion Action ID
Configuration Steps
Step 1: Access Integration Settings
Step 2: Configure Basic Settings
Required Fields
Customer ID
Customer ID
Enter your Google Ads Customer ID (10 digits, no dashes). This identifies
your Google Ads account.
Developer Token
Developer Token
Enter your Google Ads API Developer Token from the API Center.
OAuth Client ID
OAuth Client ID
Enter your OAuth 2.0 Client ID from Google Cloud Console (format:
xxxxxx.apps.googleusercontent.com).
OAuth Client Secret
OAuth Client Secret
Enter your OAuth 2.0 Client Secret from Google Cloud Console (format:
GOCSPX-…).
OAuth Refresh Token
OAuth Refresh Token
Enter your OAuth 2.0 Refresh Token obtained after authorizing the
application.
Conversion Action ID
Conversion Action ID
Enter the Conversion Action ID from Google Ads where conversions will be
tracked.
Step 3: Configure Conversion Tracking Options
Conversion Tracking
Sync Events
Sync Events
Enable this option to send custom events to Google Ads for conversion
tracking. Events will be mapped to your conversion action.
Sync Purchases
Sync Purchases
Enable this option to send purchase events with revenue data to Google Ads
for ROAS (Return on Ad Spend) tracking.
Google Ads Configuration Details
Required API Permissions
Google Ads API Permissions
API Access
API Access
Your Google Ads account must have API access enabled. This is typically
enabled by default for most accounts.
Conversion Upload
Conversion Upload
The OAuth credentials must have permission to upload conversions to the
specified conversion action.
Account Access
Account Access
Ensure the OAuth refresh token has access to the Google Ads account
specified by the Customer ID.
Conversion Tracking Process
Event Collection
Customer conversions and purchases are collected in Masivo through various
touchpoints
Conversion Mapping
Events are mapped to your Google Ads conversion action and enhanced with
customer data
Enhanced Conversions
Enhanced Conversion Data
Customer Data
Customer Data
Masivo automatically includes hashed customer data (email, phone, address)
for improved conversion matching accuracy
Privacy Compliance
Privacy Compliance
All PII data is automatically hashed before sending to Google Ads to
maintain privacy compliance
Matching Accuracy
Matching Accuracy
Enhanced conversions improve conversion matching accuracy, especially for
cross-device conversions
Monitoring and Troubleshooting
Health Monitoring
Common Issues
OAuth Token Issues
OAuth Token Issues
Customer ID Issues
Customer ID Issues
Conversion Action Issues
Conversion Action Issues