What tap stream has done with Deferred Deep Links is really pretty cool. Gathering intelligence on where your installs come from is way harder than it should be. This could go a long way toward fixing that.
When promoting their app, developers use Tapstream’s taps.io shortlinks as their ad destination URLs. When a visitor taps on one of these shortlinks, Tapstream records a snapshot of their shortlink session, including the ad’s source and their intended deep link destination.
Then, the taps.io redirect handler attempts to send the user to the deep link destination. If this fails, it means the app is not present on the user’s device; the user is then redirected to the app store but the actual deep link is stored on our servers.
Once the user installs and runs the app for the first time, the Tapstream SDK sends an installation event to the Tapstream event API. This tells our attribution engine to find a mate for the SDK session among the pool of eligible shortlink sessions.
When the attribution engine mates the shortlink session to the SDK session, we credit the shortlink with a conversion.