TechnicalCollectible prompt
Analytics event tracking for the actions that matter
Add analytics event tracking to my {{tech_stack}} site so I can see what leads to {{goal}}. The pages that matter most: {{key_pages}}. Read the existing code first. Use the analytics tool already installed; if there isn't one, recommend a privacy-friendly option and ask before adding it.
Step 1: before writing code, show me a tracking plan as a table with event name, when it fires, its properties, and whether it counts as a conversion. Keep it to 15 events or fewer, named consistently as object and action, such as form submitted.
Step 2, after I approve:
- One small tracking helper that every event goes through, so the provider can be swapped later
- Form and booking events fire on success, not on click
- Campaign source tags captured on the first visit and attached to conversions
- Payments tracked from the server once confirmed, not from the browser
- No names, emails, phone numbers or free text ever sent in events or URLs
- Cookie consent respected: no tracking cookies before someone agrees
- No tracking in local development or preview builds
When you're done, list the events added, how to check each one in the tool's live or debug view, the funnels worth building, and anything you assumed.
Technicalnvoka.com/library/nvoka-analytics-event-tracking-for-key-actionsScan to open
Technical
Analytics event tracking for the actions that matter
Track the few events that show what leads to sales, without collecting personal data.
Curated by Nvoka
Claude CodeCursorCodexLovable
Make it yours
Fill in the blanks and change any word. Only your copy changes, never the card.
Fill in the blanks
0 of 3 filledYour prompt
Add analytics event tracking to my {{tech_stack}} site so I can see what leads to {{goal}}. The pages that matter most: {{key_pages}}. Read the existing code first. Use the analytics tool already installed; if there isn't one, recommend a privacy-friendly option and ask before adding it.
Step 1: before writing code, show me a tracking plan as a table with event name, when it fires, its properties, and whether it counts as a conversion. Keep it to 15 events or fewer, named consistently as object and action, such as form submitted.
Step 2, after I approve:
- One small tracking helper that every event goes through, so the provider can be swapped later
- Form and booking events fire on success, not on click
- Campaign source tags captured on the first visit and attached to conversions
- Payments tracked from the server once confirmed, not from the browser
- No names, emails, phone numbers or free text ever sent in events or URLs
- Cookie consent respected: no tracking cookies before someone agrees
- No tracking in local development or preview builds
When you're done, list the events added, how to check each one in the tool's live or debug view, the funnels worth building, and anything you assumed.