Google Ads Integration

Server-side conversion forwarding to Google Ads via the Google Ads Conversions API (opens in a new tab). Convultra authenticates with OAuth 2.0, maps your tracked events to Google Ads conversion actions, and delivers them directly to Google's servers — bypassing ad blockers, cookie restrictions, and iOS privacy limitations.

Requirements

Requirement	Details
Google Ads account	Standard Access or higher. Basic Access is read-only and cannot send conversions.
Conversion actions	At least one conversion action must exist in your Google Ads account before mapping.
Convultra SDK	Installed and tracking events on your site.
Enhanced Conversions (optional)	Requires your SDK calls to include user data (`email`, `phone`, etc.).

⚠️

Basic Access accounts cannot write conversion data. If you receive a permission error during testing, verify that the Google account you connected has Standard Access or higher in the Google Ads account settings.

Setup

Navigate to Integrations

Go to Dashboard → Integrations and click Connect on the Google Ads card.

Complete OAuth Flow

A Google sign-in window opens. Sign in with the Google account that has access to your Google Ads account. Convultra requests the following OAuth 2.0 scopes:

https://www.googleapis.com/auth/adwords — manage your Google Ads campaigns and conversions

OAuth tokens are stored encrypted and refresh automatically in the background. You will not need to re-authenticate unless you manually revoke Convultra's access from your Google account permissions (opens in a new tab).

💡

If you manage multiple Google accounts, make sure you select the one with access to the correct Google Ads account.

Select Google Ads Account

After authentication, Convultra lists all Google Ads accounts accessible to the authenticated user. Select the account you want to connect.

If you use a Manager Account (MCC), all child accounts will appear. You can connect multiple accounts — each is configured independently with its own conversion mapping and settings.

Map Conversion Actions

Map each Convultra event type to a Google Ads conversion action. This tells Convultra which conversion action to target when forwarding each event.

Convultra Event	Example Google Ads Conversion Action
`purchase`	Purchase / Sale
`lead`	Lead Form Submit
`signup`	Account Registration
`subscription`	Subscription Start
Custom events	Any custom conversion action

Events that are not mapped will not be forwarded. You can update mappings at any time without disconnecting.

⚠️

If no conversion actions appear in the dropdown, create at least one in Google Ads under Goals → Conversions → Summary first.

Enable Enhanced Conversions (Optional)

Toggle on Enhanced Conversions to send hashed customer data alongside conversions. This improves Google's ability to match conversions to ad clicks by up to 30%.

When enabled, Convultra sends SHA-256 hashed PII (email, phone, address) from your SDK calls to Google's Enhanced Conversions endpoint. You can provide user data in two ways:

Call Convultra.enhance() before your conversion call to set user data for the session:

Convultra.enhance({
  email: '[email protected]',
  phone: '+1234567890',
  address: {
    first_name: 'Jane',
    last_name: 'Doe',
    street: '123 Main St',
    city: 'Austin',
    region: 'TX',
    postal_code: '78701',
    country: 'US'
  }
});
 
Convultra.trackPurchase({
  value: 99.99,
  currency: 'USD',
  transaction_id: 'TXN-12345'
});

Convultra hashes all PII fields with SHA-256 before transmission. Raw values never leave the browser.

Test with Test Center

Click Send Test Conversion to verify the integration end-to-end. Convultra sends a test event to Google Ads and reports the result.

A green confirmation shows the conversion action name, timestamp, and Google's response. Your integration is ready for production.

Done

Conversions are now forwarded automatically. No further action required.

Click IDs

Convultra automatically captures and forwards Google Ads click IDs appended to your landing page URLs. Three click ID types are supported:

Click ID	Parameter	Description
gclid	`?gclid=...`	Standard Google Ads click identifier. Present on most ad clicks from desktop and Android.
gbraid	`?gbraid=...`	Privacy-compliant click ID for iOS/Safari. Used when Apple's App Tracking Transparency (ATT) restricts cross-site tracking.
wbraid	`?wbraid=...`	Web campaign click ID for iOS/Safari. Similar to gbraid but specifically for web-to-web conversion paths.

The SDK captures these automatically from the URL on page load. They are included in every conversion forwarded to Google Ads for accurate click-to-conversion attribution.

You do not need to parse or store click IDs yourself. Convultra handles capture, storage, and forwarding automatically.

Conversion Forwarding

When a tracked event fires and matches a mapped conversion action, Convultra forwards it to the Google Ads Conversions API with the following data:

{
  "conversionAction": "customers/1234567890/conversionActions/987654321",
  "conversionDateTime": "2025-01-15 14:30:00-06:00",
  "conversionValue": 99.99,
  "currencyCode": "USD",
  "orderId": "TXN-12345",
  "gclid": "CjwKCAjw...",
  "userIdentifiers": [
    {
      "hashedEmail": "a1b2c3d4e5f6..."
    }
  ]
}

Automatic retry — Failed deliveries are retried with exponential backoff.
Deduplication — Conversions are deduplicated by transaction_id / orderId to prevent double-counting.

Forward Logs

Navigate to the Forward Logs tab within the Google Ads integration to inspect every forwarded conversion:

Field	Description
Timestamp	When the conversion was forwarded
Conversion action	The mapped Google Ads conversion action name
Event data	Value, currency, transaction ID
Click ID	The gclid, gbraid, or wbraid used for attribution
Delivery status	`delivered`, `pending`, `failed`, or `retrying`
Error details	Google API error code and message (if any)

Rate Limits

The Google Ads Conversions API enforces rate limits. Convultra manages these automatically:

Requests are batched and throttled to stay within API limits.
If a rate limit is hit, delivery is queued and retried automatically.
Forward Logs will show a retrying status for rate-limited conversions.

Under normal usage, rate limits are unlikely to be reached. High-volume accounts (thousands of conversions per minute) may experience brief queuing.

Multi-Account Support

Connect multiple Google Ads accounts from the Integrations page. Each account has independent:

Conversion action mappings
Enhanced Conversions settings
Forward Logs
Test Center

This is useful for agencies or businesses that run campaigns across multiple Google Ads accounts.

Troubleshooting

Problem	Solution
No conversion actions in dropdown	Create conversion actions in Google Ads first (Goals → Conversions → Summary).
Permission denied errors	Verify the connected Google account has Standard Access or higher.
Conversions not appearing in Google Ads	Google Ads can take up to 24 hours to reflect imported conversions. Check Forward Logs for delivery confirmation.
OAuth token errors	Disconnect and reconnect the integration from Dashboard → Integrations.
Test conversion fails	Check Forward Logs for the specific error. Verify conversion mapping and account permissions.

Node.js SDK Meta (Facebook)