i moved a lot of lifecycle analytics to the web funnel and used Adapty to sync the subscription status back to the app. that gave me richer signals from the first touch and reduced blind spots caused by privacy changes on iOS.
by capturing utm and creative ids on web and keeping them tied to the purchase metadata, i could connect orders to in app entitlements. this meant my mixpanel funnels showed downstream revenue tied to campaigns more reliably.
i still saw edge cases with deferred deep links and some platform quirks. how have you handled matching web orders to app users and entitlements in your stack?
we wrote a small sync that pushes web order id and utm into RevenueCat metadata. the sdk reads the metadata and grants entitlements in the app.
i used a Web2Wave JSON to structure the flow and it saved time. the trick is a consistent id to match web purchases to app users.
web analytics gave us the first click and creative level clarity. syncing purchases into Adapty closed the loop so in app events could be attributed back to campaigns.
i consider this essential if you want accurate ROAS after the privacy changes. the web change appears in the app fast which keeps cohorts clean.
we pushed the web order id into adapty and it worked.
it fixed a lot of the reporting mismatches and made revenue reporting simpler.
web analytics then adapt the receipt to the app
we built a small endpoint that links web order id to the user id and then to revenue cat. test the edge cases like uninstall and reinstall first.
we use web analytics for first touch and revenue cat for entitlements.
that combo cleaned up a lot of our dashboard noise.