Export Conversions to Meta Ads
Send attributed conversions from Vendo to your Meta Pixel through the Conversions API, so that Meta can optimize your campaigns.
Last reviewed September 15, 2026
This guide shows how to send conversions from Vendo to Meta Ads. Meta 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 Meta ad click.
- Vendo sends each conversion to your Meta Pixel through the Conversions API.
Vendo matches a conversion to a click with the fbclid click ID. It can also send hashed customer data, such as email and phone, to improve the match.
Before You Start
- A Meta Ads App connected in Vendo, with permission to upload offline conversions. Vendo uses the sign-in of this App to send conversions. You do not need an access token.
- A Meta Pixel (dataset) in your Meta business account.
- A Source that records the event that you want to count as a conversion.
- A website that keeps the
fbclidparameter from the landing page URL.
https://yoursite.com/product?fbclid=abc123def456Step 1: Get the Pixel ID from Meta
- Log in to your Meta Business Manager account.
- In the left menu, click Data Sources.
- Select your Pixel (dataset).
- Copy its ID.
Step 2: Add the Destination
- In Vendo, go to Data > Destinations.
- Click Add Destination.
- Select Meta 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. Meta then receives more than one conversion for each purchase, and its optimization 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 click ID. Send All Conversions also sends conversions without a click ID, matched with hashed customer data. | Identified Conversions |
| Pixel ID | The Pixel ID from Step 1. Required. | None |
| Conversion Event (Pixel Settings) | The Meta standard event that Vendo sends: Purchase, Lead, Add to Cart, Complete Registration, Contact, Subscribe, View Content, Search, Add Payment Info or Initiate Checkout. Required. | None |
| Action Source | Where the conversion happened, such as Website, App, Phone Call or Physical Store. Vendo sends it with each event. Required. | Website |
| 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 Meta 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 |
The form has two settings named Conversion Event. The one in Pixel Settings is the Meta event. The other one is the event from your Source.
For more information about each model, see Attribution Models.
Note: The Meta Conversions API can match on email, phone, name and address.
Step 4: Check the Export
Caution: The test sends a real event to the live Meta 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 Meta processes the events, find them in Meta Events Manager.
The Conversion Log shows the time, the user, the event, the source, the match type, the value and the status of each conversion.
Use the Conversion in a Campaign
- In Meta Ads Manager, create a campaign and an ad set.
- Select Website Conversion as the campaign objective.
- Select the Conversions API event that Vendo sends.
What Vendo Sends
Vendo sends events to the /{pixel_id}/events endpoint of the Meta Graph API.
| Field | Value |
|---|---|
event_name | The Meta standard event from Pixel Settings |
event_time | The conversion time, as a Unix timestamp in seconds |
event_id | A stable event ID. Meta uses it to remove duplicates of Pixel events. |
action_source | The Action Source setting |
user_data.fbc | The click ID, made from the fbclid, when the conversion has one |
user_data.em, .ph | Hashed email and phone, when you select them |
custom_data.value | The attributed conversion value |
custom_data.currency | The currency of the conversion |
custom_data.order_id | The order ID, when the source event has one |
Vendo does not send a conversion that has no click ID and no selected customer data. Meta cannot match that conversion.
Troubleshooting
- No conversions in the Conversion Log: make sure that your website keeps the
fbclid. Also make sure that the source Conversion Event is correct. - Pixel not found: make sure that the Pixel ID is the ID of your Pixel (dataset) from Step 1.
- Authentication errors: open the Meta Ads App in Vendo. If it shows Reconnect Required, connect it again.