Kit + Go Fig
Connect Kit (formerly ConvertKit) to Go Fig for creator-focused email marketing analytics.
Kit (formerly ConvertKit) is the email system most creator-led and education businesses run on, newsletters, digital product launches, course funnels, sponsorship flights. The native reports cover open and click rate but stop short of the questions finance actually cares about: revenue per subscriber by acquisition source, sponsorship yield per broadcast, list-decay economics, and true cost-per-acquired-customer across paid and organic channels. Go Fig connects to Kit's v4 API, pulls subscribers, tags, sequences, broadcasts, and commerce events into your Financial Intelligence Graph, and joins them to Stripe, accounting data, and ad spend so Celeste can run the segmentation and revenue-attribution work that Kit's dashboards cannot.
Key facts
- API version
- Kit v4 (legacy v3 supported)
- Auth
- OAuth 2.0 or API secret
- Sync grain
- Subscriber and broadcast-event level
- Commerce
- Kit Commerce purchases deduped against Stripe
- Refresh cadence
- Hourly for subscribers, 3h for engagement
What you can do with Kit data in Go Fig
Revenue per subscriber by acquisition source
Join Kit subscriber acquisition tags (lead magnet, referral source, paid campaign) to Stripe or Shopify revenue so you know which entry points produce subscribers who actually buy.
Broadcast and sequence yield
Measure revenue attributable to specific broadcasts and automated sequences, not just opens and clicks. Finance can finally answer 'what did last week's newsletter make?' with a real number.
Sponsorship and list economics
Combine subscriber count, engagement rate, and cost-per-acquisition data to price sponsorships, model list decay, and size the real profit contribution of the email business line.
Data available from Kit
Go Fig extracts and normalizes the following data from your Kit account:
How to connect Kit
Authorize Go Fig in Kit
From Go Fig, click Connect Kit. For team accounts, choose OAuth and approve read access in Kit's authorization prompt. Solo creators can paste an API secret from Kit Settings instead. The connection is scoped to one Kit account; agencies connect each client account separately.
Select tags and forms to treat as acquisition sources
Most Kit workflows rely on tags to mark where a subscriber came from (a specific lead magnet, a referral partner, a paid funnel). In Go Fig, pick the tags and forms that represent acquisition events, these become the dimension used downstream for revenue-per-source analysis.
Connect revenue systems
If Stripe, Shopify, or QuickBooks is already connected, Go Fig auto-matches Kit subscribers to customers on email. If you use Kit Commerce directly, purchase events sync as their own table. This is the join that turns Kit reporting into revenue reporting.
Wire up the starter flows
Celeste ships flows for revenue per subscriber by source, broadcast-level revenue attribution, and list-decay modeling. They land populated on first sync and are the baseline creators and finance leads typically customize from.
Authentication: OAuth 2.0 or Kit API Secret (v4 API). OAuth is recommended for agencies and team accounts because permissions are scoped and the token can be revoked per-integration. Solo creators typically use the API secret, which is rotatable from the Kit account page.
Common Questions About Kit Integration
Does Go Fig support Kit's v3 (legacy) or v4 API?
Both, with v4 as the default. The v4 API exposes richer subscriber and commerce data and supports OAuth properly. Accounts still on v3 can connect via API key, but we recommend migrating to v4 for new integrations because Kit is freezing v3 feature development.
How are Kit Commerce purchases reconciled with Stripe?
Kit Commerce runs on Stripe under the hood. Go Fig deduplicates by joining Kit purchase events to Stripe charges on the transaction ID, so you do not end up double-counting revenue. Refunds and failed charges are handled identically, the canonical revenue view pulls from Stripe with Kit context attached rather than Kit with Stripe context bolted on.
Can Go Fig handle high-volume accounts (100K+ subscribers)?
Yes. Kit's API rate limits at 120 requests per minute. Go Fig paginates at the maximum page size and uses incremental sync anchored on the subscriber updated_at field so a 500K-subscriber account stays well under the limit. First backfill on a large account typically completes in under two hours.
What about sponsorship tracking?
Kit does not have a native sponsorship object. Most creators encode sponsorships in the broadcast subject line or as a tag. Go Fig lets you define a sponsorship rule (tag matches, subject-line regex, or custom field) and materializes a sponsorships table on top of the raw broadcast data. That table drives the per-sponsor and per-flight revenue reporting that Kit cannot produce on its own.
How current is Kit data inside Go Fig?
Hourly incremental sync for subscribers, tags, and purchase events. Broadcast engagement metrics (opens and clicks) refresh every three hours because Kit rolls up engagement server-side. Full reindex runs nightly to catch retroactive tag changes and unsubscribes.
Related Marketing integrations
Other systems Go Fig connects into the Financial Intelligence Graph, often alongside Kit.
