UTM Builder
Assemble the final candidate URL from approved values, preserve destination parameters that still need to survive, and hand the result into QA before anything goes live.
Use the builder after naming and taxonomy are settled. Build here, run the finished candidate through QA, validate redirects when the route is not direct, then log what actually ships.
Use approved values and the real destination. The builder assembles; it does not invent policy.
Keep the parameters that still matter and surface collisions before QA.
A built link is a candidate. QA, redirect validation, and launch logging happen next.
Assemble the final candidate URL
Paste the real destination, add only the approved values, and build the candidate that will move into QA.
Built candidate URL
Assembly happens here. Approval to publish still happens later.
Use the examples to see the difference between a clean build and a deliberate overwrite scenario before you trust the output.
Build readiness verdict
Use approved values, preserve useful destination parameters, and route the final candidate into QA rather than launching directly from this page.
Destination parameter summary
- No destination URL loaded yet.
When the destination already includes UTM keys, the builder will replace those keys with the values you enter here.
Build-stage checks
- Destination URL: paste the real landing-page URL including https://
- utm_source: use an approved value before building.
- utm_medium: use an approved value before building.
- utm_campaign: use the approved live campaign label before building.
What this builder will never decide
This page does not define taxonomy, approve naming policy, validate the finished link, prove redirect safety, or log what launched. It assembles an approved candidate URL and hands it straight into the UTM QA Checker before release.
Existing destination parameters often carry state, IDs, or page logic. A good build respects them unless you are deliberately rebuilding that layer.
If the inputs are still debatable, the problem is upstream. Stop and return to naming, template, or taxonomy decisions before building.
A candidate URL is only ready for the next step when the assembly is clean, the destination is true, and QA owns the final validation pass.
Build rules that must stay true
Keep the build step narrow: assemble the candidate, preserve what must survive, and leave approval, redirect trust, and launch evidence to the right next layer.
Use approved values
Source, medium, campaign, and optional fields should already be cleaned and approved before they reach the builder.
Keep the real destination intact
Build onto the actual landing-page URL and preserve the parameters that still need to survive the route.
Output a candidate, not a launch decision
The builder assembles the candidate link. QA and redirect validation still decide whether it is safe to ship.
Log what actually ships later
Launch evidence belongs after QA, route validation, and final approval — not inside the build step itself.