White Label Pixel Setup

Overview

Serve Delivr.ai's pixel JavaScript from a subdomain you own (for example assets.yourdomain.com) instead of the shared CDN, with the same resolution capabilities. Event requests and optional partner calls may still use other hosts, as described below.

Timeline: setup is self-serve in the dashboard, with nothing to schedule with our team. You add the subdomain, publish one DNS record, and verify. The only wait is DNS propagation and certificate issuance, usually minutes and occasionally a few hours.

---

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

• Permission to edit organization settings. Pixel domains are set on the organization, not on a project, and apply to the pixels in every project under it.
• Access to DNS records for your domain.
• A subdomain to use, for example assets.yourcompany.com. Choose a hostname you control and can keep in service. Avoid names containing pixel, ads, track, analytics or cdn, which some ad blockers and privacy tools filter; the dashboard warns you if the name has one.
• An A record on your root domain, for example yourcompany.com. Registration checks for it, as described in the next section.

---

Domain Requirements & Best Practices

Complete these checks before sending traffic to the pixel domain. They help people and reviewers understand what the domain serves, but they cannot guarantee approval by Google or any other scanner.

Publish a useful root page

Self-serve registration currently requires an IPv4 A record on the registrable root (apex) of your chosen domain (for example, yourcompany.com). This is a Delivr.ai setup check, not a published Google requirement. An A record alone does not prove that the website works or that the pixel is safe.

We recommend that the apex serve a useful HTTPS page that explains the domain's purpose and provides a relevant contact or privacy resource. A redirect to a relevant, working page is also reasonable. Open it yourself and confirm it works and does not redirect unexpectedly. An apex with only an AAAA record may serve a website, but it will not pass the current self-serve A-record check; contact support if that is your setup.

Know which hosts receive requests

The white-label hostname serves the pixel JavaScript. Currently, that JavaScript sends website events as JSON POST requests to https://api.sitelytics.tech/pixel/core/api/send-event, even when the script is served from your hostname. Depending on the pixel's cookie and identity settings, it may also request additional partner hosts. Check the browser Network tab for the complete request list before installing it broadly, and account for those destinations in your consent, privacy, and Content Security Policy configuration.

Ad impression beacons are a separate integration from the website JavaScript. The platform's managed DSP impression beacon uses /pixel/core/api/ad-impression and returns a transparent 1×1 GIF. The separate event GET endpoint, /pixel/core/api/send-event/get, can also return a GIF for image requests and may redirect when configured to do so. Do not assume a website pixel script is an appropriate ad creative tag. For Google Ad Manager placements, use the applicable third-party impression tracking URL or third-party creative workflow. Review all outbound calls, macros, and vendor requirements before submitting a creative; Google says it scans creatives and restricts uncertified fourth-party calls.

Review the actual pixel behavior

• Load a test page with browser developer tools open. Confirm the pixel script and event requests use the expected HTTPS hosts, and review any additional scripts or redirects they trigger.
• Review the data that the pixel sends and configure consent and privacy choices for the site where you install it. Include the pixel in that site's privacy notice as appropriate.
• If you deploy through Google Tag Manager, inspect the published container and its third-party tags. Google scans containers for malware and may stop affected tags from firing. Google supports Custom HTML tags, but recommends templates where available. Direct installation does not bypass Google Ads destination review.
• If Google reports a compromised site or unsafe domain, record the exact affected URL and policy detail, inspect the destination and its loaded resources, review the site's Search Console Security Issues report, and use the applicable Google Ads review or appeal process. A warning does not, by itself, identify which resource caused it.

If you are unsure whether your domain is ready, share it with your Delivr.ai contact before you switch your pixels to it. We can review DNS and the expected pixel URLs, but Google makes its own policy decisions.

---

Setup Process

Step 1: Add your subdomain

1. In your organization workspace (not a project), open Settings > Pixel domains.
2. Under Add a pixel domain, enter the full hostname, for example assets.yourcompany.com, and click Add domain.

Registration checks that your root domain has an A record. If it does not, the dashboard says your root domain isn't connected yet: add the A record, then add the subdomain again.

---

Step 2: Point your subdomain at Delivr.ai

The dashboard shows one CNAME record. Add it at your DNS provider:

Type:  CNAME
Host:  [your subdomain, e.g. assets]
Value: [the target shown in the dashboard]
TTL:   300

If your DNS provider proxies records (for example, Cloudflare's orange cloud), turn proxying off for this record. The certificate can only be issued while the hostname resolves directly to Delivr.ai. Keep the record in place for as long as you use the domain.

---

Step 3: Verify

Click Verify. Until DNS propagates, verification reports that the hostname is not pointing to Delivr.ai yet. That is expected: wait a few minutes and verify again. Editing the record restarts propagation, so leave a correct record alone while you wait.

Once the hostname resolves, verification requests the certificate, and the page keeps checking until it is issued.

---

Step 4: Switch your pixels to the domain

A verified domain does not serve your pixels until you switch to it. Click Use this domain and confirm.

Every active pixel is republished to your domain, and install code uses it from then on. Pages already running the previous snippet keep loading it from the previous host, but changes you make to a pixel afterwards reach only the copy on your domain. Replace the snippet on those pages with the new install code.

---

Step 5: Test your setup

1. Open a pixel's Install tab and confirm the script URL uses your subdomain.
2. Install the pixel on a test page.
3. Load the page with browser developer tools open, and confirm the script loads from your subdomain over HTTPS.
4. Confirm events appear in your dashboard.

---

Troubleshooting

---

Support

For issues during setup, contact support or your Delivr.ai account representative.

---

Next Steps

Once your white label pixel is deployed:

1. Account Setup -- Create your first project
2. On-Domain Events API -- Create a pixel and query visitor events
3. Intent Audiences API -- Create intent-based audiences