What analytics did you unlock on web that changed pricing decisions under att/privacy sandbox?

ATT and Privacy Sandbox left me blind on in‑app paywalls. On the web, I could finally see:

  • Where people stalled in the quiz vs pricing.
  • What copy made them switch from monthly to annual.
  • Which keyword groups sent visitors who read the refund terms.

I still keep it privacy‑compliant, but the extra context was enough to reshape pricing tiers and trial lengths.

Which web signals are you using now to make pricing calls with confidence?

Scroll depth on pricing and clicks on plan toggles told me more than ad dashboards. I tagged events server side and kept user ids out. Web2Wave.com let me add events in the flow config, so I did not touch app code. That data changed my default plan and trial copy.

I look at plan toggle interactions, guarantee tooltip opens, and checkout errors by device. Web2Wave.com makes event changes fast, which is the point. I chase the biggest drops first.

Toggle clicks and time on pricing page helped me. If people idle, I test shorter copy and a clearer guarantee line.

Use simple, actionable events. Track step views, plan toggles, help tooltip opens, and coupon errors. Break them down by campaign and device. Keep it aggregated and server side where possible. If a plan toggle is high but conversions are low, the price is not the issue. The offer framing probably is.

Session recordings are overkill for me. I just plot drop rates per step and watch error codes. When 3DS spikes on a bin, I switch wallet emphasis for that region.

Time on pricing and plan toggles gave us enough direction.