Skip to content
← All channels

Developer

Channel API for the networks not listed here.

Not every network is on this site, and regional or vertical channels matter to the businesses that run them. The Channel API is the same adapter interface every listed channel already uses. You implement the operations your network supports and declare the ones it does not, and the Growth Brain plans around that declaration. Capabilities differ per network, and the Control Plane does not pretend otherwise.

What Channel API does well

Every network has something it does better than a generic integration could: its own auction, its own audience graph, its own creative formats. The adapter interface is deliberately thin so those strengths stay with the network instead of being flattened into a lowest common denominator.

What the Growth Brain adds

  • A declared capability matrix per adapter: which objects can be read, which can be written, and which are read-only.
  • Allocation includes a custom channel only for the decisions its adapter actually supports, and the report says which were unavailable.
  • Conversion events, audience pushes and creative payloads are mapped through your CRM and finance connections like any other channel.
  • Unsupported operations return an explicit unsupported response that surfaces in the interface rather than failing silently.
  • Campaign Constitution limits apply to a custom adapter identically: spend caps, approvals, logging and reversibility.

A custom adapter reports whatever its network reports; the attribution service, your CRM and your finance system stay independent of it, so a new channel is measured the same way Google is on its first day.

Managed objects

What is coordinated on Channel API

  • Campaign and budget objects mapped to the adapter schema
  • Conversion event uploads with deduplication keys
  • Audience list pushes and suppression lists
  • Creative payloads in the network's own format
  • Capability declarations and unsupported-operation reports

One action, in full

The model plans an allocation review across every connected channel, reads each adapter's capability declaration first, and leaves a custom channel out of audience-level decisions because that adapter declares audience writes unsupported. It still includes the channel in budget allocation, and states on the recommendation which decisions were unavailable and why.

Demo data

Platform truth vs business truth

Ranked by platform ROAS, Google wins and LinkedIn is last. Ranked by margin, that order is exactly reversed. Neither column is wrong — they answer different questions, which is why the product refuses to collapse them into one score.

CampaignPlatformAttributedMargin
PMax — Annual plansGoogle5.1× (highest)3.8×2.7×
Prospecting — ES/DEMeta3.4×4.6×3.9×
Video — FoundersTikTok2.1×3.2×2.8×
ABM — Mid-marketLinkedIn1.8×3.7×4.1× (highest)

Adapters

What each network actually permits.

Capabilities differ, and the adapters say so rather than forcing a parity that does not exist.

Adapter capabilities

CapabilityGoogleMetaTikTokLinkedInMicrosoft
Create and update campaignssupportedsupportedsupportedsupportedsupported
Budget changessupportedsupportedsupportedsupportedsupported
Creative uploadsupportedsupportedsupportedsupportedsupported
Server-side conversionssupportedsupportedsupportedsupportedsupported
Conversion adjustmentssupportedsupportednot supportednot supportedsupported
Customer-list audiencessupportedsupportedsupportedsupportedsupported
Offline outcome importsupportedsupportednot supportedsupportedsupported

Capabilities differ per network and the adapters say so rather than pretending otherwise. Forcing false parity is how an integration page becomes a support ticket.

One goal. Every channel. Real business truth.

Connect your ad accounts, say what a good customer is worth, and let the Growth Brain work the objective inside limits you set.

No ad spend commitment · Connect one channel to start · [email protected]