Create Custom Conversion - Markifact

Creates a Meta custom conversion on an ad account, defined by a rule over pixel events or URLs (e.g. thank-you page visits), with a standard event category and optional default value. Use meta_list_account_pixels for event_source_id and meta_list_custom_conversions to see existing ones.


App	Meta Ads
Operation ID	`meta_create_custom_conversion`
Type	Action
Connection	`meta_ads` (required)
Credits per run	2
Agent / MCP tool	Yes
Requires approval	Yes (write operation)

Inputs

Field	Type	Required	Default	Description
`account`	DynamicAccount	Yes	-	Select Meta Ads account, ask the user for it if not provided
`name`	string	Yes	-	Name for the custom conversion
`description`	string	No	-	Optional description
`event_source_id`	string	No	-	Pixel ID or offline event set ID the conversion listens to, e.g. from meta_list_account_pixels. Required in practice for pixel-based conversions.
`rule`	object or string	No	-	Conversion rule sent to Meta as-is: JSON filtering on url or event with operators like i_contains, contains, eq, gt, lt, regex_match. Example (purchase page): {“and”: [{“event”: {“eq”: “PageView”}}, {“or”: [{“URL”: {“i_contains”: “thank-you”}}]}]}. Provide rule or advanced_rule to define when the conversion fires.
`advanced_rule`	object or string	No	-	Advanced ruleset supporting multiple event sources, sent to Meta as-is. Use rule for simple cases.
`custom_event_type`	string or SelectableOption	No	-	Standard event category the conversion is optimized as, e.g. PURCHASE, LEAD, OTHER
`action_source_type`	string or SelectableOption	No	-	Where the conversion happens, e.g. website, physical_store, phone_call
`default_conversion_value`	number	No	-	Default monetary value assigned to each conversion, in the account currency

SelectableOption

Field	Type	Required	Default	Description
`value`	string	Yes	-
`label`	string	Yes	-

Output

Type: Dict Returns the created custom conversion id and name. Fields: custom_conversion_id, name