UnicomPublic reference card: visible facts, contacts and source evidence without raw/admin navigation.

LanguageRU EN

Catalog cards

Unicom

Contacts: email 1 · Telegram 2

Sources: 5 · Completeness: 100

Description

Unicom is a catalog entity in the aff.bio database. Main database domain: cpa.unicom24.ru. The card is linked to 5 sources and 5 raw evidence records. Public contact signals: email: 1, Telegram: 3. aff.bio keeps this as a verifiable evidence layer; disputed facts and contacts are not treated as confirmed without review.

What is Unicom

This card summarizes how Unicom appears as a market participant in affiliate, CPA, performance marketing or iGaming-related sources. aff.bio separates public summary information from raw evidence and does not treat source mentions as guarantees.

Work context for Unicom

The main domain linked with this card is cpa.unicom24.ru. Check that the brand, domain and public pages match before using the information for outreach, campaign launch or payment.

Linked source records in the database: 5. A higher source count can be useful for verification, but conditions, contacts, GEO, pricing and payout details should be confirmed in primary sources.

Contacts and public data

Public contacts and links are shown only after filtering obvious source noise, footer contacts, tracking links and raw parser data. If a field is missing, treat it as something to check, not as a confirmed absence.

What to verify before working with Unicom

official website and clean domain;
current terms, GEO, traffic-source restrictions or service scope;
public contacts and support channels;
related companies, programs, teams, tools or events;
whether the card is a duplicate, outdated source or thin import.

Full information about Unicom

Use this page as a structured starting point: review the summary, compare source records and check important facts manually before making business decisions.

catalog_card · editorial_html_review_v2 · 2

FAQ about Unicom

What is Unicom?

Unicom is a catalog cards. This public aff.bio reference page helps understand the entity category and what to verify before contact, campaign launch or payment. Main domain to verify: cpa.unicom24.ru.

Who may use Unicom?

Consider Unicom if you need a “Catalog cards” entity and are ready to verify terms with the official site, manager or dashboard before starting.

Who is Unicom not for?

Unicom is not enough if you need guaranteed payouts, exact GEOs, rates, licenses, prices or terms without additional verification. aff.bio does not replace a contract, program rules or official support.

How to compare Unicom with alternatives?

Compare Unicom by category, domain, source count, start conditions, traffic restrictions, payouts, support and data freshness. If a fact is missing, treat it as something to verify, not as a promise.

What should be checked before working with Unicom?

Check the official domain, current rules, GEO and traffic-source restrictions, payment terms, manager contacts and last update date. Source count linked in aff.bio: 5.

Contacts and links

Support

Email: support@cpa.unicom24.ru

Managers / people

Telegram: https://t.me/valeriya_marketing_unicom

GEO / verticals / attributes

Commissions

7.9

Payouts

5000

Related people / companies

Name / company	Role / relation
Reliable relations are not found yet; uncertain contacts stay in evidence below.

Source records and evidence

Source	Type	Name / domain	URL
CPA Club	Companies	Source record	source
cpainform	Affiliate networks	Source record	source
CPA Inform	affiliate_program_or_service	Source record	source
Gembla	Catalog cards	Unicom	source
trafopedia	Affiliate networks	UNICOM	source

Technical JSON/attributes

CPA Club · source record

{
  "attributes summary": {
    "jsonld_url": "https://cpa.club/companies/unicom/",
    "language": "ru",
    "trust": "medium-high",
    "source_import_mode": "raw_source_layer"
  },
  "email count": 0,
  "telegram count": 3,
  "verification": "Source record used for verification",
  "confidence": 1.0
}

cpainform · source record

{
  "attributes summary": {
    "offers_count": "0",
    "rating_cpainform": "7.9",
    "minimum_payout": "5000",
    "needs_manual_review": "True",
    "do_not_blind_merge": "True",
    "parser_version": "cpainform_offline_v1",
    "dry_run_db_status": "already_or_possible_duplicate",
    "source_import_mode": "pilot_raw_review_only",
    "source_language": "ru",
    "market": "RU_CIS",
    "trust": "review_only"
  },
  "email count": 0,
  "telegram count": 0,
  "verification": "Source record used for verification",
  "confidence": 0.78
}

CPA Inform · source record

{
  "attributes summary": {
    "parser": "planned_source_parser_v2",
    "http_status": "200",
    "bytes": "26406",
    "fields": [
      "UNICOM",
      "cpa.unicom24.ru",
      "0",
      "7.9"
    ],
    "llm_review_applied": "True",
    "do_not_blind_merge": "True",
    "official_site_policy": "direct/labeled only; tracking and source-owned links excluded",
    "import_batch": "planned_sources_parser_v2_20260513_043832"
  },
  "email count": 0,
  "telegram count": 0,
  "verification": "Source record used for verification",
  "confidence": 0.78
}

Gembla · source record

{
  "attributes summary": {
    "feedback": "support@cpa.unicom24.ru"
  },
  "email count": 1,
  "telegram count": 0,
  "verification": "Source record used for verification",
  "confidence": 1.0
}

trafopedia · source record

{
  "attributes summary": {
    "needs_manual_review": "True",
    "do_not_blind_merge": "True",
    "parser_version": "next_sources_offline_v1",
    "dry_run_db_status": "already_or_possible_duplicate",
    "source_import_mode": "pilot_raw_review_only",
    "source_language": "ru",
    "market": "RU_CIS",
    "trust": "review_only"
  },
  "email count": 0,
  "telegram count": 0,
  "verification": "Source record used for verification",
  "confidence": 0.78
}