Definition
action_source (Meta Conversions API)
A required Conversions API field that tells Meta where a conversion happened, such as website, phone_call, physical_store or system_generated.
Every event sent through the Meta Conversions API must carry an action_source. The allowed values are email, website, app, phone_call, chat, physical_store, system_generated, business_messaging and other. It is how Meta separates a purchase on the site from a deal closed by phone or a status change in a CRM.
The value changes what else Meta expects. Events with action_source set to website must also include event_source_url and client_user_agent, and Meta recommends sending client_ip_address with them. Non-web events only need action_source itself plus the standard fields.
The common mistake is labelling everything website. A lead qualified in the CRM two weeks after the form fill is not a website event, and sending it as one means sending a page URL and browser user agent that don't belong to it. Pick the value that describes where the action actually took place, and remember that event_time can be at most 7 days in the past: if one event in a request is older, the whole request fails.
Related terms
- Meta Conversions API (CAPI)
- Meta's server-to-server connection for sending web, app, offline and messaging events from your server or CRM directly to a Meta dataset.
- event_id and deduplication
- Meta drops a duplicate when a Pixel event and a Conversions API event share the same event name and event ID and arrive within 48 hours of each other.
- Event Match Quality (EMQ)
- Meta's score out of 10 for how well the customer information sent with your Conversions API web events can be matched to Meta accounts.
- Offline conversion import
- Uploading sales or qualified leads that happen off the website, such as by phone or in a CRM, to Google Ads so they are credited to the ad click.
Sources
Checked against the official documentation in November 2026. Platforms change; check the source for current details.