Sherlock Calls
for ClickHouse + Google Ads
ClickHouse stores and queries high-volume event and operational data at scale. Google Ads runs your paid search and display campaigns across Google's network. When you need to investigate across both, the evidence is split between two dashboards neither of which knows the other exists. Sherlock Calls bridges them — no code, no exports, no manual joins. Ask once from Slack and get a sourced answer in under 5 seconds.
TL;DR — What beta users get access to
- 1
Sherlock Calls connects to ClickHouse, Google Ads simultaneously — read-only, no code changes, no webhooks — and lets you query both with a single Slack message.
- 2
Ask questions that neither ClickHouse nor Google Ads can answer alone. ClickHouse holds the raw source of truth — but querying it for business questions requires SQL access and data engineering resources. Google Ads shows ad conversions — not which campaigns actually drove calls and won deals. Sherlock deduces the complete picture from both.
- 3
No dashboard switching, no manual joins, no fog of uncertainty — ask in Slack and receive a sourced answer with evidence from every connected provider in under 5 seconds. The game is afoot.
<5s
Answer to any database + ad campaigns query
2
Connected platforms, 1 Slack question
0
Code changes or webhooks required
The Investigation Gap
What's invisible when you use ClickHouse + Google Ads without Sherlock
Each platform shows you its own data. But the questions that matter most live in the gaps between them.
Google Ads campaign performance is optimised without ClickHouse LTV and retention data
Google Ads reports cost per acquisition and on-site conversion. ClickHouse holds the product usage, subscription state, and retention data that reveals whether those conversions became valuable customers. True ROAS lives across both — and is rarely computed.
Your most valuable ClickHouse customer segments are never activated in Google Ads
ClickHouse holds the product usage patterns and behavioural signals that define your highest-LTV customers. Google Ads has the targeting tools to find more of them. But the signal from ClickHouse never reaches Google Ads campaign audiences without a deliberate bridge.
Google Ads re-engagement campaigns reach the wrong ClickHouse segments
Google Ads re-targets based on on-site behaviour. ClickHouse holds the operational data that would identify which inactive customers are actually worth re-engaging — and which have already churned. Without the ClickHouse filter, Google Ads spend is wasted on unwinnable segments.
Cross-Provider Questions
What teams ask Sherlock about ClickHouse + Google Ads
Questions that would take hours to answer manually — answered in under 5 seconds from Slack.
- SC“Which ClickHouse customer segments — by product usage data — produce the best Google Ads campaign ROAS?”
- SC“Show me Google Ads campaign clicks from customers with the highest ClickHouse retention signals”
- SC“Find Google Ads ad audiences that overlap with ClickHouse high-value customer cohorts”
- SC“Which Google Ads campaigns produce customers whose ClickHouse application behaviour signals long-term retention?”
- SC“What's the ClickHouse usage difference between customers acquired via different Google Ads channels?”
Beta Setup
Connect ClickHouse + Google Ads to Sherlock in 2 minutes
No code, no webhooks, no new dashboards. Beta users get direct onboarding support.
- 1
Connect ClickHouse
Add your ClickHouse credentials to Sherlock Calls. Read-only access — no code changes, no webhooks, no ClickHouse configuration required.
- 2
Connect Google Ads
Add your Google Ads credentials. Sherlock indexes all ad campaign clicks, impressions, spend, and conversions automatically.
- 3
Ask your first cross-provider question. The game is afoot.
Type any question about your combined ClickHouse + Google Ads stack in Slack. Sherlock queries all connected platforms in parallel, correlates the evidence, and returns a sourced answer in under 5 seconds.
FAQ
Common questions about Sherlock + ClickHouse + Google Ads
How does Sherlock Calls connect ClickHouse and Google Ads data?
- Sherlock uses read-only API access to both platforms simultaneously. When you ask a question, it queries ClickHouse, Google Ads in parallel, correlates the results by timestamp and shared identifiers, and produces a single sourced answer — the same way a good detective correlates evidence from multiple witnesses.
Do I need to set up any data pipelines between ClickHouse and Google Ads?
- No. Sherlock Calls is entirely pull-based — it queries both APIs on demand when you ask a question. There are no webhooks, no ETL pipelines, no data warehouses, and no code changes required in any of the connected platforms.
What kinds of questions can I ask about my ClickHouse + Google Ads stack?
- You can investigate anything that spans both platforms — query volume and event ingestion rate, ROAS, cost per conversion, and impression share, cross-platform costs, handoff patterns, and performance comparisons. Sherlock translates your plain-English question into the right API calls and returns the deduced answer.
Is my ClickHouse and Google Ads data stored by Sherlock?
- No. Sherlock Calls queries your data in real time and returns results directly to Slack — nothing is stored, indexed, or replicated in any Sherlock database. All data remains in ClickHouse and Google Ads and is accessed only during an active investigation.
How long does it take to set up the ClickHouse + Google Ads integration?
- Elementary — typically under 5 minutes total. Connect each platform with read-only credentials, install the Sherlock Calls Slack app, and ask your first question. No engineering, no dashboards, no onboarding calls required.
Apply for early access to Sherlock + ClickHouse + Google Ads
We're accepting a select group of beta users to shape the ClickHouse + Google Ads combination. Tell us about your stack and we'll reach out personally if you're a fit.
Explore individual integrations