Improved deeplinks and analytics for mobile web user acquisition
There aren't good options for linking users to a skill for mobile devices on the web.
- On desktop platforms, it makes sense to link to amazon.com/db/<product id>. The user is likely to be signed-in, and the user can enable to skill in one tap.
However, on mobile web, all of the options are suboptimal:
On iOS, Linking to the amazon product link first opens the amazon app, and then the amazon app redirects the user to safari where it opens the link. I suspect that most users aren't signed-in on the web browser.
On iOS, Linking the user to the alexa app only makes sense if the user has the app. I suspect that many users have the amazon app but not the alexa app. If the user doesn't have the app, they open the alexa web app in safari, where they are probably not logged-in.
- We should link users to the alexa app deeplink
- If the user has the alexa app installed, open the skill there
- If the user doesn't have the alexa app installed, the fallback should be to open the skill in the main Amazon app.
- A deeplink for the skill using the amazon.com link should also open the skill on the Amazon app
- A user should be able to enable a skill from the Amazon app.
- If neither app is installed, make a web landing page that explains how to search and install the skill. Then there should be an option to sign-in on the web.
- We need to see impressions to each of the above
- We need to be able to segment impressions by various UTM params
- We need to see conversion rates to install, and to activation for traffic on these landing pages.