Start on the Free plan and scale as you grow. Every plan includes AI-powered product insights.
Good for testing SignalFox
For growing mobile apps
For teams and high-volume apps
| Feature | Free | Basic | Pro |
|---|---|---|---|
| Apps | 1 | Up to 5 | Unlimited |
| Monthly tracked users | 10K | 50K | 100K |
| Monthly events | 300K | 3M | 10M |
| Data retention | 30 days | 180 days | Unlimited |
| AI credits/month | 250 | 5,000 | 15,000 |
| Structure Map | |||
| Flows & Funnels | |||
| Monetization tracking | |||
| Drop-off analysis | |||
| AI Insights | |||
| Support | Community | Priority |
An event is any product signal collected by SignalFox, such as a screen view, navigation change, lifecycle event, session event, button press, modal view, purchase event, flow step, subview, or custom tracked interaction. Many common events are collected automatically through the SDK and integrations, while more specific product moments can be tracked manually when needed.
No. SignalFox automatically tracks session and lifecycle events. Navigation and purchases can also be tracked automatically using ready-made integrations for React Navigation, Expo Router, react-native-iap, and RevenueCat. You only need to enable the integrations during SDK initialization.
For buttons, modals, and important UI elements, you can usually add a signalFoxNodeId prop to the component. This gives SignalFox a stable product identifier so it can connect user interactions to your app structure and keep analytics meaningful across versions.
For more specific product moments — such as onboarding steps inside a screen, custom funnel steps, subviews, or non-standard interactions — SignalFox provides dedicated manual tracking methods. This lets you add extra context only where it actually matters.
AI credits are used when SignalFox generates intelligent analysis from your usage data, such as funnel suggestions, drop-off insights, monetization opportunities, structure observations, or recommendations about what to investigate first. Regular event collection does not consume AI credits.
SignalFox is currently focused on React Native because the SDK integrates closely with navigation, app lifecycle, screens, mobile purchases, and common React Native patterns. Support for other platforms may be added later, but the current product is optimized for React Native apps.
Traditional analytics tools are usually event-first: they show charts based on the events you manually define. SignalFox is product-structure-first: it connects screens, flows, modals, actions, purchases, and drop-offs into a living map of how your app is actually used. The goal is not just to store events, but to help you understand behavior and decide what to improve.
Yes. SignalFox can track purchase starts, completed purchases, revenue, and purchase origins. Purchase tracking can be integrated with react-native-iap or RevenueCat, helping you understand which screens, flows, or actions lead users toward monetization — and where they drop off before completing a purchase.
SignalFox will notify you when your usage approaches or exceeds your plan limits. The exact behavior may depend on your plan and account status, but the goal is to avoid surprises and give you time to upgrade or adjust usage before important data is affected.
Yes. You can upgrade or downgrade your plan as your app grows. Higher plans increase limits such as monthly events, tracked users, apps, data retention, and AI credits.
Yes. SignalFox includes a free plan so you can integrate the SDK, test the dashboard, and start collecting real usage data before upgrading. Paid plans are designed for apps with higher traffic, longer retention needs, and more frequent AI analysis.
Not necessarily. SignalFox can work alongside tools like Firebase or Mixpanel. The difference is that SignalFox focuses on product observability: structure, flows, drop-offs, monetization paths, and AI-powered insights. You can use it as your main product analytics layer or as a complementary tool for deeper product understanding.
Start with our free plan. No credit card required.