Discussion starter: an SEO measurement question, posted with an answer from Niraj Raut to open the thread. If you have dealt with this on a site, reply with what you saw, especially where it differs.
- SEO Analytics
Most conversions happen in the app after a web visit. How are you measuring organic’s contribution across web and app?
Disclosure: Niraj Raut, who posted this answer, runs the SEO consultancy linked at the end of it.
1 reply
-
adminAdmin
When most conversions happen in the app after a web visit, organic search’s contribution disappears from web-only reports, so you need to connect the two journeys deliberately. The pieces are: a shared user identity for logged-in users across web and app, deep links from the website into the app that carry attribution information, a mobile measurement partner or equivalent to attribute installs and first opens to web sessions, and analytics that combine web and app data. None of them is complete on its own, and privacy rules limit what can be joined, so the result is a range, not an exact figure. It is still far better than crediting the app with every conversion and search with none.
Where the journey breaks
- Existing app users search on the web, read a page, then open the app to buy. Without identity or deep links, the web visit is invisible to the app’s reporting.
- New users discover the brand through search, install the app later, and convert there. The install looks organic in the app store, not like a result of search.
- Different teams and tools own web analytics and app analytics, so nobody sees the combined path.
The measurement building blocks
Component What it connects Limitation Logged-in user ID across web and app Web sessions and app conversions for the same person Only logged-in users; consent requirements Deep links with attribution parameters Web page to specific app screen, carrying the source Only when the user taps the link Deferred deep linking through a measurement partner Web visit to install to first open Increasingly limited by platform privacy rules Combined web and app analytics properties Reporting across both platforms Needs consistent event naming and identity Holdout or geographic tests Incremental effect of web content on app conversions Harder to run; useful for validating models A practical set-up
- Add app handoff points to the website: smart banners and “open in app” buttons that deep link to the equivalent screen, tagged with the source of the web session.
- Use platform link standards so links open the app when installed and the web page otherwise.
- Pass identity where users are logged in, with consent, so web and app activity join in analytics.
- Attribute installs from web visits through your mobile measurement set-up, accepting that coverage will be partial.
- Build a combined report: organic web sessions, app opens from organic web sessions, app conversions from those users within a set window, and installs attributed to organic web visits.
Estimating what you cannot track
For users who cannot be joined, estimate. Compare app conversion rates among users who were joined to an organic web session with those who were not, and apply the observed rate to the organic web sessions from users you could not identify, stating the assumption. A periodic incrementality test, such as reducing app promotion on web pages in one region, helps validate the estimate.
Hypothetical example:
A food delivery business sees organic search driving large numbers of web sessions to restaurant pages, yet the web converts poorly and leadership questions SEO investment. The team adds deep links from restaurant pages into the app, tagged with the traffic source, and joins logged-in web sessions with app orders. It finds a large share of app orders from existing customers started with an organic web visit to a restaurant page in the previous day. Reported as combined web and app revenue influenced by organic search, SEO’s contribution is several times what web-only reporting showed, and the company funds more restaurant page improvements.
Watch for this:
Joining web and app data involves personal data. Make sure consent covers it, that identifiers are handled securely, and that reporting is aggregated. A measurement programme that breaches privacy rules creates more risk than the insight is worth.
Design the website to hand off well
Measurement is easier when the website is designed to pass users into the app deliberately rather than leaving them to find it. Smart banners, “continue in the app” buttons on high-intent pages and deep links that open the exact product or restaurant the user was viewing all create measurable handoffs. They also improve the experience: a user who arrives from search on a phone and already has the app installed usually prefers to complete the task there. Keep the web pages themselves complete and crawlable, though. A website that hides content to push users into the app loses the search visibility that started the journey.
What to report
Report three numbers with clear definitions: conversions directly attributable to organic web sessions on web and app, conversions from joined users who had an organic web session within the attribution window, and an estimated figure for users who could not be joined, labelled as an estimate. Alongside them, show the organic web metrics that drive the process. That gives leadership a defensible view of search’s contribution without overstating it.
Connect web and app with deep links, shared identity and install attribution, report joined journeys and a labelled estimate for the rest, validate with occasional tests, and stop judging organic search on web conversions alone when the business converts in its app.
Need help with this on your own site?
Niraj Raut works with businesses in Nepal, Australia, the UK, Europe and the US on technical SEO, ecommerce SEO, local SEO and AI search.
Add a reply Cancel reply
Replies are open to approved members. Log in or apply to join.