Integrations — which connections went quietOwner: PRODUCT (Receipt) — and Receipt-unique. Receipt is the attribution product: its integrations are where the numbers come from, so a quiet connection means silently wrong attribution — which is why stale is a first-class state here, not a footnote.
Scope (§17): every row acts on ONE creator’s connection to ONE external service. Re-sync routes via the Receipt API; nothing here touches Folo or FG state — the first-party rows are Receipt’s READ of those platforms.
Operator test: the ONE question this page answers is “which connections are stale?” — and the one action is re-syncing them.
Scope (§17): every row acts on ONE creator’s connection to ONE external service. Re-sync routes via the Receipt API; nothing here touches Folo or FG state — the first-party rows are Receipt’s READ of those platforms.
Operator test: the ONE question this page answers is “which connections are stale?” — and the one action is re-syncing them.
Connected, available and stale connections across creators — and the re-sync that wakes them up.
Live · Receipt DBDemo figures
Connected
4
across 1 creator · 5 connections total
DEMO DATA (walk capture) · source: connections tableAvailable
1
offered, never connected — gumroad
DEMO DATA · source: integration catalogStale
4
every connected row · connected but no sync in 7d+
DEMO DATA · stale = connected-no-sync-7d+ · the page’s reason to existSoon
0
announced, not yet offered
DEMO DATA · source: integration catalogConnections
One row per creator × service. Last sync is the health signal — 7 days quiet turns the row stale.
S
Stripe · @demopayments · connected · last sync 9w ago
Sh
Shopify · @democommerce · connected · last sync 9w ago
F
Fanogram · @demofirst-party · connected · last sync 9w ago · feeds FG Tracking via Growth
Fo
Folo · @demofirst-party · connected · last sync 9w ago
G
Gumroad · @democommerce · available — never connected
≡
Write path: re-sync routes via the Receipt API and lands in Receipt’s audit log (same shape as the live webhook.retry rows — actor · action · target · audit-id). Effect: a sync run is queued, never a destructive rebuild — attribution history is append-only, and “every number shows its working.”
Health at a glanceThe fraction-chip pattern, stolen from investors-dibi (walks §14: per-brand “0/2”-style connected-fraction chips). Numerator = fresh connections (synced inside 7d) · denominator = connected. One glance says which lane went quiet.
Fresh ÷ connected, per lane. A full fraction is a healthy lane.
payments 0/1commerce 0/1first-party 0/2@demo 0/4
◎
All zeros is the honest read: every connected row is stale, so every numerator is 0. The chips are meant to hurt a little — that is what makes them work.
Webhook health
Delivery truth lives on its own page — this is the summary.
| Source | Received | Failures |
|---|---|---|
| Stripe | 0 | 0 |
| Shopify | 0 | 0 |