White Label & Branding
Brand your report emails with your agency's logo, colours, and sending domain so reports appear to come from you.
ReportsMate lets you brand the report emails with your agency's identity. On Professional plans and above, you can also send reports from your own domain so emails appear to come from your agency rather than ReportsMate.
Basic branding (all paid plans)
Configure under Settings → Agency Profile:
| Setting | Description |
|---|---|
| Agency name | Shown in the email header and footer |
| Logo | Displayed at the top of every report email |
| Website | Linked in the email footer |
| Phone | Shown in the email footer |
| Address | Shown in the email footer |
| Support email | Shown as a contact link in the footer |
Custom sending domain (Professional and above)
By default, report emails are sent from ReportsMate's shared sending domain. With a custom sending domain, emails come from your own domain (e.g. reports@youragency.com), making reports appear completely white-labelled.
Setting up a custom sending domain
- Go to Settings → Sending Domain.
- Enter the domain you want to send from (e.g.
youragency.com). - ReportsMate will provide a set of DNS records to add to your domain's DNS settings.
- Add the provided records to your DNS:
- SPF record (TXT) — authorises ReportsMate to send on behalf of your domain
- DKIM record (CNAME or TXT) — adds a cryptographic signature to prove the emails are legitimate
- DMARC record (TXT, optional but recommended) — tells receiving mail servers what to do with unauthenticated emails
- Click Verify Domain in ReportsMate.
- DNS propagation can take up to 48 hours. ReportsMate will check periodically and update the status.
DNS record types
| Record | Purpose |
|---|---|
| SPF (TXT) | Authorises the sending server — added to your root domain |
| DKIM (CNAME) | Signs emails cryptographically — added as a subdomain record |
| DMARC (TXT) | Defines handling policy — added at _dmarc.yourdomain.com |
If you already have an SPF record, add ReportsMate's include directive to the existing record rather than creating a new one. Having two SPF records on the same domain breaks email delivery.
Domain verification status
| Status | Meaning |
|---|---|
| Pending | DNS records have not yet been checked |
| Verifying | Records found, waiting for full propagation |
| Verified | Domain is ready to use for sending |
| Failed | Records could not be found — check your DNS settings |
Custom sender name and email
Once your domain is verified, configure under Settings → Sending Domain:
- Sender name — What recipients see as the "From" name (e.g. "Reports from Agency Name")
- Sender email — The full from address (e.g.
reports@youragency.com) - Reply-to — Where replies are directed (can be a different address)
Troubleshooting
Verification keeps failing
- Check that you added the records to the correct domain (the root domain, not a subdomain)
- Ensure there are no extra spaces in the TXT record values
- If you use Cloudflare, set the DKIM CNAME record to DNS only (grey cloud), not proxied (orange cloud)
Emails going to spam after setting up custom domain Ensure your DMARC record is set up — even a permissive p=none policy helps. Also check that your domain does not have an existing overly-restrictive DMARC policy that would reject emails from new sending sources.
SPF record conflict You can only have one SPF TXT record per domain. If you already have v=spf1 include:someprovider.com ~all, add the ReportsMate include directive to the same record: v=spf1 include:someprovider.com include:REPORTSMATE_SPF_DOMAIN ~all.