The call to action

The button on your landing page has to become this visitor's own click-out, so pressing it records the click and reaches the offer your paths chose. There are two ways to mark it, and they are not the same mechanism.

##utmcap — the tag's hand-off

<a href="#utmcap">Get started</a>

The tag rewrites it to /out/<click id>. This works on every arrival: a redirect, parallel tracking, or somebody who found the page in search.

Any of these are recognised, if #utmcap does not suit your markup:

<a href="#offer">…</a>
<a data-utmcap>…</a>
<a class="utmcap-out">…</a>

Several buttons on one page? Give each a slot, and the reports break click-outs down by it:

<a href="#utmcap" data-utmcap-slot="hero">Get started</a>
<a href="#utmcap" data-utmcap-slot="footer">Get started</a>

#/out/{click_id} — the redirect macro

<a href="https://app.utmcap.com/out/{click_id}">Get started</a>

This is the click-out URL as it is written down, braces and all, pasted by hand. The tag substitutes the id — but only where a redirect brought the visitor.

That is deliberate. {click_id} is a macro out of a tracking URL, and a tracking URL is a redirect. Under parallel tracking there is no redirect at all, and an organic visitor never had one either. Filling it in those cases would make a redirect macro work without a redirect, which reads as the same mechanism as #utmcap when it is a different one.

#Which fills when

So: on a parallel-tracking campaign, use #utmcap. A pasted /out/{click_id} will never fill there.

Where a redirect did happen, the origin travels with the visitor in a cookie — so a pasted macro still fills on page two of the same visit, rather than working on the landing page and dying on the checkout page.

#Why an unfilled marker is left alone

A marker the tag cannot fill keeps its original href and gains data-utmcap-pending="1". It is never pointed at a URL that would 404.

That attribute is worth knowing about, because it is the honest signal that the tag ran and had nothing to fill with. If you want a button that visibly waits, you can style it:

a[data-utmcap-pending] { opacity: .6; pointer-events: none; }

#The last row of that table

#utmcap stays literal when nothing identifies the page: no click id, no utm_id, and the address is not one UTMCAP knows as a landing page.

That last part is the usual cause. The tag sends the page's own address and UTMCAP matches it against your registered landing pages — so a page whose URL in the app does not match the address a visitor actually reaches cannot be recognised. A trailing slash, www, or a staging address saved instead of the live one will all do it.

See troubleshooting.