Fictura
Apps & keys

Tools

Switch Fictura's optional tools and your third-party services on or off, and set them up right here. A switch that touches your app reaches installed devices on the next config refresh — no code change, no release, no review.

Dashboard → Tools, near the bottom of the sidebar. Everything in Fictura is one of three things:

GroupWhat it meansSwitchOn this page
Core featuresWhat every app gets.NoNo
Fictura toolsOptional, built by Fictura, with no outside account of their own.YesYes
Third-party toolsConnect to an account you own somewhere else.YesYes, with setup on the page

Old links to Setup → Connections land on this page. A switch that touches your app reaches devices that already have it installed, the next time they refresh their config — no code change, no release, no App Review.

Core features

Home, Overview, Events, Actions, Insights, Attribution, Audiences, Issues, Releases, Performance, Paywalls, Placements, Campaigns, Products and Experiments, plus Hawkings and the MCP server.

These are always there, so they have no switch. Each has its own controls where it needs them: a paywall only shows once you set one live, an event can stop recording from Events, and enableErrorCapture: false turns off error capture in the React Native SDK.

Fictura tools

Built by Fictura and marked by Fictura on their cards. There is no outside account to connect, apart from Stripe for Web Checkout.

ToolWhat it doesWhat off does
Cancel SurveyAsks people why they cancelled their trial, in the app. Answers land on your dashboard.The popup stops.
Push NotificationsSends a push to every device that granted permission.Sending stops, scheduled pushes are canceled, and the Push row hides.
LinksTracking links, creators and web-to-app, counted in Attribution.The Links row hides. Live links keep working.
Uptime MonitoringChecks your backend every minute and alerts you when it goes down and comes back.Checks stop.
Web CheckoutSends iOS users to your own hosted checkout. See below.Devices go back to Apple.

Onboarding Flows is not drawn on this page and is not offered to new accounts. It is hidden, not removed: the SDK still receives its key, an app already serving a flow keeps serving it, and /dashboard/onboarding still opens by direct URL.

Third-party tools

Each connects to an account you own. Turning one off keeps your keys, so turning it back on needs no setup.

ToolWhat it doesWhat off doesSidebar row
RevenueCatBilling signal: trials, conversions, renewals and cancels, through your per-app webhook URL.Asks first, then ignores its events. Events sent while off are not kept.—
Paid AcquisitionDaily spend sync, per-campaign ROAS, pause and budget control, AI ad copy. Meta and Apple Ads connect today; Snapchat, TikTok, Google Ads and Reddit are listed as coming soon.The row hides and pulling stops.Paid Ads
Slack AlertsExperiment winners and spend-sync problems in your Slack, through an incoming webhook.Sending stops.—
Email AlertsExperiment winners by email, through your Resend account.Sending stops.—
PostHog ExportEvery growth event mirrored into your own PostHog project.Sending stops.—
StripeYour payments account. Powers Web Checkout.Web Checkout closes. Billing events keep being read, so paying customers are not lost.—
Outgoing WebhooksBilling moments and experiment results POSTed to Zapier, Make or your own endpoint, HMAC-signed.Sending stops.—
App Store ConnectRead and create subscription products from the dashboard.Fictura stops reading from and writing to Apple.—
PostizSocial posts published or scheduled through Postiz, by channel and day.The row hides and pulling stops.Posts
Google Search ConsoleWhat people searched, which pages showed and where they searched from.The row hides and pulling stops.Search
Google Cloud CostsWhat Google Cloud charges you each day, by service.The row hides and pulling stops.Cloud Costs
AppfiguresStore downloads, revenue, ratings and reviews, for Hawkings and your coding agents to read.Pulling stops.—
AppsFlyerBrings your AppsFlyer history into Fictura. You run the import from Setup → Import data.New imports are refused, and a running one is canceled. What's imported stays, and Resume picks up where it stopped.—
LinearTurns an error issue into a Linear ticket from the issue page.Create ticket is refused and Linear leaves the menu. Filed ticket links stay.—
JiraTurns an error issue into a Jira ticket from the issue page.Create ticket is refused and Jira leaves the menu. Filed ticket links stay.—
Amazon S3 ExportsCopies your raw events to your own S3 bucket, hourly or daily. See Amazon S3.Scheduled exports and Run now stop. Missed windows export on their own when it's back on.—
Google PlayReads refunds and chargebacks, so your revenue and affiliate commission stay right. See Google Play.Asks first, then reading stops. Back on, it catches up only 30 days, because that's all Google keeps.—
OneSignalSends pushes that open a specific screen through your own OneSignal account. See Push notifications.Pushes that open a specific screen are refused, sent now or scheduled. Plain pushes still go through Expo.—
TremendousPays your affiliates from your own Tremendous balance. Shown to admins only, like Affiliates. Off by default, because it moves money.Send and Resend are refused. Payouts already sent keep being read, so they still settle.—

Audience Partners (Meta, Google Ads, TikTok and Snapchat) shows as soon with no switch. The code that sends audiences to them isn't built yet, so nothing reaches them today. Accounts stay under Audiences → Connections until it is.

What happens to what you missed:

  • Pulls catch up. When a tool that pulls data comes back on, it fetches the days it missed. Sync now is refused while the tool is off.
  • Alerts are dropped. Slack and email messages, new webhooks and new PostHog events are not sent while off, and switching back on does not replay them.
  • Queued work waits. Webhooks and PostHog batches already queued wait, and go out if you switch back on. A cohort sync waits too, then sends the changes it missed.

A page whose row is hidden still opens by direct URL.

Setting one up

Flip the switch on, and the tool's setup opens right here on the Tools page. Close it without finishing and the switch goes back to off. Once setup is done, the tool is on.

Reading a card

Each card carries the tool's name, one line on what it does, and a switch. Below that:

  • Connect — the same setup the switch opens, on a tool that needs an account and has none yet. The card shows a Not connected yet chip.
  • Manage — the same form once connected, with Disconnect. RevenueCat has nothing to paste in, so its Manage shows the webhook URL to paste into RevenueCat, and it turns on by itself when the first event arrives. Outgoing Webhooks also shows its delivery log.
  • Open — goes to the tool's own page, for the tools that have one.
  • soon — a badge for a tool listed but not built, with no switch. Audience Partners carries it today.

What reaches the SDK

GET /api/v1/sdk/config returns tools as a flat map of 17 keys, each true or false:

paywalls, onboarding, cancel_survey, ab_testing, churn_analytics, event_tracking, revenuecat, paid_acquisition, slack_notifications, email_alerts, push_notifications, posthog_export, stripe, error_tracking, outgoing_webhooks, web_checkout, app_store_connect.

  • Core features always read true. That covers paywalls, ab_testing, churn_analytics, event_tracking and error_tracking.
  • Dashboard-only tools never reach it. Links (links), Uptime Monitoring (uptime_monitoring), Postiz (posts), Google Search Console (search_console), Google Cloud Costs (cloud_costs) and Appfigures (appfigures) only change the dashboard and the server, so adding one cannot change what an installed app receives.
  • Hidden is not the same. onboarding is left off the Tools page and still sent, exactly as before.
  • web_checkout is decided per device. It reads true only when its switch and Stripe's are on, a price or checkout link is saved, and this device passes the country and platform rules.

How a change reaches a phone

Your app asks for its config on launch and periodically after that. The answer includes which tools are on. Nothing is compiled into the build, so a switch you flip now applies to every install already out there, not just to people who update.

Everything here except Web Checkout and Tremendous is on by default. A tool that needs an account starts working as soon as the account is connected, with no second step.

Before your app is active

An app with no subscription can still open Tools, and connecting accounts is part of setting up, so that all works: connect or manage any integration, and configure and switch Web Checkout. Flipping any other switch needs an active subscription; the API answers 402 with subscription_required. Your app keeps sending data and receiving its config either way.

Web Checkout is the exception

Web Checkout is the one tool that is off by default, and deliberately so. It sends iOS users to your own hosted checkout instead of Apple's payment sheet, which is why you keep roughly 27% more of each subscription — and it is also a tool that reroutes money and has tax consequences. Something that moves money should be switched on by a person who has read what it does, never inherited from a default.

It also stays off until Stripe is connected, and closes if Stripe is switched off. A switch that sends people somewhere with nowhere to send them is worse than no switch. Its settings live on Dashboard → Setup → Web checkout (the card's Open link), and devices read it as off until a price or checkout link is saved there, even if the switch here is on.

Web Checkout can additionally be limited by country, decided on our side rather than in your app. The same build sells through your checkout in one market and through Apple in another, and a device whose country we cannot determine falls back to Apple — the safe side of that mistake.

On this page