meta_ads_conversions_send
Send batch conversion events to Meta Conversions API for attribution. Supports standard and custom events with user data hashing. Returns Meta response including events_received and warnings.
Instructions
Sends a batch of arbitrary conversion events to the Meta Conversions API. Returns Meta's response including events_received and messages (warnings for missing fields). Mutating on Meta's side — events become part of the pixel's attribution stream. For common event types prefer the dedicated meta_ads_conversions_send_purchase or send_lead helpers, which enforce required fields and fewer mistakes. For other event names (AddToCart, InitiateCheckout, CompleteRegistration, custom events) use this generic tool.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| account_id | No | Meta Ads account ID in the format 'act_XXXXXXXXXX' (e.g. 'act_1234567890'). Optional — falls back to META_ADS_ACCOUNT_ID from the configured credentials. The leading 'act_' prefix is required. | |
| pixel_id | Yes | Meta Pixel ID the event is attributed to. Find via meta_ads_pixels_list. CAPI events flow into the same pixel as browser events; dedupe happens on event_id if one is supplied in user_data / custom_data. | |
| events | Yes | Event payloads to send. Meta batches are typically ≤1000 events per call. | |
| test_event_code | No | Meta Events Manager test_event_code. When set, the event is routed to the test event stream visible in Events Manager instead of production reporting. Use for validation; drop the field once verified. Get the code from Events Manager → Test Events tab. |