Optimization and retargeting to in-app events

Data format for Text & Image Ads

Rich In-App Events are supported.

Data format for smart banners and dynamic ads

The following Rich In-App Events are required:

• af_content_view: Product viewed.
• af_add_to_cart: Added to cart.
• remove_from_cart: Product removed from cart.
• af_purchase: Purchased.

Make sure to add the af_content_id parameter used to pass the product ID to all the events.

For more information, see your MMP's documentation for implementing the event code.

Requirements for the “Target cost revenue ratio” strategy

You need to set up revenue collection in the af_revenue parameter for in-app events. Instructions for developers:

• Android
• iOS

Data format for Text & Image Ads

All Adjust events are supported.

Data format for smart banners and dynamic ads

The format supports events with Partner Parameters (available in the Adjust SDK version 4.0 or higher) that expect offer_id, which can either be a Product ID or a list of products in JSON format.

Example of an event with one Product ID

AdjustEvent event = new AdjustEvent("VIEWED_CONTENT");
event.addPartnerParameter("offer_id", "10001");
Adjust.trackEvent(event);

Example of an event with a list of products

AdjustEvent event = new AdjustEvent("PURCHASED");
event.addPartnerParameter("offer_id", "[\"1234\",\"5678\"]");
Adjust.trackEvent(event);

If a product ID is used in event parameters, but its name differs from offer_id, then you don't need to make any edits to your app: you can edit this value when setting up event transmission to Yandex Direct using Parameter Mapping.

Attribution using deeplink tracking

Adjust needs to support deeplink tracking so it can attribute conversions after clicking to an app. Instructions for developers:

• Android
• iOS

Requirements for the “Target cost revenue ratio” strategy

You need to set up revenue collection in your in-app events. Instructions for developers:

• Android
• iOS

Transmitting events

Configure Adjust according to the recommendations:

1. In the Yandex Ecom Feed Counter ID field, specify the Yandex Metrica tag for the site.
2. In the Event Linking section, configure event transmission:

   • Product viewed: Viewed content.
   • Product added to cart: Added to cart.
   • Product removed from cart: Removed from cart.
   • Purchase: Purchased.
3. Enable Parameter Forwarding.
4. Enable In-App Revenue Forwarding.

If the parameter names in events deviate from requirements, map the parameters using Parameter Mapping

If a product ID is used in event parameters, but its name differs from offer_id, set up mapping for the event transmission.

General setup rules

1. Open the Integrated Partners section and select Yandex Direct.
2. Go to the Integration tab.
3. Enable Activate partner.
4. In the Yandex App ID field, specify the App ID that you obtained when adding your mobile app to Yandex Direct.
5. Enable In-app events postback to send events.
6. Select events and set up SDK Event Name > Partner Event Identifier mapping. Use the EVENT_1, EVENT_2, or EVENT_3 identifiers if none of the presets suits you.

7. Select Sending option: All media sources, including organic and Send revenue: Values & revenue to transmit revenue and event parameters.

Requirements for smart banners and dynamic ads

1. In the Yandex Ecom Feed ID field, specify the Yandex Metrica tag in 12345 format.

   We recommend that you use the tag for the site where you have set up e-commerce: in this case, machine learning algorithms will include products viewed in the app for site users, and the other way round. This helps you increase the effectiveness of retargeting.

2. Select the events:

   • af_content_view > VIEWED_CONTENT (required).
   • af_added_to_cart > ADDED_TO_CART (required);
   • remove_from_cart > REMOVED_FROM_CART (recommended).
   • af_purchase > PURCHASED (required).
3. Select Sending option: All media sources, including organic and Send revenue: Values & revenue to transmit revenue and event parameters.

Requirements for the “Target cost revenue ratio” strategy

Select Send revenue: Values & revenue to transmit the revenue.

General setup rules

1. Go to the app settings and open Partner Setup.
2. Select Add Partner → Yandex Direct → (+).
3. In the Yandex App ID field, specify the App ID that you obtained when adding your mobile app to Yandex Direct.
4. Enable In-App Revenue Forwarding, Parameter Forwarding, and Session Forwarding.
5. Set up event transmission in Event Linking by selecting the appropriate name from the list. All settings are specified for iOS and Android separately.

Requirements for smart banners and dynamic ads

1. In the Yandex Ecom Feed ID field, specify the Yandex Metrica tag in 12345 format.

   We recommend that you use the tag for the site where you have set up e-commerce: in this case, machine learning algorithms will include products viewed in the app for site users, and the other way round. This helps you increase the effectiveness of retargeting.

2. In the Event Linking section, configure event transmission:

   • Product viewed: Viewed content (required).
   • Product added to cart: Added to cart (required).
   • Product removed from cart: Removed from cart (recommended).
   • Purchased: Purchased (required).
3. If, in the event parameters, the Product ID isn't named offer_id, click Partner Parameter Mapping. In the FROM APP field, enter the parameter's name in the SDK, and in the TO PARTNER field, specify the offer_id.

Universal links

No other changes to the link are required. Clicks will be sent from Yandex Direct to AppsFlyer using the server-to-server tracking method.

Cross-server click sending is enabled when you set up a campaign in Yandex Direct. Start creating a campaign, select a goal for your mobile app. After that, a section will appear below on the page where you can enable sending clicks to your MMP.

Universal links

Add the following parameters to the universal link:

• adjust_ya_click_id={logid}
• adjust_campaign={campaign_name}
• adjust_t=abc_def: Enter the MMP's ID instead of abc for Android and instead of def for iOS. Leave an underscore in the middle. If your app is multi-platform, specify a single MMP ID: adjust_t=abc. You can use the the adjust_tracker parameter instead of adjust_t.

Sample link:

Check the AppsFlyer Help to learn how to enable it.

Required parameters

• pid=yandexdirect_int
• clickid={logid}
• is_retargeting=true.

Optional parameters:

• af_click_lookback: The attribution window (between the click and opening the app). It's specified in days (for example, 14d). The default value (if you don't pass this parameter) is 7 days.
• af_reengagement_window: The re-engagement window (between attribution and conversion). It's specified in days. The default value is 30 days.

To set up UTM tags and other custom parameters, go to the OneLink template settings.

Sample link:

See also Tracking links based on Universal Links.

The Adjust documentation describes:

• How to set up Universal Links .
• How to create a tracking link.

Required parameters

• In the tracking link: adj_ya_click_id={logid} or adjust_ya_click_id={logid}.
• In the fallback URL inside the tracking link: yclid={logid}

UTM tags are specified in the fallback URL.

Sample link:

See also Tracking links based on Universal Links.