---
search:
  tags:
    - Campaigns
    - GET
seo:
  description: >-
    Available on: Meta TikTok Google Ads Reference for the GET
    /observe/{advertiserId}/campaigns/{id} endpoint in the AdCrunch API.
sidebar:
  label: 'Live read: Get one campaign'
  badge: GET
title: 'Live read: Get one campaign'
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 campaign now, and gives its payload exactly as the provider sends it. This is the escape hatch from the normalized fields.

The keys are the provider’s. A Meta campaign answers `id`, `name`, `objective`, `daily_budget` and `lifetime_budget`; a TikTok campaign answers `campaign_id`, `campaign_name`, `objective_type`, `budget_mode` and `budget_optimize_on`; a Google Ads campaign answers `id`, `name`, `status`, `budgetAmountMicros` and `budgetTotalAmountMicros`.

**The payload holds the fields AdCrunch asks the provider for, and no more.** It is not everything the provider knows about the campaign: a bid strategy, a spending limit and a schedule are outside the set AdCrunch reads, so they are in no payload here.

## When there is nothing to give

**`404`** — the provider holds no such campaign on this ad account, the provider has no campaign 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 campaign exists to somebody who cannot read it.

`GET /observe/{advertiserId}/campaigns/{id}`