Adset.Pro Terminology Glossary
A complete reference of terms used in the Adset.Pro tracker, linked to the internal entities of the system, language files (i18n), and code identifiers. Intended for MCP assistants, buyers, and all team members.
Key Terminology of Adset.Pro
It is critically important to understand the difference between pixels and postbacks in the context of Adset.Pro:
Postback — INCOMING signal
Postback is an HTTP request that comes TO Adset.Pro FROM affiliate networks (CPA networks). The affiliate informs the tracker that a target action has occurred (registration, deposit, repeat deposit, etc.).
Direction: CPA network → Adset.Pro
Contains: click_id, status, payout, currency
Processes:
PostBackController(/postbackendpoint)In UI: Tracker → CPA → Postback tab
i18n:
Postback,Upload postbacks,Postback URL,Postback status template
Pixel — OUTGOING signal
Pixel is an HTTP request or API call that is sent FROM Adset.Pro TO traffic sources (Facebook, TikTok, etc.). The tracker informs the advertising platform about a conversion event for algorithm optimization.
Direction: Adset.Pro → Traffic source (Facebook, TikTok, URL, Telegram)
Types (PixelType enum):
facebook,tiktok,url(HTTP Get),telegram_botIn UI: Tracker → Pixels (section "Pixels and Postbacks")
i18n:
Pixels and Postbacks,Pixel,Pixel ID,Pixel access token
Summary Table of Directions
Term | Direction | Who sends | Who receives |
|---|---|---|---|
Postback | → To Adset.Pro | CPA network (affiliate, affiliate program, AP, affiliate network) | Adset.Pro (tracker) |
Pixel | ← FROM Adset.Pro | Adset.Pro (tracker) | Traffic source (FB, TikTok) |
Tracker Entities
Campaign
The main entity that combines all settings for launching traffic. Contains: domain, source, stream sets with filters, flows (offer links), pixels, PWA, landing pages.
i18n:
Campaigns,Campaign,New campaignCode:
cmp_campaign(statistics)MCP Synonyms:
campaign,кампания→cmp_campaign
CPA (Affiliate Network)
An entity representing an affiliate network / advertiser, as well as another tracker (for example, Keitaro), which stands in the chain after Adset.Pro, but before the final affiliate program. Stores status mapping, postback macros, param template, currency.
i18n:
Affiliate networks,Affiliate networkCode:
cmp_cpa(statistics)MCP Synonyms:
cpa,партнёрка,affiliate networkExamples: direct affiliate (1win, Pin-Up), or intermediate tracker (Keitaro, Binom), standing before the affiliate program
Offer
A specific offer (product, service, application) from the affiliate network. Linked to CPA. Has type, rate (revenue), countries, language.
Revenue (Base Income) — the default price of the offer used when calculating income, if the affiliate does not pass the revenue amount in the postback. When the postback contains the revenue field — the value from the postback is used.
i18n:
Offers,Offer,Offer name,Base incomeOffer types (OfferType):
cpa(affiliate),agency(agency)Code:
cmp_offer,cmp_offer_typeMCP Synonyms:
offer,оффер→cmp_offer
Flow (Offer Link / Stream)
The URL to which traffic is directed. Linked to CPA and Offer. Can be external (external URL), internal (uploaded ZIP), or a Telegram channel.
i18n:
Offer links,Offer link,Reference link to offerCode:
cmp_flowMCP Synonyms:
flow,поток,ссылка на оффер→cmp_flow
Traffic Source
The advertising platform from which traffic comes: Facebook, TikTok, Google, native networks, etc. Defines parameter template, UTM mapping, external Click ID.
i18n:
Traffic sources,Source,Traffic source nameCode:
cmp_sourceMCP Synonyms:
source,источник,traffic source→cmp_source
Set (Set / Stream Set)
A set of filters and directions within a campaign. Determines which traffic goes where. A campaign can contain multiple sets.
Filters: conditions are configured (GEO, device, OS, language, parameters) by which traffic is distributed among sets
Pixels: each set is linked to pixels that will be triggered upon receiving conversions (postbacks) on this traffic flow. This allows sending different events to different sources depending on the set
i18n:
Set,Add set,Set nameCode:
cmp_set
Rotation
A mechanism for distributing traffic among flows within a set based on weights (weights).
i18n:
RotationCode:
cmp_rotation
Creative
Advertising material (banner, video, text) used in the campaign. Tracked in statistics.
i18n:
CreativeCode:
cmp_creative
Event Types
All events tracked by the tracker. Defined in EventType enum.
Click and View Events
EventType | Name (UI) | Description |
|---|---|---|
| Click from source | Incoming click from the advertising platform |
| Filtered | The click did not pass the stream set filters — the user was sent to the Fallback Page according to the advertising campaign settings |
| Landing view | The user saw the landing page |
| Click on landing | The user clicked on the landing page |
| Post-landing view | View of the page after APP, before FLOW |
| Click on post-landing | Click on the post-landing page |
PWA Events
EventType | Name (UI) | Description |
|---|---|---|
| PWA view | The PWA Store page is shown to the user |
| PWA installation | The user installed the PWA |
| PWA open | The user opened the installed PWA |
| iOS installation | Installation of the iOS application |
Notification Events
EventType | Name (UI) | Description |
|---|---|---|
| Notification request | The browser showed a notification request |
| Subscription | The user subscribed to push notifications |
| Notification decline | The user declined the request |
| Unsubscription | The user unsubscribed from push notifications |
| Click on notification | The user clicked on the push notification |
Telegram Events
EventType | Name (UI) | Description |
|---|---|---|
| TG join | The user joined the Telegram channel |
| TG start | The user started the Telegram bot |
CPA Events (Conversions from Affiliates)
EventType | Key in statistics | Name in UI | Description |
|---|---|---|---|
|
| Reg (Registration / Hold / Reg) | The user registered |
|
| Dep (FTD / Accept / Dep / Deposit) | The first deposit was accepted |
|
| Repeat Deposits (Re-Deposit) | Repeat deposit |
|
| Declined (Decline) | The conversion was declined by the affiliate |
|
| Trash (Trash) | Garbage / fraud conversion |
Status Mapping (CpaStatusesMap):
accept→CPA_ACCEPT,redep→CPA_REDEP,hold→CPA_HOLD,decline→CPA_DECLINE,trash→CPA_TRASH
Pixels and Postbacks
Pixel Types (PixelType)
PixelType | Name | Description |
|---|---|---|
| Facebook (CAPI) | Sending events via Facebook Conversions API |
| TikTok (Events API) | Sending events via TikTok Events API |
| HTTP Get | Sending a GET request to an arbitrary URL with macros |
| Telegram Bot | Sending a message to a Telegram channel via a bot |
Pixel Terminology
Pixel ID (
pixel_id) — the identifier of the pixel in the advertising platform (for example, Facebook Pixel ID)Access Token (
access_token) — access token for the advertising platform APITest Event Code — test event code from Facebook for pixel verification
Event Mapping — mapping of internal tracker statuses to pixel events (for example,
accept→Purchase)External Event (
ext_event) — arbitrary name of the event on the advertising platform sideTrigger — condition for pixel activation (binding to a specific conversion status)
Pixel Events (i18n SourceTemplateCrudView)
Key | Name (UI) |
|---|---|
| PWA installation |
| hold |
| accepted |
| declined |
| trash |
Postback Terminology
Postback URL — the URL to which the affiliate sends conversions. Generated by Adset.Pro automatically
Postback Macros — fields in CPA settings:
clickId,status,revenue,currency,externalIdPostback Status Template — string values of affiliate statuses that map to internal event types
Postback Upload — bulk import of conversions from CSV (
clickId, status, revenue, currency)Conversion Duplicates — a setting that allows receiving multiple conversions of the same type for one click ID
PWA (Progressive Web App)
PWA is a web application that can be installed on the user's device like a regular application. In Adset.Pro, PWA is used as an intermediate step between the landing page and the offer.
PWA Types (PwaType)
PwaType | Name | Description |
|---|---|---|
| Internal | PWA built inside Adset.Pro (constructor) |
| External | PWA hosted on an external server, linked via postback URL |
| iOS App | iOS application integrated via SDK |
PWA Terminology
PWA Store — showcase page for PWA, mimicking an application page in Google Play / App Store. Contains: logo, name, description, screenshots, comments, rating, reviews, install button
PWA Constructor — tool for creating PWA within Adset.Pro with a step-by-step wizard
Manifest (
manifest.json) — JSON file describing the PWA for the browser (name, icons, colors, display mode)Service Worker — script running in the background; provides offline functionality and push notifications
Install Prompt — browser dialog offering to install the PWA
PWA Install Rate — metric
pwa_view_to_instal_rate: ratio of installs to PWA views
PWA Events in Statistics
Metric | Name (UI) |
|---|---|
| PWA views |
| Installs |
| PWA opens |
| Click to install |
| View to install |
Landings and Postlandings
Landing
The landing page that the user sees first after clicking on the ad link. In Adset.Pro it is called "Game / Pre-landing".
Hosting Types:
internal— uploaded ZIP archive (local landing)external— external link (redirect)telegram— Telegram channel
i18n:
Game / Pre-landing,Landing,Landing nameCode:
cmp_landing
Postlanding
The page shown after the subscription page (PWA Store) and before redirecting to Flow. An additional step in the funnel to increase conversion.
i18n:
Game / Postlanding,Postlanding,Postlanding nameCode:
cmp_postlandingEvents:
POSTLANDING_VIEW,POSTLANDING_CLICKMetrics:
postlanding_views,postlanding_clicks,postlanding_ctr
Fallback Page
The page served to traffic that did not match the filters of the campaign stream sets, as well as to clicks blocked by Adset Protect.
i18n:
Fallback Page,Fallback Page Type,Redirect URLTypes: system template, custom URL, fallback page from the list
Metrics and Statistics
Financial Metrics
Metric | Name (UI) | Formula | MCP Aliases |
|---|---|---|---|
| Revenue | Sum of payouts from CPA_ACCEPT + CPA_REDEP |
|
| Cost | Cost of traffic (from source expense) |
|
| Profit |
|
|
| ROI |
|
|
| CPC |
| Cost per click |
| EPC |
| Revenue per click |
| CPL |
| Cost per lead |
| CPR |
| Cost per registration |
| EPL |
| Revenue per lead |
| RPM |
| Revenue per 1000 impressions |
Conversion Metrics
Metric | Name (UI) | Description | MCP Aliases |
|---|---|---|---|
| Reg | Number of registrations |
|
| Dep (FTD) | Number of first deposits |
|
| ReDeps | Number of repeat deposits |
|
| Reg to FTD |
| — |
| Dep to ReDep |
| — |
| Click to Reg |
| — |
| Click to Dep |
| — |
Traffic Metrics
Metric | Name (UI) | Description |
|---|---|---|
| Clicks (uniq) | Unique clicks, uniqueness by IP + User Agent |
| Clicks (all) | All clicks, including repeat ones |
| Filtered | Filtered clicks — clicks sent to the Fallback Page |
| Impression | Landing views |
| Clicks | Clicks on the landing |
| CTR | Landing CTR |
LTV Metrics (Lifetime Value)
Metric | Name (UI) |
|---|---|
| LTV Day 0 |
| LTV Day 1-7 |
| LTV Day 8-30 |
| LTV Day 31-90 |
| LTV Total |
| LTV per FTD |
| LTV per Reg |
Traffic Sources
Popular Sources
Source | Description | Typical pixel |
|---|---|---|
Facebook (FB) | Meta's advertising platform. The main platform for traffic arbitrage |
|
TikTok | ByteDance's advertising platform |
|
Google Ads | Google's advertising platform |
|
Native Ads | Native advertising (Taboola, Outbrain, MGID, etc.) |
|
Push Ads | Push advertising (PropellerAds, RichPush, etc.) |
|
Facebook Terminology
BM (Business Manager) — Facebook's business management account
Ad Account — the account used to run ads
Campaign (FB campaign) — the top level of the ad hierarchy in FB
Ad Set — a group of ads with targeting settings
Ad — a specific ad creative
Pixel (FB pixel) — Facebook's tracking code
CAPI (Conversions API) — a server-side API for sending events to Facebook (instead of or together with the browser pixel)
Test Event Code — a code for testing CAPI events
TikTok Terminology
TikTok Ads Manager — TikTok's ad account interface
Events API — a server-side event API (the counterpart of Facebook CAPI)
TT Pixel — TikTok's tracking pixel
UTM Parameters
Standard parameters for tracking traffic sources. In Adset.Pro they are mapped to statistics fields:
UTM parameter | Statistics field | Typical value in FB |
|---|---|---|
|
| Ad platform name |
|
| FB Profile ID |
|
| BM Account ID |
|
| BM Campaign ID |
|
| Campaign AdSet ID |
Sub Parameters
Additional parameters for passing arbitrary data:
Parameter | Statistics field | Typical use in FB |
|---|---|---|
|
| Ad ID |
|
| Arbitrary data |
Verticals (Niches)
Gambling
Online casinos, slots, games of chance. The most popular vertical in traffic arbitrage.
Specifics: High payouts, FTD model, redeposits
Key events:
CPA_HOLD(registration),CPA_ACCEPT(FTD/deposit),CPA_REDEP(repeat deposit)PWA topics (i18n):
Gambling,Casino,SlotsPWA categories:
casino,action,arcade
Betting
Sports betting.
Specifics: Seasonality, tied to sports events
PWA topics:
Betting
Dating
Dating and dating sites.
Specifics: Smartlink model, SOI (Single Opt-In) and DOI (Double Opt-In)
Key events: Registration (
CPA_HOLD), Premium subscription (CPA_ACCEPT)
Nutra
Health products, dietary supplements, weight-loss products.
Specifics: COD (Cash on Delivery) model, single-page landings
PWA topics:
Nutra
Crypto
Cryptocurrency exchanges, wallets, ICOs.
Specifics: High payouts, long conversion cycle
PWA topics:
Crypto
Finance
Loans, microloans, banking products, insurance.
PWA topics:
Finance
Targeting and Filters
Stream Set Filters
Filters determine which traffic goes to which set of the campaign. They are grouped by category:
Group | Filters |
|---|---|
Geolocation | Country ( |
Device and browser | Device ( |
Parameters | UTM tags, Sub parameters, Query parameters, Header values |
Tracking parameters | Proxy ( |
Key Terms
GEO — the user's country / region. MCP synonyms:
geo,country,страна→user_countryDevice —
desktop,mobile,tablet,tvOS (operating system) —
Android,iOS,Windows,macOSSticky Flow — binding returning visitors to the same flow they got on their first visit
Macros and Parameters
Tracker Macros
Macros are special placeholders (variables) in links and settings that are automatically replaced with real values at the moment the user is redirected to the target page of the CPA offer (Flow).
Two groups are available: event/traffic parameters ({event.*}) and buyer parameters ({user.*}).
1. Basic event fields
Macro | Type | Description |
|---|---|---|
| Number | Event time (timestamp) |
| Number | Session start time — the first touch with the user (timestamp) |
| String | The domain the event went through |
| UUID | Unique identifier of the incoming click |
2. User (traffic) data (EventUser)
Macro | Type | Description |
|---|---|---|
| IPv6 | User's IP address |
| UInt32 | Autonomous system number of the provider |
| String | Provider organization name |
| FixedString(2) | Country code (ISO-3166: US, GB, DE) |
| String | User's region/state |
| Enum8 | Device type: |
| String | Platform (iOS, Android, Windows, macOS, Linux) |
| String | Operating system |
| String | OS version |
| String | Browser (Chrome, Firefox, Safari, Edge) |
| String | Browser version |
| String | Browser language (ISO-639: en, ru, de) |
| String | User-Agent string |
| UInt8 | Proxy flag (0 or 1) |
| UInt8 | Bot flag (0 or 1) |
3. Campaign parameters (EventCampaign)
Macro | Type | Description |
|---|---|---|
| String | Campaign owner ID |
| String | Team ID |
| String | Campaign ID |
| String | ID of the stream set within the campaign |
| String | Traffic source ID |
| String | CPA network ID |
| String | Offer ID |
| String | Flow ID |
| String | Creative ID |
| String | PWA ID (if used) |
| String | Landing ID (if used) |
4. UTM tags and external parameters
Macro | Type | Description |
|---|---|---|
| String | Traffic source (facebook, google) |
| String | Source campaign ID |
| String | Channel (for example, BM Account ID) |
| String | Content (for example, FB Campaign ID) |
| String | Keyword (for example, FB AdSet) |
| String | Custom parameter 1 (for example, Ad ID) |
| String | Custom parameters 2-10 |
| String | Click ID from the traffic source (fbclid, gclid) |
5. Buyer parameters (Buyer)
Macro | Type | Description |
|---|---|---|
| String | Campaign owner ID (equivalent to |
| String | Campaign owner name |
| String | Campaign owner email |
| String | Campaign owner role |
Using Macros
Param template (
paramTemplate) — a GET string appended to the offer URL (for example,?clickid={event.event_click_id}&sub1={event.ext_sub1})Pass all params — a button that automatically adds all macros to the template
Macros are substituted at the moment the user is redirected to the offer page
Domains and Fallback Pages
Domain
The domain that hosts the tracker and through which traffic passes.
i18n:
Domain,Choose domainCloud registrars: Cloudflare, etc.
Fallback Page
The page for traffic that did not pass the stream set filters and for clicks blocked by Adset Protect. Interface section: PWA → Fallback Pages.
Types: System template, Custom URL, Fallback Page from the list
i18n:
Fallback Page Type,Fallback Page URL,System Fallback Page
Push Notifications
Push notifications (pushes) — browser notifications sent to subscribed users via FCM (Firebase Cloud Messaging).
Terminology
Push Group — a set of push notifications attached to a campaign
Push Slot — a position/slot for sending a push
FCM — Firebase Cloud Messaging, the push delivery service
Subscribe — the user agreed to receive pushes
Unsubscribe — the user unsubscribed
Push Metrics
Metric | Name (UI) |
|---|---|
| Push Sends |
| Push Fails |
| Push Skips |
| Push Views |
| Push Clicks |
| Push CTR |
| Delivery Rate |
| Post-Click Reg |
| Post-Click Dep |
| Post-Click ReDep |
Push Attribution
Linking conversions (registrations, deposits) to the specific push notifications the user clicked.
Telegram Integration
Terminology
Telegram Bot — a bot that sends conversion notifications to a channel
Telegram Channel — the channel the bot sends messages to
TG_JOIN — event: the user joined the Telegram channel
TG_START — event: the user started the bot
Metrics
Metric | Name (UI) |
|---|---|
| TG Starts |
| TG Joins |
| Click to Start |
| Click to Join |
Teams and Access
Team
An organizational unit that groups users and resources. All entities (campaigns, CPA networks, pixels, etc.) are bound to a team.
i18n:
Team,Team NameCode:
cmp_teamMCP synonyms:
team,команда→cmp_team
Owner
The user responsible for a specific entity (campaign, CPA network, offer, etc.).
i18n:
Owner
Resource Access
The mechanism for managing users' access rights to entities.
Traffic Pricing
Cost Model
The method of calculating the traffic cost for a campaign:
CPC (Cost Per Click) — payment per click
CPA — payment per target action (registration, deposit)
CPA Event (
cpa_event) — the CPA event used for pricingCPA Price (
cpa_price) — the price per event
Synonyms for the Assistant
Term | MCP Aliases | Canonical key |
|---|---|---|
Cost |
|
|
Revenue |
|
|
Profit |
|
|
MCP Assistant Aliases and Synonyms
Mapping of user language to canonical statistics keys. Defined in statsAssistantMeta.ts.
Metrics
User says | Canonical key |
|---|---|
installs, установки, инсталлы |
|
registrations, leads, regs, рег |
|
ftd, ftds, first deposit, деп |
|
депозит |
|
повторный депозит, редеп |
|
revenue, payout, income, доход |
|
cost, spend, budget, расход |
|
profit, прибыль |
|
roi, return on investment |
|
Groupings
User says | Canonical key |
|---|---|
team, команда |
|
campaign, кампания |
|
source, источник |
|
offer, оффер |
|
geo, country, страна |
|
device, устройство |
|
Event Semantics
User term | Meaning in the system |
|---|---|
deposit, dep, FTD, принятое |
|
registration, hold, рег |
|
repeat deposit, redeposit, редеп |
|
Naming Conventions
Any key with the
_namesuffix is the human-readable name for the base field without_name(for example,cmp_team_nameis the name forcmp_team)When outputting tables, include both the ID and the
_nametogether
