Field notes
Property hygiene for session and entitlement events
Practical rules for keeping server-side session and entitlement properties consistent across connected mobile apps.
Session renewals and entitlement grants are where connected mobile apps quietly accumulate inconsistent properties. One release adds plan_id, the next adds planId, and six months later the warehouse needs a cleanup project.
Prefer stable identifiers
Use the same identifier the billing system uses. Friendly plan names can live in a dimension table; the event itself should carry the durable key. When marketing renames a plan, your historical event map stays intact.
Record who triggered the change
Server-side entitlement events should note whether the change came from user purchase, admin grant, or system migration. Without that discriminator, support teams cannot explain sudden access changes in the app.
Avoid dumping entire payloads
Copying the full API response into an analytics event feels thorough and ages poorly. Select the fields product questions actually require. Everything else belongs in application logs with a retention policy suited to debugging, not in your event map.
Review cadence
After each major app release that touches auth or billing handlers, schedule thirty minutes to compare new properties against the catalogue. Retained mapping support exists precisely for this rhythm.