Skip to content
PodSubs
ShowsPeopleGuestsJobsNewsEvents
More
BlogPodCred
Menu
ShowsPeopleGuestsJobsNewsEventsBlogPodCredNetworksSign in
Join nowSign in
  • Shows
  • People
  • Jobs
  • News
  • More
    • Guests
    • Events
    • Blog
    • PodCred
    • Networks
    Join nowSign in

Go High Level

Go High Level artwork

Track Browsers and IPs in GoHighLevel — Boost Funnel Analytics

Apr 25, 202619 minAudio
ShareXLinkedInFacebookWhatsAppEmail

🚀 Start your FREE 30-day GoHighLevel trial: https://globalhighlevel.com/trial Learn how to leverage browser and IP tracking in GoHighLevel's Funnel Analytics Dashboard. This episode covers the latest analytics features that help digital marketing agencies understand visitor behavior and enhance security monitoring across their funnels and websites. In this episode you'll learn: • How to view the top 10 browsers accessing your funnels and websites • How to identify and track the top 10 client IP addresses for security insights • Why browser and IP analytics matter for optimizing funnel performance • Best practices for using this data to improve your funnel strategy Ready to try GoHighLevel yourself? The link above gets you a FREE 30-day trial - double the standard 14-day trial. See why thousands of agencies run their entire business on one platform.

Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.

Transcript

From the show.

You know, launching a digital marketing campaign, um it often feels like throwing this massive party in a pitch black room. Oh, yeah. That's a great way to put it. Like you can hear the music playing, you can hear people talking, and you know they're uh drinking the punch, but you have absolutely no idea who is actually there. Right. You just see the cups disappearing from the table. Exactly. And in the agency world, that's kind of what relying entirely on raw anonymous traffic numbers feels like. It's it's basically the illusion of insight. Yeah, I mean, you're seeing the outcome of the activity, but you're completely blind to the mechanics of that activity. Right. And in marketing, if you can't see the mechanics, you, well, you cannot optimize the system. We all gravitate toward high traffic numbers because they're comforting, you know? Yeah. Oh, absolutely. It feels like you're winning. It does. But relying on those top of funnel vanity metrics without understanding the underlying user behavior is uh it's downright dangerous for an agency's retention rate. It really is. Well, welcome to this deep dive, everyone. And before we start turning the lights on at this party and really digging into the data, I do want to mention that we have a custom link waiting for you in the show notes below for a free 30-day GoHighLevel trial. Which is huge, by the way. Yeah. It's actually double the standard trial length so you can actually log in and test these analytics alongside us today. Honestly, it is the ideal time to get hands-on because the visibility we have into traffic right now has um fundamentally shifted recently. For sure. So, our mission today is to decode GoHighLevel's funnel analytics. And we're pulling directly from the official HighLevel Support Portal documentation, uh a really comprehensive expert analytics guide from Consultivo, and some practical insights from a recent GoHighLevel tutorial. Some really solid sources there. Yeah, they break it down perfectly. We're looking at the underlying architectures today, so how browsers, IPs, sessions, and contacts all interact. Right. The objective here is to give you, especially if you're running an agency, the operational blueprint for understanding your traffic, optimizing your client's funnels, improving undeniable ROI to your clients. Because, I mean, that's the baseline expectation now, right? Oh, 100%. The era of handing a client a monthly report that just says, you know, look, we drove 10,000 clicks and then expecting them to renew their retainer, that's over. Yeah, clients demand to know what those clicks actually mean. Like, how do they translate to pipeline revenue? Exactly. So, let's look at the literal new tools that were just handed to us on the dashboard. We should probably start right at the surface, what you actually see when you log in before we start, you know, pulling the tracking engine apart. Okay, let's do it. So, you navigate into your GoHighLevel account, you go to the sites section, click on the analytics tab, and then look under page views. And there's this significant update to the funnels and websites analytics dashboard. You now have direct visibility into two incredibly potent data sets, which are your top 10 browsers and your top 10 client IP addresses. And, you know, on the surface, browsers and IPs seem like kind of basic webmaster data. Yeah, like old school IT stuff. Exactly. But when you apply this to an agency's day-to-day operations, it dictates your entire strategy. Let's look at the browser breakdown first. Okay. You're seeing the percentage split of Chrome, Firefox, Safari, Edge. And what's fascinating here is how often this specific metric is just ignored until a campaign completely breaks. Yeah. How it would break a campaign. Well, let's say you launch a high-ticket coaching funnel. You look at the top browser's breakdown and you realize that, say, 75% of your traffic is coming from Safari. Oh, gotcha. Which tells me my client is targeting a demographic that skews heavily toward mobile Apple devices, primarily iPhones. Right. And operationally, that means your agency needs to fundamentally adjust its testing protocol. Because Safari operates with uh ITP, which is intelligent tracking prevention. Oh, Apple's privacy stuff. Yeah, exactly. It has notoriously strict security protocols and it aggressively purges third-party cookies. Right, right. So, if your funnel relies heavily on complex cross-domain tracking or if it's, you know, optimized entirely for a desktop Chrome experience and your traffic is mostly mobile Safari, your conversion rate is going to absolutely tank. Wow, which means if you're not factoring that browser data in from the start, your entire reporting structure is essentially built on sand. Pretty much. You might sit there blaming the ad copy or the creative or the offer, when the real bottleneck is simply browser compatibility on a 5-inch screen. You're adapting the environment to the user. Now, if the browser data tells you the environment the user prefers, the client IP tracking reveals the nature of the network they're using. Okay, let's talk about the IPs then. So, the dashboard now isolates the top 10 IP addresses accessing your site. I always like to think of this like running a brick and mortar store. Oh. How so? Well, the browser data is like knowing what kind of cars your customers drive, so you can build the right size parking lot. But the IP data is more like, uh, a caller ID, or like a bouncer at the door recognizing a repeat visitor. That is a perfect analogy because if I'm looking at this from an agency perspective, monitoring IPs isn't really about identifying individuals. Right, because an IP is just a network address. It could be a whole corporate office or just the local Starbucks. Exactly. It's about monitoring velocity. If I see one single IP address making, I don't know, 4,000 requests to a client's opt-in page in a two-hour window. Yeah. That is definitely not an eager customer. No. That is a bot, or a scraper, or some brute force script. And if that traffic goes unchecked, it just artificially inflates your visitor numbers. Inflates the numbers, drives your conversion rate into the ground, and burns through your server resources. It completely skews your reporting. Geez. So, if you don't have visibility into that chaotic activity, you might make terrible marketing decisions like pausing a totally profitable ad set just based on fake data. Exactly, which is why having that caller ID, as you called it, is so crucial. Which brings up a practical question for me. If I do see an IP spamming the site like that, my instinct as an agency owner is to jump into my domain registrar or, you know, Cloudflare and just block it at the network level. Right. Is that the protocol here or does GoHighLevel handle it natively? So, the official documentation advises taking direct action. While GoHighLevel does have internal protections, agency should absolutely consider blocking malicious IPs at the domain level or um implementing dedicated bot protection. Okay, so taking it into your own hand. Yeah. You use the visibility GoHighLevel gives you to inform those external security measures. It really elevates your agency from just buying ads to actively securing the client's digital real estate. I love that. So, having the top IPs and browsers on the dashboard is great for, you know, keeping the lights on and keeping the traffic flowing. But I feel like we need to get to the core of the issue here. How does GoHighLevel actually combine a browser fingerprint and an IP address to determine that a unique human being just visited the funnel? Okay. This is where we bring in the technical breakdown from the Consultivo guide. What's here? They outline what's essentially a three-part tracking engine. It's sessions, IPs, and contacts. Okay, so a trifecta. Right. So, whenever a new visit occurs in a browser, GoHighLevel initiates a session. This session connects the page views and the actions taken during that continuous period of browsing. Makes sense so far. But here's the critical vulnerability of session-based tracking. It is entirely tied to the browser on that specific device. Uh oh. So if a browser session resets the moment I switch from my phone to my laptop. Mhm. How does the system not constantly double count me? Well, like if I click a Facebook ad on my iPhone Safari browser, look at the landing page, put my phone away, and then later manually type the URL into Chrome on a desktop. Right. Initially, the analytics engine has absolutely no way of knowing those two events are the same human. Right. Exactly. Initially, you will be counted as two separate visitors, starting two separate sessions. Okay, but there has to be a secondary net caching that. Because otherwise every agency's traffic reports would be massively inflated by people just cross-device hopping. And there is. Which brings us to the second pillar of the engine. The IP address deduplication mechanism. Ah. Well. GoHighLevel uses the IP address alongside the browser data to filter out the noise. It looks for behavioral clusters. Wait, let me try another metaphor to see if I'm tracking this. Go for it. It sounds a bit like a bank's fraud detection system. Like a bank doesn't just look at the physical credit card being swiped, which in this case would be the browser. Right. It looks at the location of the terminal, the IP address, and the velocity of the transactions. If it sees the same card swiped at the same terminal 40 times in one minute, the algorithm flags it and says, "This isn't 40 different purchases, this is one anomalous event." That is a highly accurate way to visualize it, honestly. If the engine sees the same IP address and the same browser hitting a page repeatedly in a highly condensed time frame, it consolidates that activity. Oh, wow. Yeah. It basically says, "This isn't 40 unique visitors, this is one unique visitor generating 40 page views." Okay. But let me push back on this a little bit. Sure. Because I know exactly how agencies operate when testing client builds. We build a funnel, push it live, and then sit there reloading the page over and over to test the animations, the load speed, the mobile responsiveness, all that stuff. Oh, yeah. Constant refreshing. Right. Now, if I'm trying to simulate a brand new visitor to test how a form maps to the CRM, the standard advice is always to use an incognito window. Correct. But wait. An incognito window still carries the exact same IP address as my main browser. My router hasn't changed. Right. So if GoHighLevel groups by IP, doesn't my incognito test still get lumped in with my regular admin session and ruin the count? Okay, that is a fantastic technical distinction. This is where the weighting of the engine really matters. GoHighLevel requires both elements, the IP and the browser state, to consolidate a session. Oh, I see. When you open an incognito window, you are stripping away all previous session data, local storage, and cookies. You're basically presenting a completely blank browser state to the server. Ah. So the system prioritizes the clean slate over the familiar IP. Yes. Even though the IP is identical, the total absence of recognized browser data forces GoHighLevel to initiate a brand new session. Okay, that makes sense. However, there's a catch. If you are testing multiple unique user journeys, say, submitting five different test leads to check an email automation, you must close the incognito window completely and open a new one between every single test. Oh. Because if you just stay in that same incognito window and keep submitting forms, you're building a single bizarre Frankenstein session. Exactly. The IT logic and the new temporary browser state will just consolidate all those actions into one chaotic user profile, which totally ruins your test data. That is such a critical operational takeaway. Because I mean, we see support tickets all the time. Right. Where someone claims the tracking is broken because they submitted a form three times and it only shows one visitor. Right. And it is working flawlessly. Yeah. The agency just didn't clear their testing environment. Exactly. But to zoom out for a second, both browsers and IPs are ultimately just tracking anonymous behavior. They are proxies for humans. The entire architecture really exists to facilitate the third pillar. Which is the contact. The contact. The contact record is the keystone of the entire analytics architecture. The Holy Grail. Truly. A contact is generated the moment that anonymous entity finally raises their hand. They submit a form, they book a calendar appointment, or they process a payment. Right. They do something concrete. Yes. The moment they surrender first-party data, like an email or a phone number, the system fundamentally shifts. It bridges the gap between anonymous traffic and known identity. It retroactively maps the data. Once that identification occurs, all the previously anonymous session data from that specific browser and IP, every page they visited, how long they stayed, gets instantly tethered to that newly minted contact record in the CRM. Oh, that's beautiful. So, instead of just knowing that someone clicked the pricing page, you now know that John Doe clicked the pricing page three times before finally opting in. Exactly. And moving forward, any future visits from that browser are no longer anonymous. The system recognizes the returning fingerprint. Which I think leads us to the elephant in the room. The reporting discrepancy. Yeah. The classic client reporting meeting. Yeah. You hand the client a GoHighLevel dashboard showing say 1,000 unique visitors. The client pulls up their Google Analytics dashboard and it says 1,200 visitors. Always happens. The numbers do not match. Uh-huh. And as an agency owner, my hypothesis here is that Google Analytics is fundamentally built as an aggregate traffic tool optimized for ad attribution. Whereas GoHighLevel is fundamentally a CRM designed for individual contact resolution. Yep. Like their core engineering philosophies are just different. Your hypothesis is spot on. It is fundamentally impossible for those two platforms to perfectly align because their baseline logic for defining reality is different. How so? Like, specifically? Well, for example, Google might have a session timeout of 30 minutes of inactivity. Another platform might use 45 minutes. Oh, sure. Google employs a massive proprietary blacklist for known bot IPs. GoHighLevel evaluates IP velocity differently, and different platforms handle cookie-blocking browsers like Safari in completely different ways. So, what is the play for an agency? Because you can't just shrug and tell the client that the internet is a messy place. You have to control the narrative. The play, as emphasized heavily in the Consultivo guide, is to establish GoHighLevel, your CRM, as the undisputed single source of truth. Okay, I like that. You pivot the conversation away from top of funnel discrepancies. You explain to the client, look, we monitor raw traffic in Google to ensure the ad platforms are delivering volume. But the metrics that actually dictate your business survival, leads created, conversion rates between funnel steps, and pipeline revenue, those live exclusively in the CRM. Wow. It forces a pivot from top of funnel noise directly to business reality. Exactly. Because if GoHighLevel shows that your unique visitors are incredibly high, so the ad targeting is working and the IP filter's letting real people through. But your contact creation is miserably low, you don't need to argue about Google Analytics. No. You have an actionable mandate to fix the funnel. The page copy isn't landing, the offer is fundamentally weak, or maybe the form is just too complex. You stop obsessing over fractional discrepancies in IP counting and start doing actual marketing optimization. The data tells you exactly where the bottleneck is. Okay. So, we've covered securing the funnels and setting the reporting expectations. But before we wrap, the documentation also highlighted a few upcoming enhancements to this analytics dashboard. Yes, some really exciting stuff. The two that immediately caught my eye were geolocation heat maps and device analytics. Geolocation heat maps are going to be massive. It'll allow agencies to visualize the geographic distribution of visitors natively without needing a third-party tool. So, how do we actually use that? Well, imagine you're running a nationwide campaign, but the heat map shows a massive cluster of high-converting traffic isolated in the Pacific Northwest. Okay. You can instantly pivot your ad spend or adjust the funnel copy to resonate with that specific region. Oh, that makes total sense. Yeah. But the device analytics, specifically the mobile versus desktop ratio, that feels even more urgent to me. Oh, absolutely. Because if Google indexes the mobile version of a site first, and this new dashboard confirms that 85% of a client's traffic is on mobile, that isn't just a fun statistic. It dictates the entire UX budget. It means you stop designing beautiful, sweeping desktop landscapes that take five seconds to load. Every single dollar of your design and development budget needs to go toward making the mobile checkout completely frictionless. Because if your mobile ratio is high, but your mobile load speed is terrible, you are bleeding money before the user even sees the offer. Yeah, you're dead in the water. So, if we step back and look at everything we've unpacked today, tracking browsers to prevent compatibility issues, monitoring IPs to block malicious velocity, and understanding the precise mechanism of how sessions consolidate into CRM records. Yeah. None of this is just dry back office tech jargon. No, it is the foundational toolkit for proving your agency's value. You are stripping away the illusion of insight and replacing it with verifiable mechanics. And if we look at the macro trends of where digital marketing is heading. I really want you, the listener, to mull over the implications of this tracking engine. It means a big deal. We are actively witnessing the death of the third-party cookie. Apple's ITP, Google's shifting privacy sandbox, the ability to casually follow an anonymous user across the internet is just evaporating. It's going away. So, in an environment where third-party data is vanishing, the most valuable asset a company can possess is first-party data. Exactly. The data you collect directly from your users, on your own platforms, under your own terms. As GoHighLevel continues to refine its ability to unify that anonymous IP and browser data into concrete owned contact records, it really stops being just a funnel builder. Right. It becomes an engine for building an impenetrable fortress of first-party data. The true power of the funnel isn't the conversion rate of the page, it's the CRM database it feeds. Well said. So, the question is, how will you leverage that asset when your competitors are suddenly flying blind? That is going to be the defining question for the next decade of digital marketing. I couldn't agree more. And the absolute best way to start building that fortress and to get your hands on the exact IP and browser analytics we've been breaking down today is to dive into the platform yourself. Yep, get in there and see it. So, I want to remind you one last time about that special offer. You can get a free 30-day GoHighLevel trial. We are talking double the standard trial length, giving you a full month to pressure test the deduplication logic. Yeah. Map sessions to contacts and see the data for yourself. It's a no-brainer. The link is right there in the show notes below. Go click it, start optimizing those funnels and finally turn the lights on at the party. We will catch you on the next deep dive.

Open the transcript file

Hosts and Guests

Nobody is credited on this episode yet.

Credit the people on this episode

Be the first to rate this episode

More episodes

All episodes
  1. Stop Chasing Leads: Auto Follow-Up in Conversation AI

    Oct 6, 202626 minAudio

    Your AI bot can now automatically follow up with inactive contacts - no manual work required. Learn how HighLevel's Conversation AI detects drop-offs, schedules smart reminders, and closes deals on autopilot. Watch this...

    Credit the people on this episode

  2. Knowledge Base Triggers: Control Your Conversation AI Responses

    Oct 6, 202617 minAudio

    Stop letting AI guess when to show offers and pricing. Learn how GoHighLevel's Knowledge Base Triggers deliver the right content at the exact moment your prospects need it - driving more conversions and eliminating...

    Credit the people on this episode

  3. Conversation AI on Mobile: Reply to Customers Instantly (No Desktop Needed)

    Oct 6, 202617 minAudio

    Manage customer conversations from your phone with Conversation AI in the HighLevel mobile app. Learn how to use Autopilot Mode, Suggestive Mode, and control your AI assistant on-the-go across WhatsApp, Facebook,...

    Credit the people on this episode

  4. Voice AI Agent Transfer: Route Calls Without Dropping Them

    Oct 6, 202623 minAudio

    Learn how GoHighLevel's Voice AI Agent Transfer hands off live calls between specialized agents seamlessly - no dial transfers, no restarts. Discover how to route callers to sales, support, billing, or language-specific...

    Credit the people on this episode

  5. Sell Your AI Agents: GoHighLevel Marketplace Launch Guide

    Oct 6, 202620 minAudio

    Turn your Conversation AI and Voice AI templates into revenue streams. Learn how to package, list, and sell your agents on the GoHighLevel Marketplace - complete with workflows, automations, and knowledge bases...

    Credit the people on this episode