How much does a GA4 setup cost?
We quote GA4 setup as a fixed-fee project after a short discovery call, and the price depends on how many sites and domains you have, whether you sell online, and which systems GA4 needs to connect to.
A single lead-generation site with a few forms is a small project. An ecommerce store with a custom checkout, several subdomains, consent mode, BigQuery export and a CRM link is a much bigger one. Most of the cost isn't clicking settings in GA4. It is planning the events, building a clean data layer in Tag Manager, and testing every event across browsers before it goes live.
Be wary of very cheap setups that skip the plan and the testing. They usually produce a property that collects page views and little else, and you pay again to redo it. When you compare quotes, ask for the deliverables in writing: a measurement plan, the list of events and key events, a QA log, and documentation. Not sure what you have now? Start with a tracking audit.
Should we fix our current GA4 property or start over?
Fix it in almost every case, because a new property starts with no history and the old reports don't come with you.
Most broken properties are broken in the tags and settings, not the property itself. Duplicate events, missing transaction IDs, short data retention and payment gateways showing up as referrals can all be fixed in place. The history you keep stays useful for trends, even if some of it was messy. We record the date of each fix so reports can be read correctly on either side of it.
Starting over makes sense in a few cases: the property is owned by a former agency or employee and access can't be recovered, it mixes several unrelated sites, or it sits in the wrong account structure entirely. Even then, we run the old and new properties side by side for a few weeks before switching reports over. The answer is usually obvious in the first week of an audit. Our measurement practice covers the wider stack.
Can GA4 track traffic from ChatGPT and other AI assistants?
Yes. GA4's default channel group now includes an AI Assistant channel for visits from sources like ChatGPT, Gemini, Copilot and Grok, while clicks from Google's AI Overviews and AI Mode are counted as Organic Search.
That split matters. To see whether AI answers send you visitors, look in two places: the AI Assistant channel for chat tools, and Organic Search for Google's own AI features, which GA4 doesn't separate out. Some AI visits can also land as Direct when the app doesn't pass a referrer. If you want your own list, Google documents building an AI assistants channel with a regex rule in a custom channel group, placed above Referral so it catches those sessions first.
Volumes are usually small today, but these visitors tend to arrive with a specific question already answered. Make sure your key events are set up properly, then compare their conversion rate with organic search. If AI visibility is a goal, the real work happens on the content side, covered in AI search optimization.
Sources: Google Analytics Help: Default channel group, Google Analytics Help: Custom channel groups
Why do I see Unassigned traffic in GA4?
Unassigned means GA4 received traffic it couldn't match to any of its channel rules, and it is almost always a tagging problem you can fix.
The usual causes are UTM values GA4 doesn't recognize, like utm_medium=newsletter instead of email, campaign links built by hand with typos, redirects that strip parameters, and events sent through the Measurement Protocol or a server-side setup without session information. Google's own guidance on unassigned and (not set) traffic points to the same list: tag configuration that breaks session or user identity.
To find the source, open the Traffic acquisition report, filter to Unassigned, and add Session source / medium as a secondary dimension. The offender usually shows up in a minute. Then fix it where it starts: one shared UTM naming sheet, lowercase values, and the standard mediums GA4 expects. You can't edit GA4's default channel rules, but you can build a custom channel group if your naming needs it. Clean UTMs also make cost data imports line up.
Sources: Google Analytics Help: Tagging best practices to avoid unassigned, (not set), and direct traffic issues, Google Analytics Help: Default channel group
What is data thresholding in GA4, and how do I avoid it?
Thresholding is when GA4 hides rows in a report so nobody can infer who an individual user is, and it mostly appears on low-traffic reports when Google signals or demographic data is involved.
You'll see a notice in the report's data quality icon saying thresholding has been applied. Google says the thresholds themselves can't be adjusted, but you can make them less likely. Widen the date range so more users fall into each row. Switch the reporting identity to Device-based. Or turn off the setting that includes Google signals in reporting identity, which keeps signals available for audiences and Google Ads while dropping them from reports.
For small sites, the reporting identity change often makes reports usable right away, and Google notes it doesn't affect data collection or processing, so you can switch back anytime. For anything you need at full detail, use the BigQuery export, which Google lists as a way around thresholds. Signals data isn't exported to BigQuery, so expect small differences in counts.
Sources: Google Analytics Help: About data thresholds, Google Analytics Help: Reporting identity
Is GA4 HIPAA compliant?
No. Google says it makes no representation that Google Analytics meets HIPAA requirements and doesn't offer Business Associate Agreements for it, so HIPAA-regulated organizations must keep protected health information out of GA4 entirely.
In practice that means GA4 tags stay off logged-in patient portals, and off public pages tied to providing care, which Google says are more likely to be HIPAA-covered. URLs, page titles, form fields and custom dimensions can all leak sensitive details if you aren't careful, like a URL that carries a condition name and an email address.
For clinics, therapy practices and healthcare-adjacent nonprofits, we map which pages are marketing pages and which are care pages with your legal or compliance lead before tagging anything. Some organizations use a HIPAA-focused analytics tool for the sensitive parts and keep GA4 on public marketing pages only. This is a legal call as much as a technical one, so get counsel's sign-off. It comes up often in our work with ABA therapy providers.
Sources: Google Analytics Help: HIPAA and Google Analytics, Google Analytics Help: Best practices to avoid sending personally identifiable information
Can AI analyze our GA4 data for us?
Yes. Google offers an official Google Analytics MCP server that lets an AI assistant read your GA4 reports, and we connect GA4 to Buddy, our AI agent, so it flags anomalies instead of someone digging through exports.
Google's MCP server is read-only. It can run standard and real-time reports, but it can't change your settings. That is the right design: the AI asks questions of the data, and a person decides what to fix. The useful questions are specific, like which landing pages took paid traffic with no key events, where conversions dropped overnight, or which source sent sessions but no leads.
The catch is that AI can only explain what GA4 actually recorded. If the Google Ads conversion tag is missing or a purchase event fires twice, the AI will confidently explain a gap that is really broken tracking. So the order is: fix the tags first, then connect the AI. More on how we put agents to work in AI implementation.
Sources: Google for Developers: Try the Google Analytics MCP server, googleanalytics/google-analytics-mcp on GitHub
