How onboarding works
Onboarding takes your team from kickoff to a first campaign. It has four stages: plan, connect your data, set up delivery, and launch. Each stage has an owner and a finish line. After planning, the two connection stages can run at the same time, so your data team and the person who administers Iterable, Klaviyo, or Customer.io don’t wait on each other.
The four stages
Section titled “The four stages”Your marketing and engineering teams agree on owners, the customer ID that identifies each person, the profile fields and events your first campaign needs, the data source, the delivery provider, and what launch-ready means. You also request access early. For Iterable, that is someone who can manage API keys, data feeds, system webhooks, campaigns, and templates. For Klaviyo, it is an organization admin in JustAI and a Klaviyo owner, admin, or manager. For Customer.io, it is someone who can create API credentials, reporting webhooks, and a service account. Your JustAI team turns on API access for your organization.
You’re done when every item on the planning worksheet has an answer and an owner.
Connect your data
Section titled “Connect your data”Your engineering or data team sends customer profiles and customer events to JustAI. Profiles describe each person, and events record what they do. Your source can be Segment, RudderStack, Hightouch, a CSV upload, or your own backend. For Redshift, use Hightouch or your backend. Confirm any customer-specific S3 file import with your JustAI team before building an export. Start with one test profile and one test event for the same person, as described in Test your connection, then turn on the full source. Choose a data source compares the options.
You’re done when profiles from your source appear under Users with the fields you expect, and your events appear under Events > Custom events.
Set up delivery
Section titled “Set up delivery”Your delivery admin connects the provider that sends your messages. The steps depend on the provider:
- Iterable. Add the project, content data feed, and system webhook, then verify a sending profile. See Connect Iterable. An organization admin saves your company’s mailing address in JustAI before the test email. You’re done when the sending profile shows Verified.
- Klaviyo. An organization admin connects the Klaviyo account, then creates a sending profile on the shared flow and confirms a test. See Send through Klaviyo. You’re done when the profile shows Ready to send.
- Customer.io. Save the workspace credentials, reporting webhook, and delivery automation, then verify a sending profile. See Send through Customer.io. You’re done when the email profile shows Verified.
Launch
Section titled “Launch”Your marketing team creates the first journey from Journeys in the left sidebar and chooses the verified sending profile in the journey’s settings. To review the emails, they select Send proofs in the journey’s header, or Send proof in an open email step, and check each proof in their inbox. Your JustAI team walks your marketing team through building and proofing this first journey. Together, you work through the launch checklist, and then your marketing team publishes the journey.
You’re done when your first journey is live and named people are watching its data and sends.
How the stages fit together
Section titled “How the stages fit together”Plan comes first. The customer ID you choose shapes every profile and event your data team sends. Iterable and Klaviyo find email recipients by the email trait. Customer.io finds each person by the same ID your workspace already uses. See Choose a delivery provider.
After planning, connecting data and setting up delivery don’t depend on each other. Your delivery admin verifies a sending profile with a test to an address they control, so that setup needs no customer data.
Launch needs both. Send test events early. The journey event picker reads the Events > Custom events list, which shows the event names JustAI received in the last 30 days. Your marketing team can build a journey on an event only after one event with that name has arrived and appears in that list after processing.
Who does what
Section titled “Who does what”| Stage | Your marketing team | Your engineering or data team | Your JustAI team |
|---|---|---|---|
| Plan | Names owners and a launch approver. Picks the first campaign and the fields and events it needs. Decides how consent and unsubscribes work. | Chooses the customer ID and the data source. Confirms which fields and events the source can send. | Runs kickoff and gives you your organization slug. Turns on API access for your organization. Reviews your plan. |
| Connect your data | Spot-checks test profiles under Users. | Creates a JustAI API key, sets up the source, and tests one profile and one event. Then turns on the full source. | Assesses any customer-specific file import before you build an export. Helps when test data doesn’t arrive. |
| Set up delivery | Connects Iterable, Klaviyo, or Customer.io and verifies a sending profile. For Iterable, an organization admin also saves the company mailing address. | Confirms that each customer profile has the email or person ID that provider uses. | Helps when a setup step doesn’t complete. |
| Launch | Builds and reviews the first journey, approves its content and audience, and publishes it. | Watches for API errors and missing data after launch. | Reviews the launch checklist with you. |
What sets your timeline
Section titled “What sets your timeline”There is no standard onboarding duration. These factors set your pace:
- Existing tracking. If Segment or RudderStack already sends Identify and Track calls for your product, connecting data is mostly destination setup and one test cycle. New tracking code adds engineering work.
- Access approvals. Work stops while you wait for Iterable permissions, API access for your organization, or AWS permissions for a file import. Request all of them at kickoff.
- Warehouse work. A warehouse source needs models or exports that match the API or file format JustAI expects. For a customer-specific file import, confirm availability, format, timing, and acceptance checks with your JustAI team before building an export.
- Delivery admin availability. Iterable needs an API key, a data feed, a system webhook, and a campaign setting. Klaviyo needs someone who can approve access and edit flows. Customer.io needs API credentials, a reporting webhook, and a service account. Book a working session with that person.
- Verification. Leave time to compare test profiles with your source, to confirm the test email, and for new event names to appear in Events > Custom events after processing.
For an estimate, ask your JustAI team after they review your plan and a sample of your data.
Get help
Section titled “Get help”To reach your JustAI team at any stage, select Support Portal at the bottom of the app’s left sidebar. See Contact your JustAI team for what to include in a request.
