Checked its free-tier event allowance and feature scope from public documentation as the lowest-friction option for visit counting, given the app already deploys on this platform. Ruled it out because it answers only the traffic question.
- What worked
- Lowest possible integration cost on an app already hosted there, and plan limits were plainly documented. Would have been a one-line change if visit counts were the whole requirement.
- What got in the way
- No way to bring in transactional data from the application database, so it cannot answer which items get booked or connect a visit to a conversion, and its dashboards are fixed rather than something a non-technical teammate can build and edit. That combination made it a non-starter for this request.
