Google Marketing Platform Admin API

Name: Google Marketing Platform Admin API
Brand: Google Marketing Platform Admin API
Availability: InStock

✓ Official Vendor SpecMarketingMarketing Automationoauth25 Endpoints

Install Jentic One Beta

Connect the Google Marketing Platform Admin API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Google Marketing Platform Admin API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgoogleapis.com%2Fgoogle-marketing-platform-admin" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgoogleapis.com%2Fgoogle-marketing-platform-admin" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Google Marketing Platform Admin API.

List Analytics account links registered under a Marketing Platform organisation

Delete an Analytics account link from a Marketing Platform organisation

Set the property service level (Standard or 360) on a linked Analytics property

GET STARTED

Start building with Google Marketing Platform Admin API

Explore with Jentic

View OpenAPI Document

For Agents

Manage Google Marketing Platform organisation-level admin links to Google Analytics accounts and set Analytics property service levels.

Use for: List all Google Analytics account links under our Marketing Platform organisation, Set an Analytics property to the GA360 service level via the admin link, Delete an Analytics account link that no longer belongs to our organisation, Audit which Analytics accounts are currently linked to our Marketing Platform org

Not supported: Does not handle Analytics reporting, Display & Video 360 campaigns, or Search Ads 360 configuration - use for Marketing Platform organisation-to-Analytics link administration and property service level changes only.

Use Cases

Patterns agents use Google Marketing Platform Admin API for, with concrete tasks.

★ Organisation governance audit

Audit which Google Analytics accounts are linked to a Marketing Platform organisation, useful when ownership of accounts changes hands or when teams need to confirm that all Analytics accounts under a brand are governed by the expected organisation. The list endpoint returns paginated entries that an agent can walk in a single pass.

List analyticsAccountLinks for organizations/12345 and report any link whose Analytics account ID is not in our authoritative inventory

Analytics service level upgrades

Promote linked Analytics properties to the GA360 service level using setPropertyServiceLevel as part of contract activation, or downgrade them when 360 entitlement ends. The endpoint is the programmatic equivalent of changing service level in the Marketing Platform UI.

Call setPropertyServiceLevel on the analyticsAccountLink for property 444555 to GOOGLE_ANALYTICS_360

Account link cleanup after divestiture

After a divestiture or rebranding, remove Analytics account links from a Marketing Platform organisation so the divested business can attach those Analytics accounts to its own organisation. The delete endpoint detaches the link without deleting the underlying Analytics account.

Delete the analyticsAccountLink whose Analytics account ID matches the divested entity's account 999

Agent integration via Jentic

AI agents that operate as automated platform administrators can use the Marketing Platform Admin API through Jentic to enforce link inventory and service-level policy across many Analytics properties without holding the OAuth refresh token in the prompt.

Walk every analyticsAccountLink in organizations/12345 and ensure properties listed in our 360 contract are at GOOGLE_ANALYTICS_360 service level

Key Endpoints

5 endpoints — the google marketing platform admin api manages organisation-level admin links between a google marketing platform organisation and google analytics accounts, including setting analytics property service levels.

METHOD

PATH

DESCRIPTION

GET

/v1alpha/{+parent}/analyticsAccountLinks

List Analytics account links in an organisation

DELETE

/v1alpha/{+name}

Delete an Analytics account link

POST

/v1alpha/{+analyticsAccountLink}:setPropertyServiceLevel

Set service level on a linked Analytics property

GET

/v1alpha/{+parent}/analyticsAccountLinks

List Analytics account links in an organisation

DELETE

/v1alpha/{+name}

Delete an Analytics account link

POST

/v1alpha/{+analyticsAccountLink}:setPropertyServiceLevel

Set service level on a linked Analytics property

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Google Marketing Platform Admin API by hand means setting up Google OAuth 2.0 with the marketingplatformadmin and analytics scopes, refreshing bearer tokens, and tracking the v1alpha surface yourself against the marketingplatformadmin.googleapis.com host. Through Jentic you install once, import the Google Marketing Platform Admin API from the API Directory, store the OAuth credential once, and your agent calls it.

Permission scoping

This API puts the organization and link name in the URL path (/v1alpha/{+parent}/analyticsAccountLinks and /v1alpha/{+name}), so a rule can pin your agent to one Marketing Platform organization: it can list Analytics account links there and nothing else. You choose the operations it may call, so ones like deleting a link or setting a property service level are not included unless you add them.

Credential isolation

Your Google OAuth credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list Analytics account links' or 'set a GA360 service level', and Jentic returns the matching admin operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Google Marketing Platform Admin API through Jentic.

What authentication does the Marketing Platform Admin API use?

The API uses Google OAuth 2.0 with marketingplatformadmin and analytics scopes. Through Jentic, the OAuth client credentials and refresh tokens stay in the encrypted vault and the agent only handles a short-lived bearer token.

Can I change an Analytics property to the GA360 service level through this API?

Yes, the setPropertyServiceLevel endpoint on an analyticsAccountLink accepts a service level value of GOOGLE_ANALYTICS_STANDARD or GOOGLE_ANALYTICS_360 and updates the linked property accordingly.

What are the rate limits for this API?

Per-project quotas are managed in the Google Cloud Console under the Marketing Platform Admin service. The endpoint count is small so daily quotas are typically generous, but bulk service-level updates should still use exponential backoff on 429 responses.

How do I delete an Analytics account link through Jentic?

Search Jentic for delete analytics account link, load the operation mapping to /v1alpha/{+name}, and execute with the link resource path. Jentic injects the OAuth bearer and returns the empty success response.

Is the Marketing Platform Admin API free?

The API itself is free; usage is governed by quota. Costs only apply to underlying products such as Google Analytics 360 if you change a property's service level to 360.

Why is this API at v1alpha?

v1alpha is Google's pre-stable channel. Endpoints, request bodies, and behaviour can change before the API graduates to v1, so production integrations should pin to a specific revision and watch the release notes for breaking changes.