Google Ads
Connecting Google Ads lets Brixit receive submissions from your lead form extensions and assets.
What you need
A Google Cloud project with OAuth credentials, and a Google Ads developer token. The developer token is applied for in your Google Ads manager account under Tools → API Center, and Google grants it in stages — test access arrives quickly, basic access needs an application and a wait. You can save the token in Brixit before it is approved.
Fill in the fields
Settings → Integration keys → Lead sources → Google Ads.
| Field | Where to find it |
|---|---|
| Client ID | Google Cloud Console, APIs & Services → Credentials |
| Client Secret | Same credential, revealed when you open it |
| Developer Token | Google Ads, Tools → API Center |
| Webhook Verification Key | You invent this one |
Create the OAuth credential as an OAuth client ID of type Web application. Add the redirect URI that Brixit shows on the card to Authorised redirect URIs.
The Webhook Verification Key is a string you choose. Google sends it with every lead form submission and Brixit rejects anything that does not match, which is what stops a stranger posting fake leads at your webhook. It must be at least 16 characters.
Enable the API
In Google Cloud Console, under APIs & Services → Library, enable the Google Ads API for the project. Without this, authorisation appears to succeed and every subsequent call fails.
Configure the lead form
In Google Ads, open the lead form asset and set Webhook URL to the address shown on the Brixit card, with the same key you saved. Google’s Send test data button tells you immediately whether the endpoint is accepted.
Connect
In Brixit, Integrations → Google → Connect, authorise, and pick the account to draw leads from.
If leads do not arrive
Google retries a failing webhook for a short period and then stops. The Send test data button is the quickest way to see the actual error; a mismatched verification key is by far the most common cause.