Conversion types
Configure funnel statuses, postback aliases, pixel events, and custom analytics formulas.
Conversion types turn external statuses into an understandable darkcore funnel. Define once what reg, ftd, approve, or sale means, then those events work consistently in postbacks, pixels, push audiences, and reports.
Manage them in Settings → Conversions.
Quick setup
- Select the closest vertical template or create a type manually.
- Add every status your tracker or affiliate network actually sends to Aliases.
- Enable Count in revenue only for events with a monetary value.
- Check event mapping in connected Facebook/TikTok pixels or the Conversion Action ID in Google Ads.
- Send a test postback and find the event in analytics.
Conversion type fields
| Field | What it controls | Example |
|---|---|---|
| Key | Immutable system identifier | deposit, redep, approve |
| Name | Readable label in the interface | Repeat deposit |
| Aliases | External statuses mapped to this type | dep, ftd, sale |
| Count in revenue | Adds the event's payout to revenue | Enabled for a deposit |
| Active | Allows new events of this type to be accepted | Enabled |
| Send to pixel | Triggers the platform's configured event | Purchase / CompletePayment / Google Conversion Action |
| In darkcore statistics | Sets the event time used in reports | Conversion, click, or another event time |
| In Meta / TikTok / Google | Separately sets the time sent to the ad platform | Conversion, click, or another event time |
| Color | Differentiates the event in reports and badges | — |
You cannot change a key after creation. History, formulas, pixels, and audiences refer to it. You can edit the name, aliases, color, and pixel mapping.
Choose the event time
The time used in darkcore statistics and the time sent to an ad platform are configured independently. Each field supports:
- current conversion time — the default;
- click time;
- first occurrence of another active conversion type, such as registration.
If the selected earlier event does not exist, darkcore uses the actual time of the current conversion.
Meta, TikTok, and Google limit how old an event can be. If you select an old click or conversion time, the event may not be sent to the ad platform. darkcore does not replace your selected time with a newer one.
System types
A new workspace has two basic types:
- registration — aliases:
reg,registration; not counted as revenue; - deposit — aliases:
dep,deposit,ftd,first_deposit,sale; counted as revenue.
Adapt aliases to the real values from your source. Do not create a separate type merely because an affiliate network calls the same event differently.
Current vertical templates
The Templates button currently adds or updates a basic set of types:
| Template | Types |
|---|---|
| Gambling | registration, deposit, redep |
| E-commerce (COD) | lead, approve, reject, buyout |
| Dating | registration, confirm, sale |
Before applying, darkcore shows a diff: what will be created, what will be updated, and which aliases will change owner.
Custom metrics
A custom metric is a formula over report data. For example, registration conversion rate:
evt_registration / unique_clicks| Field | What to provide |
|---|---|
| Name | A readable label for the report |
| Formula | Metrics, + − × ÷ operators, and parentheses |
| Format | Number, percentage, or currency |
| Decimal places | Required precision, from 0 to 6 |
| Active | Whether to show the metric in analytics |
Formulas can use clicks, uniques, installs, revenue, and dynamic keys for every active conversion type. One custom metric cannot reference another custom metric.
What changes after saving
A new type immediately appears in:
- postback acceptance and routing;
- pixel event mapping;
- analytics metrics;
- push campaign triggers and filters.
Therefore, agree on the funnel and aliases first, then connect external systems.