🚀 Onboarding Knowledge Hub

How this guide works: Each section is a milestone. Complete them in order. Most steps link to deeper articles if you want to go further, but you don't have to. The goal is your first experience live, not perfection.

Before you dive in, here's the full picture. The main build path runs left to right. Data connections run in parallel — start that conversation early so it doesn't delay your launch.

Before you dive into the steps below, we strongly recommend registering for BlueConic University. It's where your training lives, and courses are linked throughout this guide.

💡 Total watch time: ~60 minutes. Watch one module at a time between meetings — by the time you're ready to build, you'll already feel at home in the platform.

The biggest reason first experiences stall isn't the platform. It's going in without a clear plan. Five minutes here saves hours later.

Answer these questions before you build:

💡 Pro tip: You don't need a perfect experience. You need a launched experience. A simple 4–7 screen quiz with a clear goal will always outperform a complex build that never ships.

Recommended for first-timers: Start with a quiz or survey. They're fast to configure and consistently drive strong engagement.

🎓 BlueU Course: Introduction to Jebbit | 🎓 BlueU Course: Configure Brand Environment

Time: ~30 minutes | Do this once

Your Style Guide is the foundation. It controls how every experience looks — fonts, colors, buttons, logo, and backgrounds. Setting it up now means you won't have to style each experience from scratch.

What to gather before you start:

How to set it up:

⚠️ Don't skip this step. Style Guide setup often requires input from your design or brand team. Get it done early so it doesn't block your build later.

🎓 BlueU Course: Setting Up your Style Guide

📎 Style Guide Overview | 📎 Design Spec Sheet

Time: ~5–10 minutes

Before you build anything manually, try the AI Builder Agent. It can generate a complete experience — screens, copy, structure — from a simple text prompt. Think of it as your head start.

How to access it:

Example prompts to try:

"Create a skincare quiz that asks about skin type and concerns, then recommends 3 products."

"Build a 5-question personality quiz about home decor style with 4 outcome types."

"Create a survey to collect feedback on our loyalty program."

What the AI gives you:

What you'll still do:

💡 The agent doesn't replace your strategy. It gives you a head start. The more specific your prompt, the better the output.

📎 AI Building Agent Overview | 📎 Prompt Starter Library

Time: Varies | Recommended: 60+ min/week

Whether you used the AI agent to get a draft or you're starting from scratch, here's how the build process works.

You'll land in the Screen Library, where you can add and organize screens.

🎓 BlueU Course: Introduction to Building Experiences

Use the Screen Library to add screens. Types include:

Recommended first experience structure (5–7 screens):

💡 Make the value exchange clear from screen 1. Tell users what they'll get for completing the experience (a personalized recommendation, a discount, exclusive content, etc.).

To edit any screen:

🎓 Introduction to Experience Flows

📎 Screens Overview

This is the most important concept to understand before you build.

Every screen in XP has two layers:

Key rule:

Two core screen setups:

Layout options: Within each setup, you have layout options that control how the Primary and Secondary sections are oriented and sized relative to each other.

⚠️ Common mistake: Uploading images with text or logos in the Secondary Background. This creates accessibility issues and limits flexibility across screen sizes. Always put text in the Primary layer.

⚠️ Another common mistake: Designing only for desktop without checking mobile. Toggle between views in the editor — layouts adapt automatically but spacing and font sizes may need adjustment.

Logic is how the platform connects a user's answers to personalized results.

💡 Start with Matching or Scoring for your first build. DPF is powerful but requires more lead time and planning. Your team can help you determine the right fit.

To set up Matching outcomes:

🎓 BlueU Course: Introduction to Experience Logic

🎓 BlueU Course: Introduction to Dynamic Product Feed

📎 Matching Outcomes | 📎 Logic Types Deep Dive | 📎 Prepare Your Dynamic Product Feed

Attributes are how you capture and store what users tell you. Every question-answer pair should be mapped to an attribute so the data is collected and available in reporting.

💡 Think of attributes as the "fields" in your database. If someone answers "Dry" to a skin type question, that answer should map to a skin_type attribute with a value of dry.

📎 Attributes Overview →

⚠️You don't need this done to finish your build, but don't wait until launch week to start it.

The data your customers share through your experience — their preferences, quiz answers, contact info — is only as valuable as what you do with it. Data connections are how that information flows automatically into the platforms your team already uses: your ESP, CRM, CDP, or analytics tools.

This is what turns a quiz into a first-party data engine.

Why it matters: Without a connection, results live inside XP — useful, but siloed. With one, every response flows into your marketing stack to power segmentation, personalization, and follow-up campaigns automatically.

Who owns this? If you're the marketer building the experience, data connections are likely not yours to configure alone. Most integrations require a technical contact — someone with credentials and access to your ESP, CRM, or data platform.

Your job right now, while you're still building: Identify that person and loop them in. The earlier this conversation starts, the less likely it is to delay your launch.

What types of connections are available?

💡 Most teams start with one native integration (typically their ESP) and one pixel (typically GTM or Meta). That covers personalized follow-up email and ad optimization from day one.

📎 Full Integrations Overview →

What to do now vs. later

You (while building):

Your technical contact (before launch):

⚠️ Timing note: Non-self-service integrations (API and Batch File Transfer) can take up to two weeks once all details are finalized. Starting this conversation during the build phase, not the week before launch, keeps you on track.

A note on pixels

Pixels are lightweight but placement matters. Each fires on a specific screen event (view, completion, lead capture) and sends that signal to your ad or analytics platform.

Common use cases:

💡 If your team already uses GA4 that's usually the fastest path — provides a direct way to send data on screen visits, responses, leads, and add-to-cart events.

📎 Add GTM & GA4 Pixels → | 📎 Add Meta Pixels →

Time: ~20–30 minutes

Before you publish, walk through your experience the same way your customer will.

QA Checklist:

Go to Builder Map → Preview and click through the full experience.

💡 Preview Links:

📎 Launch Checklist | 📎 Launch Overview

These are two separate steps — don't confuse them.

Publishing pushes your live version to the launch link. It does not make your experience visible to customers yet. You only need to generate launch links once — republishing updates the same link.

Launching is how customers actually find your experience. You own the actual launch of the experience.

To launch:

📎 Launch Article Collection

Once you're live, head to the Reporting tab to track performance. Key metrics to monitor:

💡 Give it time. Most experiences need at least a few hundred views to identify meaningful trends. Once you have data, use it to iterate — adjust copy, test a different intro screen, or refine your outcome logic.

📎 Analytics Overview | 📎 Campaign Status Definitions | 📎 Reporting Collection Guide