Monitor your first website free, no card needed. Explore SENRIKO

Free UTM Survival Test

Redirects, storage and form fields, in a real browser.

Paste a landing page. A real browser opens it with a test campaign tag, follows every redirect, and reads which form fields picked the tag up by the time the page settled.

Leads that arrive without a source usually lost it on the way: a redirect that rebuilt the address, a form on the next page that only reads its own URL, a script that fills the field too late. This shows where it went.

This check is switched off for the moment. Everything on this page still describes how it works.

example.com/spring-saleExample

Campaign data survives 2 redirects and reaches a hidden form field

Redirects
2 (1 server, 1 script), kept
Tags on page
Google tag, Meta Pixel
Stored on page
1 cookie
Form fields
utm_source, utm_campaign filled
Ad click IDs
Not tested here
Submission
Not tested here
What it follows

Every step between the link and the form

The test adds utm_source=senriko-scan, utm_medium=senriko-check and utm_campaign=senriko-attribution to the page you give it, and drops your own query. Then it watches where those three values go.

  • 301 → /landing

    Server redirects

    http to https, www, a trailing slash, an old address, a language. Each hop is shown with its status code and whether the values were still on the address after it.

  • location.replace(…)

    Script redirects

    A page that sends the visitor on with JavaScript, the way geo and language switches often do. Server only checkers cannot see these at all.

  • <meta http-equiv="refresh">

    Meta refresh

    Told apart from a script redirect, because it is fixed in the template rather than in the page's code.

  • history.replaceState

    The address after the page settles

    Some single page apps tidy the query out of the address once they load. Whatever read it first still has it; anything that reads it later does not.

  • _campaign=senriko-scan

    Where the page kept it

    Cookies, localStorage and sessionStorage entries that hold a test value, by name. A form on another page can only read the campaign from here.

  • <input type="hidden" name="utm_source">

    Form fields filled on load

    Every form on the page, including accessible frames, read once the fields stop changing. Fields that hold a test value, and empty ones named like campaign fields.

  • /contact

    The form on another page

    Give a second address on the same site and it is opened directly afterwards, in the same browser, to see whether cookies or storage carry the campaign there.

How to read it

One line first, then the evidence

The result opens with one sentence about where the campaign data ended up, then a table, the redirect chain and the form fields behind it.

Reaches a form field
The values survived every redirect and at least one field holds one. What happens when the form is sent is a separate question.
Dropped at a redirect
A redirect rebuilt the address without the query. The hop is named with its status code: that is the rule to fix on the server or in the page.
Removed from the address
No redirect lost it, but the page took the query off its own address after loading. Check that whatever needs the campaign reads it before then.
Reaches the page, no field picks it up
The values arrived, the page has a form, and no field held them by the time the page settled. Often a capture script that is missing, or one that fills fields only on submit.
Needs an ownership-verified test
The page sits behind bot protection, needs its own query parameters, left for another site or would not answer in time. A test you run on your own verified site can go further.
Where it usually goes

Why leads arrive without a source

The same few causes, over and over. Each one shows in a particular line of the result.

  • 01

    A redirect rule that drops the query

    http to https, non www to www or an added slash, written without the query string. Shown as the first hop that drops the values.

  • 02

    A language or geo redirect

    A script that builds a new address for the visitor's language and forgets the parameters. Shown as a script redirect.

  • 03

    The form is on the next page

    The landing page has the campaign, the contact page does not, and the hidden fields only read the current address. Give the form page to see it.

  • 04

    The field is filled too late

    A capture script that waits for consent or runs on submit. The test waits up to eight seconds after load; a field filled only on submit stays empty here.

  • 05

    The form is in someone else's frame

    An embedded form on another domain cannot read the parent page's address unless the embed passes it on.

  • 06

    The field was renamed or removed

    A template copied without its hidden fields, or a field whose name changed. Shown as a form with no campaign fields at all.

By hand

Checking it by hand

The same test, step by step, for when you want to see it yourself.

  1. Step 1

    Open the page with a test tag

    Add a test value to the address and open it in a private window.

    ?utm_source=test&utm_campaign=test
  2. Step 2

    Watch the address bar

    After the page settles, is the query still there? If not, open the Network panel and look at each redirect.

    301 Location: /landing
  3. Step 3

    Find the hidden field

    In the Elements panel, search for the field's name and check its value.

    input[name="utm_source"]
  4. Step 4

    Send a test lead and open it in the CRM

    The only proof that the value arrives where reports are built. This tool stops before this step.

Questions

Questions

What does the UTM Survival Test check?
Whether a test campaign tag survives the redirects in front of a landing page, where the page stores it, and which form fields hold it once the page has loaded. It opens the page in a real browser, so script redirects and fields filled by JavaScript are seen too.
Which UTM values does it use, and will they show in my analytics?
utm_source=senriko-scan, utm_medium=senriko-check and utm_campaign=senriko-attribution. Analytics and ad requests are blocked during the visit, so GA4 and the ad platforms get no event from it. The visit can still appear in your server's access log, like any visit with a tagged link.
A field shows as empty. Is the form broken?
Not necessarily. Some capture plugins write the values at the moment the form is sent, and some sites fill them on the server. The test reads the form before anything is sent, so it cannot see either.
Does it check gclid or other ad click IDs?
No. A made up click ID could reach analytics or an ad platform, so the public test never adds one. Ad click IDs are checked on sites whose owners have verified them, with the requests held back before they leave the browser.
My form is on another page. Can it test that?
Yes. Put the form page in the second field. It is opened after the landing page, in the same browser, so cookies and storage the landing page set are still there.
Does it work with HubSpot, Typeform or other embedded forms?
It reads frames it can reach. Many embedded forms load their fields with a data request, which this test blocks, so they may not appear. A verified test on your own site can follow them further.
Can I send the result to a client?
Yes. Share result makes a link that works for 30 days and shows the result without your address's query. You can take the link back at any time.
Is it safe to run on any site?
It makes one visit, clicks nothing, fills nothing and sends nothing. It reads robots.txt first and does not visit pages that disallow it.
The other tools

The other free tools

Check a page in one tool and open the result in another without waiting again. The four tag tools share one visit, and the two consent tools share three.

What it does not do

Where this test stops

  • 01

    It never fills or sends a form, so it cannot show whether the value travels with the lead or reaches your CRM.

  • 02

    It adds no gclid, fbclid or msclkid. Ad click IDs are tested only on a site you have verified.

  • 03

    It does not accept the cookie banner. A script that waits for consent before filling fields will look like it never ran.

  • 04

    It blocks images, media and background requests. A form that loads its fields with a data request may not appear at all.

  • 05

    The form page is opened directly, not by clicking a link, so a campaign passed only in the link itself is not seen.

The real check, in the cabinet: every step from the open page to your CRM, proved one by one or marked with what it still needs.

Verify my domain and test a real conversionCheck another page