Traffic Quality Red Flags: A Checklist for Reviewing a Source

Compare clicks with page loads

• Check whether reported clicks produce matching page loads. A click without a corresponding load may point to tracking gaps, accidental taps, or traffic that does not reach the destination.

• Review the path from click to landing page. Unexpected redirects, broken pages, or long delays can make traffic appear active while preventing visitors from seeing the content.

• Compare source reports with your own analytics. Differences in counting methods can be normal, but unexplained gaps make it harder to assess what the placement is delivering.

Look for natural variation in behaviour

• Watch for behaviour that seems unusually uniform. Visitors who arrive, act, and leave in nearly identical ways may not reflect a varied audience.

• Check whether visits show signs of meaningful engagement. Near-zero time on page across a placement can suggest that clicks are accidental, automated, or poorly matched to the offer.

• Review interaction patterns across landing pages. A source that produces the same shallow activity on every page may be sending low-intent traffic rather than interested visitors.

Investigate sudden changes and placement patterns

• Ask what caused a sudden jump from one placement. A sharp change may reflect a new position, audience, or delivery method that deserves separate review.

• Inspect results by placement rather than only in aggregate. Strong overall figures can conceal a weak location or format that is consuming budget without useful engagement.

• Check whether delivery stays consistent with the agreed setup. Unexplained shifts in format, audience, or placement can make earlier comparisons unreliable.

Verify audience claims

• Compare the claimed geography with the locations in your reports. A persistent mismatch may indicate targeting problems, imprecise location data, or traffic that does not fit the intended audience.

• Check whether device patterns match the source’s description. A marked difference between claimed and observed devices can affect page performance and the meaning of engagement data.

• Review whether the audience fits the content and targeting. Traffic can be technically valid yet still be poorly matched to the page, making clicks less useful.

Validate outcomes beyond the initial action

• Confirm that conversions hold up downstream. A form submission or other tracked action is not necessarily valuable if it fails later checks or does not progress through the intended process.

• Compare conversion events with the records used for final validation. Disagreement may reveal duplicate, incomplete, or otherwise unqualified actions.

• Treat unusually strong early conversion signals with care. If later validation does not support them, the initial tracking event may not represent a genuine outcome.

Ask clear questions about supply and controls

• Ask the source to explain where its traffic comes from. Vague descriptions make it difficult to understand the audience, the placement, and how delivery is being managed.

• Request a clear account of how placements are reviewed and moderated. Without a practical explanation, it is harder to judge whether unsuitable or misleading inventory is being filtered.

• Clarify how targeting and pacing are controlled. If the source cannot describe how delivery follows the agreed settings, monitoring and budget management become less dependable.

• Record what is known and keep reviewing performance. Traffic quality can vary by placement and over time, so ongoing checks are more informative than a single summary report.