Google Ads3

This guide will help you connect a Google Ads data grabber to the Magify analytics system.The grabber collects data on ad assets, geo performance, and other account-level metrics, enabling automated data import into your analytics pipeline.

Getting Started

  1. Go to: Configurations > Integration > UA Grabbers and select Google Ads from the list.
  2. Click the Add Grabber button to create a new data source.

This will open a configuration form where you can enter the required connection parameters. Below is a description of each field, along with instructions on where to find the necessary values.

Name

The name of the grabber configuration in the Magify system. It helps you identify this data source among other integrations.

Recommended format: Use a clear and descriptive name, for example:

  • Google Ads – Your Company
  • Google Ads – UA Tracker
  • Google Ads – Promo App

Client ID and Client Secret

These are the two key parameters required for authorization via OAuth 2.0 — the protocol used by the grabber to access the Google Ads API on behalf of your project.

How to get them:

  1. Go to the Google Cloud Console.
  2. In the top menu, click Select a project, and either:
    • choose an existing project, or
    • click New project to create a new one.
Screenshot 2025-04-18 at 16.39.18.png

If you don't have a project in Google Cloud Console yet, follow these steps:

  1. Click New project in the top right corner of the project selection window.
  2. In the popup window, provide the following:
  • Project name — enter any descriptive name (e.g., Your Application Name).
  • Optionally, select your organization and folder, if applicable.
  1. Click Create.
Screenshot 2025-04-18 at 16.56.52.png
Screenshot 2025-04-18 at 16.58.42.png
  1. Once you’ve selected or created a project, you need to configure the consent screen that will be linked to your OAuth client:
    1. In Google Cloud Console, go to APIs & Services → OAuth consent screen.
    2. On the page that opens, click Get Started.
Screenshot 2025-04-18 at 18.02.44.png
  1. A step-by-step configuration form will open:Fill out the App Information section:
    • App name — the name that will be displayed to users. For example: Magify Application
    • User support email — the support contact email (for user inquiries).
Screenshot 2025-04-18 at 18.06.26.png

Choose the user type (Audience):

  • External — select this if the integration will be used outside your organization. This is the default and most common option.
  • Internal — only available for Google Workspace accounts within your organization.
Screenshot 2025-04-18 at 18.07.11.png

Enter the Developer contact information:

  • This email will be used by Google to send important notifications related to your project.
  • Enter a valid work email (e.g., magify.application@magify.com).
Screenshot 2025-04-18 at 18.07.32.png

Finalize the consent screen setup:

  • Accept the Google API Services: User Data Policy.
  • Click Create to complete the OAuth consent screen setup.
Screenshot 2025-04-18 at 18.07.50.png
  1. Now that the consent screen is set up, you can proceed to create your OAuth client. To create your OAuth 2.0 Client:
    1. Go to APIs & Services → Credentials, then click + Create Credentials → OAuth client ID, or, if you're still on the same page after completing the consent screen, simply click Create OAuth client.
    2. Configure the OAuth client:
      • In the Application type field, select Web application. This is the appropriate option for manually retrieving a refresh token using tools like OAuth Playground.
      • In the Name field, enter a name to help you identify this client in the console. (This name is internal only and won’t be visible to end users.) Example:
        • Magify Application UA Grabber
        • Google Ads Connector
        • My OAuth Client
    3. Set up the redirect URI:
      • In the Authorized redirect URIs section, click + Add URI and enter the following: https://developers.google.com/oauthplayground. This is the URL used by Google's OAuth Playground — a tool for manually testing and retrieving tokens. Enter the URL exactly as shown — without extra characters, trailing slashes, or IP addresses.
    4. Finally, click Create.
Screenshot 2025-04-18 at 19.19.36.png
  1. After clicking Create, a dialog window will appear (see screenshot above). Once done, you will be presented with your OAuth 2.0 Client ID and Client Secret.You can download these credentials in JSON format and save them for later use.For more details, refer to the Google Ads API Authentication Guide (Step 2).

Refresh token

The refresh token is a key that allows the grabber to stay authorized in the Google Ads API without requiring repeated logins.It works together with your Client ID and Client Secret to automatically refresh the access token and maintain a persistent connection.

How to get a refresh token using OAuth Playground

  1. Open the OAuth 2.0 Playground
  2. Click the ⚙️ (gear icon) in the top-right corner and enable: ✔ Use your own OAuth credentials
  3. Set the following option: Force prompt → No. This disables extra authorization prompts during token refresh.
Screenshot 2025-04-21 at 13.29.49.png
  1. At Step 1: Select & authorize APIs, locate and expand the Google Ads API category.
  2. Check the box next to: https://www.googleapis.com/auth/adwords. This grants access to Google Ads data via the API.
  3. Click the Authorize APIs button.Sign in with your Google Ads account and confirm access when prompted.
Screenshot 2025-04-18 at 21.29.58.png
  1. After successful authorization, click Exchange authorization code for tokens.
Screenshot 2025-04-21 at 15.43.33.png
  1. The Playground will display both the Access Token and the Refresh Token.Copy the Refresh Token — you’ll need it when configuring the grabber in Magify.
Screenshot 2025-04-18 at 21.35.27.png

Developer token

The Developer Token is a unique key used to identify your application when making requests to the Google Ads API. Without it, no requests from the grabber will be accepted by Google.

Where to get your Developer Token:

  1. Go to your Google Ads Manager (MCC) account.
  2. In the left-hand navigation menu, click Admin → then select API Center (or go directly to ads.google.com/aw/apicenter if you're already in the correct account)
  3. On the page, you’ll see the Developer Token field — copy the value shown there.
Screenshot 2025-04-22 at 12.40.24.png

Manager Customer ID

The Manager Customer ID (or MCC ID) is a unique identifier of your Google Ads Manager Account. The grabber uses this ID to operate on behalf of your account when fetching data.

Where to find your Manager Customer ID:

  1. Log in to Google Ads with the account you plan to use in Magify.
  2. Open the account you intend to connect.
  3. The Customer ID will be displayed in one of the following locations:
    • In the top-right corner of the interface, near the account name
    • Or in the top-left corner, next to the dropdown menu where you switch accounts (For Manager accounts, click the down arrow next to the MCC account name — the ID will be shown there.)

The ID will follow the format: 123-456-7890 This is your Manager Customer ID — copy and paste it into the corresponding field in Magify.

Screenshot 2025-04-21 at 19.58.19.png

Related articles

Transaction Validator

Tappx

Algorix

BIGO Ads

Facebook

Facebook