Help Center

BlueConic first-party hostnames overview

The BlueConic First-Party Hostname Console enables you to create a unique, first-party BlueConic hostname for each BlueConic channel. This ensures that web browsers will appropriately recognize your web content, cookies, and the BlueConic script as first party. As web browsers continue to expand their cookie policies and ad-blocking technologies proliferate, first-party data (such as the customer profile data BlueConic collects) becomes even more valuable.

Ensuring your customer data is first-party data

Recent updates to web browser technologies emphasize the importance and value of first-party customer data. The data you collect in your BlueConic unified profiles is first-party data. By establishing a unique hostname for each BlueConic channel, you can ensure that browsers appropriately recognize BlueConic scripts on your site. 

Note that to comply with privacy legislations, data should be collected only when the visitor has given explicit consent. See the Objectives overview for more information on how to set up consent management in BlueConic.

Benefits of creating a first-party BlueConic hostname

There are several important benefits to using first-party BlueConic hostnames:

  • Because cookies set by your domain are first-party cookies, they are not affected by the Apple Safari Intelligent Tracking Prevention (ITP) feature, which deletes third-party cookies after 7 days.
  • BlueConic is not shown on the ITP privacy report.
  • Most ad-blocking technologies will not block scripts that use first-party hostnames.
  • You can continue to unify your first-party data in customer profiles and use that data to personalize and optimize customer interactions.
  • The first-party BlueConic hostname feature provides you with a centralized location to manage your first-party data collection across sites without putting the onus on marketers or IT to coordinate multiple domains, manage various databases for each domain, or maintain certificates. 

To learn more about how BlueConic works with cookies and browser technologies see our FAQ: BlueConic, cookies, and ITP.

Migrating existing first-party hostnames

For instructions on migrating an existing BlueConic hostname, see our migration guide: Migrating existing BlueConic hostnames to the new DNS protocol.

Adding a first-party BlueConic hostname for each channel

The First-Party Hostname Console provides a simple UI for you to create a customized first-party hostname for each BlueConic channel in your tenant. To do this, open the Settings menu for BlueConic channels and hostnames. As part of this process, BlueConic will generate DNS records for your domain, which your IT team will need to register with your DNS provider (for example, in Route 53 for AWS-hosted domains) within 14 days. This process works with any DNS provider. Contact your BlueConic Customer Success Manager if you have questions.


Before you begin, we recommend that you contact your IT team to share this information with them ahead of time.

If you have questions about using the First-Party Hostname Console (FPHC), contact BlueConic Support for assistance.

Migrating an existing BlueConic hostname? See our migration guide: Migrating existing BlueConic hostnames to the new DNS protocol.

Next step: Create and configure BlueConic hostnames




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