Dashboard overview

A tour of the Invitebase dashboard — organizations, apps, test vs live mode, and every section of the nav

The Invitebase dashboard at dashboard.invitebase.com is where you create campaigns, watch referrals validate, read fraud decisions, and manage payouts. This page maps the whole surface so you know where everything lives.

Organizations and apps

The dashboard is organized in two levels:

  • Organization — your company. Members, billing, and API access are org-scoped. You invite teammates by email from Settings.
  • App — a product inside the organization (for example, your iOS/Android/web app). Campaigns, users, events, keys, and analytics all belong to an app. Use the app switcher in the top bar to move between apps.

Most teams have one app per product. Create additional apps when you run separate products with separate referral campaigns, users, and keys.

Test and live mode

Every app has two fully isolated environments, selected by a global test/live toggle in the top bar:

  • The toggle persists per user, and every screen — campaigns, analytics, users, events, webhooks, payouts — scopes to the selected mode.
  • While test mode is active, an unmissable colored banner spans the app so you always know you are looking at test data.
  • Test data is never billed and never moves real money. Money-adjacent screens (Payouts, Billing) reinforce this visually.

Your API keys encode the mode: pk_test_…/sk_test_… operate on test data, pk_live_…/sk_live_… on live data. There is no separate sandbox host — the key determines the environment. See Environments and test mode.

The Get started checklist

New apps land on Get started — an ordered, auto-detecting checklist that takes you from signup to a first validated referral in under half an hour. The first two steps are dashboard work with no code; the remaining three are engineering, with copy-paste code in platform tabs (Web/JS, iOS/Swift, Android/Kotlin, React Native, Flutter) and your real test keys already injected into the snippets.

The defining feature: steps check themselves off. You never mark anything done — the dashboard detects each signal server-side the moment it happens:

StepAuto-completes when
Create your campaignYour first campaign exists. The builder opens with a starter template prefilled — adjust it, swap in a Referral Gallery recipe, or start from scratch
Design your referral pagesYou save your campaign's Appearance — the shared theme behind the offer page, referrer status page, and notification emails
Initialize the SDK and identify a userThe first SDK init ping arrives from your app and the first identify() call is received
Generate a referral link and track an eventThe first getReferralLink() call succeeds and the first tracked event lands in the event feed
Validate your first referralThe first referral reaches validated

Steps complete on activity in either mode. Integrate in test mode — every snippet and CTA defaults to your test keys, and test data never bills or moves real money — but if your first activity arrives on live keys, the checklist credits it rather than waiting for test-mode signals that will never come.

The checklist starts genuinely empty: Invitebase never pre-creates campaigns or participants in your app, so everything in your account is something you made. The event simulator provisions its own clearly labeled demo participants the first time you open it, and they stay scoped to the simulator.

A persistent progress indicator shows how far along you are, and completing the final step swaps in a go-live checklist: clone your tested campaign into live mode, create live API keys, connect reward fulfillment, and set reward safeguards. Integrating live-first still leads to the same go-live checklist — the clone step keeps asking for a campaign proven in test mode, so a test-mode dry run remains the recommended path to launch.

You do not need a running app to finish the engineering steps. The event simulator fires synthetic events from the dashboard, so you can prove the entire loop — click, signup, qualifying events, validation, reward — before writing a line of integration code.

Where to go next

On this page