This article explains how to configure DNS records for the Opensend CNAME feature. Once you generate your CNAME records in your Opensend account, follow the steps below to add them to your domain’s DNS settings and ensure proper configuration.
Why CNAME?
Modern browsers and ad-blockers increasingly limit cookies and scripts from third-party domains. By routing Opensend tracking through your own subdomain (via CNAME), the cookies and scripts are treated as first-party. This doesn’t increase deliverability or create new data by itself - but it helps prevent us from losing the data we already have by reducing the chance those identifiers are blocked or wiped early.
Why 1st-Party CNAME Matters
- Stronger persistence – Cookies set through your own domain last longer and are far less likely to be cleared by browsers.
- Higher match rates – Keep more of the user IDs and emails you’ve already identified, so fewer valuable identifiers get lost.
- Cleaner profiles – Reduce duplicates and maintain a single, unified identity for each user, giving you sharper segmentation and better personalization.
Follow these steps to set up CNAME records for your domain in Opensend
Step 1 – Generate DNS Records in Opensend
-
Log in to your Opensend account.
-
Go to CNAME Settings.
-
Click Add New CNAME.
-
Enter your website domain and select Generate My DNS Records.
-
Wait a few minutes for the DNS records to be generated.
Opensend will provide three CNAME records:
-
Certificate Validation
-
CDN Domain
-
Tracking Domain
Copy the Name and Value fields exactly as shown. They are case-sensitive and must not be changed.
Step 2 – Log in to Your DNS Provider
-
Sign in to your DNS management console (e.g., Cloudflare, GoDaddy, Google Domains, Namecheap).
-
Open the DNS Settings for your domain.
-
Opensend CNAME Setup Guide for AWS, GoDaddy & Namecheap
-
Step 3 – Create the CNAME Records
For each record provided by Opensend:
-
Type: CNAME
-
Name: Paste the Name exactly (e.g.,
_abc123.acxim.com). Use@if required for root. -
Value: Paste the Value exactly (e.g.,
_xyz987.acm-validations.aws,cdn.example.net,oirt.example.net). -
TTL: Leave as Auto or Default.
-
Proxy: Disable any proxying (e.g., Cloudflare’s orange cloud). Records must be DNS-only.
Example Records (for illustration only)
| Record Type | Name | Value |
|---|---|---|
| Certificate Validation | _abc123.acxim.com |
_xyz987.acm-validations.aws |
| CDN Domain | abc123.acxim.com |
cdn.example.net |
| Tracking Domain | abc123-api.acxim.com |
oirt.example.net |
➡️ You will create three records in total using the values generated in Opensend.
Step 4 – Wait for DNS Propagation
-
DNS updates may take a few minutes to several hours.
-
In Opensend, the record status will show as Pending until propagation is complete.
Step 5 – Verify Records in Opensend
-
Return to the Opensend CNAME setup wizard.
-
Click Verify
-
Verified = records are correct.
-
If you see No CNAME Config Available or Verification Failed, double‑check the Name and Value fields, ensure that proxying is disabled, and wait a bit longer for propagation. You can click on the “Verify” button again to reattempt verification.
If issues persist, regenerate the records in Opensend and re‑enter them or contact our support team for assistance.
-
Step 6 – Enable CNAME Configuration
-
Once verification succeeds, click Submit.
-
Go to Integrations → Opensend Pixel.
-
Enter your domain and enable Use our JS Script.
-
Click Submit.
-
Copy the updated script and embed it into your website.
Step 7 – (Optional) Test with DNS Tools
Run the following command to confirm CNAME resolution:
dig +noall +answer abc123-api.acxim.com CNAME
Example output:
abc123-api.acxim.com. 300 IN CNAME oirt.example.net.
If the expected target is returned, your record is set up correctly.
Conclusion
By adding the Opensend CNAME records to your DNS provider, you enable secure certificate validation, CDN routing, and tracking under your domain. Once verified, you can complete the integration and deploy your Opensend pixel with confidence.