integration pair · root cause analysis

Root Cause Analysis: Google Ads + GitHub

Why did this number change? askotter reads Google Ads and GitHub together and answers it for your business, by text.

● Google Ads · LIVE + ● GitHub · LIVE Root Cause Analysis
Connect Now → See how it works
the short answer

How does root cause analysis with Google Ads and GitHub work for a small business?

askotter reads Google Ads and GitHub side by side so it can test each explanation against your connected accounts and find the cause. A ranked list of likely causes, each with the evidence behind it.

Read the full answerShow less

The owner asks follow-up questions by text.

From Google Ads
Campaign performance, Keyword data and quality scores, Ad group and creative performance.
From GitHub
Commits and pull requests, Deployment events, Release tags.
Status
Both connect today.
Not for
Replacing Google Ads or GitHub. Both keep working exactly as they do now.
the problem

Why did this number change?

Bookings dropped 23%. The ad, the website and the weather all get blamed. Without your accounts side by side, it stays a guess.

How askotter handles it

askotter reads Google Ads and GitHub side by side, so it can test each explanation against your connected accounts and find the cause.

A person checks the result before it reaches you. This is part of our Google Ads management work.

matching the records

How Google Ads and GitHub records line up

Google Ads and GitHub share no customer or visit identifier. askotter puts them on one timeline instead, so a change in Google Ads clicks can be read against what GitHub recorded in the same hours.

What root cause analysis uses from each

Root cause analysis needs timestamps precise enough to put events in order.

From Google Ads that means the change history for bids, budgets and ads. From GitHub it means the commit and deploy closest to when a metric moved.

What each tool sees on its ownShow less

Google Ads on its own

Google Ads counts the conversions it can see through its own tag. It cannot tell a refunded sale from a kept one, or a junk lead from a good one.

Timing. Google Ads credits a conversion back to the date of the click, so yesterday's conversion count can still rise for days.

Access. The Google Ads API with read access to the account.

GitHub on its own

GitHub knows what code changed and when. It cannot tell you whether that change cost you leads or sales.

Timing. GitHub timestamps every commit, merge and deployment to the second.

Access. A GitHub App or token with read access to the repositories you choose.

questions

Questions about Google Ads + GitHub

Do I need a developer to connect Google Ads and GitHub?

No. Most accounts connect with a sign-in, and the rest take a file export.

How is askotter's Root Cause Analysis different from what Google Ads shows on its own?

Google Ads only sees its own numbers. askotter reads Google Ads and GitHub together and can answer the question: Why did this number change?

Connect Google Ads + GitHub. Five minutes.

Plans are on the digital marketing pricing page.

Self-managed is $99/mo and scales with the compute you use. Our team runs it from $600/mo.