Follow

Configuring Kahuna integration to track custom In-App message events

Kahuna’s SDKs offer In-App message templates that integrate automatically with engagement and click tracking on the campaign performance page. However, if a customer would prefer to use their own In-App templates the ability to track clicks and message engagement is lost.

Due to custom In-App templates being unique for every customer, there are not standard sets of buttons or actions that Kahuna can anticipate.

To help update your integration to allow for tracking within customer In-App messages, please follow the below documentation to update your settings. There are only a handful of requirements when tracking these events, and the rest are only meant to provide a finer grain tool to segment users based on their responses to these messages.

"Yes" Response Event:

A “Yes” event is a positive response of your In-App message
Event name: k_iam_clicked
Event Properties: The event properties need to be filled in with values passed to the app as deep link parameters. These keys are the keys that need to be added to the k_iam_clicked event, but the values are filled in with values from the initial message payload.

Key Value
k_c deep_link_params["k_cid"]
k_cg deep_link_params["k_cg"]
k_cs deep_link_params["k_cs"]
trackingId deep_link_params["trackingId"]
action_url (optional) Whatever value you would like to track if the “Yes” response sends the user to a deeplink within the app or a webpage outside of the app
button (optional) Any value you would like to track WHICH button was pressed. If there are multiple "Yes" responses, which yes?

 

"No" Response Event:

A “No” event is a negative response of your In-App message
Event name: k_iam_dismissed
Event Properties: The event properties need to be filled in with values passed to the app as deep link parameters. These keys are the keys that need to be added to the clicked event, but the values are filled in with values from the initial message payload

Key Value
k_c deep_link_params["k_cid"]
k_cg deep_link_params["k_cg"]
k_cs deep_link_params["k_cs"]
trackingId deep_link_params["trackingId"]
action_url (optional) Whatever value you would like to track if the “No” response sends the user to a deeplink within the app or a webpage outside of the app
button (optional) Any value you would like to track WHICH button was pressed. If there are multiple "No" responses, which yes?

 

"Displayed" Response Event:

The “Displayed” event is that the In-App message was shown on the device
Event name: k_iam_displayed
Event Properties: The event properties need to be filled in with values passed to the app as deep link parameters. These keys are the keys that need to be added to the clicked event, but the values are filled in with values from the initial message payload.

Key Value
k_c deep_link_params["k_cid"]
k_cg deep_link_params["k_cg"]
k_cs deep_link_params["k_cs"]
trackingId deep_link_params["trackingId"]

 

"Not Displayed" Response Event:

The “Not Displayed” event occurs when the In-App message is received but not shown on the device due to expiration. The expiration field (deep_link_params[“k_t”] is the latest timestamp that the message should be displayed, stored as the

Event name: k_iam_not_displayed
Event Properties: The event properties need to be filled in with values passed to the app as deep link parameters. These keys are the keys that need to be added to the clicked event, but the values are filled in with values from the initial message payload.

Key Value
k_c deep_link_params["k_cid"]
k_cg deep_link_params["k_cg"]
k_cs deep_link_params["k_cs"]
trackingId deep_link_params["trackingId"]
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments