Skip to main content
40 answers · 6 sections

The questions people actually ask before they trust a network.

Payout dates, scrub windows, rejection reasons, postback debugging and what we do when traffic goes bad. No marketing hedges — if a number is on this page it is the same number that appears in your dashboard and on your insertion order.

Payout threshold

$0

Rolls over, never expires

Payout cadence

NET-0

Weekly, every Wednesday

Approval rate

0%

Manual review, reasons given

Postback delivery

0%

p95 latency 184 ms

Section 01

Getting started

What the network is, how you get in, and what it costs. Read this section before you fill in an application — most rejections are avoidable.

4,800+ publishers 1,240 live offers 41 geos
AffiliateAdz is a performance marketing and affiliate network. On one side sit 4,800+ publishers with traffic to monetise; on the other, advertisers such as Meridian Fintech, OrbitPay, Kavach Insurance, Playloop Games, Sable Commerce, Nimbus EdTech and Voyara who pay only for defined outcomes. We operate 1,240 live offers across 41 geos on tracking infrastructure we build and run ourselves, and we paid out $24.7M in FY25.
Send an application through the contact form naming your traffic sources, monthly volume, verticals and two example placements. An automated duplicate and domain-reputation check runs in the first two hours, then a partnerships manager reviews it by hand — usually within 24 hours. Our approval rate is 87.4%, and every rejection comes with a reason.
Three reasons account for most rejections. First, undeclared or vague traffic sources — an application that says “various sources” and nothing else cannot be risk-assessed. Second, placements that misrepresent the advertiser, such as fake countdowns, invented approval odds or borrowed brand logos. Third, an applicant domain, payout destination or device fingerprint already linked to a suspended account.
No. Publisher accounts are free: no setup fee, no monthly platform charge, no revenue share taken out of the quoted payout. The number shown on the offer is the number that lands in your ledger. Advertisers carry the network fee, which is why we can keep the publisher side clean.
Five business days is the standard path: commercials and conversion definition on day one, tracking integration and postback QA on days two and three, a soft launch to a small vetted cohort under a hard cap on day four, full release on day five. Programs needing a custom CRM integration, a new mobile measurement partner or regulated-sector legal review run closer to two weeks. We tell you which track you are on at the first call.
Five core verticals: finance (lending, cards, insurance), gaming (casual and mid-core), e-commerce (retail and home), travel (OTA and hotels) and edtech (courses and trials). Traffic splits across 41 geos, led by India at 34%, South East Asia at 14%, the United States at 12%, the UAE at 11%, Brazil at 9% and the United Kingdom at 7%, with 35 further markets making up the remainder.
CPA, CPL, CPS, CPI and CPC, plus hybrid structures that pair a small fixed lead payment with a back-end revenue share. The model is chosen by how cleanly the advertiser can validate the event: CPL suits form-based finance and edtech, CPS suits e-commerce with an order value, CPI suits gaming with an MMP in place. Blended EPC across the network is $0.94.
Section 02

Publishers & payouts

Money questions, answered with dates and numbers rather than “fast payouts”. The cycle closes Sunday night and clears the following Wednesday, every week.

Payout cycle at a glance

SUNCycle closes; approved balance snapshotted.
MON–TUEScrub reconciliation and invoice generation.
WEDNET-7 run released above the $50 threshold.
Payouts run weekly on NET-7 terms and clear every Wednesday. The cycle closes Sunday night; anything that has passed its scrub window and cleared the $50 threshold by then is included in the following Wednesday run. Bank transfers typically land the same or next working day; PayPal and Payoneer are usually instant once released.
$50, or the local-currency equivalent at the rate fixed on the run date. Balances below the threshold simply roll into the next Wednesday cycle and keep accumulating — nothing expires and nothing is forfeited. If you are closing your account, the threshold is waived on the final settlement.
Domestic bank transfer via NEFT, IMPS or RTGS for Indian publishers, plus international wire, PayPal, Payoneer and USDT-TRC20. Wire and crypto network fees are borne by the recipient and shown on the remittance advice before release. Indian publishers are paid against a GST invoice where registered, with TDS deducted at the statutory rate.
The scrub window is the period an advertiser has to validate a conversion before it becomes payable — 7 to 14 days depending on the offer, and always printed on the offer page before you send a click. During that window the earning shows as pending rather than approved. Lending and insurance offers sit at the 14-day end because underwriting decisions take time; e-commerce and gaming usually clear in 7.
Blended network EPC is $0.94, but that average hides an enormous range. Intent-heavy search and comparison traffic on finance offers can run several times higher; broad push and pop inventory on the same offer often runs well below it. Treat $0.94 as a reference point for the network, not a forecast for your placement — your first two weeks of live data is the only number worth planning against.
Yes, and it is routine. Payout bumps are granted on demonstrated quality rather than promised volume, so the conversation goes better after 300–500 clean conversions on the offer. Your affiliate manager takes the case to the advertiser with your approval rate, reversal rate and post-conversion quality attached. Bumps are usually granted as a time-boxed uplift reviewed after 30 days.
Nothing is lost. The balance carries forward automatically to the next weekly run and keeps compounding until it crosses $50. There is no dormancy fee, no expiry and no minimum activity requirement to keep an approved account open. If an account stays inactive for 24 months we write to the registered address before doing anything at all.
Yes. Every rejection carries a reason code, and you have 30 days from the reversal appearing in your ledger to raise a dispute. Send the click ID (aa_xxxxxxxxxxxx) and conversion ID (cnv_xxxxxx) and we pull the raw log line, the postback payload and the advertiser validation file. Where the advertiser cannot evidence the rejection reason, the conversion is reinstated on the next payout run.
Section 03

Advertisers & campaigns

Launching a program, controlling who promotes it, and what happens when the budget runs out. Most advertiser friction traces back to a conversion definition written too loosely on day one.

CPA CPL CPS CPI CPC
Precisely enough that two people reading it would reject the same conversions. “Approved application”, “funded wallet with at least $10”, “first order over $20 excluding shipping” — those work. “Quality lead” does not. Write down the rejection reasons you intend to use at the same time, because a rejection reason invented in week three is the single most common cause of a payout dispute.
There is no contractual floor, but below roughly $2,000 a month a campaign rarely gathers enough conversions to optimise against and you end up paying integration effort for statistical noise. For a first vertical test we usually recommend one geo, one creative set and a hard daily cap for three weeks before widening. That structure costs less and tells you more.
Yes. Offers can run open, private to an allowlist, or tiered so that new publishers start on a capped version and graduate once their quality score holds. You can block individual publisher IDs (PUB-#####), whole traffic-source categories such as push or pop, or specific geos at any time from the dashboard. Blocks apply to new clicks immediately; clicks already in flight are honoured for the attribution window.
The offer flips to paused and stops accepting clicks the moment the cap is hit, and publishers see the status change in the marketplace within seconds. Conversions from clicks sent before the pause are still tracked and paid — we never retro-reject on the basis of a cap. Caps reset at 00:00 UTC unless you ask for a different timezone boundary.
You can pause instantly for compliance or budget reasons, and we would rather you did than let a broken funnel keep taking traffic. For payout cuts and material term changes we ask for 48 hours notice so publishers can retune their buying, and we hold the previous payout for any click already inside the attribution window. Repeated unannounced changes affect how aggressively publishers allocate to you.
Every creative that mentions your brand is reviewed against the compliance pack you supply at onboarding, and publishers may only use approved assets and claim lines. Trademark bidding on your brand terms is prohibited network-wide unless you explicitly whitelist a partner. Our compliance team runs sampled placement checks, and a publisher caught misrepresenting an advertiser is suspended pending review rather than warned.
You receive a conversion file at the end of each calendar month listing every conversion with its click ID, timestamp, publisher ID and status. Your named reconciliation contact signs it off within five working days, and the invoice is issued against the signed file with GST applied where the supply is taxable in India. Standard terms are NET-30 from invoice date; disputes must be raised before sign-off, not after.
Section 04

Tracking & integration

Postbacks, macros, attribution windows, deduplication and rate limits. If a conversion is missing, one of the four checks below will find it.

Postback latency distribution

p50 41ms · p95 184ms
0–25 25–50 50–75 75–100 100–150 150–200 200+ 40% 20% 5%

Milliseconds, sampled over 30 days of production traffic.

Take the postback URL from the tracking tab of your account and store our click identifier when the click lands on your side. When the conversion happens, call the URL server-side with that identifier substituted into the click_id macro. Fire a test conversion from the sandbox first — the log viewer shows the exact request we received, the response code and the latency, so you can confirm the mapping before you spend a rupee.
Work through four checks in order. One: is the click_id you sent the one we issued, or has a redirect chain or URL shortener stripped it. Two: did the call come from a server IP on your account allowlist — calls from unlisted IPs are logged and dropped. Three: did we return HTTP 200; anything else is in the log with the reason. Four: is the conversion being rejected as a duplicate against an identifier you already sent. The postback log answers all four; if it does not, send us the click ID and we will read the raw line.
On outbound clicks we pass the click ID, offer ID (OFR-####), publisher ID, up to five sub-IDs, geo, device type, operating system and a hashed source identifier. On the inbound postback we accept the click ID, an advertiser transaction ID, payout, currency, order value, event name and a status flag for pending, approved or rejected. Every macro is documented with an example call in the integration guide, and unknown parameters are stored rather than discarded so you can add fields without breaking anything.
Last non-direct click by default. The standard cookie and click window is 30 days for web offers and 7 days for app installs measured through a mobile measurement partner, with view-through attribution off unless an advertiser buys it explicitly. Individual offers can shorten the window and the actual figure is printed on the offer page. Where an advertiser runs their own MMP as source of truth, their window governs and ours is set to match.
Each conversion is keyed on the advertiser transaction ID where one is supplied, and on the click ID plus event name where one is not. A repeat of the same key inside 24 hours is recorded as a duplicate and does not create a second payable conversion. This matters most when a pixel and a postback both fire for the same order — the postback wins, and the pixel event is stored as a duplicate for audit rather than silently dropped.
Yes, image pixels and iframe tags are supported for cases where server-side calls are genuinely not possible. Be aware of the trade-off: pixels are lost to ad blockers, browser tracking protection, early tab closure and any page that does not render, so they typically under-report by a meaningful margin. Where an advertiser cannot deploy S2S we cap the offer more tightly and reconcile against their backend file monthly.
REST v2 allows 120 requests per minute per API key on reporting endpoints and 600 per minute on conversion ingestion. Exceeding a limit returns HTTP 429 with a Retry-After header rather than dropping the request; retry on exponential backoff and nothing is lost. Bulk exports should use the asynchronous report endpoint instead of paginating, and outbound webhooks retry on a backoff schedule for 24 hours before being marked failed.
Section 05

Fraud & compliance

The rules that keep advertisers paying and honest publishers earning. Every hold is reviewed by a person before money moves, and every reversal carries a reason code.

No bot traffic No cookie stuffing No trademark bidding DPDP Act 2023 GDPR
Bot, emulator and datacentre traffic; cookie stuffing and forced clicks; auto-redirects that give the user no choice; adult, hate, weapons or piracy placements; creatives that misrepresent the advertiser, invent approval odds or imitate a bank or government notice; trademark bidding on advertiser brand terms; and incentivised traffic on any offer not explicitly flagged as incent-allowed. Toolbars, extensions and adware that inject affiliate links are prohibited outright.
Only on offers carrying the incent-allowed flag, which is set by the advertiser and shown on the offer page. Certain casual gaming and app-install campaigns want it; almost no finance or insurance campaign does, because incentivised leads fail underwriting and pollute the advertiser cohort data. Sending incent traffic to a non-incent offer is treated as a term breach, not a mistake, and the conversions are reversed in full.
Every click is scored in real time on datacentre and proxy IP reputation, device and browser fingerprint entropy, click-to-conversion timing distributions, sub-ID concentration and geo-to-language coherence. Anomalies at the cohort level — a conversion rate that triples overnight, or a publisher whose conversions all arrive within four seconds of the click — trigger a hold rather than an instant reversal. A human reviews every hold before any money moves.
A clawback is the reversal of a conversion that was already approved and paid, and it is deducted from your next payout run rather than invoiced. It applies where the underlying event was fraudulent, duplicated, charged back by the end customer, or cancelled or refunded within the advertiser's stated validation period. Clawbacks are itemised with the conversion ID and reason code, and the same 30-day dispute window applies as for any other reversal.
We act as data fiduciary and controller for our own account and click data, and as processor where an advertiser instructs us on their end-customer data, with the split written into the insertion order. Tracking cookies and device identifiers are only set after affirmative consent, consent state is logged with a timestamp, and cross-border transfers rely on standard contractual clauses. Data principal requests under the DPDP Act 2023, GDPR or CCPA go to the Grievance Officer and are acknowledged within 24 hours and resolved within 30 days.
Payouts are held, not confiscated, and you are told the same day which offer and which metric triggered it. You get 7 days to respond with your own logs, placement screenshots and traffic-source evidence. If the traffic clears, the hold lifts and the balance is released on the next Wednesday run with no penalty. If it does not, the affected conversions are reversed with reason codes and the account is either capped or closed depending on severity.
Section 06

Account & billing

Payout details, tax, multiple accounts, closure and data retention. Housekeeping, but the kind that costs you a week if you get it wrong at the wrong moment in the cycle.

Retention at a glance

Raw click & impression logs24 months
Conversion & payout records8 years
KYC and tax documents8 years
Marketing contact dataUntil opt-out
Update them in the billing tab of the dashboard. Any change to a bank account, PayPal address, Payoneer account or crypto wallet triggers a re-verification step and a 7-day hold on outgoing payments — an anti-takeover control, not a delay tactic. Make changes early in the week if you want the current Wednesday run, and never send KYC documents over WhatsApp.
For publishers resident in India, tax is deducted at source at the statutory rate applicable to the payment and a TDS certificate is issued each quarter. If you are GST-registered, raise a tax invoice with your GSTIN and the payout is settled inclusive of GST at the applicable rate. Non-resident publishers are paid gross and are responsible for tax in their own jurisdiction.
One account per legal entity. If you operate genuinely separate businesses or media properties, ask your manager to open sub-accounts under the same parent so reporting stays separated while the payout ledger stays consolidated. Undisclosed duplicate accounts are treated as an attempt to evade caps or a prior suspension and result in closure of all linked accounts.
Write to the desk from your registered email address and we acknowledge within one business day. Live offers are switched off, the balance settles once the longest applicable scrub window has closed — up to 14 days — and the $50 threshold is waived on that final run. Financial records are retained afterwards for the statutory period; everything else is deleted or anonymised on the schedule in the privacy policy.
Raw click and impression logs are kept for 24 months, which covers the longest attribution window plus the dispute and audit period, then aggregated into non-identifying statistics. Conversion records, invoices and KYC material are retained for 8 years to satisfy Indian tax and company-law obligations. Marketing contact data is deleted within 30 days of an unsubscribe or erasure request.
Still stuck?

Four channels, one New Delhi team.

Pick whichever is fastest for the question you have. Anything with a click ID or conversion ID attached gets answered faster, because we can read the raw log line instead of guessing.

Email the desk

Contracts, invoices, disputes — anything you want on record with a ticket reference.

WhatsApp

Fastest in business hours. Cap changes, offer status, quick payout questions. Never KYC documents.

Phone the office

Monday–Friday, 10:00 AM – 7:00 PM IST. Outside those hours, leave a WhatsApp message.

Integration support

Postback failures, macro mismatches, API 429s and MMP attribution gaps, with logs on screen.

Send the identifiers and skip a round trip

A click ID (aa_xxxxxxxxxxxx), conversion ID (cnv_xxxxxx), offer ID (OFR-####) or publisher ID (PUB-#####) lets us pull the exact log line rather than asking you to describe what you saw. Escalations should carry “ESCALATION — PUB-##### / OFR-####” in the subject line.

Escalation path
Answers, then action

Read all forty? Then you already know how we work.

Applications are reviewed by a person inside 24 hours, campaigns go live in five days, and the payout run clears every Wednesday whether or not anyone chases it.