Export Conversions to Google Ads
Send attributed conversions from Vendo to a Google Ads conversion action, so that Google Ads can optimize your campaigns.
Last reviewed September 15, 2026
This guide shows how to send conversions from Vendo to Google Ads. Google Ads uses the conversions to measure and optimize your campaigns.
How It Works
- The source event that you select counts as a conversion, such as a purchase.
- Vendo applies your attribution model to connect each conversion to a Google Ads click.
- Vendo sends each conversion to your conversion action through the Google Ads API.
Vendo matches a conversion to a click with the gclid click ID. It can also send hashed customer data, such as email and phone, to improve the match.
Before You Start
- A Google Ads App connected in Vendo. Vendo uses the sign-in of this App to send conversions. You do not need an access token.
- A Source that records the event that you want to count as a conversion.
- A website that keeps the
gclidparameter from the landing page URL.
https://yoursite.com/product?gclid=abc123def456Step 1: Get the Conversion ID from Google Ads
Create a conversion action for imported conversions:
- Sign in to your Google Ads account .
- Click the Goals icon.
- Go to Conversions > Summary.
- Click + to create a conversion action.
- Under Select what you want to import, select “CRM, files, or other data sources”.
- Select “Track conversions from clicks”.
- Under Data source, select “Skip this step and set up a data source later”.
- Enter a conversion name and a category, such as “Purchase”.
- Click Done.
Find the Conversion ID:
- Open the conversion action that you created.
- Copy the number in the
ctIdparameter of the page URL.
For example, in https://ads.google.com/aw/conversions/detail?ctId=1234567890, the Conversion ID is 1234567890.
Note: A new conversion action accepts imports only after about 6 hours. For more information, see Google’s support article .
Step 2: Add the Destination
- In Vendo, go to Data > Destinations.
- Click Add Destination.
- Select Google Ads as the destination.
- Select the Source that records your conversion event.
Step 3: Configure the Conversion
Caution: Do not select the Participation attribution model for this export. Participation gives full credit to each touchpoint. Google Ads then receives more than one conversion for each purchase, and its bidding data is wrong.
The form shows these settings in this order:
| Setting | What it does | Default |
|---|---|---|
| Conversion Count | Every sends each conversion. Use it for purchases. Once sends only the first conversion for each customer. Use it for leads. | Every |
| Deduplication Window | Shown for Every only. Vendo ignores a repeat conversion from the same customer inside this window: 4 hours, 1 day, 3 days, 1 week or 30 days. | 4 hours |
| Attribution Model | How Vendo gives credit for a conversion: Last Click, First Click, Linear, Time Decay, U-Shaped or Participation. | Last Click |
| Lookback Window | How many days of conversions each export reads again: 1, 7, 14 or 28 days. | 7 days |
| Conversion Matching | Identified Conversions sends only conversions with a gclid. Send All Conversions also sends conversions without a click ID, matched with hashed customer data. | Identified Conversions |
| Conversion ID | The Conversion ID from Step 1. Required. | None |
| Conversion Event | The source event that counts as this conversion. Select one event for each conversion action. If you leave it empty, Vendo can send every conversion event. | None |
| Conversion Mapping | Connects Google Ads fields to properties on the source event. Email and phone come from identity resolution unless you map them. | Identity resolution |
| Dynamic Value Assignment | Sends a value from a prediction model in place of the event value. If a customer has no prediction, Vendo sends the event value. | Off |
For more information about each model, see Attribution Models.
Note: Google Ads can match on email, phone, name and address through Enhanced Conversions for Leads. Send All Conversions needs Enhanced Conversions turned on for the conversion action in Google Ads.
Step 4: Check the Export
Caution: The test sends a real event to the live Google Ads API. Use a test row, not a real customer conversion, if you can.
- On the Destination page, click Test.
- Select a row from the source table.
- Click Send Test Event.
- Click Sync Now to start an export.
- Open the Conversion Log tab.
- Make sure that your conversions show the Sent status.
- If a row shows Failed, open the Logs tab to read the error.
- After Google Ads processes the upload, find the conversions in your conversion action.
The Conversion Log shows the time, the user, the event, the source, the match type, the value and the status of each conversion.
What Vendo Sends
| Field | Value |
|---|---|
conversionAction | The conversion action with your Conversion ID |
conversionDateTime | The conversion time, in the format yyyy-MM-dd HH:mm:ss+HH:mm |
conversionValue | The attributed conversion value |
currencyCode | The currency of the conversion |
orderId | A stable event ID, so that Google Ads does not count it twice |
gclid | The Google click ID, when the conversion has one |
userIdentifiers | Hashed email, phone and address, when you select them |
Vendo does not send a conversion that has no gclid and no selected customer data. Google Ads cannot match that conversion.
Troubleshooting
- No conversions in the Conversion Log: make sure that your website keeps the
gclid. Also make sure that the Conversion Event is correct. - Conversion action not found: make sure that the Conversion ID is the
ctIdnumber from Step 1. - Uploads fail for a new conversion action: wait about 6 hours after you create the action.
- Authentication errors: open the Google Ads App in Vendo. If it shows Reconnect Required, connect it again.