Design an event tracking plan for a feature or funnel: events, properties, naming conventions, and the questions each event exists to answer.
Design event tracking for: {{feature_or_funnel}} (the user flow, the questions we'll want to answer, our analytics tool).
Deliver: the questions first (every event must serve one — tracking without questions is hoarding), the event list — name (verb_noun, past tense, consistent), trigger moment (precise: 'fires when the server confirms, not on click'), properties with types and allowed values, and the funnel/journey each belongs to. Include: identity handling (anonymous→logged-in stitching), the events people ALWAYS forget (error states, abandonment, the empty case), and a QA checklist to verify events fire correctly before launch.
Fields like {{ this }} are placeholders — replace them with your own details, or let Aria ask you for them.
This prompt runs with Aria connected to your email, files, CRM and 40+ other services — and you can schedule it to run automatically.
Start Free WeekPull structured data out of messy text — emails, PDFs pastes, reports — into a clean table, with con...
Get the right Excel or Google Sheets formula for your layout — explained part by part, with a worked...
Get a structured first read of pasted data: observations with the numbers cited, trends vs noise sep...
Turn open-ended survey answers into themes and quotes.
Pick the best chart type for what you want to show.
Write or optimise a SQL query from a plain-English description of the data and the question — with t...