Skip to main content

BlueConic Experiences Network Calls and Cookie Information

This article outlines the network calls made when a standard BlueConic Experience loads across different environments. It also covers the default cookies the experience sets, including how they function and how they can be disabled.

Updated this week

Before you begin

Before deploying an experience, consider:

  • Whether it will be hosted by Jebbit, embedded on your site, or placed on a client-hosted page.

  • If custom JavaScript (e.g., tracking pixels) needs to be included.

Network calls

BlueConic-hosted experience page

If your experience is shown through a BlueConic-hosted URL (e.g., https://yourbrand.jebbit.com/abcdefg), you can expect the following tags to fire:

  1. i.jebbit.com/javascripts/...
    Loads any custom JavaScript added by a BlueConic engineer (such as third-party tracking pixels). This call always fires—even if no custom code is included.

  2. i.jebbit.com/fonts/...
    Loads the fonts used in the experience.

  3. i.jebbit.com/images/...
    Loads business images uploaded for use in the experience.

Embedded on site

When you embed a BlueConic Experience directly on your own webpage using an iframe, you can expect to see these tags fire:

  1. yourbrand.jebbit.com/...
    This is the embedded iframe URL. It reflects the specific experience and loads both the visual content and functionality from the hosted experience.

  2. i.jebbit.com/javascripts/...
    Loads any custom JavaScript added to the experience by a BlueConic engineer. This call always fires—regardless of whether custom JavaScript is present.

    • If no script is included, no additional JavaScript is executed.

    • Most commonly used to fire third-party tracking pixels requested by the brand.

  3. i.jebbit.com/fonts/...
    Each of these calls loads a single font that is set to be displayed in the experience.

  4. i.jebbit.com/images/...
    If you have any images you have uploaded to include in the Jebbit experience, this call loads the requested image.

  • external-api.jebbit.com/moments/v2/campaigns is responsible for loading the specific Jebbit experience (images, buttons, functionality, etc.).

  • i.jebbit.com/javascripts holds any custom JS that has been placed on the experience per request.

  • external-api.jebbit.com/moments/v2/campaigns assigns a unique session ID for the user to attach to the HTTP requests made when users interact with the experience.

  • i.jebbit.com/fonts loads any custom fonts for the experience.

Client hosted web page

If you are hosting a BlueConic Experience through your own hosted web page, or a URL that is not hosted by jebbit.com, then the following tags will fire:

  1. external-api.jebbit.com/moments/...
    When you host a BlueConic Experience on your own page, it is shown in an iframe. This call reflects that experience URL and loads the experience and all functionality that comes with it.

  2. i.jebbit.com/javascripts/...
    Loads any custom JavaScript that has been added by a BlueConic engineer. This request always fires. If no custom code is present, no additional scripts are executed.

    • Typically used for third-party tracking pixels requested by the client.

  3. i.jebbit.com/fonts/...
    Each of these calls loads a single font displayed in the experience.

  4. s3.amazonaws.com/jebbit-assets/images/.../business-images
    If you have uploaded business images to use in the experience, this call loads the requested images from Amazon S3.

  • external-api.jebbit.com/moments/v2/campaigns
    Responsible for loading the experience (images, buttons, functionality, etc.).

  • i.jebbit.com/javascripts
    Holds any custom JavaScript added to the experience per request.

  • external-api.jebbit.com/moments/v2/campaigns
    Assigns a unique session ID to the user, which is used in HTTP requests as the user interacts with the experience.

  • i.jebbit.com/fonts
    Loads any custom fonts used in the experience.

Cookies

Classification: Performance

BlueConic Experiences will drop two cookies by default. Both cookies of which are unique identifiers for a given user. A session ID will be updated every time a user enters a new Jebbit experience while the user ID will remain across multiple experiences. Cookies can be turned off per request. Cookie lifespan is 1 year/as long as the browser allows.

  1. Session ID (jebbit_session_id)
    ​

  2. User ID (auth_token)
    ​

Related Articles
Set up Meta pixels and custom Conversions
Track custom GTM events in embedded experiences
Native Embed Developer Guide
Did this answer your question?