Help Center

FAQ: BlueConic first-party hostnames

This FAQ provides additional information on using the First-Party Hostname Console for creating and managing your BlueConic hostnames. For background info and detailed instructions on creating and configuring BlueConic hostnames, see:

What are BlueConic hostnames, and why would I want to use them?

The customer data you collect via BlueConic is first-party data. To ensure that web browsers appropriately recognize your scripts and data as first party, you can create custom first-party BlueConic hostnames for your BlueConic channels. This takes just few steps in the First-Party Hostname Console (FPHC) which guides you through the process of registering the hostname with your DNS provider.


For information on the benefits and importance of first-party data, see BlueConic hostnames overview.

Can I create a first-party hostname for my BlueConic site, or does it require IT?

You can use the BlueConic UI to create a first-party hostname in a few minutes using the First-Party Hostname Console. You will need someone on your IT team to register the new hostname with your DNS provider and place the (updated) BlueConic script on your channel. BlueConic takes care of the rest behind the scenes.

We'll walk you through step-by-step. See instructions for using the First-Party Hostname Console here: Create and configure first-party hostnames.

Can I customize the 4-character hostname the First-Party Hostname Console provides?

Yes but with a few guidelines:

  • You can use the random 4-character string provided or customize it (up to a maximum of 253 characters).
  • Valid characters include: a-z, 0-9 (but not as the first character), and - (but not as the first or last character).
  • Do not use brand names or other identifiable strings that might be misconstrued as third-party hosts.

For detailed steps, see Creating a first-party BlueConic hostname.

What does my IT team have to do?

Your IT team can configure your DNS provider for your new BlueConic hostname(s). You can elect to email the instructions from BlueConic to register your new first-party hostname(s) with your DNS provider. BlueConic will also send email status updates to these addresses. You or your IT team needs to place these DNS records with your DNS provider within 72 hours after creating the BlueConic hostname. See the instructions for IT teams to register DNS records here.

Note: If the BlueConic hostname status shows "Extra validation required," contact your Customer Success Manager for more information.

Where can I find the DNS records for my BlueConic hostnames?

You can download the DNS records for your BlueConic hostnames by opening the First-Party Hostname Console. Choose Settings > Channels & BlueConic hostnames and use the dropdown menu on the Add BlueConic hostname button.
How to download or export custom BlueConic hostname DNS records to my DNS provider

If I have more than one BlueConic channel, can I update each one?

You can make edits or update any number of channels at once.

Will there be any downtime for my existing BlueConic channels during migration?

No, BlueConic will keep running as before the first-party hostname. Once the DNS change is complete, you can change your old BlueConic script with the new BlueConic hostname script that we send to you. In the meantime, the old script will remain functional. There are no changes to your public-facing URLs.

What happens if a migration fails?

If during the First-Party Hostname migration, you receive an error message saying the migration has failed or is incorrect, you will receive an email with the option to revert to the old records in the meantime or make an edit to the new records. 

Will my customer profiles change?

Initially, you may see an increase in profiles because customers whose cookies were blocked will now have profiles. Conversely, infrequent visitors who formerly received a new profile after 7 days of absence from your site, will now have a single profile that persists and updates properly overtime each time these visitors return. 

What happens to my existing customer profiles when I migrate DNS protocols?

  • Customers or visitors with an existing profile who revisit your website after you set up a BlueConic hostname will keep their profile (if the cookie hasn’t expired yet).
  • The original BlueConic script will remain working. When you get the signal to update the script, replace the BlueConic script on the website. In this way, you will have no data loss.
  • If a customer or visitor only visited a subdomain (e.g. before you created a first-party BlueConic hostname, and then visits another subdomain or the main domain (e.g. after you have updated your BlueConic script, it would create a new profile. If the customer first visits the same subdomain (e.g. after the change, their profile is retained.
  • Customers who use a browser or ad blocker that blocks third-party cookies, would not previously have a profile, but will get a new customer profile the next time they visit your site. (However, if this visitor received a first-party cookie from that visit, their existing profile would still be used.)
  • Profile merge rules will apply to visitors' profiles if you've set them up.

How do first-party BlueConic hostnames affect apps?

  • Android apps
    If your Android app uses a native part and a WebView part, we advise setting the cookie on the same hostname so the cookie can be shared between these parts. So if a BlueConic hostname is used on the website, configure its URL in the app.
  • iOS and iPadOS apps
    If your iOS or iPadOS app shows web content, it is required to use WKWebView which has ITP turned on by default. So if you don’t use a BlueConic hostname, the cookie will be capped at 7 days.
  • Ad blockers
    Most ad blockers are a browser plugin or a separate browser. However, there are apps that monitor and control all traffic on a device, such as AdGuard. These are not available in the App Store and require root access. For these ad blockers, it is useful to route all traffic to the BlueConic hostname.

How do I configure an app to use the BlueConic hostname?

You can configure your app to use the BlueConic hostname URL. If your app web content is not hosted on an existing website channel in BlueConic, create a new website channel so you can create a BlueConic hostname.

How can I add the First-Party Hostname Console to my BlueConic tenant?

For information on adding the first-party BlueConic hostname feature to your tenant, contact your BlueConic Customer Success Manager.

Is there guidance for migrating existing first-party hostnames to the new DNS protocol?

Yes, see Migrating existing BlueConic hostnames to the new DNS protocol for tips.

Have additional questions?

See the Troubleshooting Tips for first-party hostnames, and contact BlueConic Support for additional help.

Was this article helpful?
1 out of 1 found this helpful