Loader Facebook Custom Audience
Facebook Custom Audience allows businesses to connect with users based on their demographics, interests, and behaviors. By creating personalized ad campaigns, businesses can deliver relevant messages to the right audience at the right time, maximizing engagement and conversions.
Business value in CDP
Using this destination loader in CDP, you can upload your customer data to create highly tailored ad campaigns. CDP users can take advantage of this feature by leveraging the rich customer insights and data stored within their CDP. By integrating their CDP with Facebook Custom Audiences, businesses can precisely target their existing customers, prospects, or specific segments. This level of targeting ensures that advertisements are relevant and resonate with the intended audience, resulting in higher engagement and conversion rates.
Difference between Facebook loaders
|FB Custom Audiences
|FB Anonymous Custom Audiences
|Criteria such as CDP, identifiable through name, email, or phone number
|Aggregated and anonymized data, based on FB client ID
Direct customer event data sent to Facebook.
The component is not intended for audience export but to enhance and enrich the direct connection between Meiro Events (web events) and FB
|Identification of Audience
|Identified through personal details (name, email, phone number)
|Not identified; retargeted based on FB client ID
|Not applicable; focuses on event tracking
|Level of Personalization
|Deeper personalization based on specific attributes and behaviors
|Broader targeting of segments with similar characteristics
|Primarily focused on event tracking
|Use Cases for CDP Users
|Flexible for providing personalized messages
|Useful for broader reach and exposure; less personalization
Complements Custom Audiences by providing accurate event tracking
|May utilize cookies or pixels for tracking
|Does not rely on cookies or pixels for tracking
|Bypasses the need for cookies or pixel-based tracking
Facebook Custom Audience provides a centralized platform for managing and optimizing your audience engagement across various channels within the Facebook/ Meta ecosystem.
- Instagram Ads: effortlessly extend your marketing reach to Instagram through this integration, enabling you to create, monitor, and optimize ad campaigns seamlessly.
- Messenger Ads: connect with your audience on a more personalized level through Messenger Ads, managing conversations and interactions efficiently within the Facebook Audience framework.
- WhatsApp Business: Seamlessly integrate WhatsApp Business to enhance customer communication, providing a direct channel for engagement and support.
Learn more: Explore additional integrations within the Facebook/ Meta.
Steps for setting up Facebook Custom Audience Loader
Follow this step-by-step guide to configure the component:
- The first step is to configure Meiro Events for Facebook Custom Audience. You can refer to this article for guidance.
- Next, set up the loader within Meiro Integration by following the instructions given in this article.
- Set up the loader as a destination in CDP. Read here.
- Continue with exporting your segmented customer profiles. Refer to this article.
Setting up the loader in MI
For setting Facebook Custom Audience as a destination within Meiro Integration, use the Facebook Audience loader component.
To use the Facebook loader, one needs to authorize the Facebook account. Authorization can be done in 2 ways:
- The user who has access to an Ad account in Facebook Business Manager and has access to Audiences clicks on the “Authorize” button in the same browser where one logged in to his Facebook Ad account.
- The authorization link can be copied by an analyst working in Meiro Integrations and sent for authorization to someone with the required level of access, who should open the link in the same browser where his Facebook Ad account is logged in.
Learn more: about Ad account permissions here.
Data In/ Data Out
It is required to have data in the bucket Data In in CSV format in
To load data properly, ensure that column names are in the correct format.
All column names must be present (even if left empty) in this order:
At least one of the identifier columns should be filled in:
Customer Audience has 2 steps: create the audience itself, then fill it with the right data.
When it fails in step 2, as, for example, data was structured in an invalid way (with other order of columns), the audience is still created but without the data.
Learn more: about column formatting please refer to the Facebook help website.
Learn more: about the folder structure here.
|Ad Account ID (required)
|Refers to the ID of the ad account. It is possible to add only one ID within one component. Ad account ID should start with “act_XXXX”.
Warning: It is essential to accept the terms of service to be able to export the custom audience for the ad account. You can accept the terms of service at
<AD_ACCOUNT_ID> with the ID of the ad account.
Remember: In the case where multiple ad accounts are present for a business account, you only need to accept the terms of service once for the business account for the export to work across all ad accounts that belong to that business account.
Learn more: custom audience terms of service here.
Learn more: about how to find an ad account ID please refer to this article.
Name of the newly formed audience in Facebook Ad. As input should be used as a reference to a workspace variable. The name of the workspace variable you choose should be the same value as the Meiro Integrations key when setting up parameters in Business Explorer for the Facebook destination.
Workspace variable name:
Meiro Integration Key in Business Explorer for Facebook Destination:
Description of the newly formed audience will be shown as additional information in the description of the Audience in the Facebook Ads account.
|Audience ID (optional)
Audience ID number in Facebook Ad account, unique for each Audience. If filled in, then the Facebook loader will update the existing Audience with this ID.
If one leaves this field empty, the component will create a new Audience.
The number of days to retain before the audience expires and is removed. It can be set up to 180 days. If left blank, the audience does not have an expiry date. It is usable only when a new audience is created.
This parameter defines the number of threads processing the input (one thread processes 10,000 records). The value must be >=1. By default is 1.
Warning: It is advised to leave the default value for
|Prehashed keys (optional)
If the checkbox is enabled, the loader will expect hashed values in the input CSV file. If there are unhashed values and the checkbox is checked, the loader will fail.