Docs › Domains
Traffic

Domains

A domain is what a human sees in the address bar before they land on your page. You park it, point it at the tracker, verify it — and it starts working as the "face" of your campaigns. The Domains screen is the garage where you keep them, fix them, and send them to retirement.

Domains are a personal item — like underwear: yours, not shared, and you want a few clean pairs in rotation. This screen is about keeping a clean set on hand at all times.

What's here: add one at a time or in bulk, verify a domain in one request (no waiting on background jobs), glue it to a campaign, manage confirmation files, and a DNS panel with ready-made records. Expiry notifications are not here — they live in Settings → Domains.

What's on screen

Toolbar on top, a checkbox domain table below, pager at the bottom. Selecting rows reveals a bulk action bar.

Toolbar:

Table columns (left to right):

  1. ☐ — row-select checkbox.
  2. # — domain number.
  3. URL — the address; if the domain is on https, an SSL lock sits beside it.
  4. IP — the address the domain resolves to.
  5. Created — date added.
  6. Expires — registration end date plus a days-left counter, coloured: red — 7 days or fewer, or already expired; amber — 30 days or fewer; green — more than 30. It's basically a countdown of how many days your domain has left to live.
  7. Status — a coloured stage icon: Waiting (wait), Active (active), Verified (ok), Error (error), Wrong (wrong); plus a separate "Protected" pill when the domain has valid SSL.
  8. Campaign (glue) — a button that opens the glue drawer; when the domain is glued, the cell shows a "glued" state.
  9. Actions — stats · files · check · delete.
Status and SSL are two different axes. A domain can sit in "Error" and still carry the "Protected" pill: verification stage and certificate validity are computed separately. Don't panic at a green lock next to a red status — that's normal.

Add one domain

  1. Type the address into the + Add domain field in the toolbar.
  2. Submit.
  3. The domain lands in the table with status Waiting.

On add, the address is cleaned and IDNA-encoded (non-ASCII names are encoded automatically), so you can write it like a human. Duplicates are rejected — if the domain already exists, you get a "duplicate" error and no new row appears.

Bulk add

  1. Click Bulk add.
  2. Type domains in the textarea — one per line.
  3. Optionally pick a campaign in "glue to campaign" (empty = don't glue).
  4. Confirm.

The list is deduplicated on the client (repeats in your own text collapse), each domain is added separately, and if a campaign is chosen, every added domain is glued to it. At the end you get a summary: "Added N · Skipped M" — skipped are the ones that already existed or failed to add.

How it works under the hood. There's no separate batch endpoint — the SPA just runs your list one request per domain, then shows one aggregate toast. So on a big list, give it a couple of seconds; it hasn't frozen.

Verify a domain

Verification is synchronous. One request returns the finished result. If the status isn't what you expected, the problem is DNS or the certificate — not "it hasn't caught up yet." Check your DNS records (panel below) and hit Check again.

Glue to a campaign

Glue is when a domain becomes the "face" of a specific campaign.

In the real AlterCPA Lite interface a "campaign" is called a поток / flow — that's the correct word, and that's what a domain glues to. We labelled it "campaign" so nothing trips you up. Settle in and you'll switch to the real word.
  1. Click the glue button in the Campaign column — a drawer opens.
  2. Pick a campaign from the list.
  3. Confirm — the domain is glued, and the cell shows a "glued" state.
  4. To detach, open the drawer and pick the empty option.

In bulk: select rows → Glue (pick a campaign) or Unglue in the bulk bar.

Glue goes by the campaign's HEX code. Under the hood the drawer sends neither the name nor the row number but the campaign's hex code (code) — or the raw integer fid. You type nothing by hand; the list fills it in. But if you're hitting the API directly: flow expects the hex code, and an empty flow means detach.

Confirmation files

Some services (webmaster consoles, ad accounts) want a marker file dropped at the domain's root.

  1. Click Files in a row — a modal opens with this domain's confirmation files.
  2. Add a file: give it a name and contents.
  3. Edit and delete files right in the modal.
This is the same confirmation-files mechanism as Landings — same modal, same files. Learn it here, and you've learned it there too.

Point your DNS

  1. Click DNS help — the "Point your DNS here" panel expands.
  2. It shows the parking IP(s) and a records table: @ / A / IP.
  3. Click the IP chip — it copies (you'll see "Copied").
  4. Set an A record for @ to that IP at your registrar.
  5. Come back and click Check on the row — the status updates.
The IP in the hint banner under the toolbar and the IP in the DNS panel are the same parking address of your tracker. Point the domain at it and you're done.

What's NOT here: expiry notifications

The "days left to live" counter on this screen is an indicator only. The expiry notifications themselves (email and Telegram) are configured not here but in Settings → Domains — the dom* config keys (domem, domeme, domtg, domtge, domtgk, domtgc). Want the tracker to message you "this domain dies in 7 days"? Go to Settings → Domains and switch it on.

→ Notification setup: Settings → Domains.

The red counter here just honestly tells you how many days the domain has left. Getting it to also DM you in advance — that's in Settings. Division of labour.

The bulk action bar

Select rows with the checkboxes — a bar appears on top with the selected count and buttons: Glue to campaign · Unglue · Check · Delete. All four apply to the selection.