Tracking clicks before installing applications?

Question

What i want to do

I want to track updates from the lite version to the paid version of the application, including: a) clicks on the CTA to update; b) conversions from clicks to actual installs; c) how does this cohort of users who clicked on behavior differ, if at all, from users who opened the application using other means. This, of course, is for an application that does not have built-in applications.

b) is the most important.

Context

I looked at several services that allow you to track clicks before installing the application -

• Distimo - http://www.distimo.com/app-analytics#conversion-tracking

• Apsalar - https://apsalar.com/products/apscience/

• I saw that you cannot get iOS IDFA from mobile safari.

• I also saw in iOS7 that you cannot use the MAC address as a unique identifier

As I understand it, how it works (using the Apsalar example)

• Apsalar provides a custom URL
• When the URL starts, it checks if a cookie exists for this device, if not a unique code is generated on the server side and a cookie is installed on the device.
• The first time you start the paid version of the application, the Apsalar SDK is installed, so does the Apsalar code somehow check if the cookie is issued? -

Question

How it works? Or what range of options? Of course, in my case, I get IDFA devices in the lite version of the application if they click to update. And check if the IDFA will appear later in the list of paid users. But I guess it will take a decent time.

Update # 1

So, having received the Distimo electronic feedback form, it looks like fingerprints using the device.

Update # 2

It would be better to use the identifierForVendor call to create a unique #, which I then pass to the analytics package, so I track individual users between Lite and paid versions of the application?

Answer 1

Only answer points a) and b).

You can use IDFA to track user clicks for updates, actual conversions, and to identify individual users between the paid and light versions of your application.

Since all activities are performed inside the application, you can simply send an HTTP request to your server using the IDFA hash, or you can even use IDFA directly, since it is confidential to track all users who click the update button.

In your paid application inside applicationdidfinishlaunching send an HTTP request to your server with an IDFA / IDFA hash and set NSUserDefault with IDFA (or any other line) as the key and IDFA value as in your application to note that you have already sent IDFA to your server. Therefore, when the application is (closed and) launched, you will need to check the value against the key ("IDFA" or that you installed it), and if the value matches your IDFA, you do not need to send a server message.

If the user resets their IDFA, you can send a message to your server with the old IDFA, as well as with the new IDFA. This will help you better track the user.

Hope this helps.

Also, could you talk about point c)?