google_ads_get_activities

Get Google Ads Activities

Google

Description

Retrieve change history for a Google Ads account: who changed what and when, with before/after values. Hopkin archives Google's change events continuously and keeps them for 25 months, well beyond Google's own 30-day limit, so older windows can be asked for directly. coverage.complete_from says how far back history is complete for this account, and coverage.note appears when the requested window starts earlier — an empty result before that point does not mean nothing changed. start_date and end_date are UTC days (not the account's time zone): a change is in the window when its changeDatetimeUtc falls on those days. Each event's changeDatetime is Google's own account-local time with no offset; changeDatetimeUtc is the same instant in UTC. Changes take a few minutes to appear. For CAMPAIGN_CRITERION events, use the description field as the definitive interpretation when present. Paginated: when pagination.nextCursor is present, call again with the same parameters plus cursor=<nextCursor>, and repeat until it is absent to get every change in the window.

Read-onlyIdempotentOpen-world

Usage

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "google_ads_get_activities",
    "arguments": {
      "customer_id": "1234567890",
      "reason": "Review recent account changes"
    }
  }
}

Parameters

NameTypeRequiredDescription
customer_id string Required The Google Ads Customer ID (10 digits, with or without dashes)maxLength: 20, pattern: ^[\d-]+$
reason string Required Why this tool call is neededminLength: 1, maxLength: 500
Optional parameters (9)
NameTypeRequiredDescription
login_customer_id string Optional MCC (Manager) Customer ID; required for managed accountsmaxLength: 20, pattern: ^[\d-]+$
start_date string Optional Start date in YYYY-MM-DD format, a UTC day (not the account's time zone): events are matched on changeDatetimeUtc. Defaults to 7 days ago. History is archived for 25 months, beyond Google's own 30-day limit; coverage.complete_from in the response says how far back it is complete for this account.pattern: ^\d{4}-\d{2}-\d{2}$
end_date string Optional End date in YYYY-MM-DD format, a UTC day (not the account's time zone), inclusive. Defaults to today (UTC).pattern: ^\d{4}-\d{2}-\d{2}$
resource_type string Optional Filter to a specific resource type: AD, AD_GROUP, AD_GROUP_AD, AD_GROUP_CRITERION, CAMPAIGN, CAMPAIGN_BUDGET, CAMPAIGN_CRITERION, ASSET, ASSET_SET
AD AD_GROUP AD_GROUP_AD AD_GROUP_CRITERION CAMPAIGN CAMPAIGN_BUDGET CAMPAIGN_CRITERION ASSET ASSET_SET
asset_ids array Optional Filter to specific asset IDs (numeric). Automatically sets resource_type to ASSET.
limit integer Optional Maximum number of activities to return (1-1000, default 50)min: 1, max: 1000
cursor string Optional Opaque cursor from the previous response's pagination.nextCursor. Pass it with otherwise identical parameters to get the next page; a cursor reused with different filters is rejected. Omit for the first page.
refresh boolean Optional Fetch the latest changes from Google before reading, even if the archive synced in the last 15 minutes. Rarely needed.
connection_id string Optional Optional ID of a specific connection to use for this call. Omit to use the actor's default connection for this network. Call <platform>_list_connections to discover available connection IDs.

Examples

Recent account activity

{
  "customer_id": "1234567890",
  "reason": "Review recent account changes"
}

hopkin google activities get --customer-id 1234567890

Campaign changes only

{
  "customer_id": "1234567890",
  "resource_type": "CAMPAIGN",
  "reason": "See recent campaign edits"
}

hopkin google activities get --customer-id 1234567890 --resource-type CAMPAIGN

Custom date range

{
  "customer_id": "1234567890",
  "start_date": "2026-02-01",
  "end_date": "2026-02-28",
  "reason": "February activity audit"
}

hopkin google activities get --customer-id 1234567890 --start-date 2026-02-01 --end-date 2026-02-28

With MCC login

{
  "customer_id": "1234567890",
  "login_customer_id": "9876543210",
  "reason": "Review changes on managed account"
}

hopkin google activities get --customer-id 1234567890 --login-customer-id 9876543210

Specific asset activity

{
  "customer_id": "1234567890",
  "asset_ids": [
    "123456789",
    "987654321"
  ],
  "reason": "Check recent changes to specific assets"
}

hopkin google activities get --customer-id 1234567890 --asset-ids 123456789,987654321