Launch your first funnel from domain to test click

This walkthrough is for an operator setting up a funnel on their ATracker instance for the first time: go from a tracking domain to a click that appears in Logs. We do not cover internal tracker architecture — only admin steps and how to verify the result.

When to use it. New instance, new teammate, or new vertical: you have (or need) a domain, but the network, source, and campaign are not ready yet. The goal is a working campaign URL and proof that a click was recorded.

What you need. Admin access (or roles with Domains, Affiliate Networks, Offers, Traffic Sources, Campaigns, and Logs). A tracking domain that resolves to your server, or an existing domain on the stand with DNS Verified. An offer URL from the network (a test URL is fine).

Step 1. Tracking domain

  1. Sidebar → Domains (/domains).
  2. If the domain is missing — New Domain, enter the hostname, save. Wait for DNS Verified and SSL active. Without that, the campaign URL cannot serve HTTPS or DNS has not converged.
  3. Remember the domain for the campaign step. The screenshot shows a working example test2.cashx.ru with Verified status.
Tracking domains list
Domains: confirm DNS Verified and SSL active before launching.

Step 2. Affiliate network and postback URL

  1. Sidebar → Affiliate Networks (/affiliate-networks).
  2. Template (or equivalent) → network name, postback parameters (subid, status, payout as your network expects).
  3. Copy the postback URL from the network card into the partner dashboard. Without an inbound postback, conversions will not reach the tracker (see the debugging article).
Affiliate networks list
Affiliate Networks: template and postback URL for the partner cabinet.
Create affiliate network template
Network template form: name and postback macros.

Step 3. Offer with a clickid macro

  1. Sidebar → Offers → Create (/offers/new).
  2. Set a name, pick the Affiliate network from step 2.
  3. In URL, paste the partner link with {subid} or {clickid} — the macro the tracker replaces on redirect. Without it, the network cannot attribute conversions to the click.
  4. Set payout (a fixed test value is fine), save.
Create offer
Offer: network, URL with subid/clickid macro, payout.

Step 4. Traffic source

  1. Sidebar → Sources (/traffic-sources) → Create.
  2. Pick a template (Facebook, Google, Custom) or map sub_id parameters manually — they flow into reports and outbound postbacks to ads when you enable S2S.
  3. Save the source. For a first launch, a name and defaults are enough.
Traffic sources list
Traffic Sources: list and create button.

Step 5. Campaign

  1. Sidebar → Campaigns → New Campaign (/campaigns/new).
  2. Fill Name, required Alias (unique, used in the URL), Domain from step 1, Traffic source from step 4. Optionally set cost model (CPC/CPM) for later reports.
  3. Save — the campaign editor opens.
Create campaign
New campaign form: alias, domain, source.

Step 6. Flow (traffic path)

  1. In the campaign editor → Flows tab.
  2. If empty — Add Flow. Simple direct setup: one offer step → your offer. With a prelander: landing then offer.
  3. Ensure the flow is Active, weight 100% (or your split). Save.
Campaign flow editor
Flows: default flow with the offer attached.

Step 7. Campaign URL and campaign postback

  1. URL & Postback tab.
  2. Click Generate if Campaign URL is empty. Copy the link for the ad platform or a manual test.
  3. The postback URL on this tab is for manual test conversions (substitute a real subid from the click log). Paste the network postback from Affiliate Network (step 2) into the partner cabinet.
Campaign URL and Postback
URL & Postback: campaign URL, postback with subid, optional signing.

Step 8. Test click and verify in Logs

  1. Fire a click: open the campaign URL in a browser; use Simulate on the campaign list if available; or send the link to a test ad account.
  2. Sidebar → Logs (/logs), Clicks tab. Period — Today or Last 7 days. Filter by campaign.
  3. You should see a fresh row with a Click ID (subid). Only then trust Dashboard/Reports aggregates — summaries without a click in logs are misleading.
Clicks log
Logs → Clicks: proof the tracker recorded the hit.

Common first-launch issues

  • No click in Logs. Domain DNS not Verified, wrong domain on the campaign, empty flow, or campaign paused. Open the URL manually — no 5xx on the tracking domain.
  • URL does not generate. No domain selected on the campaign or domain not active.
  • Redirect to offer without subid. Check the offer URL macro and that the flow points to the right offer.
  • Onboarding modal after first superadmin login blocks clicks — close Skip / Finish later.

Next: test postback and conversions — see Clicks but no conversions. Entity reference — documentation.