Affiliate programs
Dott.pro
Description
Dott.pro is a public aff.bio reference page for a affiliate program. It is designed to help compare market participants by sources, official links, visible context and facts that still need manual verification.
What is Dott.pro
This card summarizes how Dott.pro appears 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 Dott.pro
The main domain linked with this card is dott.pro. 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 Dott.pro
- 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 Dott.pro
Use this page as a structured starting point: review the summary, compare source records and check important facts manually before making business decisions.
editorial_html_review_v2 · 1
FAQ about Dott.pro
What is Dott.pro?
Dott.pro is a affiliate program. 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: dott.pro.
Who may use Dott.pro?
Consider Dott.pro if you need a “Affiliate programs” entity and are ready to verify terms with the official site, manager or dashboard before starting.
Who is Dott.pro not for?
Dott.pro 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 Dott.pro with alternatives?
Compare Dott.pro 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 Dott.pro?
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
Website
GEO / verticals / attributes
Commissions
Payouts
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 |
|---|---|---|---|
| actualtraffic.ru | company_candidate | Dott.pro | source |
| cpainform | Affiliate networks | Dottpro | source |
| CPA Inform | affiliate_program_or_service | Source record | source |
| Partnerkin | affiliate_program_or_company | Dott.pro | source |
| trafopedia | Affiliate networks | Dott.pro | source |
Technical JSON/attributes
actualtraffic.ru · source record
{
"attributes summary": {
"created_by": "master_create_cards_no_contacts",
"needs_contact_enrichment": "True"
},
"email count": 0,
"telegram count": 0,
"verification": "Source record used for verification",
"confidence": 0.72
}cpainform · source record
{
"attributes summary": {
"opened_at": "2016-05-12",
"rating_cpainform": "2.7",
"minimum_payout": "1500",
"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": "26255",
"fields": [
"Dott.pro",
"dott.pro",
"2016-05-12",
"2.7"
],
"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
}Partnerkin · source record
{
"attributes summary": {
"parser": "partnerkin_local_archive_card_v2",
"archive": "PartnerkinArchive",
"needs_manual_review": "True",
"source_policy": "offline_archive_raw_review_only",
"official_site_visible": "dott.pro",
"source_import_mode": "pilot_raw_review_only",
"source_language": "ru",
"market": "RU_CIS",
"trust": "medium",
"clean_reparsed_at": "2026-05-12T10:25:01.691635+00:00",
"clean_reparse_reason": "partnerkin_source_specific_parser_removed_navigation_footer_and_extracted_card_fields"
},
"email count": 0,
"telegram count": 0,
"verification": "Source record used for verification",
"confidence": 0.78
}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
}