Dwell time is a useful diagnostic signal for solo ad traffic, but it is not a standalone proof of quality. Always tag and isolate vendor traffic before you draw any conclusion, and treat opt-ins and downstream sales as the metrics that actually decide whether a vendor is worth repeat business. Tag each vendor and each order with distinct UTMs, then compare engaged session rate, opt-in rate, and revenue side by side.
TL;DR:
- Tagged UTMs are essential to attribute engagement metrics accurately to specific vendors and avoid mixing traffic sources.
- An engaged session lasts at least ten seconds or includes a key event or multiple pageviews, serving as a baseline for engagement quality.
- High engagement rates with low opt-in rates often indicate a mismatch between the traffic and the page or offer, not necessarily poor vendor traffic.
- Always verify click delivery and uniqueness before analyzing engagement data, and confirm proper attribution in GA4 to avoid skewed metrics.
- A comprehensive vendor vetting process includes requesting recent click logs, refund policies, and list origin details to avoid relying solely on engagement signals.
Table of Contents
- What dwell time and engagement metrics actually mean
- How to measure dwell time correctly for solo ad tests
- Benchmarks and expectations for engaged session rate
- Step-by-step solo ad testing sequence
- Vendor vetting: verification before the buy
- Interpreting results: optimize, scale, or stop
- Tools and resources to put this into practice
- Author perspective: why verification beats vendor promises
- How SoloAdsGuide.com helps you buy with more certainty
- Sources
- FAQ
What dwell time and engagement metrics actually mean
Dwell time is the amount of active time a visitor spends on your page before leaving or converting. It sounds simple, but the term does not map cleanly onto anything Google Analytics 4 actually reports, which causes a lot of confusion for solo ad buyers checking their numbers.
GA4 does not have a "dwell time" metric. Instead, it tracks average engagement time and engaged sessions. An engaged session counts when a visit lasts 10 seconds or longer, includes a key event, or includes two or more pageviews. Engagement rate is simply engaged sessions divided by total sessions. This is a meaningfully different measurement than the old bounce rate metric, which only tracked whether a session had any interaction at all and ignored how long someone actually stayed.
The distinction matters because a page can have a low bounce rate and still deliver a lot of empty, disengaged visits. Reading engagement time instead of bounce rate gives you a truer picture of whether the traffic a vendor sent you actually looked at anything.
Several ordinary factors push dwell time up or down on a solo ad landing page:
- Page load speed: slow squeeze pages lose visitors before they engage at all.
- Headline and copy match: traffic that lands on a page mismatched to the email's promise leaves fast.
- Device and formatting: mobile-unfriendly pages shorten sessions regardless of traffic quality.
- List freshness: older or over-mailed lists tend to click out of habit rather than interest.
None of these factors are about the vendor's honesty. That is exactly why dwell time alone cannot tell you if a vendor is good or bad. It tells you something is worth investigating.
How to measure dwell time correctly for solo ad tests
Trustworthy engagement data starts before the traffic ever arrives. If your tagging is sloppy, every number downstream is unreliable, no matter how good your vendor's traffic actually is.
- Assign a unique UTM per vendor and per order. Use a naming convention such as campaign equals vendor name plus order number, so every batch of traffic is separately identifiable in your reports.
- Keep the naming convention consistent across every buy. A practical UTM naming standard prevents the kind of inconsistent tagging that quietly merges two vendors' traffic into one unreadable bucket.
- Verify delivered versus unique clicks in your click tracker first. Before you even open GA4, confirm the vendor sent the number of clicks promised and that duplicate or repeat clicks are filtered out; a full click tracking walkthrough covers the setup.
- Pull reports by session source, medium, and campaign, not by a sitewide average. Analytics requires explicit UTM parameters to attribute sessions correctly, and skipping this step is the single most common reason solo ad buyers misjudge a vendor.
- Read engagement_time_msec and user_engagement data at the campaign level. GA4 records engagement time while the page is in the foreground, which is far more precise than the old average time-on-page metric.
Pro Tip: Pull your GA4 traffic acquisition report and filter by campaign name before you look at anything else. A vendor's engagement numbers mean nothing until they are isolated from every other traffic source hitting your page that week.
Watch for four pitfalls that quietly corrupt these numbers: visitors who open your page in a background tab (GA4 stops counting active time until it returns to focus), bot or click-farm traffic that registers a session but no real engagement, misattribution from missing or malformed UTMs, and truncated sessions from users who bounce off a slow-loading redirect before the page tag even fires.
Benchmarks and expectations for engaged session rate
There is no universal "good" dwell time number, and any vendor or guide that hands you a single target figure without a source is guessing. What works is comparing vendor traffic against your own site's baseline and against other vendors you have tested, using the same tagging setup for all of them.
GA4 counts a session as engaged when it lasts 10 seconds or longer, includes a key event, or includes two or more pageviews. That engaged session baseline is the floor for calling a visit meaningfully engaged rather than a drive-by click, and it is the number you should be comparing across vendors, not a vague sense of how long people "seem" to stay.
In practice, engaged session rates fall into three rough zones worth watching for:
- A low engaged session rate paired with a low opt-in rate usually points to traffic quality problems such as bots, incentivized clicks, or a list that may not match your offer.
- A middle-range engaged session rate with a healthy opt-in rate is common and often indicates your landing page may need tightening, rather than reflecting on the vendor's quality.
- A high engaged session rate with a low opt-in rate often suggests a page or offer mismatch rather than a traffic quality issue, since visitors stay engaged but do not convert.
Display and video ad benchmarks vary widely by channel and creative, which is exactly why industry-wide CTR figures from other ad formats are a poor substitute for your own baseline. Solo ads are their own channel with their own audience behavior, and the only benchmark that matters is the one you build from your own tracked history.
Never judge a vendor on engagement alone. Pair every engagement number with opt-in rate and cost per lead before drawing a conclusion, since a cost-per-lead comparison will often tell a different story than dwell time does on its own. A vendor whose traffic engages well but converts to opt-ins expensively is not automatically a bad vendor, and a vendor with mediocre engagement but a strong opt-in rate might be exactly the one worth repeating.

Step-by-step solo ad testing sequence
Testing a new vendor works best as a fixed sequence, not a single gut check after the first batch of traffic lands. Skipping steps is how buyers end up scaling a bad vendor or dropping a good one too early.
- Run a small preliminary test of 100 to 200 clicks. This size is enough to verify delivery and uniqueness without risking a large budget on an unproven source.
- Confirm attribution before reading anything else. Check that your UTMs are showing up correctly in GA4's campaign reports; if the traffic is not attributing cleanly, every later number is unreliable.
- Inspect engagement metrics for that specific campaign. Look at engaged session rate and average engagement time isolated to that vendor's tagged traffic, following the recommended measurement sequence of verifying clicks, confirming attribution, and then reading engagement.
- Measure opt-in rate and cost per lead. Compare these against your own historical numbers and against published opt-in benchmarks for context.
- Wait for email engagement and sales events before concluding anything. A vendor's real value often only shows up once new subscribers start opening emails and buying, which can take days beyond the initial click data.
Three decision triggers come out of this sequence. If engagement is fine but opt-ins are weak, the landing page usually needs work before you blame the vendor. If click logs and your own tracker disagree on delivered volume, ask the vendor for detailed click logs before buying again. If both engagement and opt-ins are consistently poor across a full test batch, stop buying from that vendor and move the budget elsewhere.
Vendor vetting: verification before the buy
Dwell time and engagement data tell you what happened after traffic arrived. Vetting is what protects you before you spend anything at all, and it is the step most buyers skip because it takes longer than clicking "buy now" on a marketplace listing.
A 21-question vendor vetting framework distills down to a handful of checks that matter most:
- Ask for recent click logs, not screenshots of dashboard totals, since logs show timestamps and IP patterns that dashboards hide.
- Ask how the vendor built their list and how old the average subscriber is, since origin transparency separates real list owners from resellers.
- Ask what happens if delivered clicks fall short of the order, and get the refund or makeup-traffic policy in writing before paying.
- Ask for a deliverability history rather than a promised open rate, since past performance is checkable and promises are not.
Vetting exists precisely because dwell time can be misread. A vendor can send traffic that engages reasonably well on a landing page and still be a poor long-term source if the list is aging or over-mailed. Verifiable artifacts like click logs and refund terms reduce how much weight any single engagement metric has to carry.
Pro Tip: Ask every new vendor the same five or six questions in writing before you buy, and keep the answers on file. A vendor who answers vaguely or refuses to answer at all has told you everything you need to know.
Interpreting results: optimize, scale, or stop
Once a test batch runs its full course, from clicks through engagement through opt-ins and, ideally, a sales event, the numbers point toward one of three actions.
- If engagement is low but opt-in rate is healthy, the traffic is probably fine and the issue is more likely deliverability or a mismatch between the email swipe and your squeeze page, not the vendor's traffic source.
- If both engagement and opt-in rate are low, pause the vendor, request detailed click logs, and run a full traffic-quality audit before spending any more with them.
- If engagement is high but conversions past the opt-in stage stay flat, the traffic is doing its job and the problem sits in your offer, your landing page copy, or a weak follow-up sequence.
This is where the buyer-first approach earns its keep. A vendor cut on dwell time alone, without checking opt-ins and revenue, risks losing a genuinely good traffic source over a landing page problem that had nothing to do with them. The reverse is just as costly: continuing to buy from a vendor because engagement looked fine while opt-ins and sales quietly stayed weak test after test.
Tools and resources to put this into practice
Turning this into a repeatable habit takes a short setup, not a new system. Start with these five actions.
- Set up UTM tagging using a consistent naming convention before your next buy.
- Read the full click tracking guide and confirm your tracker matches vendor-reported clicks.
- Bookmark the click log request guide so you know exactly what to ask for.
- Check your opt-in rate against current benchmarks before your next test.
- Run your first 100 to 200 click test using the verification protocol outlined above.
Author perspective: why verification beats vendor promises
Philip Coble has sold solo ad traffic for 11 years, and the pattern repeats: buyers who trust a vendor's pitch over their own tracking lose money slower or faster, but they always lose it. Independent tracking and a strict test sequence exist because no vendor claim, however sincere, replaces a number you measured yourself. The one habit worth adopting: always run a small, tagged test before scaling any vendor, no exceptions.
— Philip Coble
How SoloAdsGuide.com helps you buy with more certainty
Everything in this article traces back to one habit: verify before you trust. This resource builds that habit into practical tools instead of leaving you to figure it out mid-campaign.
The 21-question vendor vetting checklist gives you the exact questions to ask before any purchase, alongside tracking setup guides and verification templates built around the same UTM and GA4 methods covered above. The goal is straightforward: less budget wasted chasing vendor claims, more decisions made on signals you can actually check yourself. Visit Soloadsguide to get the checklist and start tagging your next test the right way.
Sources
The measurement guidance here draws on Google's engaged session documentation, Analytics Help's user engagement reference, and Google's campaign attribution requirements. Consult GA4's own documentation directly for exact metric definitions before building custom reports.
FAQ
What is considered a good dwell time?
There is no single universal number, since GA4 does not report "dwell time" directly. Instead, compare your engaged session rate, where sessions of 10 seconds or more, a key event, or two or more pageviews count as engaged, against your own site's historical baseline for each traffic source.
What's a good CTR for display ads?
Click-through rates vary widely by channel, creative, and audience, so industry benchmark data should be treated as a rough reference point rather than a target. Solo ad traffic behaves differently from display ads, so your own tracked history is a better guide than a cross-channel average.
What does dwell time mean in SEO?
In an SEO context, dwell time generally refers to how long a visitor stays on a page after clicking a search result before returning to the results page. GA4 does not track this directly, but its engaged session and average engagement time metrics serve a similar diagnostic purpose for judging content quality.
How is dwell time measured?
GA4 measures engagement through engagement_time_msec, which records active time while the page is in the foreground, and rolls it up into average engagement time and engaged session counts. Time spent in a background tab or an inactive app window is not counted toward this figure.
Recommended
- Solo Ad Buyers: 50–200 Click Test and 21 Questions to Verify Leads
- Marketers: Verify Solo Ad Traffic With a 100 to 200 Click Test
- Solo Ad Analytics Dashboard Setup: Verify Before You Pay
- Solo Ad Click Logs: A Buyer's Guide to Verifying Traffic
Want Verified Traffic Without the Guesswork?
PulseTraffic screens every seller, filters bot clicks in real time, and shows you verified buyer traffic labels before you spend a dollar.


