βΈExample Flurry call (the "before")
import Flurry_iOS_SDK
let builder = FlurrySessionBuilder.init()
.withAppVersion("1.0")
.withLogLevel(FlurryLogLevelAll)
.withCrashReporting(true)
Flurry.startSession(apiKey: "YOUR_FLURRY_KEY", sessionBuilder: builder)
Flurry.log(eventName: "Purchase", parameters: [
"user_id": userId,
"value": String(price),
"currency": "USD",
])Most analytics SDKs accept dozens of custom parameters per event. Respectlytics's API stores exactly five fields per event: event_name, session_id (rotated every two hours), timestamp, platform, and country. Extra fields are rejected with a 400. The discipline is structural β engineers can't accidentally add PII over time because the API refuses it.
βRemove Flurry cleanly
-
1
Remove
pod 'Flurry-iOS-SDK/FlurrySDK'fromPodfile -
2
Remove
implementation 'com.flurry.android:analytics:...'frombuild.gradle -
3
Remove
react-native-flurry-analyticsfrompackage.jsonif used -
4
Remove
Flurry.builder().build(...)initialisation andFlurry.logEvent(...)call sites -
5
If you used Flurry's Configuration Provider for remote config, plan a separate migration (e.g., Firebase Remote Config, GrowthBook)
-
6
Delete the Flurry app entry once events stop flowing (the dashboard may already be sunset by the time you migrate)
βFlurry vs Respectlytics β 5-field event schema
| Flurry | Respectlytics | |
|---|---|---|
| Stored fields per event | β see tool note above (typically dozens of params) | Exactly 5 |
| API enforcement of schema | Lenient (extras stored) | Strict (extras rejected with 400) |
| Per-user state computable | Yes (people profiles, user properties) | No (use account system) |
| Custom event properties accepted | 25β250 depending on tool | 0 |
βFrequently asked questions
How do we segment events without custom properties?
By using distinct event names. Instead of track('purchase', { product: 'gold_pack' }), fire track('purchase_gold_pack'). The aggregation buckets event names automatically; no manual configuration. Keep your taxonomy short (under ~50 distinct names per matrix axis) to stay navigable.
We need per-event price for revenue reporting β how does that work?
It doesn't β and that's the point. Authoritative revenue lives in your billing system (Stripe, RevenueCat, App Store Connect) with refund-aware totals and currency-conversion handling. Mirroring revenue into product analytics produces two truths that drift over time.
What if we genuinely need a sixth field for legitimate reasons?
Three options: (a) encode the variant into the event name (e.g., paywall_purchase_pro vs paywall_purchase_basic); (b) keep per-user state in your account system and don't mirror it; (c) use a different tool for the specific use case. Most product teams find (a) or (b) sufficient.
How does the API actually enforce this?
JSON validation at the API gateway. A POST /api/v1/events/ with any field outside the 5 allowed keys returns HTTP 400 Bad Request with a body listing the rejected field names. Your integration test catches the regression on the first commit that adds an extra field.