Free tool
Tag your campaign links so WhatsApp traffic stops hiding in direct
Build clean, consistent UTM-tagged URLs for broadcasts, chatbots and QR codes — lowercased, underscore-safe and copy-ready in seconds.
Build your tagged link
Where the click comes from — the platform.
How it was delivered — broadcast, chatbot, widget…
utm_campaign is required for campaign reporting.
Your tagged URL
Live preview using www.infiq.in as an example — enter your own URL above and it swaps in instantly.
Existing query parameters on your landing page URL are preserved — only the utm_* values are added or replaced. Everything runs in your browser; nothing is sent to a server.
How it works
Three steps, no signup
Paste your landing page URL
Drop in the full page address, https:// included. Existing query parameters are kept intact — the builder only adds or replaces the utm_* values.
Fill source, medium and campaign
Sensible WhatsApp defaults are pre-filled: whatsapp as the source and broadcast as the medium, with suggestions for chatbot, widget, signature and QR links. Name the campaign or pick an example.
Copy the tagged URL
The link updates live as you type, with values normalised to lowercase and underscores so your reports stay clean. Copy it straight into your broadcast, bio or QR code.
Why it matters
A UTM taxonomy you can actually report on
UTM tagging fails quietly. Nothing errors when one teammate tags a link with WhatsApp, another with whatsapp and a third with WA — you simply end up with three report rows for one channel, and every comparison you run afterwards is wrong by an unknown amount. The fix is boring and effective: agree on a short, enumerated list of allowed values before anyone tags anything. One spelling per source, all lowercase, and a fixed set of mediums that describe how the click was delivered — for WhatsApp that usually means broadcast, chatbot, widget, signature and qr. Write the list down where campaigns are planned, and treat any value outside it as a bug.
Tagging matters more on WhatsApp than on most channels because of how the traffic arrives. When someone taps a link inside the app, the browser typically opens without a referrer header, so analytics tools have no idea the visit came from WhatsApp and file it under direct. A channel that might be driving a meaningful share of your sales becomes invisible in exactly the report your budget decisions come from. UTM parameters solve this because they live in the URL itself: no referrer is needed, and every tagged click is attributed to the source, medium and campaign you chose.
Campaign names deserve the same discipline as sources. A pattern like festival-sale, winback-oct or new-launch — a short descriptor plus an optional date marker — sorts cleanly and still makes sense six months later. Avoid spaces (they encode to %20 or + and are painful to read in reports), and never encode information in the campaign name that belongs in another parameter: message variants go in utm_content, audience segments in utm_term.
Once links are tagged, the payoff shows up in GA4 under Reports → Acquisition → Traffic acquisition. Set the primary dimension to Session source/medium and your WhatsApp rows appear exactly as you tagged them — whatsapp / broadcast next to whatsapp / chatbot — with sessions, engagement and conversions per row. Add Session campaign as a secondary dimension to compare individual sends, and give the data a day or so to settle before judging a campaign, since GA4 reports are not fully real-time.
FAQ
Frequently asked questions
Which UTM parameters are required?
Three parameters do most of the work: utm_source (the platform the click came from, e.g. whatsapp), utm_medium (the delivery mechanism, e.g. broadcast or chatbot) and utm_campaign (the specific push, e.g. diwali-sale-2026). utm_term and utm_content are optional refinements — utm_content is useful for A/B tests where two message variants point at the same page.
Why does WhatsApp traffic show up as direct in analytics?
Clicks from the WhatsApp app usually arrive without a referrer header, so analytics tools cannot tell where the visitor came from and file the session under direct or (not set). UTM parameters travel inside the URL itself, so they survive the missing referrer and attribute the session correctly.
Are UTM values case-sensitive?
Yes. GA4 and most analytics tools treat WhatsApp, whatsapp and WA as three separate sources, which splits one channel's traffic across multiple report rows. That is why this builder lowercases values by default — pick one spelling convention and use it everywhere.
Will adding UTM tags break a URL that already has query parameters?
Not with this builder. It parses your URL properly and appends the utm_* parameters alongside any existing ones, replacing old utm_* values rather than duplicating them. Hand-concatenating strings with a second ? is the usual way tagged links break.
Where do I see UTM data in GA4?
Open Reports, then Acquisition, then Traffic acquisition, and switch the primary dimension to Session source/medium — your tagged clicks appear as rows like whatsapp / broadcast. Add Session campaign as a secondary dimension to compare individual campaigns, or build a free-form exploration if you need utm_content and utm_term breakdowns.
Still have questions?
Book a demoMore free tools
Keep your stack sharp
WhatsApp Campaign Planner
Plan audience, timing, template and follow-ups for your next campaign.
Open toolMarketing Calendar Generator
Generate a festival-aware WhatsApp campaign calendar for the months ahead.
Open toolBusiness Profile Optimizer
Score your WhatsApp Business profile and get a prioritised fix list.
Open toolSend-Time Planner
Pick the best send windows by audience routine, and avoid quiet hours.
Open tool
Now measure the campaigns behind the links.
InfiQ sends your tagged links at scale — broadcasts, chatbots and a shared inbox on the official WhatsApp Business API, with delivery and click stats in one dashboard. 7-day free trial, no card required.