Conversion tracking plan prompt
A conversion tracking plan prompt lists the actions that count as leads, names each event, says exactly where it fires and what to record, and handles cookie consent. You get a plan a developer or a tag manager setup can follow.
- Stage
- Grow, step 38 of 40
- Use it
- Before launch, so the first month of data is usable.
- You need
- The actions that count as leads
- Your booking, form and call tools
- Your cookie consent setup
- You get
- A table of events, where each fires and what it needs, plus a consent plan. Output schema included.
The prompt
Plan conversion tracking for [business]. The actions that matter:
[bookings, calls, quote forms, orders].
For each, give an event name in snake_case, where it fires
(which page, which element, after which confirmation),
what to record with it, and whether it needs consent first.
Count a lead when the booking or form is confirmed, not on the click.
Return a table, then list what can't be tracked without consent
and what to use instead.JSON version, for teams and automations
Fill each value under "inputs", keep the rest. It follows the prompt schema. When to use JSON.
{
"$schema": "https://websitesdesigner.com/insights/prompts/prompt.schema.json",
"id": "conversion-tracking",
"name": "Conversion tracking plan prompt",
"stage": "grow",
"step": 38,
"of": 40,
"version": "2026-11-19",
"url": "https://websitesdesigner.com/insights/prompts/conversion-tracking/",
"inputs": {
"business": "[business]",
"bookings": "[bookings, calls, quote forms, orders]"
},
"instructions": [
"Plan conversion tracking for {{business}}.",
"The actions that matter: {{bookings}}.",
"For each, give an event name in snake_case, where it fires (which page, which element, after which confirmation), what to record with it, and whether it needs consent first.",
"Count a lead when the booking or form is confirmed, not on the click.",
"Return a table, then list what can't be tracked without consent and what to use instead."
],
"output": "A table of events, where each fires and what it needs, plus a consent plan.",
"checks": [
"Every event fires on a confirmation.",
"Phone calls are included.",
"Each event says whether consent is needed."
],
"output_schema": {
"type": "object",
"properties": {
"events": {
"type": "array",
"items": {
"type": "object",
"properties": {
"name": {
"type": "string"
},
"action": {
"type": "string"
},
"fires_on": {
"type": "string"
},
"records": {
"type": "array",
"items": {
"type": "string"
}
},
"needs_consent": {
"type": "boolean"
}
},
"required": [
"name",
"action",
"fires_on",
"records",
"needs_consent"
],
"additionalProperties": false
}
},
"untracked_without_consent": {
"type": "array",
"items": {
"type": "object",
"properties": {
"what": {
"type": "string"
},
"alternative": {
"type": "string"
}
},
"required": [
"what",
"alternative"
],
"additionalProperties": false
}
}
},
"required": [
"events",
"untracked_without_consent"
],
"additionalProperties": false
}
}Output schema (JSON Schema)
Ready for strict structured-output modes: every field required, unknown values nullable. In a chat, paste it after the prompt with "Return only JSON that matches this schema." How output schemas work.
{
"type": "object",
"properties": {
"events": {
"type": "array",
"items": {
"type": "object",
"properties": {
"name": {
"type": "string"
},
"action": {
"type": "string"
},
"fires_on": {
"type": "string"
},
"records": {
"type": "array",
"items": {
"type": "string"
}
},
"needs_consent": {
"type": "boolean"
}
},
"required": [
"name",
"action",
"fires_on",
"records",
"needs_consent"
],
"additionalProperties": false
}
},
"untracked_without_consent": {
"type": "array",
"items": {
"type": "object",
"properties": {
"what": {
"type": "string"
},
"alternative": {
"type": "string"
}
},
"required": [
"what",
"alternative"
],
"additionalProperties": false
}
}
},
"required": [
"events",
"untracked_without_consent"
],
"additionalProperties": false
}What good output looks like
- Every event fires on a confirmation.
- Phone calls are included.
- Each event says whether consent is needed.
What experts miss
- Fire on confirmation, not on click. A click on "Book" isn't a booking. Track the confirmation step or the booking tool's own event.
- Count calls. Tap-to-call links and call tracking catch leads a form report never shows.
- Expect gaps under consent. Where analytics loads only after consent, totals will be lower than real leads. Compare monthly with your CRM or inbox.
Why it works
Traffic tells you little. Tracked leads show which pages and channels bring customers, so you can stop paying for the ones that don't.
How to adapt it
- Add a value per event if leads differ in worth.
- Add offline outcomes, such as signed contracts, to close the loop.
Mistakes to avoid
- Tracking page views as goals.
- Loading tracking before consent where consent is required.
Go deeper
See conversion tracking, call tracking and assisted conversions. This prompt is part of the grow stage. It follows the AI website design prompts guide and the six steps in how to use AI to design a website.