Help Center
Set the naming rules once. Then anyone builds a campaign URL through a guided flow that already knows those rules, checks the link against your GA4 channels, and saves it to a history you can reuse.
The glowing box is the anchor: one governed configuration that every URL obeys. A built-in flow validator blocks broken setups before it is saved.
Hover any box or step for a plain-language explanation.
Everything in Trakr hangs off a single idea: your naming convention lives in one governed configuration instead of a spreadsheet, and every URL your team generates has to obey it. The diagram above shows the three stages that follow from that. An admin configures the rules once. Anyone on the team builds URLs through a guided flow generated from those rules. And everything generated lands in a shared history you can reuse: as filterable records, as pinned templates, or through the API.
Setup starts with two doors in: pick one of the five industry templates (each seeds fields, syntax, and a channel set), or start from scratch with all 9 GA4 UTM parameters and empty structures. No account is needed for either. The details live on the getting started page.
From there, two stops define your rules:
Saving produces the anchor of the whole diagram: one configuration that acts as the single source of truth. A built-in flow validator checks it before it can be saved, so a broken setup (a reference pointing at a deleted field, two fields fighting over the same role) never reaches your team. Pro workspaces can save multiple configurations and share them, so the whole team builds against the same rules.
The builder is a step-by-step flow, and its steps are generated from your configuration: landing page, campaign fields, content fields, your custom parameters, channel, review. The order and the fields shown mirror what the admin configured, so the flow in the diagram is a typical example rather than a fixed sequence.
Two things do the quality work while you build:
The same flow powers both modes. Single mode produces one URL. The Bulk Builder (Pro) turns the channel step into a multi-select: every channel you pick becomes its own row with source and medium pre-filled from the channel definition, and one pass produces one governed URL per channel.
Every generated URL is saved automatically to your history with its full context: parameters, channel, campaign, and creator. Signed-in users get cloud history across devices; anonymous users get browser-local history capped at the most recent 50 links.
Reuse takes three shapes:
The short version: the configuration is the contract, the builder enforces it, and the history proves it. That is the whole product.
Yes, because the builder's steps are generated from your configuration. The fastest path is a template: pick one of the five industry presets and you have a complete, working configuration in one click. Everything in it stays editable afterwards.
The person who owns your naming convention today, usually an analytics lead or the marketing ops owner. They set it up once. Everyone else only uses the builder and never has to remember the rules, because the flow enforces them.
Three layers. The flow validator blocks a broken configuration before it can be saved. The builder only offers values the configuration allows and cleans what you type. And before you generate, Trakr predicts the GA4 channel the link will land in, so a wrong source and medium combination is visible immediately.
The steps stay the same. The channel step becomes a multi-select: every channel you pick becomes its own row with source and medium filled in from the channel definition, and one pass produces one URL per row. Bulk mode is part of the Pro plan.