How the bulk builder handles your campaign sheet
Each row becomes one campaign URL. UTM Harbor keeps non-tracking query segments and fragments, replaces supported tracking values, and encodes newly generated fields. Campaign IDs retain their exact values; aliases apply only to their source or medium field. Rows with missing source, medium, or campaign values stay out of the generated list until fixed.
Accepted column names
| Purpose | Accepted headers | Required |
|---|---|---|
| Destination | url, destination, landing_page, link | Yes |
| Campaign source | source, utm_source | Yes |
| Marketing medium | medium, utm_medium | Yes |
| Campaign name | campaign, campaign_name, utm_campaign | Yes |
| Variation | content, utm_content | No |
When to use shared defaults
Use defaults when many destinations belong to the same source, medium, and campaign. Import per-row values when one sheet contains several channels or creative variants. Values in a row take priority over shared defaults.
Walkthrough: one launch, three destinations
- Paste the destinations for pricing, a demo, and a guide. For one newsletter send, set source to
newsletter, medium toemail, and campaign tofall-launch. - Use a headed CSV when the same launch spans several channels. Put the source and medium on each row; keep the campaign name shared. Add content values such as
hero-ctaandfooter-ctato distinguish placements. - Build the sheet and inspect the row review. The example intentionally leaves one campaign empty so you can see a blocked row and its reason. Fill that cell or supply a campaign default and build again.
- Copy the ready URLs, or download the full review sheet. Keep the original destination column for your campaign owner to compare. Open the final URLs before adding them to a live campaign.
Expected output for a newsletter link
Destination: https://example.com/pricing?plan=pro#details
Source Newsletter, medium Email, campaign Fall Launch, content Hero CTA become:
https://example.com/pricing?plan=pro&utm_source=newsletter&utm_medium=email&utm_campaign=fall-launch&utm_content=hero-cta#detailsThe plan query and details anchor remain. The row review lists every naming change instead of silently hiding it.
Import a spreadsheet without changing the destination
Download the campaign CSV template, replace its example destinations, and save as CSV or paste spreadsheet cells as TSV. CSV files need a header row. Enclose a destination containing a comma in double quotes; for example "https://example.com/search?tags=one,two". For a plain list with one URL per line, commas remain part of the URL.
All seven supported fields can be imported: source, medium, campaign, ID, source platform, term, and content, using either short names or utm_ names. destination_url is also accepted. Term and source platform can be supplied per row in the CSV.
What each review state means
| State | Action | Export behavior |
|---|---|---|
| Ready | Required fields and local naming rules pass. Test the destination. | Included in copied URLs and CSV. |
| Review changes | Approve naming changes in the source sheet, or update the policy for an intentional source. Build again; a review export is not approval. | Retained in the review CSV; excluded from copied URLs until resolved. |
| Blocked | Fix a missing field, invalid destination, or malformed CSV row and rebuild. | Excluded from copied URLs; retained in CSV with an empty generated URL. |
Carry decisions through the handoff
For example, a source of FB becomes a proposed facebook. The builder retains that change in the review CSV and keeps it out of the ready list. Importing that CSV into the checker or builder retains the outstanding decision; it does not approve it. Confirm the source with the campaign owner, update the original sheet to the approved value, and build again. Keep the original review file alongside the approved sheet.
Before publishing
Building a URL does not verify the website, redirects, an analytics installation, or platform macros. Use fully expanded destinations. Unresolved platform templates and detected signature parameters block generation; use the platform to obtain the final visitor URL. Confirm any existing auto-tagging setup before adding manual campaign fields; non-UTM parameters are preserved. Generated values replace supported UTM fields already in the destination, and empty optional fields remove their old values. For links already published, use the UTM checker to inspect them before changing attribution.
Set a reusable vocabulary with the UTM naming convention guide. Parameter meanings follow Google's campaign URL documentation; the normalization policy is a local editing choice.