Favikon API - Campaign Enrichment

Every creator campaign has one step that quietly costs more than the rest combined, and it is never the creative.

It is enrichment: turning a list of names into records complete enough to act on. Campaign Enrichment API is coming to Pro and Enterprise. This page is about the problem it sits in front of, so you can tell us whether your version of it matches.

Where campaigns actually lose time

Ask a team where their creator campaign time goes and they will say sourcing or negotiation. Watch the calendar and it goes somewhere else.

• Filling in the gaps. A shortlist arrives with handles and follower counts. What it needs is contact paths, audience geography, posting language, category conflicts and a current price expectation. Somebody assembles that by hand, creator by creator.
• Re-checking what went stale. The records were accurate when they were gathered. Whether they are accurate now is a separate question that nobody has time to ask, so it gets assumed.
• Reconciling two systems. Creator records live in one place, campaign performance in another. The join is a person with a spreadsheet, and that person is the bottleneck every reporting cycle.

None of that is strategic work. All of it has to happen before the strategic work can start.

What we are trying to get right

Two things, because they are the ones teams tell us break first.

Freshness you can reason about. Enriched data without a timestamp is a guess wearing a suit. Any record should tell you when it was last verified, so you can decide whether to trust it rather than discovering the answer mid-campaign.

Stable identity. Creators change handles, change platforms, and change how they describe themselves. A record you stored last quarter needs to still resolve to the same person this quarter, or your historical campaign data quietly detaches from the people it describes.

Tell us your version

The scope of the first release is not locked, and that is deliberate. If campaign enrichment is a real cost centre for your team, the most useful thing you can do is describe how it breaks for you specifically: which fields you assemble by hand, how often you re-check them, and where the join to your own data fails.

Teams that describe a concrete workflow shape what ships first.

In the meantime, enrichment and contact workflows already run inside the Favikon app, and the Favikon MCP exposes them to Claude, ChatGPT and MCP-capable coding agents on the Free Trial, Pro and Enterprise plans.