How to Report Music Campaign Results After a UTM Rename
- →Use exact campaign values, including capital letters and punctuation.
- →Verify the mapping against URLs and placement records.
- →Keep the export and the combined view side by side.
- →Add equivalent counts once and calculate any rate from its combined numerator and denominator.
Check which links actually changed
You renamed the campaign on your ad links after launch. The first links may still run in an older ad, a Story highlight or an email. Pull the URLs that were actually used. Write down the old tag, the new tag, the release and the placement. Use your change log or saved ad destinations to confirm which label belongs to which buy.
Google treats UTM values as case sensitive. Night-Drive and night-drive can appear as different values, and a similar name can belong to a different channel or release. Keep each spelling exactly as it appeared in the report. Give the combined view a stable release name of your own.
Check Google’s rules for manual campaign tagsStart from one session report
In GA4, use a session-scoped report for the property that measures your release page. For a manually tagged campaign, keep Session manual campaign name and the matching session source and medium dimensions. Use one date range and the same filters for both names. Record the specific event you chose, such as a recorded Spotify button tap, and how it was counted.
Export the detail rows once. If the export has campaign detail and an overall total, keep the total as a reference. Importing the total as another detail row counts some sessions again. If you pull more than one file, check the property, dates, filters and dimensions for overlap before you add anything.
The old and new labels can both appear on the same day when old placements are still live. Mutually exclusive label rows from one session report can still be added. The overlap to avoid is including the same underlying row or sessions more than once across reports.
Read Google’s guide to acquisition report scopeVerify the match before grouping the row
Create a mapping from the exact source, medium and campaign to the release and placement you are reporting. Where you have a reliable ad ID or other placement record, use it to confirm the link. Keep organic placements in their own group even if they share the same campaign tag.
Leave the row unresolved if the name was reused and the report cannot tell which placement generated it. A name in a spreadsheet does not establish which link a listener opened. Keep the original value and the evidence needed to resolve it. The report can show a verified total and an unresolved count side by side.
Review paid and organic traffic to a shared release pageWork through a rename on release weekend
In this fictional release, one GA4 report shows 120 sessions and 24 recorded Spotify button taps for instagram / paid_social / Night-Drive. The same report shows 80 sessions and 16 taps for instagram / paid_social / night-drive. The saved ad URLs confirm both are the same buy. Report 200 paid sessions and 40 recorded taps for those two verified rows.
A row labelled night-drive has 14 sessions and three taps with no source and medium you can verify. Leave those in the unresolved row. A paid subtotal for the first two rows also shows 200 and 40. Keep that subtotal as a cross-check. Adding it to the detail would double the same recorded activity.
If the same report shows 18 and 10 sessions containing the selected action, the combined session key event rate is 28 divided by 200, or 14 percent. The 40 raw taps can include repeat taps in a session. Use the reported session count containing the event, or the rate for the combined segment, when that is the number you need.
Check the session and key event metric definitionsKeep the mapping with the next campaign report
Save the raw export, mapping worksheet, report dates and the evidence for each decision. Keep a note if the landing page, consent setup or event changed at the same time. Those changes can change what the counts represent, so review them before combining the rows.
For new placements, the VLVTN UTM builder can put your chosen source, medium and campaign into the URL. Copy the link back into your placement record. The worksheet gives you a place to record old values for as long as those links are still circulating.
Download the UTM rename reconciliation worksheetBuild the tagged link for your next placement
Use the exact campaign name you plan to look up in your report.
Open the UTM link builder→Frequently asked
Can the old and new UTM names both appear on the same day?
Yes. Links carrying both names can still be in circulation. Verify each placement and use one session-scoped report with mutually exclusive rows.
Can I group every campaign name after converting it to lowercase?
Use a normalized label only after verifying each original value belongs to the same release and placement. Keep the original spelling and separate channels when the distinction matters.
Can I add the session key event rates from both campaign names?
Calculate the rate from combined eligible sessions with the event and combined eligible sessions, or read the rate for the combined segment. The two row rates have different denominators.
What if the new link also changed the event I was counting?
Record both definitions and the change time. Keep the action counts separate until you establish a comparable metric.
Bradley J Simons founded VLVTN and runs his own paid Meta and Spotify ad campaigns as the artist Babbage. He writes about paid music marketing from the buyer's seat, with his own money on the line.
Keep reading
A simple naming system for source, medium, campaign, and content on music ad links.
Move the release page without losing track of the ads and older links that still send people there.
Your cost per result can change when the result itself changes. Here is how to check whether the two periods still have a fair comparison.
Keep one release page. Give the ad and the organic placement different tags so you can read their results side by side.