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: 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

Technical Contact

Domain Configuration

The pixel is deployed at the subdomain you provide. Choose a hostname you control and can keep in service.

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

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 the setup window. We can review DNS and the expected pixel URLs, but Google makes its own policy decisions.

---

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.

1. Receive the validation record details from our team
2. Access your domain's DNS management console
3. Add the provided CNAME record
4. 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:

1. Send the business email addresses you want invited to your Delivr.ai contact.
2. Watch for the invitation email and accept it.
3. 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:

1. Visit https://assets.yourcompany.com (your chosen subdomain). The SSL certificate should be valid
2. Create a test pixel in your dashboard
3. Install the pixel on a test page
4. Verify events appear in your dashboard (check the browser Network tab if nothing shows up)

---

Troubleshooting

---

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:

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