Skip to main content

​
Superwall Paywalls

Many founders run paywalls on Superwall and never connect RevenueCat. The co-founder treats Superwall as a first-class monetization source so those apps are not described as free or “no IAP”.

​
What it reads

After you save a Superwall organization API key in Settings → Data sources and attach Superwall application ids on the app dashboard:
  • Scheduled briefing — proceeds, MRR, and related KPIs for the attached Superwall app only
  • Chat tools — superwall_overview, superwall_dashboard, superwall_chart, superwall_transactions, superwall_campaigns
  • list_integrations — dataConnections.superwall shows whether the org key is connected
Public SDK keys (pk_…) are rejected. The org key is stored in Vault, not in the browser.

​
Scope

Metrics are scoped to Superwall applications attached on the Appeeky product (user_apps.superwall_app_ids). The agent must not copy another product’s Superwall KPIs onto this app. If Superwall is connected but nothing is attached, it should ask you to attach the matching Superwall app — not invent ids.

​
What it cannot do

There is no Superwall write action. Campaign and paywall edits stay in the Superwall dashboard. The agent can open a pricing/paywall hypothesis and tell you what to change there. RevenueCat experiment promotion (revenuecat_experiment) is separate and only applies when RevenueCat is connected. See Monetization Experiments (RevenueCat).

​
Setup

  1. Superwall → Settings → API Keys → organization key
  2. Appeeky → Settings → Data sources → Superwall
  3. App dashboard → attach the Superwall application(s) for that product