Issues / #80
Build Google Ads connector (read mode)
proposed
feature
Priority: high
Project: nimsforest2
Reporter: cederik
26 Mar 2026 16:13
Description
## Context
Required for the Growth Engine Sprint offer. Most prospects in the SME segment use Google Ads alongside Meta.
## Requirements
- Read-only connector to Google Ads API
- Extract: campaign performance, ad spend, impressions, clicks, conversions, search terms, audience segments
- Privacy controls: deterministic extraction — configure exactly which fields come in
- Profile data available (unlike Meta, Google does not restrict as heavily on sensitive topics)
- Data flows into NimsForest as a River source
## First customer: Salix
- Luxury rehab clinic spending ~€1-1.5K/month on Google Ads
- Profile data IS available from Google (unlike Meta where addiction keyword triggers restrictions)
- Need campaign performance + search term data for persona refinement
## Architecture
Follows NimsForest data flow: Source → River → Tree → Wind
- Google Ads API as Source
- River carries raw campaign data
- Tree transforms into organisational context
- Wind publishes to nims (especially Nudge/marketing nim)
## Related
- Google Workspace connector already exists (nimsforestgoogleworkspace)
- OAuth2 flow via iamnim already built — can reuse for Google Ads auth
Required for the Growth Engine Sprint offer. Most prospects in the SME segment use Google Ads alongside Meta.
## Requirements
- Read-only connector to Google Ads API
- Extract: campaign performance, ad spend, impressions, clicks, conversions, search terms, audience segments
- Privacy controls: deterministic extraction — configure exactly which fields come in
- Profile data available (unlike Meta, Google does not restrict as heavily on sensitive topics)
- Data flows into NimsForest as a River source
## First customer: Salix
- Luxury rehab clinic spending ~€1-1.5K/month on Google Ads
- Profile data IS available from Google (unlike Meta where addiction keyword triggers restrictions)
- Need campaign performance + search term data for persona refinement
## Architecture
Follows NimsForest data flow: Source → River → Tree → Wind
- Google Ads API as Source
- River carries raw campaign data
- Tree transforms into organisational context
- Wind publishes to nims (especially Nudge/marketing nim)
## Related
- Google Workspace connector already exists (nimsforestgoogleworkspace)
- OAuth2 flow via iamnim already built — can reuse for Google Ads auth
Comments (1)
nebula
26 Mar 2026 16:16
Grooming: set priority to high
Nebula's reasoning: Required for the Salix POC (#78). Google Ads is the complementary channel to Meta for most SME prospects. For Salix specifically, Google provides profile data that Meta restricts — making this connector critical for persona refinement. OAuth2 infrastructure already exists via iamnim, which reduces implementation risk.
Nebula's reasoning: Required for the Salix POC (#78). Google Ads is the complementary channel to Meta for most SME prospects. For Salix specifically, Google provides profile data that Meta restricts — making this connector critical for persona refinement. OAuth2 infrastructure already exists via iamnim, which reduces implementation risk.