Prove sponsored engagement in 6–8 weeks.
Launch one paid, measurable PLLAY pilot with a defined integration, audience cohort, campaign scorecard and production decision.
Every PLLAY pilot is a paid, scoped engagement run directly with the PLLAY team — every partner today enters at stage one — a scoped, paid engagement run directly with the pllay team. This page is how you choose the integration pattern, define the scope, and get to a production decision.
Four platform audiences. One pilot process.
Four packages, matched to how you'd actually integrate.
Best for game and web platforms.
partner-api is deployed with key auth, a documented rate limit, and signed, retried webhook delivery. @pllay/sdk v0.1.0 is built and internally tested, but not published to npm — no partner can npm install it today.
Best for gaming clips and recorded content.
All 38 of Vision AI's benchmark trials are recorded video — a clip is the case the resolver is actually validated on.
Best for connected television and video networks.
The underlying QR / second-screen mechanism is live in production — mobile web, no install, is how every fan on PLLAY plays today. A CTV-specific pairing integration has not run against a real CTV surface — today's evidence is the second-screen mechanism, not a shipped CTV product.
Best for large platforms requiring custom identity, security or procurement.
The schema is multi-tenant by design — per-partner credentials and brand configuration — but it has never been exercised by more than one real external partner at a time, so isolation at production scale is unverified. Key-based authentication (Authorization: Bearer pllay_sk_…) is deployed and admin-provisioned per partner.
What's in the box, every time.
The package you choose in §2 sets this — one pattern per pilot, not a bundle.
One surface
Generalizes the CTV-specific criterion of three challenge formats (config/media-ctv.ts) across a wider range for other surfaces.
One reward mechanism configured for the pilot's duration, not the full Rewards & Ledger catalog.
One campaign
The integration runs against real content, with a defined audience and duration, measured against the objective set in stage one. This is the stage PLLAY's Proof Sprint runs today.
6–8 weeks, start to production decision.
- Week 1
Commercial and technical alignment
A first commercial engagement, scoped and paid, with a named integration goal and success criteria set upfront with the PLLAY team.
- Weeks 2–3
Integration and campaign configuration
PLLAY provisions a partner-specific, non-production integration environment and API credentials directly with our engineering team — there is no public self-serve sandbox.
- Week 4
Testing and controlled traffic
The integration runs against a small, controlled slice of traffic before the audience cohort sees it.
- Weeks 5–7
Live pilot and optimization
The integration runs against real content, with a defined audience and duration, measured against the objective set in stage one. This is the stage PLLAY's Proof Sprint runs today.
- Week 8
Executive readout and production decision
The pilot's scope becomes the production integration — the same architecture and credential pattern, promoted rather than rebuilt.
What week 8's readout is scored against.
People present for the content the campaign ran against, and inside its eligibility rules.
People who took an action — not people who were served something.
Interactions carried through to a resolved outcome, rather than opened and abandoned.
People who came back for a second interaction. The signal that separates a novelty from a habit.
Where Vision AI resolves the pilot's outcomes: 31 of 38 recorded benchmark trials auto-settled, 0 wrong auto-settles, 7 declined rather than guessed — see /validation for the full record.
Funded rewards actually claimed, as distinct from rewards awarded.
Campaign cost over completed, verified interactions — the denominator being an action, not an impression.
These are internal engineering design targets, not results measured from production traffic. PLLAY has not published a live latency, throughput or success-rate number — see /developers. A pilot's integration is tracked against those same design targets — see /platform#performance-targets.
The terms every pilot runs on.
A first commercial engagement, scoped and paid, with a named integration goal and success criteria set upfront with the PLLAY team.
What each side may do with pilot data — and what happens to it after — is written down before the pilot starts, not negotiated after.
The pilot's scope becomes the production integration — the same architecture and credential pattern, promoted rather than rebuilt. The terms that conversion runs on are set at the same time, not renegotiated once the pilot is already live.
Week 8 is a decision, not a debate — the readout date is fixed at kickoff, and the pilot ends with a yes, a no, or a specific named gap, not an open-ended extension.
A pilot buys PLLAY's time and attention on your integration — it does not buy a lock on PLLAY working with anyone else in your category.
Custom engineering scoped for your pilot is part of the paid engagement. PLLAY does not build bespoke integration work speculatively, unpaid, ahead of a signed pilot.
Tell us what you're trying to prove.
A PLLAY team member scopes every pilot directly — there is no self-serve checkout.