Skip to main content
When you finish, one Datalyr event uploads to a Google Ads conversion action and reports a terminal state.

Before you start

Create the conversion action as Import from clicks. A GA4, website, or call action accepts no API upload, and every conversion you send to it fails.

Connect Google Ads

1

Open Sources

Open Sources. Find the Google Ads card.
2

Authorize

Select connect. Sign in with the Google user. Approve every requested scope.
3

Pick the customer account

Choose the customer account, not the manager account. Select set as primary.
The card reads needs primary account until you finish step 3.

Create the rule

1

Open the editor

Open Conversions. Select manage rules. Select new rule.
2

Set the trigger

Fill rule name. Pick the trigger event. Pick Google as target platform.
3

Pick the conversion action

Pick the action under Google Conversion Action. Select next.
4

Map the value

Set value to dynamic. Pick the numeric path. Set currency. Select save.
The editor blocks a save when the action cannot receive API uploads. It also blocks any trigger event whose name contains refund or chargeback, because Google rejects negative conversion values.

Reference

Reconnect Google Ads to move a grandfathered connection onto the Data Manager API.

Request body

Click identifiers

We send exactly one, in this order: gclid, then gbraid, then wbraid. The attribution lookup window is 90 days.

userIdentifiers

We add the address identifier only when first name, last name, country, and postal code are all present. The Data Manager API accepts no city or state field.

Delivery gate

We upload only when the event carries a click ID, an email, or a phone number. Without all three, the delivery row reads failed with missing gclid/gbraid/wbraid and no enhanced conversion data available.

Status timeline

Google accepts the upload at once and validates it later, so a Datalyr row moves through two states. We poll 30 minutes after the upload. Google conversions are never retried through the dead-letter queue.

Verify

  1. Open Sources. Confirm the Google Ads card shows the customer ID you intended.
  2. Open Conversions. Select manage rules. Open your rule.
  3. Select send test event. The request carries validateOnly: true.
  4. Confirm the rule’s sent count went up by 1.
  5. Trigger one real event. Confirm its row reaches sent within 40 minutes.

When it does not work

Next