How does Countly track installs?
By default, Countly creates a unique URL link that points to Countly server when you create a campaign. This unique clickthrough link then can be used to integrate with your campaign so you first forward your users to Countly server, and Countly server forwards this request to your provided address (for example, corresponding application store, as you can provide different links for different platforms in the same campaign).
Inbetween these actions, Countly keeps a record of fingerprint of the user device. When the user opens the app first time, this fingerprint information is matched with the record that was previously saved. If there's a match, then the user is set as "acquired".
Specifically for Google Play, campaign information is simply passed to the device when user first installs the app. Upon initial launch, this information is sent to Countly servers, and user is counted as "acquired".
What device identifiers do you use to do the attribution?
If use digital fingerprint is checked, then Countly will use all information it can gather from device, usually it is IP address, platform, paltform version, screen resolution.
If digital fingerprint is not used, Countly only uses IP address to match device, which will allow tracking across multiple platforms, as click on Windows and installation on Android. But may also result in more false positives.
Note: digital fingerprint or IP address is only stored for 1 hour after the click. If during that hour user does not install your app, matching information expires, until next assist click.
Which editions is Attribution Analytics available for?
Attribution Analytics is available for Enterprise Edition.
Which SDKs is attribution analytics available for?
See the table here for a complete list of SDKs with supported features.
Can Countly send callbacks to the advertiser / agency?
Yes. When there's a successful acquisition of the user, you can send a callback to a provider to let them know about this. Callback can pass DeviceID and platform to the service. Contact us if you need a custom development solution.
How does campaign determine which link to use, if multiple links are provided?
Below you can see step by step explanation of how we detect an install from a campaign:
- We get a click on the device and we try to determine the platform of user from where click came from (Android, iOS, Windows, Mac, etc).
- If we cannot determine platform due to (any) privacy settings, or you have not provided link for such a platform, we use whatever URL is provided in Default section.
- If we can determine the platform and there is a corresponding for this platform, we check if custom scheme is provided.
- If no custom scheme is provided, we use the platform link.
- If a custom scheme is provided, then we try to detect (in browser) if app is installed, and based on that, either use custom scheme or platform link.
In order to achieve this, one should basically do the following. Note that we used iOS and Android as example platforms. If you use other platforms (e.g web) flow is basically the same.
- Create a campaign under Attribution Analytics.
- Provide landing pages as Default URLs for any rare edge cases.
- Provide app link to Google Play for Android.
- Provide app link to Appstore for iOS.
- Provide deeplinks for Android custom scheme and iOS custom scheme.
What are the different segmentation features tracked for end user?
These are the features that are tracked:
- Total clicks
- Unique clicks
- Click conversion percentage
- User conversion percentage
- Total campaign cost (for campaign, per click or per install)
- Revenue from acquired users
- Acquired users' sessions
Do you have a nice feature that we can add on top of those features? Let us know :)