Pixel Install for Mobile Measurement Platforms

To fire an Audiohook pixel on transactions in mobile apps that use Mobile Measurement

Platforms (MMPs) like Kochava or AppsFlyer, you'll need to follow these steps:

1. Understand the MMP's SDK integration: Familiarize yourself with the specific MMP's documentation (Kochava or AppsFlyer). This will give you an understanding of how to integrate their SDK into your mobile app and use their features effectively. Kochava documentation: https://support.kochava.com/sdk-integration/ AppsFlyer documentation: https://support.appsflyer.com/hc/en-us/sections/6551164458257-Integrate-the-AppsFlyer-SDK 2. Integrate MMPs SDK: Implement the MMPs SDK in your mobile app by following their documentation guidelines. This usually involves adding the SDK to your project and initializing it in your code. 3. Configure in-app events: Identify the specific transaction event for which you want to trigger the Audiohook pixel. Configure this event within the MMPs dashboard and map it to the corresponding in-app event in your app. 4. Add the Audiohook pixel: If your marketing partner supports server-to-server (S2S) post-backs, you can set up a post-back URL with your marketing partner. This URL will include the Audiohook pixel and other necessary parameters. Configure the post-back URL in your MMP's dashboard to send event data to your marketing partner. For Kochava: https://support.kochava.com/campaign-management/create-a-kochava-certified-postback/ For AppsFlyer: https://support.appsflyer.com/hc/en-us/articles/207032126-Server-to-server-S2S-integration 5. Test the integration: Once you've configured the Audiohook pixel and set up the post-back URL, test the integration by triggering the transaction event in your app. Use your MMP's dashboard to verify that the event data is being sent to your marketing partner correctly.

By following these steps, you should be able to fire an Audiohook pixel on transactions in mobile apps using MMPs like Kochava or AppsFlyer. Make sure to consult the specific documentation for each platform, as they may have unique requirements or processes.