UTM auto-tagging
When a visitor reaches your site from an AI chat link, the redirect can add UTM parameters so that traffic is attributed correctly in your external analytics. AgentFi uses utm_source, utm_medium and utm_campaign.
Why it matters#
AI platforms frequently strip the Referer header. Without it, Google Analytics and similar tools classify those visits as direct traffic, and the AI channel is invisible in your reports. UTM parameters solve that from AgentFi's side.
The three modes#
| Mode | Behaviour | When to use it |
|---|---|---|
| Off | Adds no UTM parameters at all. Outbound links use the original URL exactly as configured. | You already handle attribution another way, or you do not want URLs altered. |
| Fill missing | Adds utm_source, utm_medium and utm_campaign only when those keys are not already present on the target URL. | The prudent option. It respects any tagging you already have. |
| Override | Always replaces all three parameters with AgentFi's values, even when the target URL already carries them. | You want all AI traffic tagged uniformly, with no exceptions. |
Fill missing is the sensible default: it tags whatever arrives untagged and never overwrites campaigns you have already set up.
Checking the result#
With tagging on, the referral visits listed in LLM referral traffic show paths carrying the added parameters:
/services/consulting?utm_source=chatgpt.com&utm_medium=referral&utm_campaign=agentfiIn your analytics tool, that traffic will be grouped under the matching source instead of showing up as direct.
UTM tagging affects attribution in your external analytics. AgentFi's own dashboard metrics do not depend on it: they are computed from the Referer header and the /agentfi/pages/ redirect.