MTK Attribution docs
Everything for setting up and understanding MTK Attribution. Install guides first — every platform is the same two ideas: load the tag, then point a few hidden fields at your attribution data. Below them, the references for what gets captured and why.
Set up on your platform
Set field names directly — the tag matches by name.
React-controlled forms — match by field title plus a helper script.
Hidden fields prefilled via SQF_ URL params — companion script included.
WordPress + GTM — drop a token into each field's Default Value.
WordPress — paste the token into a Hidden field's Default Value.
WordPress — paste the hidden-input block into the form template.
Source Code embeds fill directly; iframe embeds via the companion script.
Iframe embeds — Field Aliases plus the companion script.
Inline embeds fill directly; iframe embeds via the companion script.
Set field names in the form — the tag matches by name.
Hand-built forms — name hidden inputs, or read values in JS.
Any site that renders a real form — the universal method.
Don't see your platform? The tag works anywhere a form renders in the DOM — the same token approach applies. Stuck on something? See Troubleshooting.
Under the hood
What the tag captures, exactly how it categorizes every visit, the UTM templates that light everything up, and the full data-source reference for verifying your setup and debugging.
Every value recorded about a lead, in plain language, with example values and a worked multi-touch example.
The exact classification rules — every click ID, utm_medium value, and referrer domain the engine looks for.
Copy-paste tracking templates for Google Ads, Meta, Microsoft, LinkedIn, and TikTok that light up every field.
Developer reference for every data-source expression — Query sources, Cookies & Click IDs, Insights, resolvers.