get_bridge_daily_stats

What it does

Parameters

• source_ad_account_id string required

  The Meta ad account the ads were bridged from (act_…)

  Matches ^(act_)?\d{1,32}$

• since string required

  First day, YYYY-MM-DD

  Matches ^\d{4}-\d{2}-\d{2}$

• until string required

  Last day, YYYY-MM-DD

  Matches ^\d{4}-\d{2}-\d{2}$

Example

Your assistant calls it for you when you ask in your own words. What it sends (MCP tools/call, JSON-RPC 2.0):

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_bridge_daily_stats",
    "arguments": {
      "source_ad_account_id": "act_1234567890",
      "since": "2026-10-01",
      "until": "2026-10-21"
    }
  }
}

The same call over HTTP with an API key, for an MCP client of your own (an assistant that signs in sends its OAuth token instead):

curl -X POST https://app.apogee.ad/mcp \
  -H "Authorization: Bearer $APOGEE_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_bridge_daily_stats","arguments":{"source_ad_account_id":"act_1234567890","since":"2026-10-01","until":"2026-10-21"}}}'

Access and cost

In the REST API

The same thing for your own code, with an API key:

• Get bridge daily stats: GET /bridged-ads/daily-stats

Related tools

Bridge: Ads of one platform launched on another (Meta → TikTok or Snapchat, and back), or a Meta → Meta copy between two ad accounts. Prepared, shown in full, then run after your explicit yes; a plan runs once, within 24 hours.

• prepare_bridge_transfer: Prepares a transfer without transferring anything: the source ads (or a Meta ad set's or campaign's ads), the destination campaign and its existing ad set / ad group / ad squad or a new one copied from a template. Returns the recap and a plan_id; ready: false lists what to ask (a TikTok identity, a Snapchat public profile, a website…), then prepare again with extra_fields. Incompatibilities are listed: your yes accepts them. For a Meta → Meta copy, the destination's fields go in mapping.
• bridge_transfer: Runs a prepared transfer, once, after your explicit yes; the plan is checked again first. Answers with the outcome (completed, partial, failed…) within about 25 seconds, or running. A Meta → Meta copy reuses each ad's post (likes, comments) when Meta lets the destination use it, and copies it as a new post otherwise.
• bridge_transfer_status: Where a transfer is: running, completed, partial (with the failures), failed, not run, or unknown (check the destination before running it again).
• list_bridge_transfers: The ads already bridged from a source ad account, newest first, with where each one went.
• get_bridge_stats: The Bridge's Stats tab: each creative bridged from a Meta ad account, its Meta ad next to its TikTok and Snapchat copies, with their spend and results over the period (7-day click attribution everywhere), each platform in its own currency.