Issues / #79
Build Meta Ads connector (read mode)
proposed
feature
Priority: high
Project: nimsforest2
Reporter: cederik
26 Mar 2026 16:12
Description
## Context
Required for the Growth Engine Sprint offer. Every prospect in this segment uses Meta Ads.
## Requirements
- Read-only connector to Meta Ads API
- Extract: campaign performance, ad spend, impressions, clicks, conversions, audience data
- Privacy controls: deterministic extraction — configure exactly which fields come in
- No PII by default (important for sensitive industries like healthcare/addiction)
- Data flows into NimsForest as a River source
## First customer: Salix
- Luxury rehab clinic spending ~€1-1.5K/month on Meta
- Addiction content triggers Meta privacy restrictions ("addiction" keyword)
- Some profile data anonymised by Meta already
- Need aggregate campaign performance, not individual user profiles
## Architecture
Follows NimsForest data flow: Source → River → Tree → Wind
- Meta Ads API as Source
- River carries raw campaign data
- Tree transforms into organisational context
- Wind publishes to nims (especially Nudge/marketing nim)
Required for the Growth Engine Sprint offer. Every prospect in this segment uses Meta Ads.
## Requirements
- Read-only connector to Meta Ads API
- Extract: campaign performance, ad spend, impressions, clicks, conversions, audience data
- Privacy controls: deterministic extraction — configure exactly which fields come in
- No PII by default (important for sensitive industries like healthcare/addiction)
- Data flows into NimsForest as a River source
## First customer: Salix
- Luxury rehab clinic spending ~€1-1.5K/month on Meta
- Addiction content triggers Meta privacy restrictions ("addiction" keyword)
- Some profile data anonymised by Meta already
- Need aggregate campaign performance, not individual user profiles
## Architecture
Follows NimsForest data flow: Source → River → Tree → Wind
- Meta Ads API as Source
- River carries raw campaign data
- Tree transforms into organisational context
- Wind publishes to nims (especially Nudge/marketing nim)
Comments (1)
nebula
26 Mar 2026 16:16
Grooming: set priority to high
Nebula's reasoning: Every prospect in the Growth Engine Sprint segment uses Meta Ads — this is the most universal connector of the three. Required for the Salix POC (#78) and every future sprint engagement. Privacy restrictions around addiction keywords make this connector's deterministic extraction design especially important for the first customer.
Nebula's reasoning: Every prospect in the Growth Engine Sprint segment uses Meta Ads — this is the most universal connector of the three. Required for the Salix POC (#78) and every future sprint engagement. Privacy restrictions around addiction keywords make this connector's deterministic extraction design especially important for the first customer.