Event

Criteo allows you to run dynamic retargeting ad campaigns to drive conversions for retail, travel, and gaming apps, intelligently targeting users with personalized creatives.

Supported Features

  • Event Forwarding

Prerequisites

In order to enable our Event integration with Criteo, you’ll need to work with your Criteo Account Strategist or Technical Solutions Engineer to get your Criteo Partner Name / ID.

Event Data Mapping (Mobile)

The following table details how mParticle events are mapped into Criteo’s data model:

Description mParticle Event Criteo Event Data Mapping
When an app launches or comes into the foreground ViewHome
When a user opens a product view CommerceEvent (Android) and MPCommerceEvent (iOS and tvOS) with ActionType of ViewDetail ViewProduct
When a user adds a product to their cart CommerceEvent (Android) and MPCommerceEvent (iOS and tvOS) with Action Type of AddToCart ViewCart
When a user completes a transaction CommerceEvent (Android) and MPCommerceEvent (iOS and tvOS) with Action Type of Purchase or Checkout Purchase
When a user searches or views a list of products CommerceEvent with Impression (Android) and MPCommerceEvent with initWithImpressionName (iOS and tvOS) ViewListing

mParticle’s mobile Criteo integrations supports custom mappings. You can map your events and attributes for Criteo. mParticle provides mappings for the following Criteo event types on mobile:

  • Achievement Unlocked
  • Commerce - Transaction
  • Deeplink
  • High Purchase Intention
  • Low Purchase Intention
  • Transaction
  • Tutorial Finished
  • User Level Finished
  • User Logged In
  • User Registered
  • User Status
  • User Subscribed
  • View Item
  • View Search Results

Event Data Mapping (Web)

The following table details how mParticle events are mapped into Criteo’s data model:

Description mParticle Method Criteo Event Data Mapping Notes / Examples
When logging a homepage view logPageView viewHome customFlag of { CRITEO_VIEW_HOMEPAGE: true } must be included. ex. mParticle.logPageView('test', null, {CRITEO_VIEW_HOMEPAGE: true})
When a user opens a product view logProductAction with Action Type of ProductActionType.ViewDetail viewItem
When a user adds a product to their cart Cart.add viewCart
When a user completes a transaction logPurchase Purchase
When a user searches or views a list of products logImpression ViewListing

By default, Criteo’s setSiteType event will be ‘d’ for desktop unless you include in the JS snippet a config option of {customFlags: {CRITEO_SITETYPE: type}} where type is ‘m’ (mobile) or ‘t’ (tablet).

In order to add Criteo’s setData event, you will need to add EventAttributes to any of the above mParticle methods. Example:

mParticle.eCommerce.logProductAction(mParticle.ProductActionType.ViewDetail, [...products], { eventAttr1:'testValue1' });

mParticle’s JS Criteo integration does not support custom mappings. Leave the custom mappings portion alone.

Configuration Settings

Setting Name Data Type Default Value Description
Criteo Partner Name / ID string This is usually the bundle id/package name of your application (ex: com.myapp.ios). Please communicate to your Criteo Account Strategist what value you set for this field.