Data Destination - Facebook Offline Conversions
- Print
- PDF
Data Destination - Facebook Offline Conversions
- Print
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
summary
Help Page for ETL Configuration of Data Setting to Facebook Offline Conversions.
- Data can be extracted from any Data Source and sent to the Offline Conversion API.
You will need to map the column names and types on TROCCO to match the format of the Facebook Offline Conversions API.
Setting items
STEP1 Basic settings
| (data) item | Input Example | Description. |
|---|---|---|
| Facebook Connection Configuration | Select Connection Configuration created with an access token | |
| Business Account ID | 111111111（TROCCO） | |
| offline event set ID | 1559280064277365 | Please confirm and enter your Offline Event Set ID from the Facebook Business Event Manager. |
column mapping
In the Column Setting of STEP 2 of TROCCO, data can be sent to the Facebook Conversions API by mapping column names and types.
Match column names and types as shown in the table in the "Supplemental" section.
All of the following parameters in the offline conversion document can be supported (*except for data_processing_options).
https://developers.facebook.com/docs/marketing-api/offline-conversions/?locale=ja_JP
Creating Offline Event Sets
From the Facebook Business Manager, select Data Sources > Offline Event Sets and add.
Confirmation of transfer results
Please check the event results from the Facebook Event Manager.
From the History tab, the results of the transmission can be viewed.
supplement
Column Mapping Table
| column name | type (e.g. of machine, goods, etc.) | indispensable | Description. | Input Example | category |
|---|---|---|---|---|---|
| event_name | string | YES | inputtable item ViewContent, Search, AddToCart, AddToWishlist, InitiateCheckout, AddPaymentInfo, Purchase, Lead, Other | Lead | |
| event_time | timestamp | YES | event occurrence time | 2020-01-01 00:00:00 +00:00 | |
| currency | string | NO*Required for Purchase | |||
| value | double | NO*Required for Purchase | |||
| content_type | string | NO | |||
| contents | json | NO | |||
| custom_data | json | NO | |||
| order_id | string | NO | |||
| item_number | string | NO | |||
| string | YES※ | trocco@trocco.io | match key | ||
| phone | string | YES※ | Phone | 080-0000-0000 | match key |
| gen | string | YES※ | Gender | f | match key |
| doby | string | YES※ | Date of Birth. YYYY format | 1997 | match key |
| dobm | string | YES※ | Date of Birth. MM format | 12 | match key |
| dobd | string | YES※ | Date of Birth. DD format | 26 | match key |
| ln | string | YES※ | Last Name | Suzuki | match key |
| fn | string | YES※ | First Name | Taro | match key |
| fi | string | YES※ | First Name Initial | match key | |
| ct | string | YES※ | City | match key | |
| st | string | YES※ | State | Meguro-ku | match key |
| zip | string | YES※ | Zip | 1234567 | match key |
| country | string | YES※ | Country | jp | match key |
| madid | string | YES※ | Apple Advertising Identifier/Android Advertising ID | match key | |
| external_id | string | YES※ | Third-party user id | match key | |
| lead_id | string | YES※ | The lead id from Lead Ads | match key |
At least one column of *match key 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 + zip + gen
- dobm or dobd
- fn + gen
- ln + gen
Was this article helpful?