To ensure accurate profile unification and reliable tracking across BlueConic Experiences and CDP profiles, you need to decide how your experiences are delivered. Your experience delivery pattern determines how tracking, cookies, and profile unification work. Some setups are quicker to deploy but limited by browser restrictions, while others ensure first-party continuity. This article explains the delivery patterns, their benefits and how to set them up.

Before you begin

Confirm you have access to both Experiences by Jebbit and the BlueConic CDP.
Review Experiences by Jebbit Connection page for instructions on how to configure the connection in the BlueConic CDP.
Choose your experience delivery pattern: Jebbit.com (not-recommend when Experiences by Jebbit are paired with the BlueConic CDP), custom domain (first-party continuity), or BlueConic first-party hostname (recommended).
Involve IT if you plan to configure a custom domain or use a first-party hostname.
Identify whether you can pass a shared identifier, such as a unique ID or email hash. This is essential for the Jebbit.com hosting delivery.
If you plan to use GA4 or Meta pixel integrations, you’ll need to use either a custom domain or a first-party hostname.

Important: The following delivery patterns apply to full-page launch links.

Compare delivery patterns

When to use	Profile unification	Benefits	Data flow to BlueConic	Use case
Jebbit.com Domain	Separate profiles may exist for the Jebbit domain and your main channel, unless merged. Merging requires a shared identifier (UID/email hash).	No DNS setup required. Fastest to deploy.	Experiences auto-inject the BlueConic script once the connection is authenticated for full-page launch links. BlueConic CDP Script runs on a third party domain. Profile merging requires shared ID. Cross-domain tracking applies to full-page launches.	Getting Experiences online quickly. Small launches without IT.
Custom Domains	One continuous profile (first-party cookie). A first-party hostname must be created in BlueConic that matches the Jebbit custom domain.	Eliminates third-party cookie issues. Required for GA4 attribution and Meta. Reduces CSP issues.	Same connection and script flow as Jebbit.com, but on same origin. BlueConic CDP script and experience run together.	GA4 or Meta integrations. Brand-sensitive launches, allowing full control over subdomain URLs. Enterprise scale.
BlueConic first-party hostname	Delivers perfect cookie continuity.	BlueConic provisions and manages the hostname. Eliminates third-party cookie issues.	BlueConic provisions domain hostname and injects the script. Auto-synced into Jebbit every 10 minutes. BlueConic CDP script and experience run together.	Performance-driven campaigns. GA4 or Meta integrations. Quick to deploy for existing BlueConic CDP users.

Set up by delivery pattern

Jebbit Domain

The experience is hosted on Jebbit’s default domain (exp.jebbit.com). Mapped attributes and quiz results are stored in the BlueConic CDP profile. Because the experience runs on jebbit.com, the profile created there does not automatically match the profile a visitor has on your own site.

Confirm the Experiences by Jebbit connection in BlueConic is authenticated, this enables the auto-injection of the BlueConic script.
In Experiences by Jebbit, go to the Launch tab.
Select the Email / Social link (e.g. https://exp.jebbit.com/).
Place the link in your campaign.
Add a shared identifier (UID or email hash) as a parameter in the launch URL.
Ensure the identifier is preserved and passed back to your brand domain (for example, in a redirect URL). BlueConic can then merge duplicate profiles.

Note: To avoid profile splits or duplicates, consider using BlueConic first-party hostname outlined below ( e.g.,cdp.brand.com) instead of the default Jebbit.com domain.

Custom Domain

The experience is hosted on a customer-owned subdomain (for example, quiz.brand.com) configured with a CNAME pointing to Jebbit. BlueConic injects its script automatically into full-page experiences on that domain.

In your Experiences by Jebbit account, select your brand name in the top right corner and click Settings > Domain configuration and request the custom domain. Admins can request custom domains.
Configure the DNS CNAME records (for example, quiz.brand.com) and wait for validation (DNS propagation may take up to 48 hours).
Publish the experience to the custom domain. Note: Once published, the domain cannot be changed. To switch domains, duplicate the experience and republish.
Copy and use the launch URL in your campaign.

Note: See Configure custom domains for detailed instructions on DNS setup and validation.

BlueConic first-party hostname

The experience is hosted on a BlueConic-provisioned hostname (for example, cdp.brand.com). BlueConic manages DNS and syncs the hostname to Jebbit every 10 minutes once the connection is active.

In BlueConic, go to Settings > Channels & BlueConic hostnames and select the BlueConic hostnames tab and click Add BlueConic hostname button to create a new hostname.
Add the hostname as a new website channel or configure it as an alias of an existing channel to ensure proper profile unification.
Follow the DNS instructions until the hostname reaches READY status.
In BlueConic, activate and authenticate the Experiences by Jebbit connection.
Navigate to your campaign experience. Select your brand name in the top right corner and click Settings > Domain configuration.
Wait for the hostname from BlueConic to sync automatically into Jebbit. Once synced, you will see the status ‘BlueConic Connected’.
The Hostname then appears under Settings > Domain configuration.
Navigate to the Builder Map in your experience and select the Publish button in the top right corner. A modal will then appear.
Under Choose domain for launch links, select the synced first-party hostname.
Publish the campaign
Via the Launch tab, copy the launch link (now on the first-party domain, e.g., cdp.brand.com) and use it in your campaign.

Note: This method is highly recommended.

Next steps

Test your published launch link to ensure profile data appears in BlueConic.

FAQ

Why do profiles split when using Jebbit.com?

The BlueConic script sets a cookie with the profile identifier on the current page domain (jebbit.com) and the blueconic.net domain. If a visitor then browses to your main website, BlueConic cannot read the cookie from the jebbit.com domain and most browsers will also block reading from blueconic.net since it’s a third party domain. This means BlueConic cannot always recognize the same visitor across different domains. Adding a shared identifier in the launch URL can let you merge the profiles in BlueConic.

Do I need to use the CDP first-party hostname?

No. We strongly recommend either using a custom domain or a First Party Hostname domain. Using these options is recommended because it ensures profile unification across your brand’s site and Jebbit experiences. If the CDP script and the Jebbit experience run on different domains, profiles will not unify automatically.