Plan your onboarding

Use this worksheet at your kickoff meeting with your JustAI team. Record an answer and an owner for each item. You leave kickoff with a plan your marketing, engineering, and data teams can work from in parallel.

Before you begin

• Book the kickoff with your JustAI team. Invite the people who own your marketing programs, your customer data, and the Iterable, Klaviyo, or Customer.io account you send from.
• Bring a short list of the campaigns you want to run first. The first campaign decides which profile fields and events you need.

Line up people and access

Request each item at kickoff. Waiting on an approval later stops work.

• Members and an organization admin in JustAI. Your JustAI team sets up your organization and invites your first members. Make sure at least one of them is an organization admin. Only organization admins can invite the rest of your team from Organization in the account menu, save the company Mailing address in Settings > Delivery, and create environments. JustAI sends no email through Iterable until the mailing address is saved. To check whether you’re an organization admin, open the account menu. Organization admins see Organization in it.
• API access. Your JustAI team turns on API access for your organization. After that, any member can create API keys in Settings > API keys. See Credentials.
• An Iterable admin. You need someone with permission to manage API keys, data feeds, system webhooks, campaigns, and templates in the Iterable project you send from. Your Iterable admin also creates your sending profiles in JustAI, because each one needs a campaign change in Iterable: turning on Ignore Frequency Cap.
• Access to your data source. Your data team needs admin rights in your CDP or reverse ETL tool. For a file import, they need permission to grant read access to an Amazon S3 bucket.
• A test inbox. Pick an email address you can open in a browser where you’re signed in to JustAI. You use it to verify your sending profile. If your organization requires marketing consent, that address needs a granted email consent decision before the test. See Consent decisions in Identify.

Make these decisions

Each decision lists its usual owner. Write the name of the person who owns it next to your answer.

Note

If the left sidebar of the JustAI app shows Onboarding, record these decisions there too. On the Review & finish step, select Finish to send your answers to your JustAI team. The onboarding questions also offer an SFTP file drop and identifying Iterable recipients by user ID. JustAI doesn’t support either, so don’t choose them. Choose the options on this page, and raise anything else with your JustAI team.

While Onboarding is active, the left sidebar lists only the onboarding stages, so Users, Events, and Journeys aren’t there. To open one of those pages, edit the address in your browser: replace the part between the domain name and the ? with /users, /events/custom, or /journeys, and leave the ? and everything after it unchanged. The sidebar lists every page again after you select Finish onboarding on the Onboarding page.

Customer ID

Owner: Engineering

Choose the value JustAI uses as each person’s userId. Use your internal user ID, the stable ID your own systems give each person. Use the email address only if you have no internal ID. Send the same value in every profile update and every event for that person.

See Identity and consent.

Profile fields

Owners: Marketing Data

List the fields your first campaigns need for audiences and personalization, such as plan, signup date, or country. Include email for every person you want to email. JustAI sends email only to people whose profile has an email address, and Iterable finds each recipient by that address. Write down each field name exactly as your source will send it.

See Send customer profiles.

Events

Owners: Marketing Engineering

List the events your first journey needs: the event that starts it, any event it waits for or exits on, and the event you count as a conversion. Agree on exact names. Names match exactly, including case, so Order Completed and order_completed are two different events. Every event that drives a journey needs a userId.

See Send customer events.

Consent and unsubscribes

Owner: Marketing

Decide which system holds each person’s email subscription status and marketing consent. Iterable applies its subscription preferences to the email it sends. JustAI also skips people whose Email subscription is turned off in Users. Confirm how subscription changes are synchronized between your systems with your JustAI team. Test an unsubscribe with an address you control and verify the state in both Iterable and JustAI before launch.

Ask your JustAI team whether your organization requires marketing consent, and for which regions. If it does, JustAI doesn’t email people without a granted consent decision, so plan how to send those decisions in your Identify calls.

See Identity and consent.

Data source

Owners: Engineering Data

Choose how profiles and events reach JustAI: Segment, RudderStack, Hightouch, Amazon Redshift, Amazon S3 file import, CSV upload, or direct calls from your backend. Live events that drive journeys come through the Track API, directly or through Segment, RudderStack, or Hightouch. If you need a file import, your JustAI team must confirm its availability and procedure before you build an export.

See Choose a data source.

Existing customers and event history

Owners: Data JustAI team

Your source sends new changes, but JustAI also needs the customers you already have. Write down:

• How many existing customers to load before launch.
• How to load them: Identify calls from your source or backend, or a customer-specific file import whose availability and procedure your JustAI team confirms before you build it.
• Which environments need them. Each environment starts empty.
• Whether you need past events for history and reporting. Confirm availability and verification with your JustAI team before planning that import. Don’t replay past events through the Track API, because a replayed event whose name matches a published journey starts it.

If you load profiles with Identify calls, finish before you publish any journey whose entry is A profile attribute changes. Each Identify call that changes an attribute can start that journey.

Iterable project and identity mode

Owner: Marketing

Choose the Iterable project JustAI sends from. It must be in Iterable’s US data center. JustAI identifies each recipient to Iterable by email address, so the project must identify users by email. Iterable calls these email-based and hybrid projects. If your project is userID-based, talk to your JustAI team before you continue. Connect each Iterable project to only one JustAI connection, in one environment.

See Connect Iterable.

Environments

Owner: Engineering

Every organization has a Production environment. Decide whether you also want a separate environment for testing. Each environment has its own customer profiles, events, journeys, integrations, and API keys, and a new environment starts empty. If you add one, an organization admin creates it in Settings > Environments. For that environment’s API requests, your JustAI team gives you its path value, which replaces your organization slug in API paths, and its environment key, which you send in the X-JustAI-Environment header. Connect a separate Iterable project to it.

See Key concepts and Environments in the API overview.

Set milestones

Give each milestone an owner and a target date. A milestone is done only when its exit criteria are true.

Milestone	Owner	Done when	Target date
Kickoff	Marketing JustAI team	Every decision on this page has an answer and an owner, and every access request is filed.
API key ready	Engineering	API access is on, and an API key for the environment you send to is stored where your source or backend can use it.
Test data verified	Engineering	One test profile reads back with the expected fields and email, and one test event for the same userId appears in Events > Custom events.
Data source live	Engineering Data	Your source sends real profiles and events, and a spot check of a few people under Users matches your source.
Existing customers loaded	Data JustAI team	Every existing customer you planned to load is in JustAI: the load finished without errors, and a spot check of a few people under Users matches your source. An Identify backfill finished before any journey whose entry is A profile attribute changes was published.
Iterable connected	Marketing Iterable admin	On the Iterable connection, the API key row reads “Key saved”, the Content data feed row reads Data feed #<id>, and the System webhook row reads Webhook #<id>.
Sending profile verified	Marketing Iterable admin	The company mailing address is saved, and the sending profile shows Verified.
Launch ready	Marketing JustAI team	Every item on the launch checklist is checked, and your launch approver signs off.

Define launch readiness

At kickoff, review the launch checklist together, and agree that every item must be checked before launch.

Check your work

Your plan is complete when:

• Every decision on this page has an answer and an owner.
• Every access request is filed, and someone owns the follow-up for each one.
• Every milestone has an owner and a target date.

Next steps

Onboarding quickstartWork through every onboarding step in order.

Choose a data sourceCompare the ways to send customer profiles and events.