Create Custom Audience - Markifact

Create Meta customer-list containers, website audiences, or engagement audiences, including multiple videos and native rules. Customer records require a separate upload. FB_EVENT and MULTI_DATA audiences can only be created in Ads Manager, not through the API.


App	Meta Ads
Operation ID	`meta_create_custom_audience`
Type	Action
Connection	`meta_ads` (required)
Credits per run	1
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 audience
`description`	string	No	-	Optional audience description
`audience_type`	string or SelectableOption	Yes	-	Audience type to create. Use CUSTOMER_LIST for an empty customer-file audience container (upload users separately). Use WEBSITE for Meta Pixel retargeting such as URL visitors or pixel events. Use ENGAGEMENT for Instagram profile, Facebook Page, video, or lead form engagement; use the source/type inputs or supply an advanced rule. FB_EVENT and MULTI_DATA subtypes cannot be created through Meta’s API.
`customer_file_source`	string or SelectableOption	No	`USER_PROVIDED_ONLY`	Required for CUSTOMER_LIST audiences. Describes the source of the customer data.
`pixel_id`	string	No	-	Required for WEBSITE audiences when website_rule_type is URL_CONTAINS or EVENT. Numeric Meta Pixel ID used by the backend to build event_sources inside rule. For CUSTOM_RULE, include event_sources inside rule instead.
`retention_days`	integer	No	`30`	Website audience lookback window in days, 1-180. Used by URL_CONTAINS and EVENT to build retention_seconds inside rule. For CUSTOM_RULE, include retention_seconds inside rule instead.
`prefill`	boolean	No	`True`	For WEBSITE or ENGAGEMENT audiences, ask Meta to include past matching activity when the source supports it.
`website_rule_type`	string or SelectableOption	No	-	Required for WEBSITE audiences. Use URL_CONTAINS for visitors to pages whose URL contains a string. Use EVENT for people who fired one exact Meta Pixel event. Use CUSTOM_RULE only for advanced Meta website rule shapes that cannot be expressed by url_contains or event_name.
`url_contains`	string	No	-	Required when website_rule_type=URL_CONTAINS. URL substring matched with Meta’s case-insensitive contains operator. Examples: ‘/pricing’, ‘/checkout’, ‘example.com/blog’. Backend builds a VISITORS_BY_URL rule with event=PageView plus this URL filter. Do not put a pixel event name here.
`event_name`	string	No	-	Required when website_rule_type=EVENT. Exact Meta Pixel event name fired on the website, not an audience name or goal. Common standard events: PageView, ViewContent, AddToCart, InitiateCheckout, Lead, Purchase. Custom event names are allowed if the pixel sends that exact name.
`rule`	array of object or object or string	No	-	Advanced native Meta rule as an object, array, or JSON string. Required for WEBSITE with website_rule_type=CUSTOM_RULE; optional for ENGAGEMENT, where it replaces the simple source/type inputs. Website and non-video engagement use an inclusions/exclusions object with rules containing event_sources, retention_seconds and filter. Example: {“inclusions”:{“operator”:“or”,“rules”:[{“event_sources”:[{“type”:“page”,“id”:“<PAGE_ID>”}],“retention_seconds”:2592000,“filter”:{“operator”:“and”,“filters”:[{“field”:“event”,“operator”:“eq”,“value”:“page_engaged”}]}}]}}. Video rules use an array, e.g. [{“object_id”:“<VIDEO_A>”,“event_name”:“video_view_25_percent”},{“object_id”:“<VIDEO_B>”,“event_name”:“video_watched”}], with engagement_retention_days. For WEBSITE, use type=pixel and the pixel ID; URL rules use template=VISITORS_BY_URL, event=PageView plus a nested URL filter group. Pixel event-only rules use a direct event filter. Prefer url_contains or event_name for simple website audiences; old flat URL shorthand is unsupported. Nested rules, exclusions and source IDs are preserved. Meta validates source access and rule compatibility. FB_EVENT and MULTI_DATA audiences are Ads Manager-only; a raw rule does not bypass that restriction.
`engagement_source_type`	string or SelectableOption	No	-	Required for ENGAGEMENT unless rule is supplied. Source type for the Meta event source: INSTAGRAM_PROFILE, FACEBOOK_PAGE, VIDEO, or LEAD_FORM.
`engagement_source_id`	string or array of string	No	-	Required for ENGAGEMENT unless rule is supplied. One ID, a list of IDs, or comma-separated IDs of the selected source type: Instagram business profile ID, Facebook Page ID, video ID, or lead form ID.
`engagement_type`	string or SelectableOption	No	-	Required for ENGAGEMENT unless rule is supplied. Allowed by source: INSTAGRAM_PROFILE supports ANY_ENGAGEMENT, PROFILE_VISIT, POST_OR_AD_ENGAGEMENT, MESSAGE, SAVE; FACEBOOK_PAGE supports ANY_ENGAGEMENT, PAGE_VISIT, POST_OR_AD_ENGAGEMENT, MESSAGE, SAVE; VIDEO supports WATCHED_3_SECONDS, WATCHED_10_SECONDS, WATCHED_15_SECONDS, WATCHED_25_PERCENT, WATCHED_50_PERCENT, WATCHED_75_PERCENT, WATCHED_95_PERCENT; LEAD_FORM supports OPENED, OPENED_NOT_SUBMITTED, SUBMITTED.
`engagement_retention_days`	integer	No	`365`	Engagement lookback in days; also used for native video rule arrays. Native rule objects carry their own retention_seconds. LEAD_FORM is capped at 90 days by Meta; higher values are reduced to 90.

SelectableOption

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

Output

Type: Dict Returns created custom audience id and name. Fields: audience_id, name