# How to Improve B2B GA4 Insights: CTA Tracking

_Last updated: 2026-01-02_

Google Analytics 4 (GA4) requires call-to-action (CTA) tracking configured through Google Tag Manager (GTM) to capture meaningful user intent signals—such as clicks on navigation, hero, and footer CTAs—with context about location, origin URL, and destination URL.

## Why GA4 and GTM Together

GA4 ships with basic standard events that cannot be customized without GTM. Google removed several features from Universal Analytics (UA), including the ability to set engagement duration conversions. GTM functions as a middleman between your website and downstream platforms (Google Ads, GA4, chatbots, Reddit, LinkedIn) by watching website behavior and firing signals to systems that store and analyze data. GTM itself does not store or analyze data.

Meaningful GA4 results require GTM configuration.

## GA4 Key Events and Custom Dimensions

GA4 Key Events (formerly called "conversions" before that term was repurposed in Google Ads) are tied to website behaviors indicating user interest and intent—such as CTA clicks. These events are configured in GTM, then designated as a Key Event in GA4. You can then view Key Events in GA4 reports using custom dimensions or export them to a data visualization tool.

Custom dimensions must be registered in GA4 to be stored in long-term data. Consult GA4's [custom dimension limits](https://support.google.com/analytics/answer/14240153?hl=en) and [registration process](https://support.google.com/analytics/answer/2709829?hl=en#zippy=%2Cin-this-article) documentation.

CTAs are any clicks that are meaningful—whether they direct users to a download prompt or a new page, not only traditional buttons. Proper CTA analysis requires capturing the CTA location (navigation bar, hero, page bottom, blog post), the referring URL, and the destination URL using rigorous labeling, page architecture, JavaScript, and Google Tag Manager.

## Why and How to Tag CTAs

Tagging CTAs requires organization to capture and report data legibly. Classify CTAs by importance and hierarchy.

Top-tier CTAs deserve distinct designation. For example, a user clicking the main CTA in navigation differs from a user engaging with a landing page and clicking the hero CTA. Navigation CTAs are recorded; hero CTAs indicate landing page effectiveness. The meaning of a navigation CTA depends on its prompt—a "Log In" CTA likely indicates a customer or internal employee.

Begin by documenting all important CTAs to be tagged. Steps two and three involve understanding CTA importance, intent, and hierarchy ranking.

## CTA Capture in Google Tag Manager

GTM templates ensure consistent variables are applied across all CTA clicks, allowing designation of different categories for different click-type events. These templates also capture the click path—where the click occurred and the post-click destination.

Proprietary code leverages GTM lookup tables to translate user behavior data (such as clicked element classes and IDs) into human-friendly names for reporting. This enables visualization of data by exact page location of the CTA click.

Capturing only the CTA and click path is insufficient. Multiple page locations may host a single CTA—for example, a Demo Request button may appear in the main navigation, in a CTA above the footer on most pages, and in a landing page's hero, sometimes all on one page. Understanding where each click occurred on the page is critical.

## Consistent Website Styling for Scalable CTA Mapping

Maintaining a unique button ID for each CTA location is not scalable. Consistent website styling allows creation of an alternative ID system.

Without consistent style usage, every CTA variable appears the same (identical ID, unclear DIV1 versus DIV2 distinction), making location mapping impossible.

Proprietary code uses multiple values from the click element. JavaScript variables find and fetch the containing DIV, the DIV class, the parent DIV and its class, then translate that data into human-friendly values readable in reports.

The number of variables collected for each CTA makes it nearly impossible for multiple CTAs to meet identical parameters, whether they share button IDs or not. The detail provides a unique profile allowing differentiation between, for example, Demo Request buttons in navigation, hero, and page bottom, even if they share the same button ID.

## Next Steps

Future articles in the Better Insights in GA4 series will cover additional GTM and GA4 best practices for capturing key events, including video data points and engagement milestones.