Skip to main content

Google Ads Integration

Google Ads

Configure conversion forwarding to Google Ads using gads/google_ads provider aliases.

Audience: Performance marketing teams optimizing paid search and shopping conversions.

Critical: Preferred provider key is gads; google_ads alias is also supported for compatibility.

Who This Page Is For

Use this page when you need to forward conversion events to Google Ads and maintain a stable mapping/filter contract.

Quick Start (2-5 Minutes)

1

Configure provider

Set conversion ID/label and optional value-based option.

PUT /api/v1/sites/:siteId/integrations/gads
2

Map high-value events

Map purchase and add_to_cart equivalents for campaign optimization.

{ "eventMapping": { "purchase": "purchase", "add_to_cart": "add_to_cart" } }
3

Apply optional filters

Forward only qualifying events based on payload conditions.

{ "eventFilters": { "purchase": { "enabled": true, "conditions": [{ "field": "order.total", "operator": "gte", "value": 1 }] } } }
4

Test integration

Run connectivity test on provider route.

POST /api/v1/sites/:siteId/integrations/gads/test
5

Inspect logs

Diagnose failed sends and payload issues.

GET /api/v1/sites/:siteId/integrations/gads/logs?limit=50

Google Ads config example

{
"enabled": true,
"config": {
  "conversionId": "AW-123456789",
  "conversionLabel": "purchase_label",
  "valueBased": true
},
"eventMapping": {
  "purchase": "purchase"
},
"testMode": false
}

Required Fields / Minimum Payload

FieldRequiredTypeUsed by eventsDescription
providerRequiredgads or google_adsProvider routeIntegration provider selector.
config.conversionIdRequiredstringGoogle Ads update payloadGoogle Ads conversion ID.
config.conversionLabelRequiredstringGoogle Ads update payloadConversion label for target action.
config.valueBasedOptionalbooleanGoogle Ads update payloadUse event/order value in conversion sends.
eventMappingOptionalRecord<string,string>Google Ads update payloadCanonical event mapping table.

Currency Behavior

  • Google Ads conversion currency is resolved with fallback order: event -> order -> site -> EUR.
  • Provider forwarding does not force USD.
  • If value-based conversions are enabled, ensure currency and value come from the same source payload.

Event or Endpoint Decision Matrix

ScenarioUse ThisWhy
Preferred production setupPUT /integrations/gadsCanonical provider key for clarity.
Compatibility with legacy toolingPUT /integrations/google_adsAlias supported for backward compatibility.
Validate credentials and send pipelinePOST /integrations/gads/testPrevents silent launch failures.
Review failure diagnosticsGET /integrations/gads/logsOperational visibility into send outcomes.
Need provider defaultsGET /integrations/gads/mappingsReference starting mapping set.

Common Errors and Fixes

Test endpoint fails for Google Ads

Cause: Invalid conversion ID/label pair.

Fix: Verify values in Google Ads account and re-test.

No value passed for conversions

Cause: valueBased disabled or purchase payload missing totals.

Fix: Enable valueBased and ensure purchase/order totals are present.

Events filtered unexpectedly

Cause: eventFilters conditions too restrictive.

Fix: Audit conditions and compare with actual payload shape.

Events in logs but absent downstream

Cause: testMode enabled or downstream account policy issue.

Fix: Disable testMode and verify provider account constraints.

Production Checklist

  • Canonical provider key (gads) is used in production automation.Required
  • conversionId and conversionLabel are validated with test endpoint.Required
  • purchase mapping is explicitly configured.Required
  • valueBased behavior is aligned with campaign measurement strategy.Required
  • Delivery logs are reviewed after each major release.Required

Next Steps