Skip to main content

API Credentials and Health Checking

The API Credentials page is designed for managing integration tokens, authorization keys, and Google Credentials required for seamless interaction between the platform and external advertising system APIs.


Table Columns Description

ColumnDescription
EmailThe Google account email address through which the OAuth API access authorization was performed.
Google MCCThe identifier or title of the associated manager account (Google MCC) linked to this credential set.
Администратор (Administrator)Credentials of the user (name/email) who added or updated this specific API token configuration on the platform.
Статус (Status)The live system authorization state of the token (e.g., active, requires re-authentication, or disconnected).
Последнее использование (Last Use)The exact date and time of the last successful API request dispatched to Google utilizing this credential set.
Последняя проверка (Last Checked)The exact date and time of the last scheduled or manual connection health validation routine.
Последняя ошибка (Last Error)A technical log string mapping the exact error payload or failure response code returned from Google Ads API.

Access Health Check (Action Flow)

Video example with access health check

To minimize the risks of background routine interruptions (such as account creation failures or spend synchronization stalls), an administrator can manually initiate a connection diagnostic for each individual MCC credential set.

Step 1. Accessing the Diagnostic Menu

  1. Navigate to the API Credentials page.
  2. Locate the row with the target credentials and click the context menu button (the "Three Dots" icon) at the end of the row.
  3. Select Health Check from the dropdown menu block.

Step 2. Confirmation and Results Handling

  1. Selecting the action launches a modal confirmation window.
  2. The platform pushes a background validation request directly querying Google APIs.
  3. Error Handling: If the routing sequence detects an invalid token, revoked access scopes, or any other structural failure, the test stops. The live error message automatically prints inside the table row under the Last Error column.