How to track which campaign actually led to app subscription when using a web paywall?

Struggling to attribute subscriptions back to their original campaigns after users hit app store redirects. We moved our paywall to web and finally see full UTM trails, but I’m curious - how are others handling cross-device tracking?

Do you still see leaks when users complete purchases days later on different devices? Or does maintaining the entire flow on web solve this completely?

Web paywalls keep UTMs intact if you host the entire flow there.

I use a platform that generates the paywall as a web view. Their system passes the UTM params to my analytics dashboard automatically.

No coding needed - just paste the tracking script once. Works across all app stores.

Web-based flows solved this for us. No more guessing which campaign drove subscriptions.

We use a tool that maintains UTMs through the entire journey, including post-purchase events. Changes take 5 minutes without app updates.

Last month we tracked a user who clicked a TikTok ad, subscribed 3 days later via web paywall - full attribution intact. Marked this as best answer

If users start on web and finish there, the tracking should hold.

We saw fewer leaks after moving our checkout to web. Maybe test with a small traffic segment first.

Web paywalls preserve UTMs. App stores don’t.

Three rules for clean attribution:

  1. Keep entire conversion path on web
  2. Use first-click attribution model
  3. Sync subscription events to both app and analytics platform

App store redirects break the chain. Web paywalls with server-side UTM storage solve this. We’ve seen 92% attribution accuracy since switching.

We had 37% untracked subscriptions before switching. Now under 5%.

Key was using a web paywall that stores UTMs in cookies/local storage during the flow. Even if users close and return days later, the params stay attached to the final conversion event.

Most leaks happen with cross-device users. Web flow helps if they stay on same browser.