Frequently Asked Questions (FAQs)

Why do you say that SDKs are better than Server-to-Server integration?

Simply put, if you use our SDKs, then that gives us the best chance to match your conversions from click to conversion.

When you use a third party or supply the IDs to us yourself, there are added steps that can possibly introduce inconsistencies between the data sent to us and what we have within our platform.

Our SDKs have been thoroughly tested and are better integrated, so you are given the best chance for conversion matching leading to tangible results.

What if I don’t want to use a full SDK?

If you want a more lightweight SDK that’s focused specifically on advertiser needs, then we are also offering the App Tracking SDKs for Android and iOS as alternatives. Both are just one file and a short code snippet that you’ll need to add into your application.

What are the App Tracking ID and Tracking ID?

These are also known as the Goal ID. We use the terms App Tracking ID for in-app conversion tracking, and Tracking ID for mobile web conversion tracking.

How can I get a Tracking ID?

Once you have registered, you may request an Tracking ID yourself in mMedia by following the steps here.

If you are not using mmedia.com for your advertising needs, contact your Account Manager or contact us to hear from a trained support professional.

What do each of the parameters of the API call represent?

For Android, the App Tracking ID or Tracking ID and Android Advertising ID (AAID) or Hashed Android ID (MMDID) are passed. The App Tracking ID is what you use in the Goal ID parameter to track that specific type of conversion, and the Android Advertising ID or Hashed Android ID provides a device ID to track the event to completion.

For iOS, the App Tracking ID, Hashed Advertising Identifier (HAID) are passed for for iOS version 6 and up. The App Tracking ID and Wifi MAC address (MMDID) are passed for iOS versions prior to 6. Like with Android, the App Tracking ID or Tracking ID is what is used in the Goal ID parameter as the specific type of conversion. To get the device ID, though, the HAID is passed for iOS 6+ and the Hashed WiFi MAC Address is passed for iOS versons prior to 6.

For iOS 6+, you should use the Hashed Advertising Identifier (HAID). For iOS versions, prior to 6, you should be using the WiFi MAC Address. Go here to find and hash the Identifier for Advertisers (IDFA).

The IDFA is the preferred ID to use starting with iOS 6. If your app runs on older versions than iOS 6, we will need the WiFi Mac address to be hashed and passed in.

My ID doesn’t seem to be working. What’s happening?

If your ID doesn’t seem to be matching during testing, you may want to check your hashing. A frequent problem that users find is that they are not hashing the raw version of the ID. Remember that capitalization is important. For example, hashing aBC123 may not be the same as hashing ABC123 or abc123.

If you are using the raw version, please contact your Account Manager or contact us to reach a trained support professional.

What is the AAID?

The advertising ID is a user-specific, unique, resettable ID for advertising, provided by Google Play services.

What is the MMDID?

The ID that we use for Android conversion tracking is simply a hashed version of the device’s Android ID. For iOS it is simply a hashed MAC address.

What is the HAID?

Starting with iOS Version 6, the Identifier for Advertisers (IDFA) is being used for mobile advertising. The HAID is a hashed version of the IDFA.

How do I find these IDs?

What ways do you use this data?

We only use the data that you pass us to improve your mobile advertising experience and results. We take privacy very seriously, and anyone is able to opt out of us using these IDs for mobile advertising. We encourage you to check out our company’s Privacy Policy

What is hashing?

Hashing is a process by which you can encode the IDs that you send us to use for conversion tracking and mobile advertising.