utm_source
Name the specific origin sending traffic: instagram, linkedin, newsletter, partner_name or google.
SELY UTM
One disciplined workspace for naming, validating, shortening and sharing every campaign URL.
Build up to 100 URLs at once; shorten up to 20 per batch.
| # | Campaign | Destination | Status | Result | |
|---|---|---|---|---|---|
| Upload or paste CSV data to begin. | |||||
THIS BROWSER
Built links will appear here for quick reuse.
FIELD GUIDE
CAMPAIGN DISCIPLINE
UTM parameters become useful only when the same source, medium and campaign language is repeated across the team. Build the tracking URL first, validate it, then shorten or turn it into a QR code for distribution.
Name the specific origin sending traffic: instagram, linkedin, newsletter, partner_name or google.
Name the channel class consistently: organic_social, paid_social, email, cpc, referral or another agreed team value.
Use one stable campaign identifier across all channels so performance can be grouped after traffic reaches your analytics system.
Use it when you genuinely need to separate creatives, placements or calls to action. Do not create detail nobody will analyse.
Use it for keyword, audience or targeting detail when that distinction matters to the campaign and your reporting workflow.
Add platform or internal identifiers only when downstream systems expect them. More parameters do not automatically produce better attribution.
TEAM RULES
FAQ
The builder creates the destination URL. Your website or app still needs its own analytics implementation to receive and report the resulting campaign parameters.
No. Source, medium and campaign are the core fields for most workflows. Add term, content or custom parameters only when they answer a reporting question you intend to use.
The public builder can create campaign URLs without sign-in. Features such as Sely link management and private link analytics require the relevant account access.
Do not put passwords, access tokens, email addresses, phone numbers or other personal information in UTM fields. URLs can be copied into browser history, analytics systems, logs and screenshots. Use campaign labels rather than information identifying a person.
Current presets and recent builder history are stored in the browser unless the interface explicitly says otherwise. Treat them as local convenience rather than cloud backup.