What Is Criteo?

Criteo is a technology company specializing in digital advertising. Their platform utilizes machine learning algorithms to analyze online user behavior and deliver targeted ads across various devices and channels. By helping advertisers reach potential customers who have shown interest in their products or services, Criteo aims to improve ad performance and drive conversions.

Getting Started

1. From Your Criteo Account

• Grab your Partner ID

  1. Log into your Criteo Commerce Growth account.
  2. On the left-hand navigation, under Events, click on Events Tracking.
  3. Under the “Select a data set” drop-down, you will find your Partner ID in parentheses next to your account name.
  

2. From MetaRouter

To gather and send the anonymousID value as a cookie to Criteo’s identity endpoint, you must add a Criteo sync.

1. From the Pipelines page, find the pipeline associated with the web property you’d like to add a sync to. Hover over the three-dot dropdown and select “Build AJS File.”
2. In the Identity Syncs section, select the Criteo sync.
3. Fill out the following fields:
   1. Partner ID - The partner ID of the account you are sending the data to.
   2. First Party Name - Advertiser name. Ex. “metarouter”
   3. First Party Domain - The domain of the partner. Ex, for www.fnac.com, it could be “fnac.com” or “www.fnac.com”.
   4. Cookie Lifetime (in days) - 30 days recommended
   5. Fire on re-sync - Default set to off
4. Scroll down and click the Save and Build File button.
5. Deploy your AJS file to propagate changes to your web property.

Technical Details

Sync Types

syncType: matchPixel

Sync Ids

ids: N/A

MatchPixelSync

• This sync triggers a URL pixel and sets a marker (beaconFired) to indicate the sync's completion. Subsequent calls are suppressed until the marker expires. The marker's lifespan is defined by the cookieTimeToLive parameter.

• Partner ID and anonymous ID is passed to URL pixel for provider's match table.

• Called pixel's URL is shown below.

• Endpoint: https://https://gum.criteo.com/fpm/init?first_party_id=[ANONYMOUS_ID]&first_party_name=metarouter&first_party_domain=[DOMAIN]&p=[PARTNER_ID]

• HTTP method : GET

• Where:

  • ANONYMOUS_ID - Is the MetaRouter's payload anonymousId value.
  • DOMAIN - The value is dynamic and will be provided via our UI via the First Party Domain field. Defaults to hostname.
  • PARTNER_ID - The value is dynamic and will be provided via our UI via the Partner ID field.

Conclusions

Values added to storage

• *_criteo_beaconFired
  • Time to live: Set by the Cookie Lifetime setting in the UI(e.g. 30 days). Defaults to 365 days.
  • Notes: Created when match pixel sync fires.

Server-Side Event Payload: providers object enrichments

Upon completion of all vendor's sync, the server-side events will incorporate all resolved identifiers as described above. The following object will be appended to the context.providers property within the event's JSON payload

{
   "criteo": {
     "beaconFired": true
   }
}

UI build settings

• (Required) Cookie Lifetime (in days)
  • Defines the duration after which a stored value is automatically removed from storage unless renewed. When this time expires, the corresponding storage marker is deleted.
  • Example: 30
• (Required) Partner ID
  • Defines the partner ID value in called URL pixel.
  • Example: "3615"
• (Required) Fire On ReSync
  • Defines if the sync should be fired again when an identity call is made.
  • Example: false
• (Optional) First Party Name
  • Defines the optional first party name value used in URL pixel.
  • Example: "metarouter"
• (Optional) First Party Domain
  • Defines the optional first party domain value used in URL pixel.
  • Example: "metarouter.io"