What the validator checks
The parser first checks for a complete HTTP or HTTPS URL, unencoded whitespace, malformed percent escapes and embedded credentials. It then reads the query string, checks known UTM parameter names and identifies repeated fields. A query is the part after ? and before any # fragment.
This tool uses a manual-tagging convention that expects utm_source, utm_medium and utm_campaign to be present and non-empty. That is our review rule, not a claim that every acquisition link must carry all three. An auto-tagged Google Ads link can have a valid measurement setup without these manual fields. A detected click identifier produces a review note rather than an instruction to delete it.
Within the batch, the checker also looks for values that differ only by capitalization. It preserves what you pasted. A convention should decide whether newsletter and Newsletter refer to the same source before anyone edits live links or merges historical reports.
Read the fictional example
The first two example links use newsletter and Newsletter for the same-looking source. Both receive a capitalization finding because the difference becomes visible only when the batch is compared. The third link has no utm_medium, so it needs review under the stated manual convention.
If your team decides that lowercase newsletter is the intended source, edit the second link and add email or another justified medium to the third. Run the check again. A report with no issues means only that these supported text checks found nothing; it does not confirm that the destination is live or that Analytics receives a session.
Review findings without changing attribution accidentally
Start with the purpose of the link. A newsletter, paid placement, QR code and internal navigation button may need different measurement approaches. Use acquisition tags for an external campaign where manual labeling is appropriate. Track internal resource navigation with an interaction event instead of inventing a new acquisition campaign for every button.
Resolve a repeated parameter by checking the placement's intended value. A URL with two campaign labels is ambiguous to people and can be interpreted differently by downstream systems. Do not assume the first or last value will always win. The validator reports the duplicate and leaves the decision with the campaign owner.
A warning about a click identifier asks you to inspect the account's tagging integration. Preserve legitimate identifiers through redirects when that is the intended setup. Adding manual tags indiscriminately, stripping query strings or overwriting tracking templates can make measurement worse even if the URL looks cleaner afterward.
Finish the launch check outside the parser
Open a representative final link yourself in an appropriate test workflow. Confirm the intended offer, page and anchor load. Follow any redirects and inspect which parameters reach the final page. Then verify the relevant collection and reporting behavior using your measurement tools and applicable consent settings.
The validator deliberately does not fetch pasted URLs. It cannot inspect redirects, authentication requirements, page status, server logs, channel definitions or Google Analytics events. This keeps the tool useful for pre-publication text review while making its boundary clear.
An address may identify a person without containing an email. The checker flags a few obvious patterns but is not a privacy approval system. Review the whole destination, campaign values and any appended identifiers before publishing or sharing a report.
Save a review the next person can use
Download the CSV after checking the batch. It includes the pasted URL, extracted labels and findings, so a reviewer can connect the issue to the original input. The file is a review worksheet, not a Google Ads upload format. Its cells are quoted and spreadsheet formula prefixes are neutralized.
Keep the review date, placement owner and chosen correction in your campaign register. A naming decision should survive a handover. When a campaign is replaced, preserve the old row so someone investigating a reporting change can see what was published at that time.