Features

The Dashboard provides a real-time overview of your affiliate marketing performance. It displays key metrics, recent activity, and quick access to important functions.

Total Revenue — The total revenue generated from all conversions. Visits — The number of campaign URL visits tracked (when someone opens your tracking link). Clicks — The number of LP clicks (when someone clicks a CTA button on your lander to go to an offer). Conversions — The total number of successful conversions recorded. ROI (Return on Investment) — Calculated as ((Revenue - Cost) / Cost) × 100. CR (Conversion Rate) — The percentage of visits that resulted in a conversion. EPC (Earnings Per Click) — Average revenue generated per visit.

Use the date range selector to view metrics for specific time periods. Options include Today, Yesterday, Last 7 Days, Last 30 Days, This Month, Last Month, and custom date ranges.

A campaign is the core unit of tracking. It connects your traffic source to your offers (and optionally landing pages). Each campaign has a unique tracking URL that you use in your traffic source.

Traffic Source — Where your visitors come from (e.g., Facebook, Google, native ad networks). Landing Pages — Optional pre-sell pages shown before the offer. Offers — The affiliate offers you're promoting. Flow — The logic that determines which lander/offer combination to show each visitor.

1. Go to Campaigns → New Campaign 2. Enter a campaign name and select your traffic source 3. Optionally add landing pages with weight distribution 4. Add one or more offers with weight distribution 5. Configure advanced options (geo-targeting, device targeting, etc.) 6. Save and copy your campaign URL

Your campaign URL follows this format: https://your-domain.com/c/{campaign_hash}?sub1={sub1}&sub2={sub2}&cost={cost} Replace the placeholder tokens with your traffic source's macros.

When you have multiple landers or offers, you can set weights to control traffic distribution. For example: Lander A at 50%, Lander B at 30%, Lander C at 20%. This is essential for A/B testing to find your best performers.

A Flow is an advanced traffic distribution system that allows you to create complex routing rules. Instead of simple weight-based rotation, flows let you send visitors to different paths based on conditions like geo, device, OS, browser, and more.

Geo-targeting — Send US traffic to Offer A, UK traffic to Offer B. Device targeting — Show mobile landers to mobile users, desktop landers to desktop users. Day parting — Route traffic differently based on time of day. Custom rules — Create any combination of conditions for precise targeting.

Country, City, Region, Device Type (Mobile/Desktop/Tablet), OS (iOS, Android, Windows, macOS), Browser (Chrome, Safari, Firefox), Language, ISP, Connection Type (WiFi, Cellular), and Sub IDs.

Rules are evaluated in order from top to bottom. The first matching rule wins. Always have a default path at the bottom to catch any unmatched traffic.

A traffic source represents any platform where you purchase advertising. This includes ad networks (PropellerAds, MGID, Taboola), social platforms (Facebook, TikTok), search engines (Google, Bing), and any other traffic provider.

Each traffic source has different URL parameters and macros. By configuring them, you can automatically append the right parameters to campaign URLs, track costs, keywords, placements, and pass the correct click ID format for S2S postbacks.

PropellerAds: Click ID {clickid}, Cost {cost}, Zone {zoneid} MGID: Click ID {click_id}, Cost {cpc}, Widget {widget_id} Facebook: Click ID {{ad.id}}, Campaign {{campaign.name}} Google Ads: Click ID {gclid}, Keyword {keyword}

An affiliate network connects advertisers with publishers. Networks like MaxBounty, ClickDealer, and CrakRevenue host offers that you can promote. The tracker helps you organize offers by network and configure postback URLs.

Each network needs to know where to send conversion data. In your network's dashboard, paste your postback URL: https://your-domain.com/postback?clickid={click_id}&payout={payout}&status={status} Replace the tokens with your network's equivalents.

An offer represents an affiliate product or service you're promoting. Each offer has a URL (where traffic is sent), a payout amount, and is associated with an affiliate network.

The most important part of your offer URL is passing the click ID. This connects a click to a conversion. Your offer URL should include: https://network.com/offer/12345?aff_sub={click_id} The {click_id} token is replaced with the actual click ID when traffic is redirected.

CPA (Cost Per Action) — Fixed payout for each conversion. Revenue Share — Percentage of sale value. CPL (Cost Per Lead) — Fixed payout for lead submissions. CPS (Cost Per Sale) — Fixed or percentage for sales.

A landing page (or lander) is a pre-sell page shown to visitors before they see the offer. Landers help warm up traffic, pre-qualify leads, and significantly increase conversion rates.

Higher Conversions — Pre-sell content increases trust and intent. Better Traffic Quality — Filter out uninterested visitors early. Compliance — Many traffic sources require a landing page. Testing — Test different angles and messaging.

On your landing page, your call-to-action buttons should link to {offer_url}. The tracker will automatically replace this with the actual offer URL, passing along the click ID and all tracking parameters.

Campaign, Offer, Lander, Traffic Source, Country, Device, OS, Browser, Day, Hour, and Sub IDs.

Visits, Unique Visits, LP Clicks, LP CTR, Conversions, CR (Conversion Rate), Revenue, Cost, Profit, ROI, EPC, CPC, and CPA.

Use filters to narrow down data by date range, campaigns, offers, geos, devices, conversion status, and more. Export reports as CSV for further analysis.

Bot Detection — Identifies known bots and crawlers. Data Center Traffic — Flags IPs from data centers. VPN/Proxy Detection — Identifies masked IPs. Click Velocity — Detects unusually fast clicking. Duplicate IPs — Flags repeated clicks from same IP. Deviceglyph — Identifies spoofed devices. Referrer Analysis — Checks for suspicious referrers.

Each click receives a fraud score from 0–100: 0–20: Low risk — Normal traffic 21–50: Medium risk — Possibly suspicious 51–80: High risk — Likely fraudulent 81–100: Critical — Almost certainly fraud

When fraud is detected, the system can: Allow (logging only), Redirect (send to a different URL), or Block (show an error page).

Landing Pages — Compare different designs, copy, and CTAs. Offers — Test multiple offers to find the highest converting. Traffic Flows — Compare different audience targeting. Creatives — Track which ads perform best via sub IDs.

The tracker calculates statistical significance to tell you when results are reliable. Wait for at least 95% confidence before declaring a winner to avoid false positives.

ROI Alert — Notify when ROI drops below threshold. Conversion Alert — Notify on conversion milestones. Spend Alert — Notify when spend exceeds limit. No Conversions — Notify if no conversions in X hours. Traffic Drop — Notify if clicks drop significantly. Fraud Alert — Notify on high fraud score traffic.

Configure how often alerts can fire: immediately, once per hour, once per day, or a custom cooldown period.

Professional appearance, better deliverability (avoid blocklisted domains), brand consistency, and traffic source compliance.

Add a CNAME record pointing your subdomain (e.g., track.yourdomain.com) to our servers, plus a TXT record for verification. SSL certificates are automatically provisioned once verified.

1. User clicks your campaign URL 2. Tracker generates a unique click ID 3. Click ID is passed to the offer URL 4. User converts on the offer 5. Network fires postback with click ID and payout 6. Tracker matches click ID and records conversion

clickid (required) — The click ID passed to the offer. payout (optional) — Conversion payout amount. status (optional) — approved, pending, or rejected.

API keys allow external applications to interact with your tracker programmatically. Use them for custom integrations, automations, and third-party tools.

Never share API keys publicly. Use different keys for different integrations. Rotate keys periodically. Delete unused keys. Use read-only keys when possible.