---
search:
  tags:
    - Ad groups
    - GET
seo:
  description: >-
    Available on: Meta TikTok Google Ads Reference for the GET
    /observe/{advertiserId}/ad-groups/{id} endpoint in the AdCrunch API.
sidebar:
  label: 'Live read: Get one ad group'
  badge: GET
title: 'Live read: Get one ad group'
type: openapi-operation
---
**Available on:** [![Meta](/providers/meta.svg)](https://docs.adcrunch.dev/connect/providers) [![TikTok](/providers/tiktok.svg)](https://docs.adcrunch.dev/connect/providers) [![Google Ads](/providers/gads.svg)](https://docs.adcrunch.dev/connect/providers)

Asks the provider for one ad group now, and gives its payload exactly as the provider sends it.

The keys are the provider’s, and so is the shape. A Meta ad set answers `id`, `name`, `campaign_id`, `status` and its two budget fields; a TikTok ad group answers `adgroup_id`, `budget_mode`, `optimization_goal`, `billing_event` and `placement_type`; a Google Ads ad group answers `id`, `name`, `status` and `campaignId`.

**The payload holds the fields AdCrunch asks the provider for, and no more.** Targeting is outside that set at every provider, so no payload here carries it.

## When there is nothing to give

**`404`** — the provider holds no such ad group on this ad account, the provider has no ad group at all, or your organization does not own the advertiser in the path. They are deliberately not told apart: distinguishing them would confirm that a ad group exists to somebody who cannot read it.

`GET /observe/{advertiserId}/ad-groups/{id}`