Dashboard › sentry › Session 0RWjaKd61yx3
0RWjaKd61yx3dfSEFThe transactions dataset is being deprecated. Please use Explore / Traces with the is_transaction:true filter instead. Please read these FAQs for more information.
Let me check Explore/Traces:
[tool results provided]
Here's the Explore/Traces link:
https://sentry.sentry.io/traces/?query=transaction%3A%2Astripe-projects%2A%20is_transaction%3Atrue&statsPeriod=14d&project=-1
Can you check if this shows results? If is_transaction:true works in Explore but not in the spans dataset API, we might be able to use the Explore-backed dataset for the dashboard widgets. Let me know what you see.
link opens and the query seems correct but after a long while of loading, I got "Internal error. Please try again."
Probably a timeout on the query. The Explore/Traces view queries differently than spans — it might be scanning too much data for a 14d window. Try narrowing to 7d or 1d to see if it loads.
But this confirms the fundamental issue: is_transaction:true isn't reliably queryable for this project's data. The transactions aren't properly indexed as spans in ClickHouse yet.
For now, the dashboard with count_unique(trace) is the best we can do — it gives the real sampled count (7 traces) without inflation. The discover link I gave you earlier still works for the weighted extrapolation (33).
The honest takeaway doesn't change regardless of which number you use: since launch on April 28th, there have been single-digit real user interactions with Stripe Projects onboarding. Even if the true number is 3-5x the sampled count due to sampling gaps, that's still under 50 total actions in 10 days — essentially no organic adoption yet.