Crossdeck University
Docs Start free
Watch — proving it works, both directions, in a minute Film in production
0:00 / 0:00
Lesson 6 of 6 · Get started

Verify your setup

Before you build on it, prove the whole chain works with your own eyes. It's a one-minute check, both directions — paid unlocks, free stays locked.

2 min Dashboard · Web

When you're done: you've seen paid unlock and free stay locked — your integration is proven, not assumed.

1 What this is & why it matters

Prove it works before you trust it

You've wired the whole chain — install, identify, entitlement, mapping, gate. That's everything. The one habit that separates a smooth launch from a 2 a.m. incident is this: see it work with your own eyes before you build on it. It takes about a minute, and you check both directions — that paying customers get in, and that everyone else stays out.

One order rule, because it has bitten people: if you're replacing an old access check with Crossdeck's, verify Crossdeck's gate first, then remove the old one. Pull the old gate before the new one is proven and you've locked every paying customer behind an untested integration. Verify in the middle; tidy up last.

2 How to verify it

Two accounts, two outcomes

Run the same check as two different people. Sign in as a paying account, warm the cache, and confirm the gate opens. Then sign in as a free account and confirm it stays shut.

await Crossdeck.getEntitlements();
console.log(Crossdeck.isEntitled("pro"));
// signed in as a paying account  → true   (feature shows)
// signed in as a free account    → false  (feature hides)

Then open Developers → Heartbeat in the dashboard. It runs live health checks across the SDK — analytics, payments, errors — and shows each one green when it's wired right, with a plain remediation hint when it isn't. It's the fastest way to spot a setup gap without reading a single log line.

3 How it works, piece by piece

The heartbeat is the SDK checking in

From the moment it boots, the SDK sends a heartbeat — a quiet check that confirms your key is valid and your signals are landing. The Heartbeat surface reads those checks and reports pass or fail per area, so "is my integration actually working?" has a one-glance answer instead of a guess.

Your two-account test and the Heartbeat surface answer different questions, and you want both: the test proves this customer resolves to the right access; Heartbeat proves the plumbing — keys, events, errors — is sound. Green on both, and you can build on it with confidence.

4 The green result in your dashboard

Proven, both ways

Paid unlocks, free stays locked, and Heartbeat is green across the board. That's a verified integration — and the end of Get started.

app.cross-deck.com · heartbeat
all checks green

Analytics, payments, and errors all reporting. Paid unlocked; free locked. You're set up — for real, not on faith.

Open Heartbeat in your dashboard

You proved the gate both ways — paid in, free out — and watched Heartbeat go green. Verify before you remove any old gate: reads-before-writes, verify in the middle, tidy up last. That's Get started, done.