Replace GameAnalytics: 5-field schema

Q: 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.

Q: 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.

▸Example GameAnalytics call (the "before")

swift Respectlytics

import GameAnalytics

GameAnalytics.configureBuild("1.0.0")
GameAnalytics.initialize(withGameKey: "YOUR_KEY", gameSecret: "YOUR_SECRET")

GameAnalytics.addProgressionEvent(
    withProgressionStatus: GAProgressionStatusComplete,
    progression01: "world_1",
    progression02: "level_5",
    score: 1200
)
GameAnalytics.addBusinessEvent(
    withCurrency: "USD",
    amount: Int32(priceInCents),
    itemType: "iap",
    itemId: sku,
    cartType: "main_paywall"
)

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 GameAnalytics cleanly

1
Remove pod 'GameAnalytics' from Podfile
2
Remove implementation 'com.gameanalytics.sdk:gameanalytics-android-sdk:...' from build.gradle
3
Remove GameAnalytics.initialize(...) and GameAnalytics.addBusinessEvent(...) call sites
4
Replace progression and resource event call sites with Respectlytics.track("event_name") using distinct event names per level / resource type
5
If you used GameAnalytics's benchmark comparisons as a product KPI, plan how you'll source those numbers post-migration

⇋GameAnalytics vs Respectlytics — 5-field event schema

	GameAnalytics	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.

⇢Related migration guides

Replace GameAnalytics with a strict 5-field event schema