Bots and scrapers
Bursts or behavior patterns that do not resemble a plausible buying journey. They are candidates for investigation, not proof of automation.
Qualified Traffic Audit for GA4
Audit the GA4 traffic you don’t want to optimize around.
Review the last 90 complete days of one GA4 property for traffic that may not represent prospective buyers: bots or scrapers, internal visits, existing customers, and low-intent sessions.
You get the evidence, the estimated impact, and the unanswered questions—not a confident label based on one odd metric.
- 90 complete days
- One selected GA4 property
- Evidence before exclusions
The problem with “traffic”
A clean trend line can still be telling the wrong story.
Sessions are not interchangeable.
A customer returning to sign in is not a new prospect. An employee checking a page is not demand. A burst of automated visits is not campaign momentum. And an informational visit can be useful without belonging in the same conversion denominator as someone evaluating the offer.
Leave those visits mixed together and the numbers still add up. The decisions built on them get worse.
Four common sources of noise
Find the traffic that needs a different interpretation.
GA4 does not hand you a trustworthy “qualified traffic” switch. The definition depends on the question, so the audit builds a case from the evidence available in your property.
Internal traffic
Visits from employees, agencies, QA work, or monitoring. Useful for running the site; misleading when it appears in acquisition reporting.
Existing customers
Sign-in, account, and support behavior can make an acquisition channel look healthier—or weaker—than it really is.
Low-intent visits
Information-seeking sessions can be valuable. They may simply need a different denominator from visits with a realistic path to signup or purchase.
Example output
A useful finding shows its work.
Illustrative example only. The figures are fictional and show the structure of an audit, not a customer result.
Illustrative audit excerpt
InvestigatePaid social volume is up. Buyer behavior isn’t.
Traffic affected18% of paid-social sessions
ConfidenceMedium
DecisionVerify before filtering
Evidence
Campaign sessions rose 62%. Its key-event rate is 0.2%, versus 2.6% for the property overall. Most of the increase lands on one informational page and records no downstream key event.
What remains uncertain
Weak targeting, a landing-page mismatch, invalid clicks, or missing event collection could all produce this pattern. GA4 alone cannot distinguish those explanations.
Next check
Confirm key-event collection on the landing page, then split the campaign by placement and geography.
Current recommendation
Do not exclude it yet.
No false certainty
No magic quality score. No silent filters.
- Odd is not automatically bad.A strange segment may expose broken tracking, campaign mismatch, or a legitimate audience you did not expect.
- Uncertain stays uncertain.The audit separates what the data supports from what still needs checking.
- You make the exclusion.EverOpt recommends the next check; it does not quietly rewrite your GA4 property.
One property, one audit
Start with the denominator before debating the conversion rate.
- 01
Choose the property
Connect Google Analytics and select the GA4 property you want to review. The investigation stays tied to that property.
- 02
Run the built-in audit
EverOpt reviews the last 90 complete days using the dimensions, events, and key-event behavior the property makes available.
- 03
Question the findings
Follow up in the same conversation: split a channel, inspect a landing page, or test another explanation while the evidence is in view.
- 04
Decide what changes
Save a supported finding as an opportunity, schedule the analysis if it needs watching, or leave the segment alone when the case is weak.
What you leave with
Enough detail to defend the decision.
- The segments most likely to distort the question you are asking
- The GA4 evidence behind each finding
- An estimate of how much each segment affects the reported result
- A plain statement of what the data cannot establish
- Recommended filters or follow-up checks before an exclusion
When the evidence supports a real CRO opportunity, save the finding, hypothesis, target metric, recommendation, and source evidence together. EverOpt can propose the opportunity. You decide what happens to it.
Before you connect GA4
Sensible questions about traffic quality.
What does qualified traffic mean in GA4?
There is no universal qualified-traffic metric. It means traffic that reasonably belongs in the business question you are answering. An existing customer may be qualified for retention analysis and inappropriate for a new-customer acquisition report. The audit makes that distinction explicit.
Can GA4 identify bots, internal users, or existing customers with certainty?
Usually not from one signal. EverOpt reviews the available patterns, quantifies their impact, states what remains uncertain, and recommends a check before you treat a segment as excluded traffic.
Does EverOpt automatically exclude traffic or change my GA4 property?
No. The audit returns findings and recommended checks. It will not silently add a filter or make the exclusion decision for you.
Why does the audit use 90 complete days?
The audit needs enough history to make repeated and intermittent patterns easier to examine, without letting the current partial day skew the result. Its fixed review window is the last 90 complete days.
Is this another GA4 dashboard?
No. A dashboard monitors metrics you have already chosen. This is an investigation: question a finding, request another segment, and keep going until the evidence is useful.
Bring one property
Start with the denominator.
Choose a GA4 property and run the 90-day audit. See what may not belong in your acquisition numbers—and what still needs checking before you change anything.
Start a Qualified Traffic AuditFree plan available.