EXPERIENCE · POWERED BY ORACLE
Pulsetype=promo

Give brands a reason
to sponsor your audience.

Pulse turns a recorded challenge into a sponsor-funded campaign. Your audience plays free, the brand funds the rewards, and every result comes back verified, with the evidence a sponsor can show their own team.

Available through enterprise access, as managed engagements scoped with the PLLAY team.

Pulse demo

Interactive demo · simulated result

  1. 1Sponsor funds it
  2. 2Free to join
  3. 3Prediction
  4. 4Recorded outcome
  5. 5Verified result
Presented byYour sponsor hereA fictional placeholder, not a partner.

Overtime challenge

Rocket League · Recorded match · overtime

Example reward: a sponsor-funded perk. Illustrative only.

This website demo awards nothing and collects nothing.

Step 1 of 5: Sponsor funds it

How a Pulse campaign runs
  1. Campaign setupSponsor and partner

    The sponsor funds the pool and agrees the rule. The partner publishes the challenge on their own surface.

  2. Audience participationYour audience

    Your audience joins free on your game, portal or channel. Entry and sign-in stay with you.

  3. VerificationPLLAY

    PLLAY reads the recorded clip and settles it, holds it for a person or voids it. You get a settlement_id and the evidence.

  4. Partner reward fulfillmentYour team

    You deliver the reward to the people who got it right. PLLAY invoices the brand; no stake is involved.

Illustrative campaign

Illustrative: 10 recorded creator challenges, $5K pool each, 90% settle → $45K paid out through the partner; PLLAY clearance $6,750. Not a customer result.

Technical details
Event
POST /v1/events with type=promo, path=vod. No stake and no stake_ref; the brand is invoiced.
States
open, locked, then settled, held or voided. Settled returns a settlement_id.
Live
Live runs only with a reviewer, and every live result carries a reviewer_id.
Record
A reversal is recorded as a new entry; the original settlement_id is kept.

Verification does not know whether a stake was attached. Same event_id, same evidence, same settlement_id in every mode.

API reference → · Settlement contract →