Meta Ads / API Reference
meta_ads_upload_enhanced_conversions
Meta Ads tool. Upload offline or enhanced conversion data with hashed PII for Meta matching. Used for offline purchase matching, CRM uploads, and enhanced conversions. PII fields (email, phone, fn, ln) are auto-hashed with SHA-256 before sending. Args: pixel_id: Meta Pixel (or dataset) ID (required). events: JSON array of conversion events. Each event supports: - event_name: PURCHASE, LEAD, COMPLETE_REGISTRATION, etc. (required) - event_time: Unix timestamp (required) - value: Order value as float - currency: ISO currency code, e.g. ILS, USD - order_id: Unique order/transaction ID (for deduplication) - email: Customer email (will be SHA-256 hashed) - phone: Customer phone with country code (will be hashed) - fn: First name (will be hashed) - ln: Last name (will be hashed) - external_id: Your internal customer ID (will be hashed) - country: Two-letter country code (will be hashed) - city: City (will be hashed) - zip: Postal code (will be hashed) Example: '[{"event_name":"PURCHASE","event_time":1700000000, "value":250.0,"currency":"ILS","order_id":"ORD-001", "email":"customer@example.com","phone":"+972501234567"}]' upload_tag: Optional label to identify this upload batch in reporting. account_id: Ad account ID. Leave blank for default.
This is a write tool: it uploads enhanced conversions in your Meta Ads account. Claude asks you to confirm before it runs.
Ask Claude
You do not call this tool yourself. Ask for the outcome and the client picks the tool:
Upload enhanced conversions in my Meta Ads account for [pixel id], [events].
It takes 2 required and 2 optional parameters.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
pixel_id | string | Yes | Pixel Id |
events | string | Yes | Events |
upload_tag | string | No | Upload Tag |
account_id | string | No | Account Id |
Related Meta Ads tools
meta_ads_upload_ad_videometa_ads_upload_customer_list_to_audiencemeta_ads_upload_image_file_bytes_to_metameta_ads_upload_image_to_metameta_ads_upload_product_feedmeta_ads_upload_video_file_bytes_to_meta
Before you can call it
This tool needs a connected Meta Ads account. The Meta Ads connect guide covers the OAuth flow and the permissions it asks for, and the quickstart gets a client talking to the server in about five minutes.
Workflows that use this
Rather than calling tools one at a time, these skills run a whole procedure against the same account: