C. Website Launch Readiness · Prompt 29

Analytics & Measurement Setup

Get the free PDF

Why it matters

If you cannot see what visitors do, you find out a launch failed only after the chance to fix it has passed.

Modeled on

Privacy-conscious analytics: measure outcomes, keep personal data out of events, and respect consent.

How to run this prompt

Switch to a mode that does not edit files. In Cursor that is Ask or Plan. In Claude Code that is Plan mode.
Paste the audit prompt. Wait for the report. It must stop and ask which IDs to fix.
Read the report. Keep the IDs you agree with.
Switch to a mode that can edit. Paste the fix prompt and the IDs you chose.
Switch back to the read-only mode and paste the same audit prompt again. Confirm those IDs are gone.

Cursor: audit in Ask mode or Plan mode. Fix in Agent mode.
Claude Code: audit in Plan mode (Shift+Tab cycles to it). Fix in Normal mode, which can edit.
Any other tool: audit in Chat, Discuss, or Plan mode, whichever answers without editing files. If the tool has no such mode, the prompt itself forbids edits. Fix in the mode that is allowed to edit files.

The audit prompt

MODE: AUDIT ONLY. Do not create, edit, or delete any file. Do not run commands
that change anything: no installs, migrations, git commits, deploys, or "--fix" flags.
If your tool has an Ask, Plan, Chat, or Discuss mode, use it for this prompt.

Before you start:
- Tell me the stack you detect (framework, language, database, auth, hosting,
  payment provider) and which folders you will review.
- If a check below does not apply to this stack, write "Not applicable" and why.
- If you can run read-only commands, run the ones listed. If you cannot, list them
  so I can run them and paste the output.

Analytics & Measurement Setup: what to check
Review analytics. Do not add a new vendor. Do not send a test event that includes an email address.
1. Say which analytics tool is installed, whether it is on every page or only some layouts, and whether it loads before consent. If consent is not implemented, say so.
2. List custom events and where they fire. Flag an event property that includes an email, name, or other personal data.
3. Say which event is the conversion for the main action, and whether a double click could record it twice.
4. Say whether utm_source, utm_medium, and utm_campaign are read on landing and still available when a form is submitted. Cite the storage (cookie, sessionStorage, or none).
5. Say whether local and staging hosts are excluded from production analytics.
6. Say whether frontend errors are reported anywhere, and whether that report includes the error message (which might contain personal data).
7. Describe a weekly check I can do in the vendor's UI: visitors, sources, top pages, conversion rate, and top calls to action. Do not invent a dashboard that is not in the repo.
8. Return the event list, the file that fires each event, and how I can verify it once without putting personal data in the payload.

Evidence rules:
- Every finding cites a file path and line number, or the exact command output used.
- Mark each finding Confirmed (seen in the code) or Needs manual check (depends on
  something outside the repo, such as a dashboard setting or production data).
- Never print a full secret. Show the first 4 characters and the location only.
- If you are not sure, say so. Do not invent files, settings, or results.

Severity: Critical = exploitable now, or leaks real data or money. High = serious
with little effort. Medium = weakens defenses or needs a second bug. Low = hygiene.

Report:
- Summary: count of findings by severity.
- Table: ID | Severity | Confirmed? | Finding | Evidence | Why it matters | Suggested fix | Effort
  (IDs for this prompt use the prefix P29, for example P29-1, P29-2.)
- Checked and fine: what you verified is already OK.
- Could not check: what I need to look at myself, and where.

Then stop. Do not fix anything. Ask me which IDs I want fixed.

Get the free PDF

Related prompts

Share this prompt

WhatsApp LinkedIn X

How to run this prompt

Switch to a mode that does not edit files. In Cursor that is Ask or Plan. In Claude Code that is Plan mode.

Paste the audit prompt. Wait for the report. It must stop and ask which IDs to fix.

Read the report. Keep the IDs you agree with.

Switch to a mode that can edit. Paste the fix prompt and the IDs you chose.

Switch back to the read-only mode and paste the same audit prompt again. Confirm those IDs are gone.

Cursor: audit in Ask mode or Plan mode. Fix in Agent mode.

Claude Code: audit in Plan mode (Shift+Tab cycles to it). Fix in Normal mode, which can edit.

Any other tool: audit in Chat, Discuss, or Plan mode, whichever answers without editing files. If the tool has no such mode, the prompt itself forbids edits. Fix in the mode that is allowed to edit files.

The audit prompt

MODE: AUDIT ONLY. Do not create, edit, or delete any file. Do not run commands that change anything: no installs, migrations, git commits, deploys, or "--fix" flags. If your tool has an Ask, Plan, Chat, or Discuss mode, use it for this prompt. Before you start: - Tell me the stack you detect (framework, language, database, auth, hosting, payment provider) and which folders you will review. - If a check below does not apply to this stack, write "Not applicable" and why. - If you can run read-only commands, run the ones listed. If you cannot, list them so I can run them and paste the output. Analytics & Measurement Setup: what to check Review analytics. Do not add a new vendor. Do not send a test event that includes an email address. 1. Say which analytics tool is installed, whether it is on every page or only some layouts, and whether it loads before consent. If consent is not implemented, say so. 2. List custom events and where they fire. Flag an event property that includes an email, name, or other personal data. 3. Say which event is the conversion for the main action, and whether a double click could record it twice. 4. Say whether utm_source, utm_medium, and utm_campaign are read on landing and still available when a form is submitted. Cite the storage (cookie, sessionStorage, or none). 5. Say whether local and staging hosts are excluded from production analytics. 6. Say whether frontend errors are reported anywhere, and whether that report includes the error message (which might contain personal data). 7. Describe a weekly check I can do in the vendor's UI: visitors, sources, top pages, conversion rate, and top calls to action. Do not invent a dashboard that is not in the repo. 8. Return the event list, the file that fires each event, and how I can verify it once without putting personal data in the payload. Evidence rules: - Every finding cites a file path and line number, or the exact command output used. - Mark each finding Confirmed (seen in the code) or Needs manual check (depends on something outside the repo, such as a dashboard setting or production data). - Never print a full secret. Show the first 4 characters and the location only. - If you are not sure, say so. Do not invent files, settings, or results. Severity: Critical = exploitable now, or leaks real data or money. High = serious with little effort. Medium = weakens defenses or needs a second bug. Low = hygiene. Report: - Summary: count of findings by severity. - Table: ID | Severity | Confirmed? | Finding | Evidence | Why it matters | Suggested fix | Effort (IDs for this prompt use the prefix P29, for example P29-1, P29-2.) - Checked and fine: what you verified is already OK. - Could not check: what I need to look at myself, and where. Then stop. Do not fix anything. Ask me which IDs I want fixed.