Skip to main content
Question

WhatsApp links drop our UTM parameters (only mcp_token arrives)

  • Nov 16, 2026 12:13 AM UTC
  • 1 comment
  • 5 views

yovely

On WhatsApp, both an "Open website" button in a broadcast reply and a plain text link in a regular message (auto-shortened to mc.ht) open our landing page with ?mcp_token=... only. Our utm_source and utm_campaign are gone.

The Pixel help article shows mcp_token appended next to existing UTMs, and the AI support assistant said it is expected and cannot be controlled.

Has anyone kept custom query parameters on WhatsApp links? A custom field in the URL, another button type, a setting?

1 reply

SumGenius
Forum|alt.badge.img
  • Smooth talker
  • Nov 16, 2026 4:51 AM UTC

The fix that doesn't depend on any ManyChat setting is to link to a redirect you control instead of to the landing page itself.

Set up something like yoursite.com/go/wa-broadcast that 302s to your landing page with utm_source and utm_campaign already on it. Whatever happens to the link on the way (mc.ht shortening, token appended), the UTMs get added on your side after the click, so they always arrive.

Have the redirect also pass through any query string it receives. That way mcp_token still reaches the page and the Pixel keeps working alongside your UTMs.

You can do this without code using Cloudflare redirect rules, a WordPress redirect plugin, or a Bitly link with the UTMs baked into the destination. One redirect per campaign is enough.