Setting Up Strike-Based Policies

many brands use a three strike approach for affiliate violations this gives affiliates a chance to correct behaviour while maintaining clear consequences for repeat offenders why use strike based policies? clear escalation path for repeat violations gives affiliates opportunity to explain and correct documents your enforcement process ensures consistent treatment across all affiliates provides evidence trail for network escalations creating your strike system step 1 create three playbooks build separate playbooks for each strike level "hijacking first strike" "hijacking second strike" "hijacking final warning" do the same for brand bidding, voucher sites, or any violation type you want to manage with strikes step 2 define escalating consequences first strike warning email requesting explanation commission cancellation for violation period 3 day response deadline documentation of the violation second strike stronger warning language commission rate set to 0% for a period 2 day response deadline cc affiliate network on communication note "this is your second violation" third strike immediate programme suspension all pending commissions cancelled network escalation (if applicable) permanent removal from programme step 3 set time based rules many brands apply strikes based on timeframes use custom tags to track strike dates "strike 1 15/01/25" see docid\ uobza3bw2zhqbqheglufl for how to create these tags step 4 apply the right playbook when an affiliate reappears in your reports check the advertiser's task history in task manager see which playbook was previously applied apply the next strike level manually document the escalation in task comments checking past warnings all previous tasks remain visible in task manager past playbooks appear under the advertiser when detected again custom tags show violation history comments provide context about previous communications example strike workflow day 1 affiliate detected hijacking → apply "first strike" playbook → tag as "strike 1 15/01/25" day 10 same affiliate detected again → check task history (shows strike 1) → apply "second strike" playbook → tag as "strike 2 25/01/25" → set commission to 0% in network day 20 detected for third time → apply "final warning" playbook → remove from programme → escalate to network managing different violation types you may want different strike policies for different violations hijacking one strike (aggressive enforcement) brand bidding two strikes (clear policy violation) voucher sites two strikes with discussion opportunity create separate playbook sets for each type tips for effective strike policies be consistent apply the same rules to all affiliates, regardless of size or revenue document everything use task comments to note why you applied each strike level communicate clearly make sure your email templates reference previous warnings (e g , "as this is your second violation ") review regularly check task manager weekly for repeat offenders who need escalation set expectations include your strike policy in affiliate programme terms so partners know the consequences