What is the traffic source for all of your app installations?
We all know where our customers visit our web site from, what campaign led us to the highest conversions, what is the best keyword that drives the most valuable customers.
In apps we tend to lose it, there are many vendors such as AppsFlyer and Kochava that track all apps installs and support very good marketing analysis.
Their advantage is that this is what they do, so they do it best, they have integration with Facebook and all you need to do is install their SDK in your app and you’re done. Ahh, and they charge few cents every time someone downloads your app.
If you’re reading these lines you are probably an advanced GA user, you enjoy all of the analyzing benefits GA provides: User, session and hits segmentation, custom dimension and custom metrics in various scopes, custom report, adding secondary dimension anywhere, viewing up to 20 different goals achievement etc.
Well, none of these are possible in with any of these vendors.
What if GA could also track the traffic source that led to the installation?
I’ll take you through all of the stages you need to do in order to get to the report as seen in Figure A
Figure A: Report that presents number of first visit after install, visits and duration average
This article refers to Android app’s:
Step 1: Install the Google play SDK
Step 2: Enable Advertising Features
Under Admin, Property, go to Property Settings, then under Advertising Features, as seen in Figure B, (Enable Demographics and Interest Reports) switch the button to ON.
Figure B: Enabling Advertising Features
Step 3: Link your Google Play account
Under Admin, Property, go to All Products, then hit the button “Link Google Play” or as seen in figure C, “Adjust Link” – this is because I’ve linked it already.
Figure C: Linking Google Play account with the Google Analytics Property
Choose the relevant app in case you have more than one, hit continue and then save.
Notice that this linking can only be done by someone who has Edit permission in Google Analytics. This means you are using the same email address in both the Play Developer Console and in the Analytics account. Linking a Google Analytics account that’s associated with one email address with a Google Play Developer Console that’s associated with a different address, is currently not supported.
Step 4: Enable the IDFA collection
enabled true if the advertising information should be collected. False otherwise.
This sets whether the advertising id and ad targeting preference should be collected while sending hits to GA servers. The collection of advertising id and the ad targeting preference is disabled by default and needs to be turned on for mobile audience features and any other features that require advertising id.
Step 5: Update your project’s AndroidMenifest.xml file to include the INTERNET and ACCESS_NETWORK_STATE permissions:
android:name=”AnalyticsApplication”> … </application> </manifest>