Branding (Custom Domains)

Every publisher can serve the Bidkernel SDK, wrapper tags, and compliance files (ads.txt, sellers.json, floors.json) from their own domain (e.g. ads.yourmedia.com) instead of the default Bidkernel domain. Each account includes up to 3 custom domains; additional hostnames cost $2/month each.

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:

  1. You provide a subdomain prefix. The custom domain must be a subdomain of your property's registered root domain — you enter only the prefix (e.g. tags becomes tags.yourdomain.com).
  2. We provide a CNAME record target. You then enter this CNAME record in your domain registrar's DNS settings, pointing your subdomain to the Bidkernel target.
  3. Automated Provisioning: Bidkernel periodically checks the DNS record. Once we detect the CNAME has propagated, an SSL certificate is provisioned for your custom domain via Cloudflare and traffic is routed automatically.
  4. Graceful Fallback: While the DNS changes are pending (which can sometimes take a few hours), Bidkernel scripts will continue to load and operate from the default domain.

Setup Process Link to section

  1. Navigate to the Branding section under your Property settings.
  2. Enter your desired subdomain prefix (e.g. monetize becomes monetize.mydomain.com) in the relevant field.
  3. Set a CNAME record in your DNS provider pointing your subdomain to the target shown on the Branding page.
  4. Bidkernel evaluates the routing and provisions SSL automatically.
  5. All provided integration scripts and compliance files (ads.txt) switch to your custom domain automatically once SSL is active and the configuration republishes.

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, so traffic routes correctly through Cloudflare's edge.

Confirm Action