Branding (Custom Domains)

For enterprise tier publishers and advanced setups, you can serve the bidkernel SDK, Prebid bundles, and supply chain files strictly from your own domain (e.g. ads.yourmedia.com) instead of relying on by.bidkernel.io.

Why Custom Domains? Link to section

Ad Blocker Mitigation: Prevents generic ad blocker rules that blindly block third-party scripts.
Brand Consistency: Looks more professional to media buyers inspecting the page network traffic.
First-Party Cookies: Allows first-party cookies if cross-site tracking is restricted.

How it Operates Link to section

When you configure a custom domain in bidkernel:

You provide a sub-domain (e.g., tags.yourdomain.com).
We provide a CNAME record target. You then enter this CNAME record in your domain registrar's DNS settings, pointing your sub-domain to the bidkernel target.
Automated Provisioning: bidkernel periodically checks the DNS record. Once we detect the CNAME has propagated, our infrastructure automatically provisions a secure SSL certificate for your custom domain and routes the traffic seamlessly.
Graceful Fallback: While the DNS changes are pending (which can sometimes take a few hours), bidkernel SDK scripts will gracefully continue to load and operate from by.bidkernel.io.

Setup Process Link to section

Navigate to the Branding section under your Property settings.
Enter your desired subdomain (e.g. monetize.mydomain.com) in the relevant field.
Set a CNAME record in your DNS provider pointing monetize to by.bidkernel.io.
Bidkernel evaluates the routing and provisions SSL automatically.
All provided integration scripts and compliance files (ads.txt) will instantly switch to utilizing your custom domain.

Best Practices Link to section

Use a dedicated sub-domain: We recommend using something like tags.yourdomain.com, ads.yourdomain.com, or cdn.yourdomain.com.
Ensure DNS correctness: Make sure that you only configure a CNAME record, as opposed to an A record, to allow bidkernel's load balancers to effectively handle traffic.