> ## Documentation Index
> Fetch the complete documentation index at: https://developers.criteo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Criteo Integration With Kochava [iOS]

> Configure your Criteo App campaign for iOS with Kochava.

## Overview

Criteo serves personalized ads to mobile app users that have a high probability of clicking through and either installing your app or making an in-app purchase. Criteo technology is based on real-time product recommendation optimization and prediction engines.

In order to enable its technology, Criteo needs:

* App Events — App events and relevant data correctly captured on your mobile app
* Catalog Feed — A CSV or XML file (called a Catalog Feed) containing product information of a large portion of your mobile app's offers
* (For Retargeting) Deeplink and Universal Link capability — Product level deep link capabilities in app to take users to the products they clicked on

This document provides detailed information on the following integration stages:

* App events and parameters
* Kochava dashboard configuration, including postbacks
* Generation of tracking links
* Catalog feed integration (for product-level ads)
* Deeplinking & Universal Linking (for Retargeting)
* Testing process

## Integration Steps

| Steps to Follow                                  | Where to Integrate                   |
| ------------------------------------------------ | ------------------------------------ |
| Integration Questionnaire                        | Client                               |
| Integration Kickoff Call                         | Criteo & client technical teams      |
| Dashboard Configuration                          | Client-side or (recommended) on call |
| (for product-level ads) Catalog Feed Integration | Criteo & client technical teams      |
| (only if needed) Criteo Event Integration        | Client-side                          |
| (only if needed) Testing events                  | Criteo & client technical teams      |
| (only if needed) App Submission & Release        | Client-side                          |
| Pre-Launch Checks                                | Criteo                               |
| Campaign Launch                                  | Criteo (with client's authorization) |

## App Events & Data

If you already have Kochava events configured, please skip this section.

To integrate the Kochava SDK and events from scratch, or add additional ones, please expand this section.

<Accordion title="Expand">
  ### SDK Initialization

  <Warning>
    Please ensure the 'language' parameter in the identity link is the two character language code (lower case) and matches the language of the app to ensure the events are sent to the correct endpoint.
  </Warning>

  Use the following code snippet at app launch:

  ```objc theme={null}
  NSDictionary *identityLinkDictionary = [NSDictionary dictionaryWithObjectsAndKeys:
                                          @"TEST_USER_ID", @"myInternalUserID",
                                          @"1235467890123456", @"service ID",
                                          @"en", @"language",
                                          @"46457bb078c674176a72c3a9ac40ba666244652f1b813f8bd839d529285cfa47", @"email_sha256",
                                          nil];
  NSDictionary *initDict = [NSDictionary dictionaryWithObjectsAndKeys:
                                @"REPLACE_WITH_YOUR_KOCHAVA_APP_ID", @"kochavaAppId",
                                @"USD", @"currency", // optional - usd is default
                                @"0", @"limitAdTracking", // optional - 0 is default
                                @"1", @"enableLogging", // optional - 0 is default
                                identityLinkDictionary, @"identityLink", // optional
                                nil];
  kochavaTracker = [[KochavaTracker alloc] initKochavaWithParams:initDict];
  ```

  ### Events Implementation in the App

  Below are examples of the different event types Criteo recommends that you integrate using the Kochava SDK:

  | Kochava event        | Description                                                 |
  | -------------------- | ----------------------------------------------------------- |
  | SessionBegin         | App open/brought to the foreground                          |
  | View Listing         | View of a list of products                                  |
  | View Product         | View of a specific product                                  |
  | View Basket          | View of the shopping basket, or an addition made to it      |
  | Purchase             | Purchase of one or more products                            |
  | Level Achieved       | User Level (for Gaming apps)                                |
  | Status               | User's Subscription Status (i.e. subscriber, free, premium) |
  | Achievement Unlocked | Major milestone reached within a game (for Gaming apps)     |

  #### SessionBegin

  The `sessionBegin` event should be sent to Kochava with each new session, after Kochava SDK initialization. *SessionBegin* is a standard event supported by the Kochava SDK.

  ```objc theme={null}
  [delegate.kochavaTracker trackEvent:@"SessionBegin":@"{}"];
  ```

  #### View Listing

  The `viewListing` event should be triggered on pages displaying product lists like a category page or a search results page. You should include in the array the **IDs of the top 3 products** (it's fine to include more). These IDs must match those passed in the catalog feed. Note that *viewListing* is not supported out of the box using Kochava's SDK and must be implemented as a custom event.

  ```objc theme={null}
  NSMutableDictionary * viewListing = [[NSMutableDictionary alloc] init];
  [viewListing setObject:[NSArray arrayWithObjects:@"1", @"2", nil] forKey: @"product"];

  jsonData = [NSJSONSerialization dataWithJSONObject:viewListing options:0 error:nil];

  [delegate.kochavaTracker trackEvent: @"viewListing": [[NSString alloc] initWithData:jsonData encoding:NSUTF8StringEncoding]];
  ```

  #### View Product

  The `View` event should be triggered on all product details pages. You should include the ID of the product detailed on the page by the Event Item name, and send the Event Item with the event. It must be the same ID as used in the catalog feed, and must be unique. The Kochava event corresponding to the Criteo Event Type `viewProduct` is *View*. *View* is a standard event supported by the Kochava SDK.

  ```objc theme={null}
  NSDictionary * viewProduct = @{@"product": @"1"};
  jsonData = [NSJSONSerialization dataWithJSONObject:viewProduct options:0 error:nil];
  [delegate.kochavaTracker trackEvent: @"View": [[NSString alloc] initWithData:jsonData encoding:NSUTF8StringEncoding]];
  ```

  #### View Basket

  The viewBasket event should be triggered on the basket-details pages. You must include the IDs, prices, and quantities of the basket's products by the Event Items array. Note that *viewBasket* is not supported out of the box using Kochava's SDK and must be implemented as a custom event.

  ```objc theme={null}
  NSDictionary * viewBasket = @{
                  @"currency": @"USD",
                  @"product": @[
                      @{@"id": @"1",@"price": @"2.95",@"quantity": @"5"},
                      @{@"id": @"2",@"price": @"19.99",@"quantity": @"1"}
                  ],
                  @"din": @"2026-09-07",@"dout": @"2026-09-10" // optional for Travel booking apps
              };

  jsonData = [NSJSONSerialization dataWithJSONObject:viewBasket options:0 error:nil];
  [delegate.kochavaTracker trackEvent: @"viewBasket": [[NSString alloc] initWithData:jsonData encoding:NSUTF8StringEncoding]];
  ```

  <Note>
    din/dout parameters are only required for Travel apps (Flights/Hotels/Car Booking) clients.
  </Note>

  #### Purchase

  The `Purchase` event should be triggered on order confirmation pages. You should include a unique transaction ID and place the IDs, prices, and quantities of the products bought in the transaction into the Event Items array. *Purchase* is a standard event supported by the Kochava SDK.

  ```objc theme={null}
  NSDictionary * trackTransaction = @{
                  @"nc": @"1",
                  @"id": @"transaction_id",
                  @"currency": @"USD",
                  @"product": @[
                      @{@"id": @"1",@"price": @"2.95",@"quantity": @"5"},
                      @{@"id": @"2",@"price": @"19.99",@"quantity": @"1"}
                  ],
                  @"din": @"2026-09-07",@"dout": @"2026-09-10" // optional for Travel booking apps
              };

  jsonData = [NSJSONSerialization dataWithJSONObject:trackTransaction options:0 error:nil];
  [delegate.kochavaTracker trackEvent: @"Purchase": [[NSString alloc] initWithData:jsonData encoding:NSUTF8StringEncoding]];
  ```

  #### Level Achieved

  The `userLevel` event allows Kochava to identify the highest level achieved by a user. This event is specific to the Gaming vertical. It should be triggered every time the user levels up. *userLevel* is a standard event supported by the Kochava SDK.

  ```objc theme={null}
  NSDictionary * userLevel = @{@"ui_level": 5};
  jsonData = [NSJSONSerialization dataWithJSONObject:userLevel options:0 error:nil];
  [delegate.kochavaTracker trackEvent: @"userLevel": [[NSString alloc] initWithData:jsonData encoding:NSUTF8StringEncoding]];
  ```

  #### Status

  The `userStatus` event allows Kochava to identify a user's subscription status (free, subscriber, premium). This event should be triggered to initialize the user's status, and every time when user status changes. Note that *userStatus* is not supported out of the box using Kochava's SDK and must be implemented as a custom event.

  ```objc theme={null}
  NSDictionary * userStatus = @{@"ui_status": @"subscriber"};
  jsonData = [NSJSONSerialization dataWithJSONObject:userStatus options:0 error:nil];
  [delegate.kochavaTracker trackEvent: @"userStatus": [[NSString alloc] initWithData:jsonData encoding:NSUTF8StringEncoding]];
  ```

  #### Achievement Unlocked

  The `achievementUnlocked` event allows Kochava to identify whether a user has reached a specific milestone within the game. *achievementUnlocked* is a standard event supported by the Kochava SDK.

  ```objc theme={null}
  NSDictionary * userAchievement = @{@"ui_achievement": @"Gold_Medal"};
  jsonData = [NSJSONSerialization dataWithJSONObject:userAchievement options:0 error:nil];
  [delegate.kochavaTracker trackEvent: @"achievementUnlocked": [[NSString alloc] initWithData:jsonData encoding:NSUTF8StringEncoding]];
  ```
</Accordion>

## Hashed Email for Cross-Device Targeting (Recommended)

Clients have the option of sending Criteo the email address of app users when available. This will enable the cross-device Criteo targeting feature.

<Accordion title="Expand">
  To generate an SHA256 hash of an email address:

  1. Convert all characters to lower case
  2. Remove any blank spaces
  3. Convert to UTF-8
  4. Hash using SHA256 algorithm

  The email can be sent to Criteo by associating it with the identity link during SDK initialization.

  Use the following code snippet as an example of sending a SHA256 hashed email:

  ```objc theme={null}
  NSDictionary *identityLinkDictionary = [NSDictionary dictionaryWithObjectsAndKeys:
                            @"CriteoKochavaTest", @"myInternalUserID",
                            @"1235467890123456", @"service ID",
                            @"en", @"language",
                            @"46457bb078c674176a72c3a9ac40ba666244652f1b813f8bd839d529285cfa47", @"email_sha256",
                            nil];

  NSDictionary *initDict = [NSDictionary dictionaryWithObjectsAndKeys:
                            @"komobile-in--app-events5565020f2e19b",
                            @"kochavaAppId",
                            @"USD", @"currency", // optional - usd is default
                            @"0", @"limitAdTracking", // optional - 0 is default
                            @"1", @"enableLogging", // optional - 0 is default
                            identityLinkDictionary, @"identityLink",
                            nil];
  ```

  Kochava's SDK also allows client apps an option to send email in clear text. Kochava servers will hash this email address before forwarding it to Criteo.

  Use the following code snippet as an example of how to send raw email addresses:

  ```objc theme={null}
  NSDictionary *identityLinkDictionary = [NSDictionary dictionaryWithObjectsAndKeys:
                            @"CriteoKochavaTest", @"myInternalUserID",
                            @"1235467890123456", @"service ID",
                            @"en", @"language",
                            @"kochava@criteo.com", @"email_raw",
                            nil];

  NSDictionary *initDict = [NSDictionary dictionaryWithObjectsAndKeys:
                            @"komobile-in--app-events5565020f2e19b",
                            @"kochavaAppId",
                            @"USD", @"currency", // optional - usd is default
                            @"0", @"limitAdTracking", // optional - 0 is default
                            @"1", @"enableLogging", // optional - 0 is default
                            identityLinkDictionary, @"identityLink",
                            nil];
  ```
</Accordion>

## Kochava Dashboard Configuration

### Adding the 'Criteo New' Network

To add 'Criteo New' as a partner on Kochava's dashboard:

1. Login to Kochava Dashboard
2. Select your App
3. Under App Configurations, go to the **Partner Configurations** tab
4. Click **Add Configuration** button

<Frame>
  <img src="https://mintcdn.com/criteo-e1682996/_Y5ppJi5blUNBSuu/images/mobile-integrations/kochava/kochava_add_configuration_ios.png?fit=max&auto=format&n=_Y5ppJi5blUNBSuu&q=85&s=4e5f434638345ea9a2e196f55dbf3e42" alt="Image" width="2626" height="855" data-path="images/mobile-integrations/kochava/kochava_add_configuration_ios.png" />
</Frame>

Finally, input 'Criteo New' into the Media Partner text field and select the 'Criteo New' network option when it appears below the text field. To save Criteo as a partner, click on the Go button.

<Frame>
  <img src="https://mintcdn.com/criteo-e1682996/_Y5ppJi5blUNBSuu/images/mobile-integrations/kochava/kochava_select_media_partner_ios.png?fit=max&auto=format&n=_Y5ppJi5blUNBSuu&q=85&s=8afb82653bec2404bc477ba491aed92d" alt="Image" width="848" height="232" data-path="images/mobile-integrations/kochava/kochava_select_media_partner_ios.png" />
</Frame>

### Configuring Criteo Postbacks

Once the partner is configured, postbacks can be set up for each event type.

1. Expand the 'Criteo New' module and go to the **Postbacks** tab.

<Frame>
  <img src="https://mintcdn.com/criteo-e1682996/_Y5ppJi5blUNBSuu/images/mobile-integrations/kochava/kochava_postbacks_tab_ios.png?fit=max&auto=format&n=_Y5ppJi5blUNBSuu&q=85&s=caa0a34233edeabfb00ac408b2e3e070" alt="Image" width="1880" height="506" data-path="images/mobile-integrations/kochava/kochava_postbacks_tab_ios.png" />
</Frame>

2. *Install* is automatically listed and its status is **Configured Postback**, however, it still needs additional setup (please see step 4 below for details). *SessionBegin* and the other post-install events will be listed once received by Kochava. All the events (except Install) are initially in status **Active Event**, meaning the postback is available but is not sending to Criteo yet. Once a postback is configured, its status becomes **Configured Postback**.

<Frame>
  <img src="https://mintcdn.com/criteo-e1682996/_Y5ppJi5blUNBSuu/images/mobile-integrations/kochava/kochava_postback_event_status_ios.png?fit=max&auto=format&n=_Y5ppJi5blUNBSuu&q=85&s=85b5766afbf1dd7df5408a1adf18b3ab" alt="Image" width="1583" height="349" data-path="images/mobile-integrations/kochava/kochava_postback_event_status_ios.png" />
</Frame>

3. Click the **+** icon next to an event to create a postback for it.
   * The postbacks need to be configured for: **Install**, **SessionBegin**, and all other relevant events for the campaign, such as post-install **KPI events**.
   * For Retargeting, it's highly recommended to also postback the key stages of the purchase funnel (for a retail app this would be events similar to SessionBegin, Search/Category Results, Item Details, Add to Cart, Basket View, Purchase Confirmation).

<Frame>
  <img src="https://mintcdn.com/criteo-e1682996/_Y5ppJi5blUNBSuu/images/mobile-integrations/kochava/kochava_create_postback_ios.png?fit=max&auto=format&n=_Y5ppJi5blUNBSuu&q=85&s=f1042b5cfc14d3fb8a442a3f5d7eb54a" alt="Image" width="1583" height="349" data-path="images/mobile-integrations/kochava/kochava_create_postback_ios.png" />
</Frame>

4. All the following settings are **required** for postbacks to function well:
   * **CRITEO BUNDLE ID**: Unique bundle ID of the app (this uniquely identifies the app to Criteo)
   * **SEND ALL EVENT DATA**: Switch the toggle **ON** to send all data to Criteo. Essential for harnessing Criteo's machine learning at its full potential (predictive bidding and product recommendations), and useful for other use cases such as audience segmentation and custom reporting.
   * **DELIVERY DELAY**: Select **Realtime Delivery**
   * **DELIVERY METHOD**: Select **All** to send attributed, unattributed and organic events to Criteo. Essential for the same machine learning purposes mentioned above, and also to better suppress installed users from your App Install campaigns. Then, click **Save**.

<Frame>
  <img src="https://mintcdn.com/criteo-e1682996/_Y5ppJi5blUNBSuu/images/mobile-integrations/kochava/kochava_postback_required_settings_ios.png?fit=max&auto=format&n=_Y5ppJi5blUNBSuu&q=85&s=ff5f5ec80aa5daad97d1c88d413c845d" alt="Image" width="1646" height="723" data-path="images/mobile-integrations/kochava/kochava_postback_required_settings_ios.png" />
</Frame>

<Note>
  For **Install**, there is no **Send All Event Data** option to toggle.
</Note>

### Attribution Settings — Partner Level

<Note>
  Keep in mind that the following settings are Criteo's recommendations but the ultimate goal is to match the options you want to take into account for your setup!
</Note>

Kochava attributes conversions through a fallback chain, from most to least precise: **Device Lookback** (deterministic, matches on a hard device ID) is tried first, then progressively looser probabilistic methods — **Fingerprint Lookback** (IP + user agent + other signals), **IP Lookback** (full IP address only), and **Partial IP Lookback** (first three octets of the IP) — to recover attribution for conversions that would otherwise go unmatched.

1. Under App Configurations, go to **Partner Configurations**
2. To the right side of the 'Criteo New' module, select the three-dots menu
3. Click **Reconciliation**

<Frame>
  <img src="https://mintcdn.com/criteo-e1682996/_Y5ppJi5blUNBSuu/images/mobile-integrations/kochava/kochava_reconciliation_menu_ios.png?fit=max&auto=format&n=_Y5ppJi5blUNBSuu&q=85&s=0ea402c142bde3d62ecf8ffbd1b4b4e4" alt="Image" width="1882" height="505" data-path="images/mobile-integrations/kochava/kochava_reconciliation_menu_ios.png" />
</Frame>

4. Configure the windows below according to your attribution model, or these suggested defaults:

**<u>\[Optional] Impression Reconciliation</u>**

<Warning>
  Setting up Impression based attribution is optional. Enable these options ONLY if taken into account.
</Warning>

The Impression Reconciliation settings control how Kochava attributes installs/conversions to impression (view-through) ads when no click is available.

* **Device Lookback** — Uses a device identifier to match an ad impression to an install/conversion. If set to `24` hours: if the install/conversion happens within 24 hours after the impression, attribution is allowed.
* **Modeled Lookback** — The maximum time before an install during which Kochava considers an impression for attribution when a modeled/probabilistic match is used. Modeled attribution is used when no usable device identifier is available and relies on probabilistic device information—primarily IP address and User Agent. If set to `24` hours: Attribution is allowed if the install/conversion occurs within 24 hours of the impression.
* **IP Lookback** — The maximum time prior to an install during which Kochava considers impressions for attribution using a modeled IP-based match, where the impression and install are matched using the full IP address, without requiring the User Agent to match. If set to `24` hours: Attribution is allowed if the install/conversion occurs within 24 hours of the impression, when device/modeled matching aren't available.
* **Partial IP Lookback** — Uses a less precise version of the IP address. If set to `24` hours: expands probabilistic matching coverage for impression attribution.
* **Device Attribution Behavior** — Determines whether Kochava will attempt fingerprint matching when a Device ID is present on the engagement. The default is **Standard**, which means it will not attempt fingerprinting if the device ID is present.

More info [here](https://support.kochava.com/articles/campaign-management/15961-partner-reconciliation-settings).

**<u>Click Reconciliation</u>**

The Click Reconciliation settings control how Kochava attributes installs/conversions to actual ad clicks.

* **Device Lookback** — Uses device IDs to match clicks to installs/conversions. If set to `30` days: if the install/conversion happens within 30 days after clicking the ad, attribution is allowed.
* **Modeled Lookback** — Modeled Lookback determines how far back, from the time of install, to consider engagements for attribution on a Modeled based match. If set to `7` days: Attribution is allowed if the install/conversion occurs within 7 days after the click.
* **IP and Partial IP Lookback** — If set to `24` hours: Allows Kochava to use IP-only and partial-IP matching for click attribution when device/fingerprint matching aren't available.
* **Device Attribution Behavior** — Determines whether Kochava will attempt fingerprint matching when a Device ID is present on the engagement. The default is **Standard**, which means it will not attempt fingerprinting if the device ID is present.
* **Modeled Attribution Tier** — Modeled Attribution Tier determines the Modeled validation configuration. The Standard setting validates based on a combination of IP Address and User Agent. The Full IP Address setting validates based on IP Address regardless of User Agent. The Partial IP Address setting validates based on the first three stanzas of the IP Address. By default, Modeled Attribution is set to **Standard**.

More info [here](https://support.kochava.com/articles/campaign-management/15961-partner-reconciliation-settings).

## Tracking Links

### Install Tracking

<Accordion title="Click to Expand">
  1. **Add Tracking to the Campaign**
     * Log in to Kochava
     * Select the desired App
     * Go to Engagement > Campaign Manager
     * Click 'Add a Tracker' or Select Segment > 'Add a Tracker'

  <Frame>
    <img src="https://mintcdn.com/criteo-e1682996/_Y5ppJi5blUNBSuu/images/mobile-integrations/kochava/kochava_add_tracker_install_ios.png?fit=max&auto=format&n=_Y5ppJi5blUNBSuu&q=85&s=71c35d360d729c78961ba6784e5c66bf" alt="Image" width="1011" height="373" data-path="images/mobile-integrations/kochava/kochava_add_tracker_install_ios.png" />
  </Frame>

  2. **Set the Tracking**

  * **Required:**
    * Select Campaign
    * Select Segment
    * Set Tracker Name
    * Select Tracker Type: **Acquisition**
    * Select Media Partner: **Criteo New - iOS**
    * Check the box for **Share with Publisher**
    * Set Destination URL: Custom / Landing page / Google Referrer

  <Frame>
    <img src="https://mintcdn.com/criteo-e1682996/_Y5ppJi5blUNBSuu/images/mobile-integrations/kochava/kochava_set_tracking_install_ios.png?fit=max&auto=format&n=_Y5ppJi5blUNBSuu&q=85&s=3c8731d923755bd64f424923456b7405" alt="Image" width="867" height="818" data-path="images/mobile-integrations/kochava/kochava_set_tracking_install_ios.png" />
  </Frame>

  * **Optional:**
    * Agency Partner
    * UTM Parameters
    * Custom Parameters
    * Pricing

  3. **Copy Click URL and Impression URL**

  <Frame>
    <img src="https://mintcdn.com/criteo-e1682996/_Y5ppJi5blUNBSuu/images/mobile-integrations/kochava/kochava_copy_urls_install_ios.png?fit=max&auto=format&n=_Y5ppJi5blUNBSuu&q=85&s=953887f7ff432d35a1cac55e345d385d" alt="Image" width="2522" height="1672" data-path="images/mobile-integrations/kochava/kochava_copy_urls_install_ios.png" />
  </Frame>
</Accordion>

### Retargeting Tracking

<Accordion title="Click to Expand">
  1. **Add Tracking to the Campaign**
     * Log in to Kochava
     * Select the desired App
     * Go to Engagement > Campaign Manager
     * Click 'Add a Tracker' or Select Segment > 'Add a Tracker'

  <Frame>
    <img src="https://mintcdn.com/criteo-e1682996/_Y5ppJi5blUNBSuu/images/mobile-integrations/kochava/kochava_add_tracker_retargeting_ios.png?fit=max&auto=format&n=_Y5ppJi5blUNBSuu&q=85&s=38f03a8cd2b56fe61beeb1c81d80bcdd" alt="Image" width="1011" height="373" data-path="images/mobile-integrations/kochava/kochava_add_tracker_retargeting_ios.png" />
  </Frame>

  2. **Set the Tracking**
     * **Required:**
       * Select Campaign
       * Select Segment
       * Set Tracker name
       * Select Tracker Type: Reengagement
       * Select Media Partner: **Criteo New - iOS**
       * Check the box for **Share with Publisher**
       * Set Destination URL: Custom / Landing page / Google Referrer
       <Frame>
         <img src="https://mintcdn.com/criteo-e1682996/_Y5ppJi5blUNBSuu/images/mobile-integrations/kochava/kochava_set_tracking_retargeting_ios.png?fit=max&auto=format&n=_Y5ppJi5blUNBSuu&q=85&s=08aff64d92838ee696b601235b653e1e" alt="Image" width="877" height="826" data-path="images/mobile-integrations/kochava/kochava_set_tracking_retargeting_ios.png" />
       </Frame>
     * Select Event(s) for Reengagement: 'All' (if All is not selected and an event is not in the list, Criteo will not be able to effectively optimize toward the KPI events).
       <Frame>
         <img src="https://mintcdn.com/criteo-e1682996/_Y5ppJi5blUNBSuu/images/mobile-integrations/kochava/kochava_select_events_retargeting_ios.png?fit=max&auto=format&n=_Y5ppJi5blUNBSuu&q=85&s=b97a559ffb9a8c6e88569b66c09b94ab" alt="Image" width="718" height="165" data-path="images/mobile-integrations/kochava/kochava_select_events_retargeting_ios.png" />
       </Frame>
     * **Optional:**
       * Agency Partner
       * UTM Parameters
       * Custom Parameters
       * Pricing
  3. **Set a custom lookback window**
     * Tracker-level lookback windows can be set within Power Editor → Tracker Overrides, however this is a paid feature of Kochava.
  4. **Copy Click URL and Impression URL and send to your Criteo contact**

  <Frame>
    <img src="https://mintcdn.com/criteo-e1682996/_Y5ppJi5blUNBSuu/images/mobile-integrations/kochava/kochava_copy_urls_retargeting_ios.png?fit=max&auto=format&n=_Y5ppJi5blUNBSuu&q=85&s=5f999cd6bea157343c1d31e03f2c799a" alt="Image" width="2378" height="1556" data-path="images/mobile-integrations/kochava/kochava_copy_urls_retargeting_ios.png" />
  </Frame>
</Accordion>

## Catalog Feed

A catalog feed is an XML or a CSV file containing product information (name, price, deep link, image link…) that allows Criteo to dynamically generate product-level banners tailored to each user. Therefore, it is important to keep this file up to date in order for Criteo to show the right data in your banners.

The following points need to be kept in mind:

* Each product must have a unique ID that must be identical to the one passed in the events.
* The catalog feed must contain all or at least most of your apps' products for Retail apps, and hotels/airline routes for Travel apps.
* Recommended image resolution is 300x300 pixels to 400x400 pixels.

Note: In some instances (i.e. live campaigns on mobile web or desktop), Criteo will already have the catalog feed.

For more information, please request the dedicated guide from your contact.

## Testing Process

Once all events and postbacks have been implemented, you should contact your Criteo representative to begin the testing phase.

<Warning>
  If you are adding/updating Kochava app events, this will require a release to the app store. In this case, please allow sufficient time (at least a week) for testing **prior** to the app submission in order to ensure that the data you are sending is complete.
</Warning>

Criteo requires the following elements:

* App build to test the collection of events on Criteo side.
* If testing remotely, the IDFA of the test device.
* (For Retargeting) Deeplink and Universal Link examples — homepage & product details page.