Data Destination - Facebook Custom Audience(Beta Feature)
- Print
- PDF
Data Destination - Facebook Custom Audience(Beta Feature)
- Print
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
summary
Help page on Facebook Custom Audiences.
From the transferred data (customer list), you can create custom audiences (targets to which your ads will be served) for Facebook ads.
Available in beta version
This Connector is available as a beta version.
Specifications are subject to change when the official version is released.
constraints
Transfer data hashing
All data transferred must be SHA-256 hashed , with the exception of the MADID column value.
Unhashed data is hashed in SHA-256 format during transfer.
Formatting of transfer data
Please transfer data based on the format listed in the "Guidelines" column of the table found in the Official Documentation - Multiple Key Hashing and Normalization.
Transferring data that is not based on the format may result in an error.
Maximum number of rows of transferred data
Due to the rate limitation of the Meta Marketing API used to transfer data to this Connector, the maximum number of rows of data (customer list) that can be transferred per hour is approximately 50 million rows.
If you want to transfer more than 50 million rows of data, divide the data into multiple ETL Jobs and run an ETL Job every hour.
Setting items
STEP1 Basic settings
Authorization Required for Connection Configuration
The required permissions vary depending on how Connection Configuration is created.
- When creating with a Facebook account
The Facebook account to be used must meet one of the following criteria- Is the owner of an advertising account associated with Meta Business Manager
- You have been granted administrative or advertiser access by the ad account owner.
- When created by a system user
The access token to be used must have the ads_management privilege.
For more information, see Facebook Ad Reporting, Conversions, Facebook Offline Conversions, and App Creation and Token Acquisition Procedures for Custom Audiences.
| item name | indispensable | Contents |
|---|---|---|
| Facebook Connection Configuration | ✓ | Select the previously registered Connection Configuration with the necessary permissions described above. |
| Ad Account ID | ✓ | Specify the ad account ID for which you want to create a custom audience. Please refer to the Meta Business Help Center " Finding Your Facebook Ad Account ID Number " for information on how to verify your ad account ID. |
| Custom Audience Name | ✓ | Specify custom audience names to create and update. If an existing custom audience is specified, the custom audience with the same name with the most recent update date will be updated. If you specify a custom audience that does not exist, a new custom audience will be created. |
STEP1 detailed settings
Click on Set Details to display the configuration items.
- Wait for custom audience creation and updating to complete
If the checkbox is checked
Continue the ETL Job until the creation and updating of the custom audience is complete.
If the ETL Job does not finish after an hour or more has passed after starting the ETL Job, please refer to the following remedies.If the checkbox is unchecked
Terminate the ETL Job without waiting for the creation and updating of the custom audience to complete.
ETL Job saves time because it does not wait for the custom audience creation and update to complete.
The status of creating and updating custom audiences can be viewed in the Meta Ads Manager.
column mapping
In order to create a custom audience from the data to be transferred, column names and types must be mapped on TROCCO.
Please do the mapping in STEP 2 Column Setting tab of ETL Configuration in TROCCO.
For more information on columns to map, see the official documentation - Multiple Key Hashing and Normalization. The "Key" column in the linked table corresponds to the column name.
About required columns
All columns are optional, but be sure to specify at least one column.
What to do if an ETL Job does not finish
ETL Configuration Jobs that wait until the Custom Audience has been created and updated will typically take about an hour to complete.
However, it may take more time due to the Meta Marketing API used.
If a line containing "code":414 or "code":300 is printed in the ETL Job execution log, the transfer job may be canceled.
Since the transfer of the customer list is complete, the creation and updating of custom audiences will not be interrupted.
The status of creating and updating custom audiences can be viewed in the Meta Ads Manager.
Was this article helpful?