2. Growth & Campaigns
The MVP includes a configurable campaign engine. Aerion sets bonus rules, windows, codes and caps from the admin console; the platform enforces them at entry and records every result. No guaranteed-return or passive-income language is used in any campaign surface.
2.1 Campaign engine
Aerion controls the following from the admin console, without a deployment.
| Ref | Capability | What Aerion controls |
|---|---|---|
| CE-01 | Bonus configuration | Bonus percentage and eligibility rules per campaign, applied automatically to qualifying allocations. |
| CE-02 | Allocation windows | Open and close times for private-sale, public-sale and pool-specific windows. |
| CE-03 | Invite & referral codes | Issue codes, attach them to a campaign, and see which code produced each signup and each allocation. |
| CE-04 | Campaign caps | Hard ceilings on participants, total allocation or per-account amount. The engine stops accepting entries at the cap. |
| CE-05 | Landing routes | Campaign URLs linked from Aerion's existing launch site that route visitors into platform registration. |
| CE-06 | Dashboard banners | Campaign-specific banners shown to the right audience inside the authenticated dashboard. |
| CE-07 | In-platform offers | Promotional offers shown to logged-in users, targeted by audience and campaign state. |
| CE-08 | Admin controls | Start, pause, edit and stop any campaign from the admin console without a deployment. |
2.2 Campaign playbook
Seven configurations of the same engine, all supported by the MVP. Aerion selects which run, in what order and on what terms.
| Ref | Campaign | Mechanism |
|---|---|---|
| CM-01 | Early dashboard access | A capped group is admitted to the platform before general availability. Access is granted per account and the queue position is recorded. |
| CM-02 | Private-sale allocation window | A timed window opens for approved investors only. Eligibility, cap and closing time are set once and enforced by the engine. |
| CM-03 | Public-sale registration window | An open registration period that runs before the sale. Each registrant is created as a platform account with campaign attribution attached. |
| CM-04 | Purchase bonus campaign | An extra percentage attached to allocations made inside the campaign period. The bonus value is an Aerion decision; the platform applies and records it. |
| CM-05 | Founder & community invite | Named invite codes issued to founders, partners or community members. Each signup and allocation is attributed to the code used. |
| CM-06 | Service-credit priority | Participants are queued ahead for future compute and service credits. The reservation is visible in the investor's Service Credits view. |
| CM-07 | Pool-specific allocation | A campaign scoped to a single mining or AI/HPC pool, with its own window and cap, leaving other pools unaffected. |
2.3 Tracking & CRM
Campaign data is captured in the platform and exported as a structured file. No third-party CRM integration is included; Aerion imports the export into its own tooling.
- 1Email capture on campaign landing routes and inside the platform.
- 2UTM parameters are recorded on entry and kept attached to the resulting account.
- 3Invite and referral codes are stored against every signup for attribution.
- 4Campaign analytics: entries, conversions and allocation volume per campaign.
- 5Waitlist-to-dashboard conversion: count of waitlist users that became active platform accounts. Waitlist migration into platform accounts is scoped at §1.1.
- 6CRM export of contacts and campaign context as a structured file, produced on demand from the admin console.
2.4 Anti-abuse measures
The MVP ships the controls below. Items 1 to 4 are enforced at entry, before an allocation record is created; 5 to 8 are enforced by review and are available to admins after entry.
- 1Account uniqueness checks on registration.
- 2Wallet uniqueness checks: one wallet address cannot be reused across accounts.
- 3Invite-code tracking, so a single code cannot be recycled beyond its limit.
- 4Campaign caps applied per account and per campaign.
- 5Admin approval queues before an allocation record is created.
- 6KYC status fields on each account, visible to reviewers.
- 7Suspicious-activity review from the admin console.
- 8Audit logs covering the admin actions that grant or revoke access.
Exclusion — Not included in this scope