Google Customer Match

Built by John Rippy | johnrippy.link

🏆 2025 Zapier Automation Hero of the Year — Project Phoenix: A 95-step AI sales pipeline cutting development time by 50%. Read more →

Google Ads Audiences - Upload Customer Lists with Auto-Hashing

Create and manage Google Ads Customer Match audiences via the Google Ads API. Upload customer lists with automatic SHA256 hashing, create similar audiences, and upload offline conversions.

Features

Customer List Management

• create_customer_list - Create a new customer match list
• get_customer_list - Get details of a specific list
• list_customer_lists - List all customer match lists
• update_customer_list - Update list name/description
• delete_customer_list - Delete a customer list

User Management

• add_users - Add users to a list (auto-hashes PII)
• remove_users - Remove users from a list

Advanced Features

• create_similar_audience - Create similar audience from source list
• get_audience_insights - Get audience size and status
• upload_offline_conversions - Upload offline conversion data

Authentication

Requires Google Ads API credentials:

• Developer Token - From Google Ads API Center
• OAuth 2.0 Client ID/Secret - From Google Cloud Console
• Refresh Token - Generated via OAuth flow

Setup Steps

1. Create a Google Cloud project
2. Enable the Google Ads API
3. Create OAuth 2.0 credentials (Desktop app)
4. Get a developer token from Google Ads API Center
5. Generate refresh token via OAuth consent flow

User Data Format

Contact Info Upload

[
  {
    "email": "john@example.com",
    "phone": "+15551234567",
    "firstName": "John",
    "lastName": "Doe",
    "countryCode": "US",
    "postalCode": "10001"
  }
]

Automatic Hashing

The actor automatically:

1. Normalizes data (lowercase, trim whitespace)
2. Formats phone numbers (E.164)
3. SHA256 hashes all PII fields

If your data is already hashed, set isAlreadyHashed: true.

Field Requirements

Field	Format	Required
email	Lowercase, trimmed	Recommended
phone	E.164 with country code	Optional
firstName	Lowercase, trimmed	Optional
lastName	Lowercase, trimmed	Optional
countryCode	2-letter ISO code	Optional
postalCode	No spaces	Optional

Consent Requirements

Google requires consent signals for EU users. Provide consent JSON:

{
  "ad_user_data": "GRANTED",
  "ad_personalization": "GRANTED"
}

Values: GRANTED, DENIED, or UNSPECIFIED

Use Cases

Build Remarketing List

1. Export customer emails from CRM
2. Use add_users to upload to Google Ads
3. Create campaigns targeting the list

Create Similar Audience

1. Build list of best customers
2. Use create_similar_audience
3. Reach new users similar to your customers

Track Offline Conversions

1. Collect gclid from ad clicks
2. Record offline purchases/signups
3. Use upload_offline_conversions to attribute

Offline Conversions Format

[
  {
    "gclid": "EAIaIQobChMI...",
    "conversionAction": "customers/123/conversionActions/456",
    "conversionDateTime": "2024-01-20 14:30:00-05:00",
    "conversionValue": 99.99,
    "currencyCode": "USD"
  }
]

Rate Limits

• 10,000 operations per day per customer
• 10MB per upload request
• Recommended batch size: 100,000 users per job

Output Format

Customer List

{
  "resourceName": "customers/123/userLists/456",
  "id": "456",
  "name": "High Value Customers",
  "description": "Customers with LTV > $500",
  "membershipStatus": "OPEN",
  "sizeForSearch": 15000,
  "sizeForDisplay": 14500,
  "eligibleForSearch": true,
  "eligibleForDisplay": true
}

Upload Response

{
  "uploadedUserIdentifierCount": 1000,
  "matchedUserCount": 850,
  "failedUserIdentifierCount": 5
}

Pricing

$0.01 per query (all tasks)

Compliance Notes

• Obtain proper consent before uploading user data
• Include consent signals for EU users (GDPR)
• Data is hashed before transmission
• Google matches hashes against their user base
• Minimum 1,000 users for list to be usable