How to Track Button Clicks with Google Tag Manager

In your GTM workspace, click Variables in the left menu, then click Configure in the Built-In Variables section.

A panel opens with a long list of checkboxes. Scroll to the Clicks section and check all six:

• Click Element
• Click Classes
• Click ID
• Click Target
• Click URL
• Click Text

These are GTM’s built-in click variables: pre-made variables that capture information about whatever someone clicks on your page. (Click Target captures the link’s target attribute, like _blank. You won’t use it often, but checking everything is the simplest path.) GTM ships with them turned off, which is why this step comes first. Without it, every click variable stays empty.

Close the panel. You should see the click variables listed in your Built-In Variables table.

Before you can tell GTM “track this button,” you need to know what makes that button unique. Preview mode shows you.

Click Preview in the top right of your workspace. A tool called Tag Assistant opens in a new tab. Here’s what that means: Tag Assistant is GTM’s testing environment, which loads your site with a debug connection so you can watch what GTM sees, without affecting real visitors.

Enter your site’s URL and click Connect. Your site opens in another tab with a “Tag Assistant Connected” badge in the corner. Go to the page with your button and click the button once.

Now switch back to the Tag Assistant tab. This is the part where most tutorials lose you, so let’s read the debug pane together.

Down the left side you’ll see a timeline of events: Container Loaded, maybe DOM Ready and Window Loaded, and near the top, a new entry called Click (or Link Click if your button is a link). That entry is your button click.

Click that Click entry, then click the Variables tab across the top of the main panel. You’ll see a table listing each variable with its current value. Find the click variables you enabled in Step 1 and note their values. For a typical CTA button:

You should see real values next to the click variables. If they all show “undefined,” go back to Step 1: the built-in variables aren’t enabled.

Write down one value that uniquely identifies your button. Which one should you pick?

Click ID is the most reliable when it exists, because IDs are meant to be unique on a page. Click Text is the most common fallback and works well when no other button shares that text.

Back in your GTM workspace, click Triggers in the left menu, then New.

Name the trigger something you’ll recognize later, like “Trigger - Get a Quote Click.” A naming pattern saves you real pain once your container holds 30 triggers.

Click the trigger configuration box and choose Click - All Elements. This trigger type fires when someone clicks anything on the page: buttons, links, images, divs. (Click - Just Links only fires on <a> link tags. All Elements is the safer default, and the FAQ below covers the difference.)

Under “This trigger fires on,” select Some Clicks. This matters: All Clicks would fire your tag on every single click anywhere on your site.

Now set the condition using the value you noted in Step 2:

Click Text > contains > “Get a Quote”

Or, if you’re using an ID: Click ID > equals > “quote-button”.

Click Save. You should see your new trigger in the Triggers list with its condition summarized under the name.

The trigger knows when to fire. Now build the tag that tells GA4 what happened.

Click Tags in the left menu, then New. Name it to match the trigger, like “GA4 Event - Get a Quote Click.”

Click the tag configuration box and choose Google Analytics: GA4 Event. Two fields matter here:

1. Measurement ID: enter your GA4 Measurement ID (the one that starts with G-). The tag loads the Google tag for you and routes the event to the right GA4 property. Older containers may show a Configuration Tag dropdown instead; pick your GA4 tag there.
2. Event Name: what this click will be called in GA4 reports. Use lowercase with underscores, and be descriptive:

cta_click_get_quote

An event in GA4 is a recorded interaction, and the name is how you’ll find it in every report, so pick something future-you will understand. If you want the deeper background on naming and how events flow into reports, see how GA4 events work.

Optional but recommended: expand Event Parameters and add context. A parameter is an extra detail attached to the event.

• button_text with value {{Click Text}}
• page_url with value {{Page URL}}

The double curly braces tell GTM to fill in the variable’s value at click time.

Finally, scroll down to Triggering, click it, and select the click trigger from Step 3. Click Save.

You should see the tag in your Tags list, with your event name in the configuration and the trigger listed beside it.

Nothing is live yet. Click Preview again, connect to your site, go to the page, and click your target button.

In the Tag Assistant debug pane, click the new Click entry in the left timeline. Check two things:

1. Your GA4 event tag appears under Tags Fired (not under “Tags Not Fired”).
2. Clicking the tag shows the trigger conditions, each with a green check.

Then confirm the data reached GA4. Open GA4 and go to Reports > Realtime. Find the “Event count by Event name” card.

You should see cta_click_get_quote (or your event name) in the list within a few seconds. Click the event name and you’ll see its parameters, including button_text.

If the tag fired in Preview but nothing shows in GA4, skip ahead to the troubleshooting section. The fix is usually the Measurement ID.