If you have BlueConic hostnames in your tenant that were set up prior to July 1, 2023, there is a simple migration that needs to occur to achieve the benefits of the updated First-Party Hostnames feature. These benefits include:
- Extending cookie lifetime beyond a 7-day timeframe
- Ensuring you can continue to...
- Increase the number of customers with a profile
- Boost site visitor count via a reduction in the number of false unique visitors
- Show dialogues to as many online visitors as possible by reducing the risk that ad blockers mistake the BlueConic script for a third-party script
Note: Existing NS records for the first-party hostname need to be removed before a CNAME record for that same hostname can be added.
Migrating existing BlueConic hostnames to the new DNS protocol
- Access the BlueConic First-Party Hostname Console by clicking the Settings cogwheel icon in the main navigation menu and choosing the Channels & BlueConic hostnames option.
- Once on this page, a submenu will appear and you will click the BlueConic hostnames option.
- Here you will find a list of all the BlueConic hostnames in your tenant. There is a new column in the table labeled DNS migration status. This is where you will find which hostnames need to be migrated according to the new protocols.
- To begin the migration process, click on one hostname at a time. This will bring you to the overview page for that hostname where there is now a DNS migration field. Click the Migrate option.
- A pop-up window appears with instructions for replacing the existing DNS records with new DNS records for your domain. These instructions can be emailed to you, your IT team, or both. They can also be viewed or resent at any time by clicking the buttons next to DNS migration instructions.
Note: We recommend that you let your IT team know about this request to ensure they have the time and resources to help with the process. If you receive an email indicating there are problems, you can either revert to your old records or fix the new records. - You need to complete the entire process within 14 days or the migration will timeout and have to be started again. When a migration is complete, the DNS migration status changes to Migration successful. The existing BlueConic hostnames will continue to work throughout the migration process.
Troubleshooting tips for configuring hostnames
Reverting while troubleshooting
If your DNS records are incorrectly changed, you will receive an email indicating there are problems. Note that you can either revert to your old records or fix the new records.
Remove existing NS records first
Existing NS records for the first-party hostname need to be removed before a CNAME record for that same hostname can be added.
Add the initial underscore for the CNAME validation record
Remember to add the initial underscore for the CNAME validation record, and be sure to use the exact name/value including underscore when entering the CNAME validation record.
If you have questions about any part of this process, see our FAQ or contact BlueConic Support for assistance.