Supported Keys for Meta Conversions API

See what events and data can be passed to Meta Conversions API once the integration has been set up.

📘

Attention

The below list of supported keys is subject to change. For the most up-to-date list check Facebook's documentation.

❗️

Unless marked as Required, most parameters in this page are optional.

📘

To view more (optional) parameters you can send to Meta, see Meta's documentation "List of Standard Events".

Event Keys

📘

Page View Event

The page view event is already included as a part of your pixel base code. Page view tells you when someone lands on a web page with the pixel base code installed.

User Data Keys

Standard Data Keys

Customer Information Keys

Property	Definition	Description	Usage	Web	Mobile
ge string or list	Gender	We accept gender in the form of an initial in lowercase.	'm' or 'f'	✅	✅
subscription_id string	Subscription ID	The subscription ID for the user in this transaction; it is similar to the order ID for an individual product.	'fb.1.1596403881668.1116446470'	✅	✅
ct string or list	City	We recommend using Roman alphabet a-z characters. Lowercase only with no punctuation, no special characters, and no spaces. If using special characters, the text must be encoded in UTF-8 format.	'london'	✅	✅
st string or list	State	We recommend the 2-character ANSI abbreviation code in lowercase. Normalize states outside the U.S. in lowercase with no punctuation, no special characters, and no spaces.	'ca'	✅	✅
country string or list	Country	We recommend the lowercase, 2-letter country codes in ISO 3166-1 alpha-2. Important Note: Always include your customers' countries’ even if all of your country codes are from the same country. Facebook matches on a global scale, and this simple step helps Facebook match as many Accounts Center accounts as possible from your list.	'us'	✅	✅
fb_login_id integer	Facebook Login ID	The ID issued by Meta when a person first logs into an instance of an app. This is also known as App-Scoped ID.		✅	✅
lead_id integer	Lead ID	The ID associated with a lead generated by Meta's Lead Ads.		✅	✅

App Data Keys

Property	Definition	Description	Usage	Web	Mobile
advertiser_tracking_enabled boolean	Advertiser Tracking Permission	Use this field to specify ATT permission on an iOS 14.5+ device. Set to 0 for disabled or 1 for enabled.	'0' or '1'	❌	✅
application_tracking_enabled boolean	Application Tracking Permission	A person can choose to enable ad tracking on an app level. Your SDK should allow an app developer to put an opt-out setting into their app. Use this field to specify the person's choice. Use 0 for disabled, 1 for enabled. `	'0' or '1'	❌	✅
extinfo object	Extended Device Information	Extended device information, such as screen width and height. This parameter is an array and values are separated by commas. When using extinfo, all values are required and must be in the order indexed below. If a value is missing, fill with an empty string as a placeholder.		❌	✅

Extended Device Information Keys

When using extinfo, all values are required and must be in the order indexed below. If a value is missing, fill with an empty string as a placeholder.

Property	Definition	Description	Usage	Web	Mobile
0 string	Extinfo version	Note: version must be a2 for Android version must be i2 for iOS Required when using Mobile events	'i2'	❌	✅
1 string	App package name		'com.facebook.sdk.samples.hellofacebook'	❌	✅
2 string	Short version		'1.0'	❌	✅
3 string	Long version		'1.0 long'	❌	✅
4 string	OS version	Required when using Mobile events	'13.4.1'	❌	✅
5 string	Device model name		'iPhone5,1'	❌	✅
6 string	Locale		'En_US'	❌	✅
7 string	Timezone abbreviation		'PDT'	❌	✅
8 string	Carrier		'AT&T'	❌	✅
9 string	Screen width		'320'	❌	✅
10 string	Screen height		'568'	❌	✅
11 string	Screen density		'2'	❌	✅
12 string	CPU cores		'2'	❌	✅
13 string	External storage size in GB		'13'	❌	✅
14 string	Free space on external storage in GB		'8'	❌	✅
15 string	Device timezone		'USA/New York'	❌	✅