Jotform
Which Jotform install you need comes down to one thing: where the fields live. The Source Codeembed drops the form's real HTML into your page, so the tag fills the fields directly — that's the simplest install. The Standard and iFrameembeds both render the form on Jotform's domain, where the tag can't reach it; there you pass the values in on the form's URL and let Jotform prefill the fields itself. Steps 1 and 2 below are shared by all three — then pick your method.
Load the tag on the page that hosts the form
The tag belongs on your site — the page the visitor is actually looking at — never inside the form. Paste the loader into the <head> on every page, or add it as a Custom HTML tag in Google Tag Manager firing on all pages.
<script src="https://attr.boggsmtk.com/v1/tag.js?k=YOUR_LICENSE_KEY"></script>
Swap YOUR_LICENSE_KEYfor the client's key from the dashboard.
If you send traffic to a Jotform-hosted form page (form.jotform.com/…) rather than embedding it, there is no page of yours to tag. Link to it with the values already on the URL — see the iFrame guide for how those parameters are built.
Give each field a Unique Name
In the form builder, add a field for each value you want to capture. Then on each one, open Properties → Advanced, expand Field Settings, and set the Unique Name to the field's HTML Name from your field map (e.g. mtk_first_source). Tick Hide Field so it never shows to the visitor.
The Unique Name is what every method here keys on — it's the query parameter Jotform prefills from, and it has to match character-for-character. Re-open the field after saving to confirm Jotform kept what you typed; if it rewrote it, use whatever Jotform saved and map it in the companion script's RENAME list.
Pick your embed method
In the form builder, go to Publish → Embedand look at what you're using. Jotform offers three, and each has its own guide below. Source Code is only offered for Classic forms — Card forms have the other two.
A single <script src="…/jsform/…"> tag. It writes an iframe into the page, so the values ride in on the form URL — companion script, no edit to the embed code.
An <iframe src="…"> plus Jotform's resize handler. Same story as the Standard embed: the companion script tags the URL before the frame loads.
The form's raw HTML, pasted into your page. The fields are in your DOM, so the tag fills them directly — no companion script. Classic forms only.
Journey JSON and Attribution Summary. The trade-off is that the pasted HTML is a snapshot — re-copy it whenever you edit the form.[mtk:…]tokens into a Standard or iFrame embed's fields.Nothing on Jotform's side replaces them, so the literal token text submits into the lead record. Tokens are for the Source Code route only; on the two iframe routes the fields stay empty in the builder and are filled from the URL.?utm_source=googleads&utm_medium=cpc, submit, and check the entry under Submissions in Jotform. Stuck? Troubleshooting.