The following document defined the process for creating a reengagement Campaign within Kochava. If you are planning on running a re-install Reengagement campaign you will want to first make sure you have updated the install reprocessing lookback window, this process is outlined here.
NOTE: The Reengagement Campaign setup process for iOS and Android is similar and therefore this document will cover the setup for both operating systems, with specific differences noted.
Create a Reengagement Campaign
- Log in to Kochava.
- Locate the desired app.
- Select App Tools>Campaign Manager.
- Click Add a Tracker or Select Segment Tools>Add a Tracker.
- Enter Tracker Name.
- Select Tracker Type>Reengagement.
- Select a Media Partner.
- Select a Agency Partner. (optional)
- Enter an Install URL.
- Enter a Deeplink. (optional)
- Enter a Custom Parameter. (optional)
- Enter Pricing Type and Target Pricing. (optional)
- Select Event(s) for Reengagement attribution.
- Click Save (If no further trackers need to be created).
- Click Save & Add Another Tracker (If additional trackers need to be created).
a. Select the Campaign.
b. Select the Segment.
NOTE: In order to streamline the Campaign/Segment/Tracker creation process a feature has been added to allow the creation of campaigns and segments while creating a new tracker. For more information about creating a campaign or segment while adding a new tracker, refer to our Create an Install Campaign support document. support documentation.
NOTE: The Share With Publisher setting allows the associated publisher to view the settings for this tracker. If unchecked, the associated publisher will not be able to view the settings for this tracker.
NOTE: For more information about deeplinks, refer to our Deep Linking support documentation.
NOTE: The selected event(s) will be the point of conversion for the reengagment campaign. Attribution will be awarded to the click that led to the reengament event based on attribution configuration. Any LTV (Lifetime Value) will also be awarded to the source that drove the reengagement.
NOTE: The lookback window for each post-install event may be individually set. For more information on setting an event lookback window, refer to our Post-Install Event Creation and Configuration support documentation.
NOTE: If an event that is required for reengagement is not present, ensure that the event is being passed to Kochava via the SDK or Server-to-Server integration.
A. Campaign and Segment selection/creation section.
B. Select Event(s) for Reengagement
Minimum Time to Reengagement
Minimum Time to Reengagement (MTR) settings within Kochava provides the ability to establish specific lookback windows for any post-install event. MTR settings provide the ability to set a window for how long after attribution occurs that a device can then be eligible to be re-attributed for a reengagement campaign. For more information on setting an event lookback window, refer to our Post-Install Event Creation and Configuration support documentation.
NOTE: The “mtr_rejected”:”86400″ flag being present in the custom_dimensions column in an event detail report indicates that that instance of the event did not meet the minimum time to reengagement requirements and that it is not eligible for reengagement. This feature can be configured in the dashboard under the “Events” tab. By default, it is set to 24 hours, which is why you see “mtr_rejected”:”86400”, 86400 = amount of seconds in 24 hours.