FAQ
Frequently asked questions about SmartAppPush.
How does SmartAppPush send notifications?
SmartAppPush orchestrates delivery through your existing push provider (Firebase FCM or OneSignal). We don't replace your provider — we add intelligence on top: behavior triggers, targeting, localization, rotation, and analytics.
What events can I use as triggers?
Any event your mobile app tracks. Common examples: app_open, purchase, cart_abandoned, level_complete, signup. You can also define custom events with parameters (strings, numbers, booleans) for precise targeting.
How does language matching work?
Each user's device reports a locale (e.g., 'de' for German, 'ja' for Japanese). When a campaign fires, SmartAppPush checks if a localization exists for that locale. If yes, it sends that version. If not, it falls back to the app's default language.
What happens if a user has push notifications disabled?
SmartAppPush checks the user's push-enabled status before sending. If push is disabled on the device, the notification is skipped (not counted as a delivery failure). Your analytics will show the push-enabled rate for your audience.
Can I switch from Firebase to OneSignal (or vice versa)?
Yes. Your campaigns, targeting rules, and analytics are provider-agnostic. Change your provider credentials in Settings and everything continues to work.
How do cooldowns work with message rotation?
When a campaign has multiple message variants and a cooldown of (e.g.) 1 day: the user receives Variant 1, then waits 1 day, then receives Variant 2, and so on. After the last variant, the cycle restarts from Variant 1.
Is there a rate limit on API calls?
Yes. The Developer Push API allows 100 requests per second per IP. Event tracking and push open tracking endpoints allow 10 requests per second per IP. These are per-endpoint limits, not per-plan. For high-volume sends, use campaigns instead of the Developer API.
Where is my data stored?
Your data is fully isolated per organization — no cross-account access. Encrypted in transit and at rest. GDPR-friendly by design. SOC 2 compliance on the roadmap.