Lesson 6.1 · 45 minMeasurement plan

What you will have

The student has docs/measurement-plan.md: a short table of the events the site will send, the question each one answers, and which tool will answer it. Nothing is installed yet.

Video

The video for this lesson is not recorded yet.

Prompts used in this lesson

Part 5 — Drafting the plan with Claude

Purpose: I want a measurement plan for this site before any tracking is installed,
so that we only collect data I will act on.

Context: read docs/brief.md for the business and the conversion action, and look at
the landing page and lead form code to see what a visitor can actually do. The CRM
already records lead stages (new, contacted, qualified, won, lost).

Done looks like: a new file docs/measurement-plan.md containing
1. The two business questions: where do leads come from, and where do visitors drop off.
2. The funnel: visit, engagement, form start, lead, qualified lead, sale, with a note
   on which tool records each step (GA4 or the CRM).
3. A table of events with columns: event name, when it fires (trigger), parameters,
   the question it answers, the tool that reports it.
4. A short naming convention section.
5. A "not collected" section.

Constraints:
- Use exactly these event names: cta_click, form_start, form_submit, generate_lead.
  generate_lead fires once, only after /api/leads confirms the lead was saved, and
  it is the GA4 key event.
- Page views are collected automatically; list them but do not invent an event for them.
- Parameters must never contain personal data: no name, email, phone or message text.
  Suggest only parameters that describe the page element (for example which form,
  which button, where on the page).
- Every event must name the question it answers. If you cannot name one, leave the
  event out.
- Do not write or change any code. Do not install anything. Only create the document.
- When finished, list any element on the page you were unsure whether to track, and why.

Part 6 — Trimming

In docs/measurement-plan.md remove the events I list below, and move each one to the
"not collected" section with one line saying why: <list the events>.
Do not change anything else. Show me the final event table when done.

Do along

Work on your own project. Pause the video where a step says so.

1. Start from lesson-5.7. Open docs/brief.md and re-read your conversion action.
2. Pause when the prompt appears in Part 5. Run the drafting prompt. If your conversion action is not a quote request (a booking, a call, a sign-up), say so in the context line; the event names stay the same.
3. Review the draft against the four checks: exact event names, a question per event, no personal data, generate_lead after server confirmation.
4. Pause after Part 6. Trim. For each event, write what you would do if the number changed. Remove events where you have no answer.
5. Fill in the funnel section with your own stage names from the CRM if you changed them in 5.1.
6. Commit the document:

git add docs/measurement-plan.md
git commit -m "Lesson 6.1: measurement plan"
git push

Check your work

1. Open docs/measurement-plan.md. Expected: an event table in which every row has a non-empty "question it answers" cell.
2. Read the event names. Expected: cta_click, form_start, form_submit, generate_lead, spelled exactly so, plus automatic page views.
3. Search the document for "email", "phone" and "name". Expected: they appear only in the rule that forbids them, never as a parameter.
4. Find the funnel. Expected: six steps, each marked GA4 or CRM.
5. Read one row aloud as a sentence: "We collect X to find out Y, and if Y changes we will do Z." Expected: it makes sense for every remaining row.

Common problems

• The plan has twenty events. → Claude was thorough and you did not trim. → Run the trimming step; keep only events where you can name the action you would take.
• Claude used different event names (lead_created, formSubmit). → The constraint was dropped or edited out of the prompt. → Tell Claude: "Rename the events to exactly cta_click, form_start, form_submit, generate_lead and update every mention in the document."
• A parameter contains the visitor's email or city typed in the form. → Claude mirrored the form fields. → Tell Claude: "Remove every parameter that comes from what the visitor typed. Parameters describe page elements only."

Homework

About 25 minutes, after the lesson. Nothing here is needed to start 6.2. Write in your course notes and leave the event table in docs/measurement-plan.md as it is; later prompts read it.

1. What the site will never see (~10 min). List every way a customer reaches your business other than the form: a phone call, a messenger, walking in, a recommendation. For each, write how often it happens in a normal week and whether you will enter those people into the CRM by hand. Done when: every way a customer reached you last month is either in the event table or on this list.
2. A baseline before any tool (~5 min). Open the CRM dashboard and write down today's date and the number of leads in each stage. For visit, engagement and form start write "not measured yet". Done when: each of the six funnel steps has a number or "not measured yet" next to it.
3. A plan for a second business (~10 min). Without Claude, write a small plan for a business you know as a customer, such as a dentist or a gym: its conversion action, then up to four events, each with the question it answers and what the owner would do if the number changed. Done when: every event has a question and an action, and no parameter describes a person.