Kahuna provides push messaging services that are based on real-time user analytics. mParticle fully supports Kahuna with a Kahuna-specific embedded software kit. This allows Kahuna clients to realize the full benefit of Kahuna capabilities and still deploy a single SDK with mParticle.
In order to deploy Kahuna the following major steps are required:
Go through the standard Kahuna implementation process with your Kahuna customer success representative, including completion of your Kahuna blueprint.
Create a Kahuna output configuration:
Connect inputs to the Kahuna output configuration
mParticle forwarding will filter any data that is sent to Kahuna based upon what is entered into the Event name list and Event attribute list to ensure that Kahuna is only receiving event data that is part of your Kahuna blueprint. In other words, if an event or event attribute is detected that is not on the event name list / event attribute list, mParticle will not forward that event data to Kahuna.
You should always validate that your integration setup is working as desired before moving on to additional integration setups and/or the final step of submitting your app to the app store. mParticle recommends the following quality assurance measures:
For inbound messages, in order to confirm that your instrumented app is receiving inbound events, you will need to log into mParticle, choose your workspace, click Connections, Live Stream from the left navigation panel. Once everything looks fine, enable the Kahuna connection and inspect that outbound messages are flowing as expected.
As long as the Kahuna Kit is included in your app, mParticle will pass any Push Notifications from Kahuna to the kit for display. However, you will need to provide credentials in the Kahuna dashboard.
For Android push notifications you will need to provide your Server Key to Kahuna. See the Kahuna documentation for more.
For iOS push notifications you will need to upload your APNs Push SSL certificate to Kahuna. See the Kahuna documentation for more.
Depending upon when you implement Kahuna in relation to your mParticle implementation, your deployment sequence may be slightly different. Let’s look at 3 basic implementation scenarios:
A. Implementing Kahuna and mParticle at the same time:
In this scenario you would:
B. Have already instrumented your app using mParticle, and now want to implement Kahuna:
In this scenario you would:
C. Already have been working with Kahuna, and now want to implement mParticle:
|Setting Name||Data Type||Default Value||Description|
||Your application’s Secret Key value, found on the Configuration tab of the Kahuna Settings page|
|Setting Name||Data Type||Default Value||Platform||Description|
|Send transaction data||
||False||All||If true, transaction events will be forwarded to Kahuna|
|Event name list||
||All||List of event names that will be forwarded to Kahuna. For example: flight_selected. Each name in this list must be entered on its own line. This field is no longer used starting with mParticle IOS SDK 3.5.0, Android SDK 2.4.0.|
|Event attribute list||
||All||List of event attributes that will be forwarded to Kahuna as user attributes. Each attribute in this list must be entered on its own line. This field is no longer used starting with mParticle IOS SDK 3.5.0, Android SDK 2.4.0.|
Was this page helpful?