If your trigger email notifications are landing in your affiliates' spam folders, it is likely because your domain has not authorized our servers to send messages on your behalf. Setting up a Sender Policy Framework (SPF) is the best way to ensure maximum deliverability and add a professional, personal touch to your affiliate program.
The Role of SPF
An SPF record acts as a security certificate for your domain. Without it, many email providers (like Gmail or Outlook) may flag your automated notifications as suspicious. Your developers can configure this by following our technical setup guide.
Using DMARC?
Larger domains often use DMARC records for an extra layer of security. If you have a strict DMARC policy, validation may fail due to an alignment mismatch between your "From" domain and the sending domain.
A possible solution is to:
Send emails from a specific subdomain (e.g.,
@affiliates.your-domain.com).Create the appropriate SPF record for that specific subdomain.
Implement a more relaxed DMARC record (e.g.,
p=none) specifically for that subdomain to ensure emails are delivered successfully.
Next Steps
Fix Deliverability: Ready to authorize your domain? Follow our guide on Setting up your Sender's Email (SPF) to get started.
Verify Configuration: If you have already added a record but emails are still missing, visit our FAQ: Troubleshooting Sender Email & SPF issues.
Review Automations: Once your emails are landing in the primary inbox, ensure your messaging is effective by Creating Trigger Emails for your affiliates.