Forwarding - Facebook Conversion API
  • 17 Jul 2024
  • PDF

Forwarding - Facebook Conversion API

  • PDF

Article summary

summary

  • Help page for setting up data transfer to the Facebook Conversion API.
  • Data can be extracted from any transfer source and sent to the Conversion API.
    Column names and types must be mapped on TROCCO to match the format of the Facebook Conversion API.

forwarding destination setting item

(data) itemInput ExampleDescription.
Facebook Connection InformationSelect the connection information created by the access token.
Business Account ID111111111 (TROCCO)Business account IDs can be obtained from the page linked below.
Link: https://business.facebook.com/settings/info
image.png
Pixel ID242300000000 (TROCCO)Enter the Facebook Business Event Manager applicable Pixel ID.
image.png

column mapping

In the column definitions in STEP 2 of TROCCO, data can be sent to the Facebook Conversion API by mapping column names and types.
Match column names and types as shown in the table in the "Supplemental" section below.
All of the following parameters in the Conversion API documentation can be supported (*except for data_processing_options)
https://developers.facebook.com/docs/marketing-api/conversions-api/parameters

Creating a Facebook Pixel

Add a new data source from the Facebook Business Manager.

Confirmation of transfer results

Check the event results from the Facebook Event Manager.
Even if the transfer is successful, the event may be rejected by Facebook if the parameters are insufficient.
Make sure the number of cases matches.
image.png

supplement

Column Mapping Table

column nametype (e.g. of machine, goods, etc.)indispensableDescription.Input Examplecategory
action_sourcestringYESSource of conversion origin
inputtable item
. email
website
App.
phone_call
CHAT
Physical_store
system_generated
Other
website
event_namestringYESinputtable item
Purchase
Lead
AddToCart
(lessening the significance or value of the previous word) the likes of

https://developers.facebook.com/docs/facebook-pixel/reference#standard-events
conform to
Lead
event_timetimestampYESevent occurrence time
Enter a value 7 days before or after the TROCCO transfer execution date and time.
2020-01-01 00:00:00 +00:00
emstringYES*Emailtrocco@trocco.iouser_data
phstringYES*Phone080-0000-0000user_data
gestringYES*Genderfuser_data
dbstringYES*Date of Birth19971226user_data
lnstringYES*Last NameTROCCOuser_data
fnstringYES*First NameTarouser_data
ctstringYES*CityTokyouser_data
ststringYES*StateMeguro-kuuser_data
ZPstringYES*Zip1234567user_data
countrystringYES*Countryjpuser_data
external_idstringYES*External IDuser_data
client_ip_addressstringYES*Client IP addressuser_data
client_user_agentstringYES*Client user agentuser_data
fbcstringYES*Click IDuser_data
fbpstringYES*Browser IDuser_data
subscription_idstringYES*Subscription IDuser_data
lead_idstringYES*Lead IDuser_data
fb_login_idstringYES*FB Login IDuser_data
custom_datajsonNOCustom data can be passed 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_urlstringRequired if action_source is website
opt_outbooleanNO
event_idstringNO

At least one of the *user_data columns is required.

*Column mapping table combinations that contain only parameters consisting of one or a subset of the following are considered invalid
* ct + country + st + zp + ge + client_user_agent
* db + client_user_agent
* fn + ge
* ln + ge


Was this article helpful?