Mobile Tracking Parameters

Mobile Tracking Parameters

As more and more people come to rely on their mobile devices to live, socialize, and play, the demand for mobile apps has never been greater. The mobile application ecosystem has exploded over the past few years, so has the demand for performance-based marketing initiatives. Being someone that works in performance marketing, you want to know where your users and installs come from, and you want to make sure that your affiliates are sending in valid, high-quality leads. HasOffers has always built upon its rock-solid foundations for affiliate attribution and now offers an expansion into the mobile marketing space by extending the amount of data that your network can collect.

With our mobile tracking parameters, we extend your network's ability to receive data parameters; i.e. those that are specific to the mobile space. This means you can dive into much more detail for each conversion that your system receives for a mobile-based offer. This is a great value in getting concrete, relevant information about what kind of users are installing apps from your offers, and all the unique data that shows that each install is unique. If you are working with a MoblieAppTracking client, then good news! Our mobile tracking parameters match up exactly with their parameter set, so tracking between your affiliate network and the MobileAppTracking client will be highly accurate and transparent; two critical elements when tracking between multiple systems.


How It Works

On a typical setup between your HasOffers network and a mobile app tracking client, you will be directing traffic to MobileAppTracking client through an offer. This will create a session in you and the MobileAppTracking client and they will redirect to the app install page:

Once the user has chosen to install the app on their mobile device, the install event will be triggered in the MobileAppTracking SDK and will then call your networks postback URL, passing back your systems transaction ID to record the conversion as well as any desired parameters from their system:

While the example above shows how this attribution is used with MobileAppTracking, this functionality should work with any mobile attribution provider.

Getting Started

The first step is to enable the mobile tracking parameters in your system to head on over to Company > Customize Application > Tracking Settings. In there you want to scroll down to the setting "Show Mobile Tracking Parameters" and set it to enabled. All this will do is turn on the mobile tracking parameters for your reporting, if it is enabled the values can still be passed and stored in your network data, even if it is not visible.

It might be worth mentioning that HasOffers does not gather this information automatically, it has to be setup in the postback and macros should be added on the MobileAppTracking side so that these values can show in HasOffers. The MobileAppTracking SDK will get all these values and pass them on when the event/install takes place.

Note: Only Enterprise clients have mobile tracking parameters available for their network.

Supported Tracking Parameters

The following parameters are currently supported:

  • device_brand
  • device_model
  • device_os
  • device_os_version
  • device_id
  • device_id_md5
  • device_id_sha1
  • google_aid
  • google_aid_md5
  • google_aid_sha1
  • android_id
  • android_id_md5
  • android_id_sha1
  • mac_address
  • mac_address_md5
  • mac_address_sha1
  • odin
  • open_udid
  • ios_ifa
  • ios_ifa_md5
  • ios_ifa_sha1
  • ios_ifv
  • user_id
  • unid

To understand what each of these values relate to, see this article on the MobileAppTracking site for their descriptions:

These values can be passed into a HasOffers tracking link, impression pixel, or conversion tracking methods, as well as macros in affiliate pixels and postbacks. To pass the value onto an affiliate pixel/postback, simply wrap the field name with curly brackets { }. Here is how the device_id macro would look like:

{device_id}

These variables are made to help track back which conversions come from which device. However they do not help authenticate the conversion in HasOffers, which is still done with the transaction ID. These values are also not required to be passed in the tracking URL.

Passing Mobile Parameters Into Your Network

Currently your network will allow you to pass these parameters at the impression, the click and the conversion. Here are a few examples to give you an idea of how you can set these up. In these examples we are only passing in the device ID and and the MAC address to keep things simple, you can add as many or as few parameters as you need.

On Impression

To pass on impression, simply pass in the values by adding them to the end of the impression pixel URL:

These values will be passed to the click server logs upon click.

On Click

The same rules apply for tracking clicks, only the values will be written to the raw click logs:

http://demo.go2jump.org/aff_c?offer_id=2&aff_id=1&device_id=868652013311575&mac_address=EC:85:2F:99:49:22

On Conversion

When passing these values on conversion, the format is:

http://demo.go2jump.org/aff_lsr?transaction_id=10234698450382&device_id=868652013311575&mac_address=EC:85:2F:99:49:22

When this fires, the postback will then be able to post these values into the conversion report where you can see them.

Viewing the mobile tracking parameters in your reports, you can currently view them in your click log CSV files, and as selectable columns in the Conversion Report. They are all grouped together in the data section in the ‘Mobile Data’ section:

Currently only conversions that are setup as postbacks (aff_lsr in the URL) will display in the conversion report. If you try to pass the mobile parameters with a pixel URL like this:

http://demo.go2jump.org/aff_l?offer_id=2&device_id=868652013311575&mac_address=EC:85:2F:99:49:22

The mobile parameters will not be passed. Only URLs that contain "aff_lsr" will pass these parameters to the Conversion Report.

Integration with MobileAppTracking

With mobile parameters being passed into HasOffers networks, the ability to pass in more information will help properly attribute conversions correctly. Luckily, HasOffers and MobileAppTracking are designed to work together passing this data.

On HasOffers side, grab the publisher link generated in from MobileAppTracking and use this format as your default offer URL for your offer:

http://hastrk1.com/serve?action=click&publisher_id=10010&site_id=2969&campaign_id=237911&sub_publisher={affiliate_id}&sub_campaign={offer_id}&ref_id={transaction_id}

If you need help in setting up your network as a publisher on the mobile app tracking side, then this article will show you how to setup a HasOffers client as a publisher.

Then, have the offer postback added into the MobileAppTracking interface so that conversions can be tracked accordingly in both systems:

http://demo.go2cloud.org/aff_lsr?transaction_id={publisher_ref_id}&device_id={device_id}&mac_address={mac_address}
Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk