Custom Domains: White-Label Consent for Agencies and Enterprise

The Ad Blocker Problem

Some browser extensions block requests to well-known consent management domains. No request means no banner, no banner means no consent, and no consent means analytics stays denied by default.

Serving the widget from your own subdomain avoids blocklists that match on third-party consent domains, and it also helps with strict Content Security Policies.

Why Custom Domains Matter

Ad Blocker Compatibility

Many ad blockers maintain lists of known tracking and consent domains. Even though consent platforms help users control tracking, some blockers treat them as tracking infrastructure.

First-party domains bypass these blocks:

• cdn.getcookies.co → may be blocked
• consent.yourdomain.com → typically allowed

White-Label Branding

For agencies serving multiple clients:

• Each client gets their own subdomain
• On the Enterprise plan, white-labeling removes the GetCookies attribution
• Full brand ownership of the consent experience

Enterprise Trust

Enterprise users often scrutinize third-party integrations:

• Security teams prefer first-party resources
• Privacy auditors trust same-domain content
• Procurement questions decrease

Performance Perception

Same-origin requests feel faster:

• No DNS lookup for new domain
• Connection reuse possible
• Browser prioritizes same-origin resources

How Custom Domains Work

Architecture

Default Setup:

Your Website                  GetCookies CDN
    ↓                              ↓
Browser loads page → Requests cdn.getcookies.co/widget.js
                              ↓
                    Returns widget.js

Custom Domain Setup:

Your Website          Your CDN/Proxy         GetCookies Origin
    ↓                      ↓                       ↓
Browser → consent.yourdomain.com → CNAME to  → GetCookies
                     ↓
            Returns widget.js
            (appears first-party)

DNS Configuration

Point your subdomain to our servers with a CNAME record. The exact target is shown on the Branding page in your dashboard:

consent.yourdomain.com CNAME <target shown in your dashboard>

SSL/TLS

Custom domains include automatic SSL:

• Certificate provisioned automatically
• Renewed before expiration
• TLS 1.2+ enforced

Setup Guide

Step 1: Choose Your Subdomain

Common choices:

• consent.yourdomain.com
• privacy.yourdomain.com
• cookies.yourdomain.com
• cmp.yourdomain.com

Step 2: Configure DNS

Add a CNAME record:

Host: consent
Type: CNAME
Value: <target shown in your dashboard>
TTL: 300

Step 3: Verify in Dashboard

1. Go to Branding in the dashboard
2. Enter your subdomain
3. Click Verify DNS
4. Wait for the SSL certificate to be issued

Step 4: Update Widget Script

Change your script source:

Once the domain is verified, the install snippet in your dashboard uses it automatically.

Before:

<script src="https://app.getcookies.co/api/v1/widget/loader.js"
        data-domain-id="YOUR_DOMAIN_ID" async></script>

After:

<script src="https://consent.yourdomain.com/api/v1/widget/loader.js"
        data-domain-id="YOUR_DOMAIN_ID" async></script>

Agency White-Label Setup

For agencies managing multiple clients:

Per-Client Subdomains

Each client gets their own subdomain:

consent.client1.com → Client 1's consent widget
consent.client2.com → Client 2's consent widget
consent.client3.com → Client 3's consent widget

Agency Master Domain

Branding Removal

A custom domain changes where the widget is served from. Removing the GetCookies attribution is a separate white-label option on the Enterprise plan.

Verification and Testing

DNS Verification

Check your CNAME:

dig consent.yourdomain.com CNAME

Expected output:

consent.yourdomain.com. 300 IN CNAME <target shown in your dashboard>.

SSL Verification

Check certificate:

openssl s_client -connect consent.yourdomain.com:443 -servername consent.yourdomain.com

Should show valid certificate for your domain.

Widget Test

Load the widget and verify:

1. Network tab shows requests to your subdomain
2. No requests to getcookies.co
3. Widget functions normally
4. Consent is stored correctly

Troubleshooting

DNS Not Propagating

Symptoms: Verification fails, widget doesn't load

Solutions:

• Wait up to 24 hours for propagation
• Check for conflicting records
• Verify CNAME points to correct value
• Try different DNS (8.8.8.8, 1.1.1.1)

SSL Certificate Issues

Symptoms: Browser security warnings

Solutions:

• Wait 10-15 minutes after DNS verification
• Check for CAA records blocking issuance
• Ensure no existing certificate conflicts
• Contact support if issues persist

Widget Not Loading

Symptoms: Script returns 404 or error

Solutions:

• Verify domain ID in script URL
• Check network tab for actual error
• Ensure API allows custom domain
• Test with default CDN first

Performance Impact

Latency

Custom domains add minimal latency:

• One additional DNS lookup (cached after first request)
• One CNAME resolution step
• Offset by potential caching benefits

Caching

Configure caching headers appropriately:

• Widget JS: Cache with short TTL (1 hour)
• Config endpoints: No cache
• Static assets: Long cache with versioning

Security Considerations

Subdomain Isolation

Use a dedicated subdomain:

• Don't use bare domain
• Don't reuse existing app subdomains
• Keep consent isolated

CSP Configuration

Update Content Security Policy:

Content-Security-Policy:
  script-src 'self' https://consent.yourdomain.com;
  connect-src 'self' https://consent.yourdomain.com;

Cookie Scope

Consent cookies scope to main domain:

• Widget runs on consent.yourdomain.com
• Consent cookie set on .yourdomain.com
• Works across all subdomains

Plans

Custom domains are available from the Starter plan. A custom SLA is available on Enterprise; there is no standard uptime SLA on other plans.

Getting Started

1. Plan: Choose subdomain naming convention
2. Configure: Add DNS records
3. Verify: Complete verification in dashboard
4. Update: Change script sources
5. Test: Verify functionality across sites

Custom domains are about control—control over branding, control over blocking, and control over how consent appears to your users.