- 07 Dec 2022
- Print
- DarkLight
- PDF
Data Destination - Facebook offline conversions
- 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 Facebook offline conversions.
- You can extract data from any source and send it to the Offline Conversions API.
To match the format of the Facebook Offline Conversions API, you will need to map column names and types in trocco.
Setting items
STEP1 Basic settings
Item | input example | explanation |
---|---|---|
Facebook connection information | Select the connection information created in the access token | |
Business Account ID | 111111111(trocco) | |
Offline Event Set ID | 1559280064277365 | Go to your Facebook Business Events Manager to find and enter your offline event set ID. |
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.
All of the following parameters for offline conversion documents are available (excluding data_processing_options).
https://developers.facebook.com/docs/marketing-api/offline-conversions/?locale=ja_JP
Creating an Offline Event Set
Select Data Sources > offline event sets from Facebook Business Manager and add them.
Checking the Transfer Results
Check the results of your event in Facebook Events Manager.
From the History tab, you can check the transmission results.
supplement
Column mapping table
column name | typerequired | descriptioninput | examplecategory | ||
---|---|---|---|---|---|
event_name | string | YES | Enterable fields 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 | Required for NO*Purchase | |||
value | dobule | Required for NO*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 the match key 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 + zip + gen
- dobm or dobd
- fn + gen
- ln + gen