A click trigger is a condition in Google Tag Manager that sets off one or more tags whenever someone clicks a particular element on the page, such as a phone number, an email address, a “Book now” button or a link to another website. It is how most businesses start measuring the actions that do not load a new page.
How a click trigger works
Tag Manager listens for clicks in the browser. When one happens, it captures details of the clicked element in built-in variables: Click URL, Click Text, Click ID, Click Classes, Click Element and Click Target. They are switched off in a new container and need enabling under Variables. The trigger compares those values with the conditions you set and, when they match, fires every tag attached to it.
There are two click trigger types:
- Just Links responds only to clicks on links. It suits tel:, mailto: and outbound links, and has an option to wait briefly for tags to finish before the browser follows the link.
- All Elements responds to clicks on anything: buttons, images, menu items, accordion headings. It is more flexible and more likely to misfire.
Either type can fire on all clicks or on some. In practice you nearly always choose some clicks and add a condition, for example Click URL starts with tel: to catch taps on a phone number, or Click Element matches the CSS selector .book-button to catch one particular button.
Why it matters
For many UK service businesses, a tap on the phone number from a mobile or a tap through to WhatsApp is the enquiry. If those clicks go unrecorded, a campaign can look as though it produces nothing while it is in fact producing conversations. Click triggers turn those actions into GA4 events and, once marked as key events, into conversions you can import into Google Ads for bidding.
Every tag a click trigger fires still has to respect the visitor’s consent. On a UK site, analytics and ad tags should only fire once the visitor has accepted the matching cookie category, so in Tag Manager the click trigger and the consent check work together; one does not replace the other.
Common mistakes
- Missing clicks on the inner part of a button. With All Elements, the click registers on the innermost element, often an icon or a span inside the button, so a condition on the button’s class fails. A selector that also matches its children, such as .book-button, .book-button *, fixes this.
- Relying on Click Text. Button wording changes, and browser translation changes it again. Use a stable ID, class or data attribute, and ask your developer to add one if there is none.
- Treating a submit-button click as a lead. The click fires even when the form fails validation. Track successful submissions instead, with a form submission trigger or, better, a confirmation the form sends after it succeeds.
- Duplicating enhanced measurement. GA4 already records outbound clicks and file downloads automatically, so a click trigger for the same action counts it twice.
- Reading a tel: tap as a call. A tap opens the dialler; it does not prove anyone rang. For phone leads that drive ad bidding, pair it with call tracking.
How to act on it
- Write down the clicks that matter to the business: phone, email, WhatsApp, booking buttons and links to an external booking system. Leave the rest alone.
- Enable the built-in click variables, create a Just Links trigger for each type of link, and use All Elements only where the button is not a link.
- Test in Tag Manager’s preview mode. Click each element and check that the trigger fires once, and that it does not fire on similar elements nearby.
- Confirm the event arrives in GA4’s DebugView, then mark the ones that represent enquiries as key events.
Paid campaigns are only as good as the actions they are judged on, so check this tracking before any budget is scaled up in performance marketing. A bidding strategy fed miscounted clicks will happily spend more on the wrong thing.