Your funnel should speak your vertical's language
DarkCore does not force every campaign into registration and deposit. Each workspace can create the conversion statuses its vertical actually uses — lead, approve, buyout, rejected, redeposit, trial, renewal or any stable event key — and reuse them across the whole system.
If a tracker only understands two or three fixed statuses, the team starts hiding real business logic in notes, spreadsheets and naming conventions. The result is broken reporting: pixels fire on the wrong events, push audiences cannot target the right users, caps count the wrong thing and CRM finance has to guess what a conversion really means.
Workspace-level status registry
Every status is a registry row with an immutable key, aliases, revenue behavior, pixel event names, color and active state. The key is stable because ClickHouse, pixels, postbacks and reports all depend on it.
Real examples: lead, approve, buyout, rejected
COD/nutra flows can track lead → approve → buyout → rejected. Gambling can track registration → deposit → redeposit. Dating, crypto and sweepstakes can define their own funnel without waiting for product support.
Aliases normalize messy postbacks
Affiliate networks and trackers send different raw statuses: sale, ftd, approved, paid, trash. Aliases map those inbound values into one clean event key for reporting and automation.
Statuses drive actions, not just labels
The same status can fire or suppress pixels, route postbacks, segment push audiences, trigger event-based push campaigns, feed auto-rules and appear in analytics metrics.
Built for custom payout logic
A custom status can become the billable event behind an offer type and cap logic, so CRM can monitor the exact event the advertiser pays for, not just generic registrations or deposits.
- ✓ Model any vertical's funnel without hard-coded tracker limits.
- ✓ Keep postbacks, pixels, push, analytics and CRM finance on the same event vocabulary.
- ✓ Use aliases to turn messy external statuses into clean reporting dimensions.
- ✓ Build caps and payouts around the event that actually creates revenue.
The related DarkCore pages Google and readers should connect with this topic.