Skip to content

docs(clay-ads): explain 95%+ match rate display for Meta, Reddit Ads, Bing Ads - #2507

Open
george-dilthey wants to merge 2 commits into
mainfrom
docsbot/doc-2291-product-update-0902-27f05278
Open

docs(clay-ads): explain 95%+ match rate display for Meta, Reddit Ads, Bing Ads#2507
george-dilthey wants to merge 2 commits into
mainfrom
docsbot/doc-2291-product-update-0902-27f05278

Conversation

@george-dilthey

Copy link
Copy Markdown
Contributor

What changed

Updated docs/clay-ads.md: replaced the closing sentence of the FAQ "Why is my matched count higher than the number of contacts I sent?" with two sentences that also explain that when this behavior drives the match rate to 95% or higher, Clay displays the rate as 95%+ rather than an exact percentage on the professional network, Meta, Reddit Ads, Bing Ads, and Vibe, and that a tooltip on the 95%+ display confirms the behavior.

Why

Commit e6017f3 (deploy e0b7a81...e6017f3https://github.com/clay-run/clay-base/actions/runs/33689435705) extended the 95%+ match-rate display cap from the professional network and Vibe to also cover Meta, Reddit, and Bing Ads. Customers using Meta (the most common platform) will now see "95%+" in the Sync History and provider card when their match rate is very high — triggered by Enhanced Matching sending up to 3 hashed emails per contact, which can push the platform's matched count above the contacts-sent count, driving the raw rate above 100%.

The existing FAQ explained why matched count can exceed contacts sent, but never mentioned that the match rate itself also displays as "95%+" in that situation. Fin and customers searching "why does my match rate show 95%+" had no targeted answer in the docs.

Source link(s)

Uncertainties

None. The changed line is directly verified against the deployed code.

Related observations

Confidence: high

Closes DOC-2291

@linear-code

linear-code Bot commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

DOC-2291

@george-dilthey
george-dilthey marked this pull request as ready for review September 2, 2026 23:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant