Connecting Google Ads

Connect Convultra to Google Ads and conversions are uploaded straight to Google’s servers through the Google Ads API. Google Ads forwarding and enhanced conversions are live. This gives Smart Bidding complete data, corrects under-reported ROAS, and recovers the 30 to 40% of conversions that the browser tag misses.

Why connect Google Ads

• Recover lost conversions. Ad blockers, cookie expiry and iOS restrictions silently drop conversions from Google’s tag. Convultra sends them server-side.
• Better Smart Bidding. When Google sees more of your real conversions, automated bidding optimizes on real data.
• Accurate ROAS. Reports reflect what actually happened.
• Enhanced conversions. Hashed customer data gives Google a second way to match a conversion when the click ID is gone.
• Spend sync. Convultra imports your Google Ads cost so the dashboard shows spend, blended ROAS and CPA next to conversions.

Requirements

Setup

1. Go to Integrations

In Convultra, open Integrations, find the Google Ads card and click Connect.

2. Sign in with Google

A Google sign-in window opens. Sign in with the account that has access to your Google Ads account. Convultra uses OAuth, so your password is never shared. It asks for three permissions:

• Google Ads, to read your accounts and upload conversions
• Data Manager, which Audience Sync needs to manage Customer Match lists
• Basic profile, so the dashboard can show which Google account is connected

Tokens are stored encrypted and refresh automatically. If you manage several Google accounts, sign in with the one that reaches the right Google Ads account.

3. Work through the setup wizard

Back in Convultra the card opens a four-step wizard: Account → Conversion action → Value and matching → Confirm. Each step saves as you complete it, and you can reopen the wizard from the card at any time.

Account. Convultra lists the Google Ads accounts your login can reach. Pick the one to connect. If you use a Manager Account (MCC), every child account appears, and you can connect more than one; each is configured independently. Selecting an account also starts spend sync.

Conversion action. Choose which Google Ads conversion action receives your conversions. If the list is empty, create at least one conversion action in Google Ads first under Goals → Conversions → Summary. Only the seven conversion types (purchase, lead, signup, subscription, download, contact, schedule) are forwarded; micro events and custom event names are not.

Value and matching. Decide where the conversion value comes from, and switch Enhanced conversions on to send SHA-256 hashed customer data (email, phone, name, address) with each conversion. Google uses it to match conversions that the click ID alone cannot. You can supply the data through the WordPress plugin, the SDK’s enhance() method, or auto-detection from your conversion payloads. See Enhanced conversions for the marketer’s view and Enhanced conversions in the SDK for code.

Confirm. Review the account, conversion action and matching settings, then confirm. Conversions are now forwarded automatically.

4. Send a test conversion

Click Send a test conversion on the card. It opens the Conversion Test Center, which sends a test event through the full pipeline to Google Ads and shows the result within a few seconds.

• Success: a confirmation with the conversion action name, timestamp and Google’s response.
• Failure: read the error. The usual causes are no conversion action chosen (reopen the wizard), insufficient permissions (the account needs Standard Access), or an expired token (disconnect and reconnect).

Click IDs

Convultra captures Google’s click IDs from your landing page URLs and includes them in every upload:

You never need to parse or store these yourself. See Click ID persistence.

What gets uploaded

When a tracked event matches a mapped conversion action, Convultra uploads it to the Google Ads API with data shaped like this:

{
  "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. A failed upload is tried again automatically, up to 3 attempts in total. After that it stays Failed until you retry it by hand from the Conversion delivery page.
• Deduplication. Conversions are deduplicated by orderId (or transaction_id) so nothing is double counted. See Deduplication.
• Retry window. Google Ads accepts a conversion up to 90 days after the click. Beyond that, a retry is refused.

Audiences

The same connection can take Audience Sync destinations: rule-based Customer Match lists that Convultra creates and keeps up to date. Connections made before Audience Sync shipped need a one-off reconnect so Google can grant the Data Manager permission; the New audience modal on the Audiences page shows Reconnect to enable audience sync when that applies.

Conversion delivery

Open Conversion delivery in the sidebar to inspect every upload. Each row is one attempt, with:

Filter by status, select rows and Retry selected, or Retry all failed. A conversion’s own drawer on the Conversions page links to its attempts here.

Rate limits

The Google Ads API enforces its own limits. Convultra batches and throttles uploads to stay inside them, queues and retries when a limit is hit, and shows retrying on the Conversion delivery page. Under normal volumes you will not notice; very high-volume accounts may see brief queuing.

Multiple accounts

Connect as many Google Ads accounts as you need from the Integrations page. Each has its own conversion action, enhanced conversions setting and test conversion. This suits agencies and businesses running several accounts.

Troubleshooting