High-Level Concepts

Before integrating, it helps to understand the main concepts BitEasy uses internally.

Apps

An App represents a single mobile application (iOS, Android, or both).

Each app has:

• an appId
• an attribution mode:
  • code (explicit, recommended)
  • window (best-effort fallback)
• associated partners and referral links

The attribution mode determines which flows are allowed.

Partners

A Partner is an entity that can refer users to your app.

Examples:

• creators
• affiliates
• other apps
• communities
• internal referral programs

Partners do not directly receive payouts from BitEasy automatically — BitEasy tracks attribution and earnings; payouts are executed separately (e.g. via Stripe Connect).

Referral Links

A Referral Link is a human-friendly identifier (slug) that maps a partner to an app.

Examples:

• alice
• promo-123
• launch

Referral links:

• belong to exactly one app
• belong to exactly one partner
• can be activated or deactivated
• are validated at defer / claim time

Pending Referrals

A Pending Referral represents a potential referral that has not yet been confirmed.

Think of it as:

“Someone might have been referred here.”

Pending referrals are:

• temporary
• time-limited

They exist in two forms:

• explicit (code-based)
• window-based (time-limited)

Actual attribution only happens when a pending referral is successfully claimed.

Attributed Installs

An Attributed Install is the finalized, successfully tracked referral event.

• Created once per install
• Immutable
• Tied to:
  • app
  • partner
  • referral link
• This is the source of truth for attribution

If an attributed install record exists, attribution has happened.