---
title: "Estimate audience overlap between Meta ad sets from synced targeting (shared custom audiences + age/gender/geo/interests)"
method: POST
path: "/api/v1/estimate_meta_audience_overlap"
tags: ["Ads"]
---

# Estimate audience overlap between Meta ad sets from synced targeting (shared custom audiences + age/gender/geo/interests)

`POST /api/v1/estimate_meta_audience_overlap`

## Request

- Base URL: `https://api.pymaia.com`
- URL: `https://api.pymaia.com/api/v1/estimate_meta_audience_overlap`
- Auth: HTTP bearer

Estimate audience overlap between Meta ad sets from synced targeting (shared custom audiences + age/gender/geo/interests). Flags ad sets competing for the same people (self-competition → inflated CPM, slow learning). NOT Meta's real overlap % (not exposed via API); a targeting-based estimate. Returns the ad set pairs with highest overlap.

## Request body

- object
  - `days` number: Window of days to take ad sets with recent activity
  - `min_overlap` number: 0-1 threshold to report a pair

## Response `200`

Tool executed successfully

- object
  - `ok` boolean
  - `result` unknown
  - `duration_ms` number

## Other responses

- `400`: Invalid params or handler error
- `401`: Missing or invalid Bearer token
- `403`: Missing required scope(s) (`denied_scope`), or the tool's module is disabled for the organization (`module_disabled`, with `why`, `fix` and `module`)
- `404`: Tool not found, internal-only, or excluded for OAuth connectors
- `429`: Rate limit exceeded

---

[API](https://skmtc.dev/pymaia/apis/pymaia-api.md) · [All operations](https://skmtc.dev/pymaia/apis/pymaia-api/llms.txt) · [OpenAPI document](https://skmtc.dev/pymaia/apis/pymaia-api/revisions/d0c98499e173?raw)