Skip to main content

Full meta category browsing

Please add a typed endpoint backed by Meta’s targeting browse capability, using the existing connected ad account. We need category names, selectable Meta IDs, parent/child relationships or category paths, and pagination where applicable. Please distinguish selectable targeting entities from organizational category nodes.

Status: Completed1 comment

Log in to comment and vote

Comments1

  • Miquel Palet López

    Team•

    Oct 9

    This is live: GET /v1/ads/targeting/browse returns Meta's targeting category tree for a connected ad account.

    Request: GET /v1/ads/targeting/browse?accountId=<your Meta ads connection id>&adAccountId=act_<id>. Optional filters: type (e.g. interests, behaviors, income, life_events, industries, education_statuses, relationship_statuses, family_statuses), parentNodeId (returns every descendant of that branch) and selectable=true|false.

    Each node has nodeId, parentNodeId, name, path (array of ancestor names), type, id (the Meta targeting id), selectable, plus description and audienceSizeLowerBound / audienceSizeUpperBound when Meta provides them.

    Selectable vs organizational: selectable: true nodes carry a Meta id you can put in a targeting spec. Organizational category nodes (e.g. Demographics > Financial > Income) have id: null and selectable: false. A few typed groups (Schools, Employers, Job titles, Fields of study) are only reachable through search on Meta's side, so they appear as non-selectable nodes; use GET /v1/ads/targeting/search for those.

    Pagination: Meta returns the whole catalog in a single response with no cursor, so there is no pagination; narrow it with type, parentNodeId or selectable instead. Results are cached for an hour per ad account.

    Note that the interests branch is Meta's curated browse list, not every interest Meta can target; keyword search still covers the long tail. Full schema and an example are in the API reference under browseAdTargeting.