Skip to main content

How to Send Loyalty Emails From Your Own Store Domain

Written by Ateeb

Overview

By default, Casa Loyalty sends notification emails (Points Earned, Reward Redeemed, Referral, Birthday, etc.) from a shared sending domain via our email provider, Mailjet. This is because sending from your own store domain requires domain verification first — you can't send authenticated email from a domain until it's been added and verified with our email provider.

If you want your loyalty emails to come from your own domain (e.g. hello@yourstore.com instead of the shared default), follow the process below.

Step-by-Step Process

  1. Give us the sender email address you want to send from (e.g. hello@yourstore.com). Share this with support.

  2. Verification email sent — our email provider sends a verification email to that address.

  3. Click the verification link in that email, then let support know it's been confirmed.

  4. Approval — once verified, the provider approves the sender address, usually within 24 hours.

  5. You can now use that email as your sender for loyalty notifications.

  6. Add DNS records — support will provide three records to add to your domain's DNS:

    • SPF — an include:spf.mailjet.com value. If you already have an SPF record (e.g. for Google Workspace or another provider), merge this into your existing record — never add it as a second SPF record, as multiple SPF records will cause delivery failures.

    • DKIM — a TXT record under the mailjet._domainkey selector. This value is domain-specific and can only be generated once your domain is added inside our live email provider account, so it's provided after step 1, not upfront.

    • CNAME — used for click-tracking only (so links in your emails show your domain), not for bounce/return-path handling.

Branding / "Powered by Casa" Footer

The "Powered by Casa" footer only appears on older (v1 legacy) email templates. As soon as you edit and save any template — even just customising your own copy — it automatically migrates to the newer template version, and the footer is removed. This isn't tied to any plan tier.

Notes

  • The DKIM value and CNAME target can't be shared before your domain is added on our end — this is the one step that depends on our team rather than your DNS setup, so build in some turnaround time.

  • Only one SPF record should exist per domain. If you already have SPF entries for other tools (Google Workspace, HubSpot, etc.), the Mailjet include needs to be merged into that same record.

  • DKIM records can be added alongside existing DKIM records from other providers — these don't need to replace anything.

Related Articles
Did this answer your question?