Universal Events and Parameters for Online Conversions API Program
LiveRamp’s Online Conversion API program utilizes unified schema parameters with a mapping system that translates our parameters to each platform’s specific ones.
This article lists the following:
Available event types and the platforms that support them
Custom data parameters for passing additional data related to the event
Contents parameters for passing SKU-level data
Required parameters for API implementation
For instructions on implementing the Online Conversions API for ATS for Web, see "Implement Online CAPI"
For instructions on implementing the Online Conversions API with ATS API calls, see "Online Conversions API Program for API Implementation".
Note
The tables in this article will continue to expand as LiveRamp works with additional platforms. Stay up-to-date by regularly checking the "Release Notes and System Information" page to be notified when a new platform is supported.
Tip
If an event or parameter is not supported by one of your enabled CAPI platforms, the event data will still be sent to other platforms that do support it.
For example, you've enabled Meta, Pinterest, Snapchat, and TikTok in your CAPI integration. You then create an Add Payment Info event, which is only supported by Meta and TikTok. When the specified event takes place, the conversion data will be sent to Meta and TikTok only.
Caution
The Trade Desk Online Conversions API connectors are currently in limited availability. If you're interested in being considered to participate, contact your LiveRamp representative.
Tips on Using This Article
Learn which information is relevant depending on your implementation method and event source.
For ATS.js implementation (web): Use the following tables to check which platforms each event type supports, and our recommendations on passing additional data.
For API implementation (web and app): In addition to the tables above, refer to the tables below for info on required parameters and additional data you can pass to enrich your event.
Important
Check the Universal Key columns from each table and copy the desired key to use in your payload.
Event Types
The table below lists the conversion events you can send, the platforms that can receive them, and the supported event source.
App-only events can only be passed through API calls, while web events can be passed via ATS.js as well as direct API calls.
Universal Key | Description | Destination Platforms | Available for Web Events | Available for App Events |
|---|---|---|---|---|
AchieveLevel | A user reaches a certain level that you have defined in your game. |
| No | Yes |
AchievementUnlocked | A user unlocks a certain achievement that you have defined in your app. |
| No | Yes |
AdClick | A user clicks an ad. |
| Yes | Yes |
AdView | A user views an ad. |
| Yes | Yes |
AddBilling | A user configures their payment information. |
| Yes | Yes |
AddPaymentInfo | A user adds their payment information at checkout. |
| Yes | Yes |
AddToCart | A user adds a product to the shopping cart. |
| Yes | Yes |
AddToWishlist | A user adds a product the wishlist. |
| Yes | Yes |
AppInstall | A user installs your app. |
| No | Yes |
AppOpen | A user opens your app. |
| No | Yes |
ApplicationApproval | An application submitted by a user is approved. |
| Yes | No |
Checkout | A user is ready to check out an order in your app. |
| No | Yes |
CompleteRegistration | A user signs up or creates an account by completing a registration form. |
| Yes | Yes |
CompleteTutorial | A user completes a tutorial. |
| No | Yes |
Contact | A user contacts your business via chat, email, telephone, etc, |
| Yes | No |
ConvertedLead | A user completes a step in the (pre-defined) lead conversion process. |
| Yes | Yes |
CreateGroup | A user creates a group or team in your game. |
| No | Yes |
CreateRole | A user creates a role or character in your game. |
| No | Yes |
CustomizeProduct | A user customizes a product. |
| Yes | No |
Donate | A user donates to your organization or a cause. |
| Yes | Yes |
Download | A user downloads something from your websites. |
| No | No |
Engagement | A user performs an action that indicates engagement. |
| Yes | Yes |
FindLocation | A user searches for a location on your website, such as looking for the location of a physical store. |
| Yes | No |
GenerateLead | A user leaves contact information, such as a phone number or email, in your app. |
| No | Yes |
ImportedLead | A user has been qualified as a lead from an external source. |
| Yes | Yes |
InAppAdClick | A user clicks on an advertisement displayed in your app. |
| No | Yes |
InAppAdImpr | A user views an advertisement displayed in your app. |
| No | Yes |
InitiateCheckout | A user starts the checkout flow to purchase items. |
| Yes | No |
Invite | A user invites another user. |
| Yes | Yes |
JoinGroup | A user joins a group or team in your game. |
| No | Yes |
Lead | A user completes a form (sign up) to get more information. |
| Yes | Yes |
LevelComplete | A user completes a level. |
| Yes | Yes |
ListView | A user views a list. |
| Yes | Yes |
LoanApplication | A user applies for a loan in your app. |
| No | Yes |
LoanApproval | A user receives approval for a loan in your app. |
| No | Yes |
LoanDisbursal | A user successfully receives a loan in your app. |
| No | Yes |
Login | A user logs into your app. |
| No | Yes |
Other | A user performs actions that don't fit the definition of the standard conversion types. |
| No | Yes |
OutboundClick | A user clicks on a link to an external website. |
| Yes | Yes |
PageView | When a user visits a product or article page. |
| Yes | Yes |
Purchase | A user completes the checkout flow or a purchase. |
| Yes | Yes |
QualifiedLead | A user performs an action that qualifies them as a lead. |
| Yes | Yes |
Rate | A user rates a product or a service. |
| Yes | Yes |
Registration | A user registers in your app. |
| No | Yes |
RequestQuote | A user requests a quote. |
| Yes | Yes |
Reserve | A user makes a reservation. |
| Yes | Yes |
Save | A user saves content, product, or offer to revisit later. |
| Yes | Yes |
Schedule | A user schedules an appointment to visit your business. |
| Yes | No |
SearchCategory | A user searches for a category. |
| Yes | Yes |
Search | A user searches or uses the search bar. |
| Yes | Yes |
Share | A user shares content such as posts, products, or promotions. |
| Yes | Yes |
SpentCredits | A user spends credits, such as in-app currency, in your app. |
| No | Yes |
StartTrial | A user begins a free trial to use a product or service your business offers |
| Yes | Yes |
StoreSale | A user makes a purchase at your physical store. |
| Yes | Yes |
StoreVisit | A user physically visits your store |
| Yes | Yes |
SubmitApplication | A user applies for something that your business offers. |
| Yes | No |
SubmitForm | A user submits a form or application. |
| Yes | Yes |
Subscribe | A user subscribes to content on your website, including paid subscription. |
| Yes | Yes |
ViewCategory | A user views a product category page. |
| Yes | Yes |
ViewCart | A user views the contents of the shopping cart. |
| Yes | Yes |
ViewContent | A user visits a specific page related to your business, such as a product page or landing page. |
| Yes | Yes |
WatchVideo | A user watches a video. |
| Yes | Yes |
Custom Data
Parameters marked as "Recommended" mean that including them will help create more accurate and higher quality conversion data. Parameters marked as "Optional" mean that including them can provide more context in your conversion data.
We highly suggest including as many recommended parameters as possible when you set up your event in Console or when you are constructing you request payload.
For API implementations, you can pass the following data as part of the custom_data object for both web or app events. For ATS for Web (ATS.js) implementations, you can include the parameters by enabling "Add Custom Data Parameters" in your event's setting.
Universal Key | Description | Destination Platforms | Available for Web Events | Available for App Events |
|---|---|---|---|---|
content_ids Array of string Optional | The product IDs (or SKUs) associated with the event. |
| Yes | Yes |
content_category Array of string Optional | The category of the product. |
| Yes | Yes |
content_name Array of string Optional | The name of the product. |
| Yes | Yes |
content_type Array of string Optional | Used to indicate what the keys the content IDs represent; individual items or multiple items in group. |
| Yes | Yes |
currency Array of string Required for purchase events | ISO 4217 code of the currency associated with the value. |
| Yes | Yes |
Array of string Recommended | The user's email address. |
| Yes | Yes |
num_items Array of string Optional | The number of items the user has during checkout. |
| Yes | Yes |
order_id Array of string Optional | A string of ID for this specific transaction. |
| Yes | Yes |
description Array of string Optional | A string description of the product. |
| Yes | Yes |
phone_number Array of string Recommended | The user's phone number. |
| Yes | Yes |
predicted_ltv Array of string (stringified float) Optional | The predicted lifetime value of a conversion event. |
| Yes | Yes |
search_string Array of string Optional | The text that was used for the search event. |
| Yes | Yes |
value Array of string (stringified float) Required for purchase events | Total value of items with item_price attribute within the "contents" object (i.e. basket-level value). |
| Yes | Yes |
content_brand Array of string Optional | The brand associated with the content ID. |
| Yes | Yes |
event_tag Array of string Optional | Custom event set label. |
| Yes | Yes |
shop_id Array of string Optional | The shop ID. |
| Yes | Yes |
first_name Array of string Recommended | The user's first name. |
| Yes | Yes |
last_name Array of string Recommended | The user's last name. |
| Yes | Yes |
zip_code Array of string Recommended | The user's zip code. |
| Yes | Yes |
date_of_birth Array of string Recommended | The user's date of birth. |
| Yes | Yes |
gender Array of string Recommended | The user's gender. |
| Yes | Yes |
city Array of string Recommended | The city associated with the event. |
| Yes | Yes |
country Array of string Optional | The country associated with the event. |
| Yes | Yes |
state Array of string Optional | The state associated with the event. |
| Yes | Yes |
fb_login_id Array of string Optional | The ID issued by Meta when a person first logs into an instance of an app. This is also known as App-Scoped ID. |
| Yes | Yes |
lead_id Array of string Optional | The ID associated with a lead. |
| Yes | Yes |
subscription_id Array of string Optional | The subscription ID of the user in the event. |
| Yes | Yes |
anon_id Array of string Optional | Unique application install ID. |
| No | Yes |
limited_data_use Boolean Optional | Set this field to specify when data should be processed in compliance with various US state privacy regulations. Set the value to
Set the value to |
| Yes | Yes |
Content Properties
Include the optional parameters in the following table to provide more context on every individual item in an event.
For API implementations, you can pass the following data as part of the contents object. For ATS for Web implementations, you can include the parameters by enabling "Add Contents" in your event setting.
Universal Key | Description | Destination Platforms | Available for Web Events | Available for App Events |
|---|---|---|---|---|
item_id array of string Required if | Unique ID of the individual item. |
| Yes | Yes |
item_price array of string (stringified float) Optional | Price of the individual item. |
| Yes | Yes |
item_quantity array of string (stringified integer) Optional | Quantity of the individual item. |
| Yes | Yes |
item_name array of string Optional | Name of the individual item or page. |
| Yes | Yes |
item_brand array of string Optional | Brand of the individual item. |
| Yes | Yes |
item_brand_id array of string Optional | Brand ID of the individual item. |
| Yes | Yes |
item_category array of string Optional | Product category of an individual item. |
| Yes | Yes |
item_subcategory array of string Optional | Sub-category of an individual item. |
| Yes | Yes |
Additional Parameters for API Implementations
Customers calling the CAPI connector API should pass additional event and user-level data in their request payload to ensure events can be accurately matched to ad exposures, and support reliable measurement and optimization.
Do not send conversions that occurred more than 7 days ago.
Do not send conversions with a conversion date in the future.
Note
For ATS.js implementations, the data below would be provided by customers directly in Console or automatically obtained and passed by ATS.js.
Required Event Data
When sending web and app events via API calls, you are required to include all the parameters below in your request payload as part of the events object.
Universal Key | Description | Applicable for Web Events | Applicable for App Events |
|---|---|---|---|
event_name string Required | The event type key from the list all universal event types. | Yes | Yes |
event_id string Required | A unique string that identifies the event and can be used for deduplication between events. | Yes | Yes |
event_time integer Required |
| Yes | Yes |
event_source_url string Required | The browser URL when the event happened. | Yes | Yes |
event_source string Required | Where the event occurred, value must be set to either | Yes | Yes |
User Data Keys
When sending web and app events via API calls, we recommend always adding the following identifier data to enrich your events and improve match rates. Especially with upper-funnel events such as Page View, View Content, or Search, which often lack identifiers. Pass the following data as part of the user_data object.
Universal Key | Description | Applicable for Web Events | Applicable for App Events |
|---|---|---|---|
envelope string Recommended | Identity envelope value. If pulled from storage, the value must be Base64-decoded before sending. | Yes | Yes |
fb_envelope string Recommended | Facebook-scoped envelope value. If pulled from storage, the value must be Base64-decoded before sending. | Yes | Yes |
gaid string Recommended | Advertising identifier for Android devices. | No | Yes |
idfa string Recommended | Advertising identifier for iOS devices. | No | Yes |
idvf string Recommended | Vendor identifier assigned to apps on iOS devices. | No | Yes |
user_agent string Recommended | The user agent from the user's device where the event occurred. CautionIf the user_agent parameter is not present in your API payload, the adapter retrieve user agent from the request header. | Yes | Yes |
ip_address string Recommended | The IP address of the user's device. CautionIf the ip_address parameter is not present in your API payload, the adapter will automatically retrieve IP address from the request header. | Yes | Yes |
Provider Data for Web Events
When sending web events via API calls, we recommend to include the following provider data keys so platforms can directly tie each conversion back to the exact ad click or view that generated it. Pass the following data as part of the provider_data object.
Universal Key | Description | Destination Platforms |
|---|---|---|
fb_click string Recommended | The Facebook click ID value stored in the See Meta's article "Managing fbc and fbp Parameters" for more info. | Meta |
fb_view string Recommended | The Facebook browser ID value stored in the See Meta's article "Managing fbc and fbp Parameters" for more info. | Meta |
pin_click string Recommended | The This parameter is mapped to See Pinterest’s article “Managing Click ID Parameters” for more info. | |
sc_click string Recommended | The ID value stored in the landing page URL’s This parameter is mapped to See Snapchat’s article “Managing Click ID and View ID Parameters” for more info. | Snapchat |
sc_view string Recommended | The 1st party cookie if you are using the Pixel SDK, which can be accessed by looking at the This parameter is mapped to See Snapchat’s article “Managing Click ID and View ID Parameters” for more info. | Snapchat |
tt_click string Recommended | TikTok Click ID, a data connection parameter appended to a landing page URL whenever a user clicks on an ad on TikTok. The value can be found in the This parameter is mapped to Send TikTok's article "Send TikTok Click ID" for more info. | TikTok |
tt_view string Recommended | Cookie ID. If you also use Pixel SDK and have enabled cookies, Pixel SDK automatically saves a unique identifier in the This parameter is mapped to See TikTok's article “Send TikTok Cookie” for more info. | TikTok |
ttd_view string Recommended | The Trade Impression ID, appended to the landing page URL at ad bid time. | The Trade Desk |
oai_view string Recommended | OpenAI-provided privacy-preserving identifier, which value can be found in landing page URL within the | OpenAI |
Required Parameters for App Events
In addition to the required event data parameters above, customers passing app events must include additional fields about the application and device where the event occurred.
All fields in the below table must be present as part of the app_data object, but not all require values to be included. You can pass empty string ("") on fields that don't require values. See the full schema below:
"app_data": {
"advertiser_tracking_enabled": "true",
"application_tracking_enabled": "true",
"app_id": "1",
"app_name": "CAPI",
"device_type": "Motorola",
"device_brand": "Motorola",
"language": "en",
"wifi": "false",
"extinfo_version": "Android",
"app_pack_name": "com.some.app",
"short_version": "771",
"long_version": "Version 7.7.1",
"os_version": "10.1.1",
"device_model": "OnePlus6",
"locale": "en_US",
"timezone_abbr": "GMT-1",
"carrier": "TMobile",
"screen_width": "1920",
"screen_height": "1080",
"screen_density": "2.00",
"cpu_core": "2",
"ext_storage_size": "128",
"free_space": "8",
"device_timezone": "USA/New York",
"form_factor": "cellphone",
"network_type": "wifi",
"os_family": "android"
}Universal Key | Value Required? | Description | Destination Platforms |
|---|---|---|---|
advertiser_tracking_enabled boolean Required | Yes | Use this field to specify ATT permission on an iOS 14.5+ device. Set value to |
|
application_tracking_enabled boolean Required | Yes | Use this field to specify user's choice regarding tracking on an app level. Set value to |
|
app_id string Required | Optional | The unique ID assigned for a given application. |
|
app_name string Required | Optional | Name of the app. |
|
device_type string Required | Optional | Type of the user device. |
|
device_brand string Required | Optional | Brand of the user device. |
|
language string Required | Optional | Two-character ISO-639-1 language code indicating the user's language. |
|
wifi boolean Required | Optional | Whether the event occurred when the user device was connected to wifi. |
|
extinfo_version string Required | Yes | Device version, value can be |
|
app_pack_name string Required | Optional | App package name. Example: com.liveramp.sdk |
|
short_version string Required | Optional | App version (short). Example: 1.0 |
|
long_version string Required | Optional | App version (long). Example: 1.0 long |
|
os_version string Required | Yes | The OS version. Example: 13.4.1 |
|
device_model string Required | Optional | Device model name. Example: iPhone13 |
|
locale string Required | Optional | The device's region. Example: En_US |
|
timezone_abbr string Required | Optional | Timezone abbreviation. Example: PDT |
|
carrier string Required | Optional | The device data carrier. Example: AT&T |
|
screen_width string Required | Optional | The device's screen width. Example: 320 |
|
screen_height string Required | Optional | The device's screen height. Example: 568 |
|
screen_density string Required | Optional | The device's screen density. Example: 2 |
|
cpu_core string Required | Optional | The CPU core Example: 2 |
|
ext_storage_size string Required | Optional | The external storage size in GB. Example: 13 |
|
free_space string Required | Optional | The free space on the external storage in GB. Example: 8 |
|
device_timezone string Required | Optional | The device's time zone. Example: USA/New York |
|
form_factor string Required | Optional | Device form factor. Example: cellphone |
|
os_family string Required | Optional | The device's OS family. Example: ios |
|
network_type string Required | Optional | The device's network type or capability. Example: 4G, 5G |
|