Introduction

The PlayOps SDK is a Unity package developed by Tactile Games that connects your game to the PlayOps backend services. It is designed for partner studios who want to instrument their games with analytics and deliver live configuration changes — without building or maintaining their own backend infrastructure.

What’s included

The SDK ships two services out of the box:

Analytics — Log player behaviour events from your Unity game code. Events are defined as plain C# classes decorated with attributes. The SDK batches and flushes them to Tactile’s analytics pipeline. A build processor automatically generates an event schema file that you upload to the PlayOps dashboard so events can be validated and queried.

Remote Configuration — Download and apply JSON configuration from the PlayOps backend at runtime. Configuration is deserialized into strongly-typed C# classes, so you interact with plain objects rather than raw dictionaries. Changes made in the dashboard are delivered to players on their next session without a new app release.

Who this is for

This documentation is written for Unity C# engineers at partner studios integrating PlayOps into a mobile game. You will need:

• Access to your PlayOps credentials (provided by your Tactile integration contact)
• Unity 6000.0 LTS or newer
• Familiarity with Unity’s Package Manager and C# scripting

Using AI to integrate

If you use an AI coding assistant (Claude, ChatGPT, Cursor, Copilot, etc.), you can give it llms.txt — a lightweight index of the SDK documentation with links to each section. The AI can use it as a map to find exactly what it needs.

If your tool doesn’t support fetching URLs, use llms-full.txt instead — the complete SDK documentation compiled into a single file you can paste or attach directly.

Next steps

Follow the Installation guide to set up registry access, then continue to the Quick Start to initialize the SDK.