@kapa.ai I want to fetch demographic data like age and gender from the facebook-marketing connector. Is that possible in the current connector implementation and how would that work?

The knowledge sources do not explicitly mention any fields or endpoints in the Facebook‑Marketing agent connector that expose audience demographic breakdowns (such as age or gender) for insights data. From the docs we have, the connector supports entities like

ads_insights

,

campaigns

,

ad_sets

,

ads

, etc., and you can list or search insights records via the

ads_insights

entity. [[FB‑Mktg entities](https://docs.airbyte.com/ai-agents/connectors/facebook-marketing#full-documentation); [Ads insights search](https://docs.airbyte.com/ai-agents/connectors/facebook-marketing/REFERENCE#ads-insights-search)] However, the provided reference pages only describe generic query/filter parameters and do not enumerate the available metrics/dimensions or show any demographic fields. Because of that, I cannot confirm from these docs that age/gender breakdowns are currently available through this connector, nor how exactly you would specify them (e.g., which field names to use). What we can see is: - You can query

ads_insights

with filters and other conditions, for example:

python   await facebook_marketing.ads_insights.search(       query={"filter": {"eq": {"account_id": "<str>"}}}   )

[[Ads insights search](https://docs.airbyte.com/ai-agents/connectors/facebook-marketing/REFERENCE#ads-insights-search)] - The search API supports operators like

eq

,

neq

,

gt

,

gte

,

lt

,

lte

,

in

,

like

,

fuzzy

,

keyword

,

not

,

and

,

or

, and lets you specify

fields

to include in results. [[Ads insights search](https://docs.airbyte.com/ai-agents/connectors/facebook-marketing/REFERENCE#ads-insights-search)] But the docs here do not list which

fields

are valid for demographics. So, based only on the available knowledge sources: - It is clear you can query

ads_insights

. - It is not documented here whether demographic dimensions like age and gender are exposed, or what their exact field names are. - Therefore I cannot give a reliable, field‑level example for fetching age/gender via this connector. If you have access to the full connector reference outside these excerpts, you’d need to check the

ads_insights

response schema or field list there to see if demographic dimensions are supported and then pass them via the

fields

parameter in your

ads_insights.list

or

ads_insights.search

calls.