Core concepts

A short glossary to make the rest of the documentation easy to read. Terms are ordered from what you show to how you measure it.

Workspace

The place where your team, PWAs, streams, domains, and campaigns live. All resources and the balance belong to the workspace rather than an individual user. Members are invited with roles and permissions.

PWA

A progressive web app with a Google Play- or App Store-style installation page. Traffic opens the page, installs the app, and goes to the offer according to the configured scenario. PWA Editor → Config stores the icon, iOS interaction, push prompt, and webview bypass. One workspace can have many PWAs for different GEOs and verticals.

Direct Link

An alternative stream-rule target without a store-style page. Traffic stays in the same flow with its rules, cloaking, and analytics, then goes straight to the offer after Direct Link is selected.

Direct Link can also use webview bypass, a push prompt, and a Mini-PWA. It does not inherit PWA or stream settings: these values are stored independently in the Direct Link. It is a full alternative to a PWA for audiences that may be wary of a store-style page or an extra installation step.

Stream

The main traffic-routing unit. A stream connects domains to rules that select a PWA or Direct Link, cloaking, and tracking links to the offer. It does not control PWA behavior. The buyer places the active stream's domain in the ad campaign. When Keitaro is the offer, its Campaign URL is added to the stream tracking link. See Streams for details.

Domain

The address that serves a stream. You can buy a domain on the platform (DNS is configured automatically) or connect your own through CNAME. A domain must complete DNS → SSL → Active before it starts routing traffic. See Domains for details.

Cloaking

Stream-level cloaking configuration: mode, allowed OSs, anonymizers, and whitepage. See Cloaking for details.

Whitepage

A safe page shown to blocked or moderation traffic instead of the offer. It can be empty (410), redirect to an external URL, be a generated fantasy-app page, use a real-store listing, or be an AI page from AI Whitepages.

Offer

The URL that conversion traffic ultimately reaches, often with macros such as {click_id}. It can be a direct affiliate-program URL or a Keitaro Campaign URL. Offers are saved in a library so you do not need to enter the URL each time, then selected in a stream tracking link.

click_id

A unique identifier darkcore generates for every click. It is the key that matches all later events. For a tracker to return a conversion, pass click_id in the offer URL with the {click_id} macro: the tracker stores it and returns it in the postback.

Postback

Server-to-server event exchange over HTTP (s2s):

• Incoming — a tracker or affiliate network tells darkcore about a conversion (registration or deposit) at /p.
• Outgoing — darkcore forwards a conversion back to your tracker using a template configured on the stream.

See stream postbacks and the Keitaro integration for details.

Conversion type

A named conversion status in your workspace: registration, deposit, and any custom types such as redep. Each type has a key (immutable), aliases (what the tracker calls it, such as reg, ftd, or sale), and a flag indicating whether to count it as revenue. See Conversion types for details.

Pixel

A Facebook, TikTok, or Google Ads integration attached to a stream. Install, registration, and deposit are sent to the ad account through the platform's configured channel; for Google this is sGTM or the Data Manager API. See Pixels for details.

Macro

A placeholder such as {click_id}, {payout}, {geo}, or {sub1} that darkcore replaces with the real value when building an offer URL or outgoing postback. See the full macro reference.