Campaign Tracking Spreadsheet
Log published links, final destinations, owners, and launch evidence in one place so reporting has a real source of truth after QA has passed and the link goes live.
What is a campaign tracking spreadsheet?
A campaign tracking spreadsheet is a campaign link log for approved marketing links. It keeps the published URL, final destination, source, medium, campaign name, placement, owner, status, notes, and launch evidence in one reviewable row.
This is the recordkeeping layer that sits after UTM Builder, UTM QA Checker, and Redirect Checker. Use it to preserve what actually shipped instead of reconstructing it from memory later. The sheet should record approved launches, final destinations, ownership, and proof of release — not become the place where broken links are discovered for the first time.
Boundary: this page owns the post-QA evidence ledger: what shipped, where it was placed, who owned it, and what it resolved to. It is not the pre-build control sheet — keep that in the UTM Naming Template — and it should not carry the whole governance policy or become the place where naming is designed.
Download the starter CSV if you want the fields immediately, generate starter rows via the Link Tracker Generator when you need row structure, then use this sheet after UTM QA and redirect checks have passed.
Create the row before the link goes live so the published asset is tied to one approved source of truth.
Keep both the placed link and the final destination so redirect changes stay visible later.
Track who launched the link, what state it is in, and where to look when results or failures show up.
Log the asset before it disappears into launch chaos
The spreadsheet should make it obvious what was published, where it was placed, who owned it, and what it finally resolved to. Treat each row as an evidence record, not as a casual note.
Sheet preview
One row per published link. Keep the fields stable so the record still makes sense a month later.
| Date | Campaign | Channel | Placement | Published URL | Final URL | Owner | Status |
|---|---|---|---|---|---|---|---|
| 22 Mar | Spring sale launch | TikTok | Bio link | short.ly/sale | /sale?utm_campaign=spring_sale | Emily | Live |
| 22 Mar | CRM reactivation | Newsletter CTA | example.com/offer?... | /offer?utm_campaign=crm_reactivation | Dean | Planned | |
| 21 Mar | Influencer partner push | Affiliate | Creator bio | partner.link/abc | /bundle?utm_campaign=creator_bundle | Nancy | Review |
What every row needs
- Published URL + final URLKeep the exact link that appeared in the campaign and the destination it resolves to after redirects, short links, or network hops.
- Source, medium, campaign, placementRecord the UTM fields and placement so the campaign name still matches the intended reporting contract later.
- Owner, status, review dateLog who owns the row, whether it is planned, live, paused, or retired, and when the route needs checking again.
- Notes and launch evidenceUse notes for redirect checks, affiliate hops, creative swaps, approval references, exceptions, and result context.
Build the link
Use approved values from naming and taxonomy, then assemble the final URL in the builder.
If the row is heading into Google Ads, decide whether Final URL suffix, a tracking template, or custom parameters should own the append layer before the sheet becomes the source of truth.
Run QA
Validate the finished link in the UTM QA Checker so missing UTMs, duplicates, and malformed parameters are caught before launch.
Check redirects
Confirm the final page is correct and that redirects do not drop parameters or send people to the wrong destination. If the route will be printed, shared offline, or turned into signage, add the controls from QR code tracking for offline campaigns before you approve the row.
Log what shipped
Record only the checked and approved live asset, final destination, owner, and status so your reporting has a stable source of truth.
Choose the right workflow layer
Keep the campaign spreadsheet focused on evidence. Use the surrounding tools for generation, validation, and long-term governance.
Campaign tracking spreadsheet
Records approved campaign evidence after the link has passed QA: published URL, final URL, campaign fields, placement, owner, status, notes, and proof.
Link tracker generator
Creates starter tracking rows and a CSV structure for managed links before the live campaign record is ready.
Generate starter rows →Link inventory system
Governs the full live-route estate when links, owners, review dates, and repair responsibilities outgrow a campaign sheet.
Plan the inventory layer →UTM QA Checker
Validates the structure of the candidate URL before the row is treated as approved campaign evidence.
Validate before logging →What to log, and what breaks the sheet later
The sheet should stay boring, stable, and useful. Add the fields you actually need, then use the same structure every time a link goes live. If your team still needs a pre-build control for approved values, row ownership, and launch-state handoff, keep that in the UTM naming template rather than bloating the live log.
Published asset
Log the exact published URL that went live plus the placement where it appeared. This is the field people usually forget, and it is the first thing they need later.
Final destination
Keep the final URL that the link resolves to so redirect changes, short links, and network hops do not hide where traffic really went.
Tracking contract
Store source, medium, campaign name, content, term, and any approved custom field so reporting stays tied to the naming decision.
Ownership context
Include owner, launch date, status, review date, and evidence notes so fixes do not depend on memory or message threads.
Changing names mid-flight
When the campaign label changes after launch, the sheet stops matching reports and GA4 starts splitting traffic across multiple names.
Logging only the destination
If you only keep the intended landing page, you lose the actual published URL and the whole redirect or short-link path goes invisible.
No owner, no follow-through
If nobody owns the row, nobody updates the status, validates the redirect, or fixes the link when attribution goes wrong.
Ready to start the log?
Generate the sheet, log the asset before launch, then route the finished record through QA and redirect checks before you treat it as launch-ready or automate anything around it.
UTM QA Checker
Validate the finished link before launch so the spreadsheet never becomes a record of a broken asset.
Use the QA Checker →Redirect Checker
Trace the live route and confirm the final destination so the published record includes what the link actually does in the wild.
Inspect the redirect path →Tracking Automation
Only automate the logging workflow after your naming, QA, and redirect controls are already stable and trusted.
See the automation layer →Automate link logging
Use this when the sheet is no longer the whole workflow and you need publish URLs, final URLs, owners, statuses, and review notes to move faster without losing evidence.
Open automated logging guide →FAQ
Short answers for the operational questions teams ask when they try to keep one campaign tracker clean across multiple channels.
What is the point of a campaign tracking spreadsheet if I already have GA4?
GA4 shows what happened after launch. The spreadsheet records what you intended to publish, who owned it, which URL went live, and where it finally landed.
What should I log before launch?
Log the destination URL, published URL, final destination if redirects are involved, source, medium, campaign, placement, owner, status, and launch timing.
When should I update the sheet after launch?
Update it when the link goes live, when the final destination changes, when ownership changes, and when there is a result or anomaly worth preserving.
Should I still use QA and redirect checks if I log everything here?
Yes. Logging is the recordkeeping layer. You still need the QA Checker to validate the built link and the Redirect Checker to confirm the live route.