Using a 3rd party tracker

If the app has integrated a SDK different of the eMMa SDK you can get the conversions in real time in your eMMa account through the server to server pixel.

STEP-BY-STEP GUIDE

  1. Set the eMMa pixel in the 3rd party tracker
    • http://eat.emmasolutions.net/postback?eid=[eMMa_ID]

      In the click event, eMMa will redirect the user to the 3rd party tracker URL adding the [eMMa ID] as a parameter

      E.g. http://www.yoururl.com?eid=[eMMa_ID]

      The variable eid gives the value of the eMMa ID. The 3rd party tracker must return this parameter in the conversion event as detailed.

  2. Set your eMMa campaign with the tracking link the 3rd party tracker sent. Have a look to this post to create new apptracker campaigns.

  3. Create the different sources or tracking links into your new campaign introducing the transaction id parameter name the 3rd party needs.

    By default eMMa send the variable eid but you can replace it into the source edition:

    • Use the parameter exid if it’s an eMMa account the one is going to notify the conversion.

    • Use the parameter aid if it’s an AppBurn the one is going to notify the conversion.

    • Use the parameter aff_sub if it’s Hasoffers the one is going to notify the conversion.

    • Use the parameter tags if it’s ClicksMob the one is going to notify the conversion.

    • Use the parameter eid (not replacing needed) if it’s Appsflyer the one is going to notify the conversion.

    • Contact with the 3rd party tracking team to get the transaction id, for other server to server conversion notifications.

 

Have more questions? Submit a request

0 Comments

Article is closed for comments.