Running a Portfolio Campaign on PLLAY

A platform that runs more than one game can now buy five managed campaigns on PLLAY: Clutch Moment, Achievement Challenge, Portfolio-Wide Weekly Challenge, Sponsored Leaderboard, and Cross-Title Seasonal Network. PLLAY configures and operates each one across the titles in the portfolio. The participation mechanic is the one that already ships on Twitch. The public page is /solutions/gaming-platforms. The product record for the mechanic is /pulse.

Connection today is one of two paths, both provisioned with the PLLAY team. The Server Event API is how a platform's own systems open, collect, and settle an interaction — key authentication, a documented rate limit, and signed webhook delivery. Partner placements are the other path: a themed embed inside the platform's own product. Reward delivery runs on every settlement, and the participation record is written per interaction.

Three surfaces are still not listed on the public offer. A client library in the repo now returns the embed token a launch already mints and can mount the participation component that already ships. The package is not on a public registry, so a platform cannot install it. The overlay path still requires a PLLAY account. A provisioned partner's server can record a choice under the player id it already holds, and that call does not create a PLLAY account. The same key can read how those choices split by option. That response has no player ids and no reward. There is no browser single sign-on, and the public page does not list it. The participation report can be read by a partner who already has a sponsor-portal sign-in for that engagement. PLLAY provisions that sign-in. It is not self-serve, and the public offerings page does not list the report as available.

The operator dashboard and that sponsor portal read the same rollup for one campaign: open, resolved, rewards issued, and held, plus exposure and completed participation. Those counts come from the participation rows, the exposure events, the response rows, and the reward deliveries written on settlement. A game title is not stored on the participation row. The client library is the second surface, and it stays off the public offer until a partner can install it. Partner identity is the third, and it stays off the public offer until a platform's own player is recorded on a live prediction.

None of this is a self-serve console. A portfolio campaign is still configured and operated with the PLLAY team. The developer map of what is live and what is not lives on /developers.