- 07 Dec 2022
- Print
- DarkLight
- PDF
Data Destination - Facebook Conversions API
- Updated on 07 Dec 2022
- Print
- DarkLight
- PDF
This is a machine-translated version of the original Japanese article.
Please understand that some of the information contained on this page may be inaccurate.
summary
- This is the help page for setting up data transfer to the Facebook Conversions API.
- You can extract data from any source and send it to the Conversions API.
To match the Facebook Conversions API format, you need to map column names and types in trocco.
Transfer destination setting items
Item | input example | explanation |
---|---|---|
Facebook connection information | Select the connection information you created in the access token. | |
Business Account ID | 111111111(trocco) | You can get your business account ID from the page linked below. Link:https://business.facebook.com/settings/info |
Pixel ID | 242300000000(trocco) | Enter the Pixel ID that corresponds to your Facebook Business Events Manager. |
Column Mapping
You can send data to the Facebook Conversion API by mapping column names and types in the column definition in STEP2 of trocco.
Match the column names and types as shown in the table in the "Supplements" section below.
All of the following parameters in the Conversions API documentation are available (*except for data_processing_options):
https://developers.facebook.com/docs/marketing-api/conversions-api/parameters
Create a Facebook pixel
Add a new data source from Facebook Business Manager.
Checking the Transfer Results
Check the results of your event in Facebook Events Manager.
Even if the transfer is successful, the event may be played by Facebook's processing in cases such as missing parameters.
Make sure the numbers match.
supplement
Column mapping table
column name | typerequired | descriptioninput | examplecategory | ||
---|---|---|---|---|---|
action_source | string | YES | Source of conversion origin Enterable fields ・Website ・APP ・phone_call ・Chat ・physical_store ・system_generated ・Other | website | |
event_name | string | YES | Enterable fields ・Purchase ・Lead ・AddToCart etc https://developers.facebook.com/docs/facebook-pixel/reference#standard-events Conform to | Lead | |
event_time | timestamp | YES | Event occurrence time Please enter a value that is 7 days before the trocco transfer execution date and time. | 2020-01-01 00:00:00 +00:00 | |
em | string | YES※ | trocco@trocco.io | user_data | |
ph | string | YES※ | Phone | 080-0000-0000 | user_data |
ge | string | YES※ | Gender | f | user_data |
.db | string | YES※ | Date of Birth | 19971226 | user_data |
ln | string | YES※ | Last Name | Trocco | user_data |
fn | string | YES※ | First Name | Taro | user_data |
ct | string | YES※ | City | Tokyo | user_data |
st | string | YES※ | State | Meguro-ku | user_data |
zp | string | YES※ | Zip | 1234567 | user_data |
country | string | YES※ | Country | jp | user_data |
external_id | string | YES※ | External ID | user_data | |
client_ip_address | string | YES※ | Client IP address | user_data | |
client_user_agent | string | YES※ | Client user agent | user_data | |
fbc | string | YES※ | Click ID | user_data | |
fbp | string | YES※ | Browser ID | user_data | |
subscription_id | string | YES※ | Subscription ID | user_data | |
lead_id | string | YES※ | Lead ID | user_data | |
fb_login_id | string | YES※ | FB Login ID | user_data | |
custom_data | json | NO | You can pass custom data in JSON format. The items that can be set are as follows. https://developers.facebook.com/docs/marketing-api/conversions-api/parameters/custom-data | ||
event_source_url | string | Required if the action_source is a website | |||
opt_out | boolean | NO | |||
event_id | string | NO |
* At least one column of the user_data is required.
* Among the combinations of column mapping tables, if they contain only parameters consisting of one of the following or a subset of them, it is considered invalid.
- ct + country + st + zp + ge + client_user_agent
- db + client_user_agent
- fn + ge
- ln + ge