▸Example Amplitude call (the "before")
import { Amplitude } from '@amplitude/analytics-react-native';
await Amplitude.init('YOUR_API_KEY', userId, {
trackingOptions: { ipAddress: true, language: true, platform: true },
});
await Amplitude.identify({
email: email,
plan: 'pro',
});
await Amplitude.track('Paywall Purchase', { value: 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 Amplitude cleanly
-
1
Remove the Amplitude SDK from your build (CocoaPods / SPM / Gradle / npm / pub)
-
2
Remove
Amplitude.initialize(...)andtrack(...)call sites — replace withRespectlytics.configure()andRespectlytics.track("event_name") -
3
Audit for
Identifyoperation usage — those set per-user properties; remove them -
4
If you used Amplitude Experiment for feature flags, plan a separate migration (e.g., GrowthBook or LaunchDarkly) — Respectlytics is analytics, not flagging
-
5
Confirm IDFA / AAID surfaces in your Info.plist + AndroidManifest are no longer needed by other SDKs before removing them
⇋Amplitude vs Respectlytics — 5-field event schema
| Amplitude | 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.