Sherlock Calls
for Datadog + Google Ads
Datadog monitors every layer of your infrastructure with metrics and traces. 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 Datadog, 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 Datadog nor Google Ads can answer alone. Datadog shows infrastructure events — not how they map to call failures or customer impact. 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 observability + ad campaigns query
2
Connected platforms, 1 Slack question
0
Code changes or webhooks required
The Investigation Gap
What's invisible when you use Datadog + Google Ads without Sherlock
Each platform shows you its own data. But the questions that matter most live in the gaps between them.
Datadog campaign launches create Google Ads incidents nobody anticipated
When a Datadog campaign drives a traffic spike, it often triggers a Google Ads infrastructure event. By the time engineering investigates, the Datadog context has been forgotten — and the connection is never made.
Capacity planning ignores Datadog campaign calendar
Your Google Ads team scales infrastructure based on historical patterns. Your Datadog team plans campaigns independently. The result: the campaigns that most stress your infrastructure are the ones engineering least expected.
Google Ads post-mortems don't include Datadog demand triggers
After a Google Ads incident, the post-mortem focuses on infrastructure. The Datadog campaign that drove the traffic spike that caused the incident is rarely part of the analysis — and so it recurs.
Cross-Provider Questions
What teams ask Sherlock about Datadog + Google Ads
Questions that would take hours to answer manually — answered in under 5 seconds from Slack.
- SC“Which Google Ads campaign launches correlated with Datadog infrastructure incidents?”
- SC“Show me Datadog alerts that fired in the 6 hours following a major Google Ads campaign activation”
- SC“What's the Datadog infrastructure load increase per 10,000 Google Ads campaign sessions?”
- SC“Find Google Ads campaigns that drove traffic spikes Datadog shows caused service degradation”
- SC“Which Google Ads campaigns should trigger a Datadog infrastructure pre-scale before next launch?”
Beta Setup
Connect Datadog + Google Ads to Sherlock in 2 minutes
No code, no webhooks, no new dashboards. Beta users get direct onboarding support.
- 1
Connect Datadog
Add your Datadog credentials to Sherlock Calls. Read-only access — no code changes, no webhooks, no Datadog 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 Datadog + 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 + Datadog + Google Ads
How does Sherlock Calls connect Datadog and Google Ads data?
- Sherlock uses read-only API access to both platforms simultaneously. When you ask a question, it queries Datadog, 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 Datadog 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 Datadog + Google Ads stack?
- You can investigate anything that spans both platforms — alert rate, latency, and service health, 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 Datadog 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 Datadog and Google Ads and is accessed only during an active investigation.
How long does it take to set up the Datadog + 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 + Datadog + Google Ads
We're accepting a select group of beta users to shape the Datadog + Google Ads combination. Tell us about your stack and we'll reach out personally if you're a fit.
Explore individual integrations