Uploading Schemas to the Dashboard

The PlayOps analytics pipeline validates every incoming event against a registered schema. Before your game can send events successfully, you must upload the generated schema file to the dashboard. You must re-upload whenever you add, rename, or remove event classes or properties.

Note

If you do not have access to the PlayOps dashboard, contact your Tactile integration contact to upload the generated schema file on your behalf.

Schema upload workflow — click a step to expand

1🔨 Build & Locate Schema▶

2⬆️ Upload to Dashboard▶

3🔍 Review Diff▶

4✅ Confirm & Publish▶

Breaking changes

Removing a required property or renaming an event is a breaking change. Events that do not match the active schema are rejected by the pipeline. If you need to remove or rename an event, coordinate with your Tactile contact to ensure a smooth transition.

Schema versioning

Every upload creates a new versioned snapshot. Previous versions are retained and can be viewed in the dashboard’s schema history. If a new schema causes unexpected issues, you can roll back to a previous version from the history view.

When to upload

Situation	Upload required?
New event class added	Yes
Existing event: new required property	Yes
Existing event: new optional property	Yes
Existing event: property removed	Yes (breaking change — coordinate with Tactile)
Event class renamed	Yes (breaking change)
Event description or category changed	No — descriptions are informational only
No event class changes in this build	No