---
type: method
slug: marketing-analytics-tracking-plan
title: "Create a marketing tracking plan (GA4 & events)"
category: "Marketing"
subcategory: "Marketing analytics"
level: intermediate
source: https://deepstoryresearch.com/method/marketing-analytics-tracking-plan
publisher: Deepstory Research
---

> **How to use this file:** attach it to ChatGPT, Claude, Gemini or Copilot (or paste the prompt section), replace every [PLACEHOLDER] with your details, and add any data or Deepstory evidence files the method needs.

## When to use this method
- Setting up analytics on a new site or app.
- Numbers in different tools do not match.

## Prompt

# Create a marketing tracking plan (GA4 & events)
Method by Deepstory Research: deepstoryresearch.com/method/marketing-analytics-tracking-plan

You are a marketing-analytics engineer. Follow the method below step by step. Goal: An event tracking plan with naming, parameters, conversions, UTMs and a dashboard spec.

## My inputs
- Site or app: [SITE_OR_APP]  (example: e-commerce store on Shopify)
- Business goals: [BUSINESS_GOALS]  (example: purchases, newsletter signups)
- Tools: [TOOLS]  (example: GA4, Meta Pixel, Google Ads)
- Consent requirements: [CONSENT_REQUIREMENTS]  (example: GDPR/UAE PDPL)

Before you start: if any input above is still in [BRACKETS] or missing, ask me for it in one short numbered list and wait. Do not guess. If I attached files (data, briefs, Deepstory evidence files), treat them as the primary source.

## Steps to follow
1. List user actions that matter to the funnel.
2. Define events with naming convention and parameters.
3. Mark key events/conversions.
4. Define a UTM convention.
5. Specify consent handling.
6. Spec a dashboard: metrics, dimensions, filters.

## Deliver the output in this structure
- Event table (name, trigger, parameters, conversion?)
- UTM rules
- Consent notes
- Dashboard spec
- QA checklist

## Quality rules
- Never collect personal data (emails, phone) in event parameters.
- Label every number as FACT (with source and date), ESTIMATE (show the calculation) or ASSUMPTION.
- If a Deepstory evidence file is attached, use its figures as the reference values and cite its source references; tag claims that are not from it as [UNVERIFIED].
- End with: the 3 assumptions that matter most, what would change the answer, and the single best next step.

## Evidence you can attach
- E-Commerce Share of US Retail: https://deepstoryresearch.com/data/us-ecommerce-share (AI context file: https://deepstoryresearch.com/context/us-ecommerce-share.md)
- UPI vs Visa & Mastercard: India’s Payments Rewiring: https://deepstoryresearch.com/data/upi-vs-cards (AI context file: https://deepstoryresearch.com/context/upi-vs-cards.md)
- Six-Economy Macro Baseline: https://deepstoryresearch.com/data/global-macro-baseline (AI context file: https://deepstoryresearch.com/context/global-macro-baseline.md)

---
Deepstory methods are process guidance for AI tools. Review AI output before relying on it; legal, tax, medical and investment matters need a qualified professional.