List Google Ads top asset combinations

Changed on

<Info>This API is in beta. Endpoints, fields, and behavior may still change, so avoid depending on it in production.</Info>

Returns the asset combinations Google Ads served most often in the account's Performance Max campaigns, so you can see which creative it actually pairs together.

At most 100 combinations come back and there is no paging.

The read is best-effort: when Google Ads is unavailable you get an empty list under a 200 rather than an error, so an empty list does not prove the account has no combinations.

<Note>Performance Max campaigns only. An account without one returns an empty list.</Note>

<Note>This endpoint accepts a personal API key. Workspace API keys are not authorized for it and are rejected with a 403.</Note>

get/api/apps/{app_id}/google-ads/analytics/asset-group-top-combinations

Request

  • Base URL: https://app.base44.com
  • URL: https://app.base44.com/api/apps/{app_id}/google-ads/analytics/asset-group-top-combinations
  • Auth: HTTP bearer

Path parameters

app_idstring required

ID of the app whose Google Ads reporting you want to read.

Response

Up to 100 combinations.

asset_groupstring required

Name of the asset group the combination belongs to.

asset_group_idstring required

ID of that asset group, matching asset_group_id on List asset performance.

campaignstring required

Name of the campaign the asset group belongs to.

assetsstring[] required

The assets in the combination, each as its text or its Google Ads name. An asset Base44 could not label falls back to its resource name.

Example response

[
  {
    "asset_group": "Spring sale - Asset Group",
    "asset_group_id": "9988776655",
    "campaign": "Spring sale - Performance Max",
    "assets": [
      "Handmade oak furniture",
      "Free delivery across Germany",
      "spring-hero-1200x628"
    ]
  }
]

Changes

    • info

      the security scope read_only was added to the endpoint's security scheme PersonalAccessTokenAuth

    • info

      the security scope full_access was removed from the endpoint's security scheme PersonalAccessTokenAuth

    • info

      the endpoint scheme security PersonalAccessTokenAuth was added to the API