EMMA Pixel s2s Integration

If your app has integrated a different SDK than EMMA SDK, or you want to measure conversions of a mobile web, you can follow up these attribution in your EMMA dashboard through a pixel server to server.

1. You should configure the EMMA pixel in the 3rd party tracker or in your mobile web. This postback should be called every time there are conversions. 

  • http://eat.emmasolutions.net/postback?eid=[CLICK_ID]

The "eid" variable will be sent by EMMA through the redirect. This variable should be catched and completed in the postback for doing match between the EMMA Click and the attribution.

2. Set up your campaign in the dashboard of EMMA with the tracking link that the 3rd party tracker send you. Visit this article to create new campaigns in the AppTracker:

When a click was produced through the tracking link, EMMA will redirect the user to the destination URL by adding the [CLICK ID] as parameter.

For example:

EMMA Tracking Link :


The EMMA tracking link redirect to http://www.yoururl.com?eid=[CLICK_ID]

3. You can create different sources or tracking links in your new campaign by introducing the parameter name click id , that the 3rd party tracker or the msite needs to capture this value.

Automatically, EMMA uses the eid variable to send the CLICK_ID, but you can replace editing the source:

  • Use the exid parameter if it´s another EMMA account that will notify the conversion. 

  • Use the aid parameter if it´ll notify the conversion from AppBurn. 

  • Use the aff_sub parameter if it´ll notify the conversion from Hasoffers. 

  • Use the tags parameter if it´ll notify the conversion from ClicksMob

  • Use the eid parameter( it isn´t required to replace) if it´ll notify the conversion from Appsflyer. 

  • Make contact with the 3rd party tracking team to get the click id for others notification of server to server conversations. 

Have more questions? Submit a request


Article is closed for comments.