The short answer
UTM parameters label the traffic arriving through a campaign link. They help organize acquisition reporting, but adding a campaign tag does not by itself collect purchase revenue, import spend, or establish causation. A useful ROAS report needs those additional records and a consistent matching rule.
Choose a naming convention
Google Analytics documents custom campaign URLs and parameters such as utm_source, utm_medium, and utm_campaign. Use a shared convention for the source, channel, and campaign names your team actually uses. Avoid personal information in URL parameters.
For example, choose whether campaign labels use lowercase and hyphens, then apply that rule consistently. Preserve a mapping between the label and the advertising platform's campaign identifier. Renaming a label midway through a campaign can fragment reports unless you keep a mapping.
Join three pieces of information
You need campaign-labeled traffic, eligible conversion revenue, and matching advertising spend. Confirm how your analytics system assigns a purchase to a source and how the reporting date is selected. A URL label is not a replacement for that attribution definition.
Illustrative example: a consistently defined campaign has $2,400 of attributed revenue and $800 of imported or reconciled spend. Its ROAS is $2,400 / $800 = 3×. If another $200 of spend belongs to that same campaign but was omitted, the corrected denominator is $1,000 and ROAS becomes 2.4×.
Test the full journey
Open a tagged link in a permitted test workflow, check redirects, and confirm the landing URL retains the intended parameters. Then inspect the analytics report after its normal processing delay. Test the purchase event separately, including value and currency. Do not assume a successful page visit proves conversion tracking is correct.
Document gaps
Consent choices, missing identifiers, cross-device journeys, and different attribution rules can leave reports with different totals. Keep unmatched traffic or revenue visible. Use tags to improve consistency, while retaining an order-level and spend-level reconciliation for important budget decisions.
Audit the campaign join
- Gather: Use consistent source, medium and campaign names and map them to the spend export.
- Produce: Test redirects, revenue events and cost matching as separate steps.
Decision boundary: Campaign tags alone do not collect purchase values or import advertising spend.
Next reading
Examples are illustrative, not client results or benchmarks. The calculations use the inputs shown; real-world decisions depend on your records and assumptions. Report a correction.