← marketing-mindset
UTM + GA4 event naming builder
A channel only becomes readable when two things exist: a session that carries its
source, and an event that ends the test. This page writes both — the tagged url and the
gtag('event', ...) line — and runs the checks that decide whether the numbers will line
up next month. Everything happens in your browser; nothing is sent anywhere.
1. The destination and the campaign
Destination url (absolute, https)
utm_source — where the click came from
utm_medium — the medium reports group by
utm_campaign — one pattern, dashes
utm_content (optional) — which creative
utm_term (optional)
2. The event that ends the test
Event name, lower snake_case
One parameter that survives the report (optional)
Its value
Your tagged url
Copy the url
Your gtag line
Checks
Once the session is tagged and the event fires, the next question is size:
how many contacts the test needs ,
the kill rule ,
the sending ramp .
Agent-readable version of the same numbers:
llms.txt ·
npx marketing-mindset sample .
Want the loop built instead? Write to me on Telegram →
Also: AI crawler robots.txt generator — who may cite you and who may train on you, written as robots.txt groups you can paste.
Also: A/B verdict calculator — was the difference separated from zero, and was the volume ever above the floor the observed lift needs?
Also: honest test queue planner — turn volume into a queue: the floor per arm, the days each test needs and the day each verdict lands.
Also: what one honest test costs to finish — the contacts a verdict needs, the days it takes and how many funded tests a budget carries.
Also: which step of your funnel can fund a verdict — the floor, the events each arm sees in a month, and the months a readable unit takes at your volume.
Also: which of your channels can actually fund a verdict — floor per arm, months to verdict, the cost of one full two-arm test and the channel to run first at your volume.