API Reference

Meta Ads / API Reference

meta_ads_send_server_event

Meta Ads tool. Send a server-side conversion event to Meta via the Conversions API (CAPI). Emails, phone numbers, first name, and last name in user_data are automatically SHA-256 hashed. Use event_id to deduplicate with browser pixel events (same event_id on both sides). Args: pixel_id: Meta Pixel ID (required). event_name: Event name: Purchase, Lead, ViewContent, AddToCart, CompleteRegistration, etc. (required). event_time: Unix timestamp of the event as a string, e.g. '1735689600' (required). user_data: JSON object with user info. Fields: email, phone, first_name, last_name, country, city, zip, client_ip_address, client_user_agent, fbc, fbp (required). pixel_access_token: Pixel-specific access token (different from ad account token) (required). event_source_url: The URL where the event occurred (for website events). custom_data: Optional JSON object with: value, currency, order_id, content_name, content_type, contents (array of {id, quantity}). test_event_code: Optional test event code from Meta Events Manager to verify the event. event_id: Unique ID for deduplication with browser pixel. Must match the event_id sent by the browser pixel for the same event. action_source: Where the event happened. One of: website, app, email, phone_call, chat, physical_store, system_generated, other. Default: website.

This is a write tool: it sends server event 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:

Send server event in my Meta Ads account for [pixel id], [event name], [event time].

It takes 5 required and 5 optional parameters.

Parameters

ParameterTypeRequiredDescription
pixel_idstringYesPixel Id
event_namestringYesEvent Name
event_timestringYesEvent Time
user_datastringYesUser Data
pixel_access_tokenstringYesPixel Access Token
event_source_urlstringNoEvent Source Url
custom_datastringNoCustom Data
test_event_codestringNoTest Event Code
event_idstringNoEvent Id
action_sourcestringNoAction Source

Related Meta Ads tools

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:

Start using MCP Ads