meta_ads_conversions_send_purchase
Sends a single Purchase event via Meta Conversions API. Requires purchase amount, currency, and hashed user identifiers for attribution.
Instructions
Sends a single Purchase event via the Meta Conversions API — the most common CAPI use case. Returns Meta's events_received acknowledgement. Mutating on Meta's side. Required fields model a typical purchase: amount, currency, and hashed user identifiers. For other event types use meta_ads_conversions_send_lead (leads) or the generic meta_ads_conversions_send (AddToCart / custom events / batching multiple events).
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| value | Yes | Purchase amount in the specified currency. Decimal for currencies with minor units (USD 9.99); integer is fine for JPY. | |
| currency | Yes | ISO 4217 currency code (USD, JPY, EUR, GBP). Must match the ad account's reporting currency or be one that Meta can convert. | |
| 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. | |
| user_data | Yes | User identifying fields for attribution. Supported keys: em (email), ph (phone), fn (first_name), ln (last_name), zp (zip), ct (city), st (state), country, external_id, client_ip_address, client_user_agent, fbc (click ID), fbp (browser ID). mureo hashes em / ph / fn / ln / zp / ct / st / country / external_id with SHA-256 before sending — pass raw PII; do not pre-hash. | |
| 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. | |
| event_time | Yes | UNIX timestamp (seconds) of the purchase. Must be within the last 7 days. | |
| content_ids | No | Product IDs associated with the purchase — catalog retailer_ids for DPA attribution. Optional but recommended when a catalog is in use. | |
| 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. | |
| event_source_url | No | Fully-qualified URL where the event occurred. Required by Meta for action_source='website' events; recommended for any browser-triggered CAPI event to improve attribution match rate. |