Custom audiences (customer file and website)

맞춤 타겟 (고객 파일·웹사이트)

Upload customer details or site visits as hashes and Meta matches them to its users to build an ad audience.

Also known as: Custom Audiences고객 목록 타겟customer list audience
···

A custom audience is like handing over your regulars list in a sealed envelope. Meta compares your envelope (hashes) with its own and shows ads only to the overlap.

A customer file audience is built from emails, phone numbers, names, birthdates, advertising IDs and similar details, shared in hashed form. You create an empty audience with subtype=CUSTOM and a customer_file_source, then post the list to the /users endpoint. customer_file_source declares how the data was collected: USER_PROVIDED_ONLY, PARTNER_PROVIDED_ONLY, or BOTH_USER_AND_PARTNER_PROVIDED. Upload at most 10,000 records per request; the audience itself can hold an unlimited number, and changes usually take up to 24 hours.

If you already send events through the Conversions API, you can create a website custom audience without more uploads. Starting September 2, 2025, restrictions are being rolled out in phases: audiences that suggest health conditions or financial status are flagged and prevented from running campaigns, and customer file audiences unused in active ad sets for over two years are flagged for deletion.

Names and descriptions can be reviewed too, so avoid labels that assert a person's condition, such as a "diabetes list".

When to use

Use it to exclude existing customers, nudge returning visitors, or seed a lookalike audience.

Open as page ↗

Suggest an entry

Tell us about a term, effect or component that’s missing. We read every suggestion.