# Connect Google Ads

> Connect Google Ads to DataFirefly Server-Side: Connect Google Ads OAuth, customer ID, MCC account, conversion action mapping per event.

- Original page: https://server-side.datafirefly.com/en/docs/google-ads.html
- Language: en
- Updated: 2026-09-01
- Publisher: DataFirefly (Datafirefly Limited), https://server-side.datafirefly.com/en/

---

One OAuth authorization, your customer ID, and the mapping of your conversion actions: three steps.

## 1. Authorize access

1. On your site page, click **"Connect Google Ads"**.
2. Authorize with the Google account that manages your Google Ads account.

The authorization token never passes through your browser and can be revoked at any time from your Google account.

## 2. Fill in the identifiers

| Field | Where to find it |
| --- | --- |
| Google Ads customer ID | Top right of the Google Ads interface, in the `123-456-7890` format |
| Google Ads manager (MCC) ID, optional | If your account is managed through an MCC: the manager account's identifier, shown in the same place when you are on the MCC |
| Conversion actions | Google Ads > **Goals > Conversions**: open each conversion action and note its numeric identifier |

## 3. Map your events

The **Conversion actions** field links your events to your Google Ads conversion actions, one line per event:

```
purchase = 987654321
lead = 123456789
```

Mappable events: `page_view`, `view_content`, `add_to_cart`, `initiate_checkout`, `add_payment_info`, `purchase`, `lead`, `complete_registration`, `search`.

An event without a mapping is **not sent** to Google Ads. Map `purchase` at the very least.

## Verify

1. After saving, the console automatically tests the credentials.
2. Conversions appear in Google Ads with Google's usual processing delay, count on several hours.

Updated: September 1, 2026
