Loader Facebook Conversion
This component adds events to the Facebook Conversion API.
Requirements
To use the Facebook loader, one needs to authorize the Facebook account. Authorization can be done in 2 ways:
- The user who has access to an Ad account in Facebook Business Manager and has access to Audiences click on the “Authorize” button in the same browser where one logged in in his Facebook Ad account.
- Authorization link can be copied by an analyst working in Meiro Integrations and sent for authorization to a person who has the required level of access and should open the link in the same browser where one logged in in his Facebook Ad account.
- Users would then have to set up a Facebook pixel with conversion API.
Learn more: How to set up a Facebook pixel with conversion API here.
Learn more: How to verify that the events have been received on Facebook here.
Data In/ Data Out
Data In
|
CSV for events should be located in /data/in/tables/imports.csv
Learn more: about column formatting please refer to the Facebook help website.
Warning: Requests to Facebook Conversion API are sent in batches of 1000 events, if any given event in a batch is invalid, the entire batch will be rejected.
Required input
user_gender
event_name (required)
|
string,String.
m(male)event_name oris f(female)also used in deduplication.
|
|
event_nameevent_time (required)
|
string |
event_time (required) |
Integer integer,- Unix timestamp
Warning: This needs to be earlier than 7 days ago otherwiseotherwise, the request would be invalid.
|
|
user_gender (required)
|
m(male) or f(female)
|
| and at least one user's information (prefix user_) is required |
|
Other possible inputs
event_id
custom_currency
|
string
|
custom_value |
float |
custom_currency |
string -String, must be valid valid ISO 4217 currency code
|
user_email
custom_value
|
string
Float
|
user_phone
event_id
|
String
This ID can be any unique string chosen by the advertiser. Event_id is used to deduplicate events sent by both Facebook Pixel and Conversions API. Event_name is also used in deduplication.
For deduplication, the eventID from a browser event must match the event_id in the corresponding server event.
Learn more: about event id from here.
|
user_date_of_birth
user_browser_id
|
string, fbp browser cookie
“yyyymmdd”Learn eg:more: “19971226”about fbp browser cookies here
|
user_last_name
user_city
|
string
|
user_first_name
user_country
|
string |
user_city |
string |
user_state |
string |
user_zip |
string |
user_country |
string -string, lowercase two-letter country code, eg. “us”
|
user_external_id
user_click_id
|
string , fbc browser cookie
Learn more: about fbc browser cookies here
|
|
user_client_ip_address
|
string
|
|
user_date_of_birth
|
string, “yyyymmdd” eg: “19971226”
|
|
user_email
|
string
|
|
user_external_id
|
string, any unique id from advertisers
Learn more: about external id here
|
user_client_ip_address |
string
|
user_client_user_agent |
string
|
user_click_id |
string , fbc browser cookie
Learn more: about fbc browser cookies here
|
user_browser_id
user_facebook_login_id
|
string,integer, fbpID browserissued cookie
by Facebook
Learn more: about fbpID browserissued cookiesby Facebook here
|
user_subscription_id
user_first_name
|
string
|
user_facebook_login_id
user_last_name
|
integer, ID issued by Facebook
Learn more: about ID issued by Facebook herestring
|
|
user_lead_id
|
integer,Integer, ID from Facebook’s Lead Ads
Learn more: about ID from Facebook Lead Ads here
|
|
user_phone
|
string
|
|
user_state
|
string
|
|
user_subscription_id
|
string
|
|
user_zip
|
string
|
|
|
Data Out
|
N/A
|
Learn more: about the folder structure here.
Parameters
|
Pixel_ID (required)
|
This is the Pixel ID of the Facebook Pixel you created. Conversion API events will be sent to this Pixel.
Learn more: about Facebook Pixel with Conversion API here.
|
