Published in: Data Analytics

What Data Are Google Analytics Goals Unable to Track

Author clara evangeline

Published on: 23/07/2024

What Data Are Google Analytics Goals Unable to Track

Accurate goal tracking is the backbone of any robust Google Analytics implementation, yet even seasoned marketers often overestimate what these goals can capture. Understanding what data are Google Analytics goals unable to track is not just a technical exercise—it is a strategic necessity. Google Analytics goals are designed to measure specific,s predefined user actions, such as reaching a thank-you page, spending a certain amount of time on site, or clicking a button. However, they inherently exclude vast swaths of user behavior, engagement quality, offline interactions, and cross-channel attribution nuances. For example, a destination goal can tell you that a user landed on a confirmation page, but it cannot reveal how many times they visited before converting, what they read, or whether they engaged with a live chat. Similarly, time-based goals cannot differentiate between a user actively reading content and one who left a browser tab open while making coffee. These limitations create blind spots that can lead to misguided optimization efforts and inflated or deflated ROI calculations. This article dives deep into the specific data categories that Google Analytics goals cannot track, covering URL-based, time-based, event-based, e-commerce, and custom goals, as well as funnel visualization, cross-domain tracking, mobile app measurement, attribution models, and offline conversions. By the end, you will have a clear roadmap for supplementing your analytics with alternative tracking methods to achieve a complete picture of your customer journey.

The Core Limitations of URL-Based Goals: What They Miss

URL-based goals, also known as destination goals, are the most common type of conversion tracking in Google Analytics. They fire when a user reaches a specific URL, such as a /thank-you or /confirmation page. While simple to set up, these goals are blind to everything that happens before that final page load. They cannot track engagement metrics like scroll depth, time on page before conversion, or interactions with page elements like forms, videos, or accordions. For instance, a user might land on a product page, scroll through reviews, watch an explainer video, and then proceed to checkout. A URL-based goal on the order confirmation page will record the conversion, but it will not capture the video view, the scroll depth, or the time spent reviewing testimonials. This means you cannot attribute conversion quality to specific content interactions.

Another critical blind spot is dynamic URL parameters. Many websites append session IDs, tracking tokens, or campaign parameters to URLs. If your goal is set to match an exact URL like /checkout/success, but the actual URL is /checkout/success?session=abc123, the goal may not fire unless you use a “begins with” match type. Even then, you risk matching unintended pages. Furthermore, URL-based goals cannot track users who convert via alternative entry points, such as deep links from emails or direct access to the confirmation page without following the standard funnel. This creates a false sense of linearity in the conversion path. To address these gaps, combine URL-based goals with event tracking for pre-conversion interactions like button clicks or form field completions. Implement scroll depth tracking via Google Tag Manager to measure content consumption before the destination URL is reached. Also, use regular expression match types carefully to account for dynamic parameters while avoiding over-matching.

From an expert perspective, I have seen organizations miss over 30% of genuine conversions because their URL goals were too restrictive. For example, an e-commerce site set a “begins with” goal on /checkout/ but failed to include a parameter like ?order=confirmed. Users who reached the confirmation page without the parameter were not counted. A better approach is to use a combination of a “begins with” rule and a secondary event tag that fires only when the order ID is present in the page source. This ensures you capture all confirmed orders regardless of URL structure. Additionally, URL-based goals cannot track exit intent—users who leave without converting. Implementing a pop-up survey or exit-intent event can capture reasons for abandonment, data that URL goals completely ignore.

Time-Based Goals: The Illusion of Engagement

Time-based goals measure the total duration a user spends on your website during a single session. The most common threshold is 5 or 10 minutes. However, these goals cannot distinguish between active engagement and passive presence. A user who opens your blog in a browser tab and walks away for 10 minutes will trigger the same goal as a user who reads every word of a 3,000-word article. This is a fundamental flaw that inflates engagement metrics. Time-based goals also suffer from page load time distortions. If a page takes 30 seconds to load due to heavy images or slow server response, the session timer may start before the user can actually interact. This artificially increases session duration without any real engagement.

Multi-tab browsing further complicates time tracking. A user may have your site open in one tab while actively working in another. The timer continues to run, but the user is not viewing your content. Mobile users face similar issues with interruptions from notifications, calls, or app switching. Time-based goals cannot pause or reset during these interruptions. As a result, you may overestimate engagement for users who are not truly focused. To mitigate this, use scroll depth events as a proxy for active engagement. For instance, fire a custom event when a user scrolls to 50% or 75% of the page. Then create a secondary goal that requires both a minimum time threshold and a scroll event. This filters out passive sessions. Also, consider using page-level time tracking via Google Tag Manager to measure time spent on individual pages rather than the entire session. This gives you a more granular view of content consumption.

In practice, I have seen B2B software companies misallocate budget based on time-based goals. They assumed users spending over 10 minutes on their pricing page were highly engaged, but follow-up surveys revealed many were simply comparing prices across multiple tabs. The actual engagement was low. By adding a scroll depth requirement (e.g., scroll to 80% of the pricing page), they reduced false positives by 40% and improved lead scoring accuracy. Time-based goals are best used as a secondary metric, not a primary conversion indicator. Pair them with event-based triggers to validate genuine interest.

Event-Based Goals: Pre-Tracking and Integration Blind Spots

Event-based goals track specific interactions like button clicks, video plays, file downloads, or form submissions. They offer greater granularity than URL or time goals, but they come with significant limitations. First, event goals cannot capture interactions that occur before your Google Analytics tracking code loads. If a user clicks a button within the first 200 milliseconds of page load, before the analytics script initializes, that click is lost forever. This is especially problematic on pages with heavy JavaScript or slow network connections. Second, event goals cannot track interactions with third-party tools that operate independently of your analytics setup. For example, a user might engage with a live chat widget from a different provider, submit a form to an external CRM, or click a link to a third-party payment gateway. These actions are invisible to Google Analytics unless you explicitly integrate them via custom code or Google Tag Manager.

Offline interactions represent another major gap. Event goals are purely digital—they cannot track phone calls, in-store visits, or email inquiries that result from online marketing. A user might read your blog, click your phone number, and call to place an order. The call itself is not tracked unless you use a call tracking service that sends data back to Google Analytics as a virtual event. Similarly, in-store purchases influenced by online ads remain unmeasured without a closed-loop system. To address these gaps, implement a tag that fires on page load to capture early interactions. Use the “gtag.js” library’s “config” command with the “send_page_view” parameter set to false, then manually fire the pageview after the tracking code is ready. For third-party integrations, use Google Tag Manager’s custom HTML tags or API calls to push data into the dataLayer. For offline conversions, integrate a call tracking platform like CallRail or WhatConverts, which can send call data as events to Google Analytics. Also, set up a CRM integration that pushes offline conversion data (e.g., lead status, deal value) into Google Analytics via the Measurement Protocol.

From a technical standpoint, event goals also suffer from implementation fragility. A single JavaScript error can break an entire event tag without any visible alert. I have audited sites where 15% of event goals were not firing due to a misplaced semicolon in a custom HTML tag. Regular audits using Google Tag Manager’s preview mode and the GA4 DebugView are essential. Additionally, event goals cannot track the sequence of interactions within a single session unless you build complex custom dimensions. For example, you might want to know if a user watched a video before submitting a form. Standard event goals treat these as independent events, so you need to create a session-scoped custom dimension that captures the video watch event and then reference it in the form submission goal. This adds complexity but provides richer data.

E-Commerce Goals: Missing the Customer Journey Middle

E-commerce goals in Google Analytics typically measure transactions, revenue, and product purchases. However, they are blind to the entire middle of the customer journey—the research, comparison, and consideration phases. A user might browse five product pages, add items to a wishlist, read reviews, and then leave without purchasing. Standard e-commerce goals will show zero conversions, but the user was highly engaged. This is a critical data gap because it prevents you from measuring the effectiveness of content, product pages, and marketing channels in driving consideration. E-commerce goals also cannot measure individual product performance within a multi-item transaction. If a user buys a laptop and a mouse, the goal records the total revenue but not which product drove the purchase decision. You cannot attribute the sale to specific product pages or marketing campaigns.

Cart abandonment is another major blind spot. Users who add products to the cart but do not complete checkout are invisible to standard e-commerce goals. This is a high-intent segment that represents lost revenue, but without explicit cart-level tracking, you cannot analyze why they left. Enhanced E-commerce in Universal Analytics and the GA4 “view_cart” and “add_to_cart” events provide this data, but they require additional implementation. Many sites skip this step, leaving a significant gap. Furthermore, e-commerce goals cannot track offline sales that originate from online research. A user might see a product on your site, visit your physical store, and buy there. The online goal shows no conversion, but the offline sale was influenced by your digital presence. Without a closed-loop system integrating point-of-sale data with Google Analytics, you systematically underreport the impact of your online marketing.

To fill these gaps, implement Enhanced E-commerce for product-level metrics like product views, add-to-cart actions, and checkout steps. Use event goals to track wishlist additions, review reads, and comparison tool usage. For cart abandonment, set up a custom event that fires when a user adds an item to the cart but does not reach the checkout confirmation page within a session. Then, use remarketing lists based on this event to re-engage users. For offline sales, use the Measurement Protocol to send offline transaction data back to Google Analytics. You can import CSV files with transaction IDs, revenue, and product SKUs that match online user IDs. This gives you a unified view of online-to-offline conversions. I have seen retailers increase their reported conversion rate by 25% after integrating offline sales data, revealing that their online marketing was far more effective than standard e-commerce goals suggested.

Goal Funnel Visualization: Limitations in Scope and Flexibility

Goal funnel visualization is a powerful feature that shows the steps users take before completing a destination goal. However, it has strict limitations that many analysts overlook. First, funnel visualization only works with destination goals. You cannot create a funnel for time-based, pages-per-session, or event-based goals. This forces you to structure your conversion paths around URLs, even if other goal types would be more accurate. For example, if your conversion is a form submission tracked via an event, you cannot visualize the steps leading to that submission within the funnel tool. Second, funnel visualization assumes a linear, sequential path. It cannot handle non-linear behavior like skipping steps, revisiting previous steps, or entering the funnel mid-way via a direct URL. Real user journeys are rarely linear—users may jump from a product page to a blog post to a pricing page and back. Funnel visualization will either ignore these deviations or break the funnel entirely.

Another limitation is attribution scope. Funnel visualization treats each step as a mandatory checkpoint, but it does not attribute conversions to specific channels at each step. You cannot see if users from organic search behave differently than those from paid ads within the same funnel. This lack of segmentation reduces the tool’s diagnostic value. Additionally, funnel visualization has a data freshness issue. It relies on processed data, which can take up to 24 hours to appear. Real-time adjustments are impossible, making it unsuitable for rapid testing or campaign optimization. Finally, funnel visualization cannot track users who enter the funnel after the first step. If a user lands directly on step 3 via a bookmark, the funnel will not count them because step 1 was not completed. This artificially lowers conversion rates and hides valuable data about alternative entry points.

To overcome these limitations, use the “reverse goal path” report in GA4 or the “funnel exploration” tool, which is more flexible than the classic funnel visualization. You can create custom funnel steps based on any event or page, not just destination URLs. For example, you can define step 1 as a “video_play” event, step 2 as a “form_start” event, and step 3 as a “form_submit” event. This gives you a true picture of engagement-based funnels. Also, use segment overlays to compare funnel behavior across channels. For non-linear paths, consider using path analysis tools like the “User Explorer” or “Pathing” reports to see the most common sequences, even if they skip steps. For real-time insights, set up custom alerts in Google Analytics that trigger when funnel step drop-off rates exceed a threshold. This allows you to react quickly without relying on delayed funnel visualization data.

Cross-Domain Goal Tracking: Cookie and Attribution Fragmentation

Cross-domain goal tracking is essential for businesses that operate multiple domains, such as a main site and a separate checkout domain. However, Google Analytics uses first-party cookies that are domain-specific. When a user moves from domain A to domain B, the cookie from domain A is not accessible on domain B. This means the user appears as a new visitor on domain B, even if they just came from domain A. This breaks goal attribution and inflates user counts. Referrer information also gets lost. A user who clicks a link from domain A to domain B will show as “direct traffic” on domain B because the referrer header is not passed across domains. This misattributes conversions to direct traffic when they should be attributed to the marketing campaign that drove the user to domain A.

Cross-domain tracking requires explicit configuration via the “linker” parameter or Google Tag Manager’s cross-domain tracking setup. Without this, goals that span multiple domains will not fire correctly. For example, if your goal is a purchase on a checkout.domain.com, but the user started on your main domain, the goal will only be recorded if the session is properly linked. Implementation complexity is high—one misconfigured tag can break tracking for weeks before it is noticed. Additionally, event tracking across domains is problematic. An event fired on domain A may not carry over to the session on domain B, even if the user is the same. This leads to fragmented event data and incomplete user journeys.

To address these issues, implement Google Tag Manager’s cross-domain tracking by adding the “autoLink” function with the domains you want to link. Also, use the “allowLinker” parameter in your tracking code to ensure that the linker cookie is passed via URL parameters. For event continuity, set up a custom dimension that stores the user’s original domain source. This allows you to segment users who came from another domain. For referrer preservation, use the “referrerOverride” parameter to manually set the referrer when a user crosses domains. I have worked with a SaaS company that had a blog on blog.example.com and a product on app.example.com. Without cross-domain tracking, 40% of blog-to-product conversions were attributed to direct traffic. After implementing proper linking, they discovered that their blog content was driving 60% of sign-ups, leading to a major content marketing investment. Regular testing using Google Tag Manager’s preview mode and the Network tab to check for linker parameters is critical to maintain data integrity.

Mobile App Goal Tracking: Platform-Specific Constraints

Mobile app goal tracking via Firebase and Google Analytics for Firebase has unique limitations compared to web tracking. First, event tracking options are more restricted. While web tracking can capture a wide range of interactions via custom JavaScript, mobile apps require specific SDK methods for each event type. Certain actions like scroll depth, mouse hover, or right-click are not applicable in mobile apps, but even common actions like swiping through a carousel or long-pressing an item may not be tracked unless explicitly coded. This leads to blind spots in user engagement measurement. Second, app attribution is complex. Users often discover apps through app store searches, paid ads, or social media links that open the app store. The connection between the marketing click and the app install is tracked via attribution partners like AppsFlyer or Branch, but this data must be manually imported into Google Analytics. Without this integration, you cannot attribute installs to specific campaigns.

Cross-device journeys are another major gap. A user might research a product on your website, then download your app and complete a purchase. The web session and the app session are tracked separately, and Google Analytics cannot automatically link them unless you implement User ID tracking. Even then, linking requires a consistent login across platforms, which not all users do. This means you cannot measure the complete conversion path across devices. Additionally, mobile app sessions are more prone to interruptions from notifications, calls, or app switching. Time-based goals in apps suffer from the same passive engagement issues as web time goals, but with added complexity from background app behavior. An app might remain active in the background while the user does other tasks, inflating session duration.

To mitigate these, implement Firebase’s recommended events for e-commerce, engagement, and retention. Use the “user_engagement” event to measure active time, which is more accurate than raw session duration. For attribution, integrate a mobile measurement partner (MMP) like Adjust or Kochava with Google Analytics via the Firebase SDK. This gives you a unified view of install sources and in-app events. For cross-device tracking, implement User ID by requiring login and passing the same ID across web and app. Use the Google Analytics 4 “connected site tags” feature to link your web and app properties. For offline app conversions, use the Measurement Protocol to send data from your app’s backend, such as subscription purchases or in-app purchases that occur without an active internet connection. Regular testing using Firebase’s DebugView and real-time reports is essential to ensure events are firing correctly.

Attribution Model Limitations: Cookie Dependencies and Causality

Attribution models in Google Analytics determine how credit for a conversion is distributed across touchpoints. However, all models are fundamentally limited by their dependence on cookies. With increasing ad-blocker adoption, browser privacy changes (like Safari’s Intelligent Tracking Prevention and Chrome’s cookie deprecation), and users clearing cookies, the data used for attribution is incomplete. A user who blocks cookies will appear as a new visitor each time, making it impossible to attribute conversions to previous touchpoints. This leads to over-attribution to the last click and under-attribution to upper-funnel channels. Additionally, different attribution models produce wildly different results. A last-click model might give 100% credit to a branded search term, while a linear model distributes credit across 10 touchpoints. Choosing the right model is subjective and can significantly impact budget allocation.

Attribution models also cannot distinguish correlation from causation. A user might see a display ad, then later search for your brand and convert. The display ad might have influenced the search, but the last-click model gives all credit to the search. Multi-touch models improve this by distributing credit, but they still cannot prove that the display ad caused the conversion. Without controlled experiments like conversion lift studies or A/B testing, you cannot know the true incremental impact of each channel. Furthermore, offline touchpoints are completely invisible to attribution models. A user might see a billboard, visit your site, and convert. The billboard influence is unmeasured, and the conversion is attributed entirely to digital channels. This systematically overvalues digital marketing and undervalues offline efforts.

To address these, use data-driven attribution models when you have enough conversion data (typically 15,000+ clicks and 600+ conversions per month in GA4). Data-driven models use machine learning to estimate the actual contribution of each touchpoint based on patterns in your data. Supplement this with conversion lift studies using Google’s Brand Lift or a third-party tool like Facebook’s Lift Test. For offline attribution, integrate POS data with Google Analytics via the Measurement Protocol or use a CRM like Salesforce to push offline conversion data back into your analytics. Also, implement server-side tracking to reduce cookie dependency. Server-side tagging via Google Tag Manager’s server container allows you to set first-party cookies that are more resilient to browser restrictions. Regular model comparison reports in GA4 can show you how different models affect channel performance, helping you make informed decisions despite the inherent limitations.

Custom Goal Implementation: Complexity and Reliability Risks

Custom goals allow you to track business-specific conversions beyond the standard goal types, such as completing a multi-step wizard, watching a specific video segment, or filling out a form with certain fields. However, implementing custom goals requires technical expertise that many organizations lack. You must define events in Google Tag Manager, set up triggers, and configure goal parameters in Google Analytics. A single mistake—like using the wrong event category or action—can break the goal silently. Unlike standard goals, custom goals do not have built-in validation tools. You must manually test each implementation using the preview mode and real-time reports. This is time-consuming and prone to human error.

Reliability is another major concern. Custom goals depend on the stability of your tracking code. A JavaScript update, a tag manager migration, or a site redesign can break custom goals without any obvious error message. I have seen cases where a custom goal for “video completion” stopped firing after a YouTube API update, and the team did not notice for three months. During that time, they were making decisions based on incomplete data. Custom goals also suffer from data accessibility issues. Unlike standard goals, which appear in pre-built reports, custom goal data must be accessed via custom reports or segments. This adds friction and reduces the likelihood that stakeholders will use the data regularly.

To improve reliability, implement a robust testing protocol for every custom goal. Use Google Tag Manager’s preview mode to simulate events and verify that the correct dataLayer values are being pushed. Set up custom alerts in Google Analytics that notify you if a custom goal’s conversion rate drops below a certain threshold. This acts as an early warning system for tracking failures. For data accessibility, create custom dashboards in Google Data Studio or Looker Studio that display custom goal metrics alongside standard goals. This makes the data visible to all stakeholders. Also, document every custom goal implementation with clear instructions for maintenance and troubleshooting. I recommend using a version control system for your tag manager workspace to track changes and revert if needed. Finally, consider using GA4’s recommended events and parameters whenever possible, as they are more stable and better supported than custom events. Only use custom events when absolutely necessary, and always have a fallback plan, such as a secondary event that fires on a similar action.

Offline Conversions and Closed-Loop Tracking

Google Analytics goals are inherently digital. They cannot track conversions that happen offline, such as phone calls, in-store purchases, or email inquiries. This is a critical blind spot for businesses with omnichannel operations. A user might see a Google ad, visit your website, call your phone number, and place an order over the phone. The goal for the phone call is never recorded in Google Analytics unless you use a call tracking service that sends data back as a virtual event. Similarly, a user might visit your store after seeing a Facebook ad, but the in-store purchase is invisible to your analytics. This leads to a systematic underreporting of conversion volume and ROI. Without closed-loop tracking, you cannot connect online marketing efforts to offline results.

Closed-loop tracking requires integrating your CRM, call tracking platform, and point-of-sale system with Google Analytics. This is technically challenging and requires ongoing maintenance. For example, you need to match phone call timestamps with website sessions, or match in-store purchases with user IDs from online accounts. This often involves manual data reconciliation or custom API integrations. Many organizations give up on closed-loop tracking because of the complexity, leaving a significant data gap. Even with integration, there are latency issues. Offline conversions may take days or weeks to appear in Google Analytics, making real-time optimization difficult. Additionally, privacy regulations like GDPR and CCPA restrict how you can match offline data with online identifiers, adding compliance complexity.

To implement closed-loop tracking, start with call tracking. Use a service like CallRail or WhatConverts that can assign a unique phone number to each marketing campaign. When a user calls that number, the service sends an event to Google Analytics with the call duration, source, and outcome. For in-store purchases, use a loyalty program or email capture at checkout to link the transaction to an online user ID. Then, use the Measurement Protocol to send the transaction data back to Google Analytics with the same user ID. For CRM data, use Google Analytics 4’s offline conversion import feature, which allows you to upload CSV files with conversion data. You can map columns like “user_id,” “conversion_value,” and “conversion_time” to your GA4 property. This gives you a unified view of online and offline conversions. I have seen a retail chain increase their reported conversion rate by 35% after integrating in-store purchases, revealing that their digital ads were driving far more offline sales than they realized. Regular data reconciliation is essential to ensure accuracy—compare your offline data with your CRM records monthly to catch discrepancies.