White Label Pixel Setup
Overview
Host Delivr.ai's resolution pixel on your own domain. Your customers see a subdomain you own (for example assets.yourdomain.com) instead of Delivr.ai's CDN, with the same resolution capabilities.
Timeline: 2-3 business days after providing required information.
What You'll Get
- A pixel served from a subdomain you choose (for example
assets.yourdomain.com) - Full SSL/TLS security
- Same resolution capabilities as Delivr.ai's CDN
Before You Start
Have this information ready:
Business Contact
| Field | Example |
|---|---|
| Name | Jane Smith |
| [email protected] | |
| Timezone | EST / GMT-5 |
Technical Contact
| Field | Example |
|---|---|
| Name | John Developer |
| [email protected] | |
| Timezone | PST / GMT-8 |
Domain Configuration
| Field | Example |
|---|---|
| Organization Name | Your Company Inc |
| White Label Domain | assets.yourcompany.com |
The pixel is deployed at the subdomain you provide. Pick one that is available and follows the naming guidance above (avoid
pixel,cdn,track,ads,analytics).
Requirements
- Submit this information at least 48 hours before your target deployment date
- Technical contact must have DNS record access for your domain
- Plan for approximately 30 minutes of coordination time during US morning hours
- Delivr.ai will invite your technical contact to a Slack channel for real-time coordination
Domain Requirements & Best Practices
These keep your white-label pixel from being flagged by browsers, ad blockers, or security scanners. The first item is required before setup; the rest are strongly recommended and improve domain reputation.
Required: your root domain must resolve to a real destination
The root (apex) of your domain (for example, yourcompany.com) must have an A record that points to a working page. A simple 301 redirect to your main website is enough (for example, yourbrand.com redirecting to yourcompany.com).
Without this, the pixel domain can trigger "deceptive site," "uncrawlable destination," or "malicious software" warnings in browsers and security scanners, which break pixel delivery. This is the single most important step.
Recommended
| Guidance | Why |
|---|---|
Avoid words like pixel, ads, track, analytics, or cdn in the hostname where possible. | Ad blockers and reputation scanners filter on these words. A neutral host (for example s.yourcompany.com or assets.yourcompany.com) is less likely to be blocked. |
| Use an established domain. | Very recently registered domains (under roughly six months old) are more likely to be flagged. A domain with some history is safer. |
| Keep WHOIS registration transparent. | Public, accurate registration data improves legitimacy. Fully private or proxied registration can lower trust. |
| Be cautious with international registration. | Domains registered in some regions draw extra scrutiny from security scanners. This will not block setup, but it can affect reputation. |
If you are unsure whether your domain meets these, share it with your Delivr.ai contact before the setup window and we will pre-check it.
Setup Process
Step 1: Certificate generation and validation
What happens: Delivr.ai requests an SSL certificate for your domain.
Your action: Add the certificate validation CNAME record we provide.
- Receive the validation record details from our team
- Access your domain's DNS management console
- Add the provided CNAME record
- Reply to confirm; we wait for the certificate to be issued (usually minutes, occasionally up to a few hours)
Example DNS record:
Type: CNAME
Host: [provided by Delivr.ai]
Value: [provided by Delivr.ai]
TTL: 300
Step 2: Point your domain at our CDN
What happens: Delivr.ai creates your pixel on our multi-tenant CDN and gives you a single target to point at.
Your action: Add one CNAME record from your chosen subdomain to the target we provide.
Type: CNAME
Host: [your chosen subdomain, e.g. assets]
Value: [target provided by Delivr.ai]
TTL: 300
DNS propagation can take up to 24 hours. We verify the certificate and routing before live traffic is switched over.
Step 3: Account Registration
What happens: your Delivr.ai contact creates your organization and links it to the white label pixel, then invites your first user(s) by email.
Your action:
- Send the business email addresses you want invited to your Delivr.ai contact.
- Watch for the invitation email and accept it.
- Sign in at app.delivr.ai. Once you're in, invite the rest of your team from Settings > Members.
Step 4: Verification
Test your setup:
- Visit
https://assets.yourcompany.com(your chosen subdomain). The SSL certificate should be valid - Create a test pixel in your dashboard
- Install the pixel on a test page
- Verify events appear in your dashboard (check the browser Network tab if nothing shows up)
Troubleshooting
| Issue | Solution |
|---|---|
| SSL certificate not valid | The validation CNAME may not have propagated yet. Wait and retry. |
| Domain not resolving | Check the CNAME points to the exact target we provided. |
| No events appearing | Verify pixel script is loading (check browser Network tab). |
| 403 Forbidden | Account may not be linked. Contact support. |
Support
For issues during setup, contact your Delivr.ai account representative or the Slack channel created for your setup.
Next Steps
Once your white label pixel is deployed:
- Account Setup -- Create your first project
- On-Domain Events API -- Create a pixel and query visitor events
- Intent Audiences API -- Create intent-based audiences
Updated 3 days ago