You can use the conversion object to define any one of the in-app events based on your objective. Conversion count and CPA are the additional metrics that Kayzen will be able to measure in the UI and in the reports after you define a conversion object.
If your objective is to focus on users who verify their email after registration, and you pass an in-app event (by MMP or Event API) “email_verified”, you can define a conversion object for the event “email_verified”.
Similarly, if your objective is to focus on the purchase of products in your app, and you pass an in-app event (by MMP or Event API) “purchase” to Kayzen, you can define a conversion object for the event “purchase”
Based on the above two examples, the conversion object is flexibly defined and can totally depend on what your focus is on.
Once a conversion object is enabled it can be edited or deleted by contacting your programmatic success manager only (currently not possible through the UI).
Only one conversion object can be created for each App. Android and iOS versions of the same app are treated as different apps in Kayzen and hence you can have separate conversion objects for android and iOS versions of the same app.
Once your conversion object is created, you will be able to track CPA and count the number of conversions on the Dashboard and Campaigns pages.
Steps to create Conversion Object
You can create a conversion object under Admin Console > Settings tab. If you have an Enterprise account, you would need to select an advertiser first and then go to the Settings tab.
Conversion event: depending on your objective you can choose any one event that is passed by your MMP (or to Kayzen using Events API) to create a conversion object.
Attribution Type: you can specify the attribution type to be either Click-Through (CT) or View-Through (VT) or Total, which is a sum of both CT and VT.
Allowed conversion per User: there are two options available, one is to count every conversion and the other is to count 1 conversion (unique) per user as per the defined time window. Example: assume you choose 2nd option and time period is set to 30 days, if a user X has triggered a conversion event on the 7th day and again on 28th day, in this case, Kayzen will record only one conversion for this user, though this user has triggered two events.
Unique user per actions: in this section, we are counting the number of unique users for a defined time window. Example: assuming you defined the time period to be 30 days, user X has triggered a conversion event on the 7th day and again on the 35th day, in this case, Kayzen counts as two unique users. Reason being, the second event triggered on the 35th day is counted as one more unique user, as this event is triggered after the defined time window of 30 days.