Glossary
This glossary defines the terms used across these docs, in alphabetical order. Each entry links to the page that covers the term in depth.
Account name
Section titled “Account name”The name you give an Iterable connection in Settings > Integrations, such as “Iterable production”. Each connection needs a unique account name, and journeys list connections by it. See Add your Iterable project.
Anonymous ID
Section titled “Anonymous ID”The anonymousId field on a Track event. It holds an ID for a visitor you don’t know yet. JustAI records events that have only an anonymous ID, but they never start or move journeys, never count as conversions, and never link to a profile later. The Identify API ignores the field. See Identity and consent.
API key
Section titled “API key”The JustAI secret that authenticates requests to the Identify, Track, and Profiles APIs, and to other JustAI APIs in its environment. You create it in Settings > API keys, and JustAI shows it only once. A key starts with jai_, belongs to the environment that was selected when you created it, and has no per-API scopes. See Credentials.
Attribute
Section titled “Attribute”The app’s name for a trait. Users shows each person’s attributes.
A one-time send to an audience, created from Blasts in the left sidebar of the JustAI app. A JustAI blast isn’t the same as an Iterable blast send.
Blast send
Section titled “Blast send”See Triggered send and blast send.
A customer data platform, such as Segment or RudderStack. A CDP collects calls from your apps and forwards them to other tools. JustAI receives a CDP’s Identify and Track calls through a webhook destination. See Choose a data source.
Configured
Section titled “Configured”The status an Iterable connection shows in Settings > Integrations after its API key, data feed ID, feed token, and system webhook header are in place. Until then, it shows Need Setup. The badge doesn’t check whether the webhook is enabled in Iterable. The connection’s System webhook step does. See Connect Iterable.
Consent decision
Section titled “Consent decision”An entry in the consent array of an Identify call. It records a person’s consent status for email or sms as granted, withdrawn, or unknown, and it applies to the address on their profile. The newest decision wins. See Identity and consent.
Content data feed
Section titled “Content data feed”The data feed in your Iterable project, named JustAI content feed, that Iterable calls to fetch each prepared message from JustAI when it sends. The feed authenticates with a feed token. See Set up the content data feed.
CSV upload
Section titled “CSV upload”The in-app import at Users > Import users. It matches people by email, links each person to your user ID when the file has a user_id column, and takes up to 50,000 rows and 20 MB per file. See CSV upload.
Custom events
Section titled “Custom events”The page at Events > Custom events. It lists the event names that JustAI received in the current environment, with First seen and Last seen times. By default, it shows events received in the last 30 days. New events can take time to appear. See Send customer events.
Customer event
Section titled “Customer event”See Event.
Customer profile
Section titled “Customer profile”The record of one person in an environment: their user ID, email address, and traits. Identify calls and CSV uploads create and update profiles, and Users lists them. A customer profile isn’t a sending profile. See Send customer profiles.
Data feed ID
Section titled “Data feed ID”The number Iterable assigns to your content data feed. You copy it from Iterable’s list of data feeds into the Iterable connection and select Save data feed. You can’t change it after the connection has sending profiles. See Set up the content data feed.
Direct API
Section titled “Direct API”Sending Identify and Track calls from your own backend, without a CDP or sync tool in between. See Direct API.
Environment
Section titled “Environment”A separate space for data and settings inside your organization, with its own people, segments, journeys, events, integrations, and API keys. Every organization has Production, and organization admins can add more in Settings > Environments. A new environment starts empty. See Key concepts.
Environment key
Section titled “Environment key”The value that selects a non-production environment in an API request. You send it in the X-JustAI-Environment header, and you put that environment’s path value in place of the organization slug. Your JustAI team gives you both values. For production, omit the header or send prod. See API overview.
A record of something a person did, such as Order Completed, sent with the Track API. Each event has a name, a messageId, a timestamp, an ID for the person, and optional properties. Events start journeys, end waits, trigger exits, and count as conversions. See Send customer events.
Event triggered
Section titled “Event triggered”A journey entry under Starts when. It starts a run when a matching Track event arrives. The event name must match exactly, including case, and the event needs a userId. See Send customer events.
Exit conditions
Section titled “Exit conditions”The journey setting that decides when people leave a journey before its last step. Everyone leaves after sets a time limit. Or leaves if adds rules, such as a custom event, a profile field, or a segment join. An event ends the run the moment it arrives. See Send customer events.
Feed token
Section titled “Feed token”The secret that lets Iterable fetch content from your content data feed. JustAI generates it when you select Generate token and shows it only once. You paste it into the feed’s Authorization token field in Iterable. Generating a new token stops the old one at once. See Set up the content data feed.
Hybrid project
Section titled “Hybrid project”An Iterable project that can identify users by email or by user ID. JustAI supports hybrid and email-based Iterable projects, because it finds each recipient in Iterable by email. It doesn’t support userID-based projects. See Connect Iterable.
Identify API
Section titled “Identify API”The endpoint that creates or updates a customer profile: POST https://ingest.justwords.ai/api/identify/{org_slug}. It merges the traits you send into the profile and returns 200. See Identify API.
Ignore Frequency Cap
Section titled “Ignore Frequency Cap”An Iterable campaign setting under Delivery settings. Each JustAI campaign needs it on before you select I’ve turned it on in JustAI, because Iterable locks the setting once the campaign is active. See Create a sending profile.
Iterable API key
Section titled “Iterable API key”A server-side key with full read and write access, created in your Iterable project and saved on the Iterable connection. JustAI uses it to set up the system webhook, create templates and campaigns, and trigger sends. See Add your Iterable project.
Iterable connection
Section titled “Iterable connection”An Iterable project added in Settings > Integrations, in one environment. It holds the Iterable API key, the content data feed, the system webhook, and the sending profiles. Connect each Iterable project to only one connection. See Connect Iterable.
Journey
Section titled “Journey”An automated path that people follow in JustAI. People enter through the entry under Starts when, move through steps such as messages and Wait until, and leave when they finish the steps or meet the exit conditions. A draft starts running when you select Publish. See Key concepts.
Key metric
Section titled “Key metric”The conversion event a journey is measured on. You choose it in the journey’s analytics, under Measurement. A conversion counts when the same person, matched by user ID, sends the event after entering the journey. See Send customer events.
Mailing address
Section titled “Mailing address”Your company’s physical mailing address, saved by an organization admin in Settings > Delivery. JustAI puts it in the footer of every email. Test emails and sends are refused until it’s set. See Create a sending profile.
Message ID
Section titled “Message ID”The messageId field, a unique ID for one Identify or Track call. Reuse it only to retry the same call. Track events that share a messageId count once. An Identify messageId reused with different content returns 409. See Errors and retries.
Message type
Section titled “Message type”Iterable’s subscription category for a send. It decides which subscription preferences Iterable applies. On an email sending profile, it’s optional. On an SMS or push sending profile, it’s required, and it also decides which sender or push integration Iterable uses. See Create a sending profile.
Only when
Section titled “Only when”A condition on an Event triggered entry that compares a field in the event’s properties with a value. Values match by type, so the text "14" doesn’t match the number 14. See Send customer events.
Organization
Section titled “Organization”Your company’s account in JustAI. It contains one or more environments. The account menu shows it as <Organization> / <Environment> under your name. See Key concepts.
Organization admin
Section titled “Organization admin”A member who manages your organization in JustAI. Only organization admins invite members from Organization in the account menu, save the company Mailing address in Settings > Delivery, and create environments in Settings > Environments. See Plan your onboarding.
Organization slug
Section titled “Organization slug”The lowercase identifier for your organization in API paths, such as acme in /api/track/acme. Your JustAI team gives it to you at kickoff. In the Production environment, it also appears inside the system webhook and content data feed URLs on your Iterable connection. Other environments use a path value instead. See Key concepts.
Path value
Section titled “Path value”The value that replaces the organization slug in API paths for a non-production environment, for example acme_staging. Your JustAI team gives it to you with the environment key. See API overview.
Profiles API
Section titled “Profiles API”The endpoint that reads one customer profile by user ID: GET https://ingest.justwords.ai/api/profiles/{org_slug}/{user_id}. It returns the saved traits in fields. See Profiles API.
A test send of one journey message, started with Send proof. Email proofs go through a verified email sending profile. SMS and push proofs don’t go through Iterable, so you test those channels from the sending profile. See Create a sending profile.
Properties
Section titled “Properties”The properties object on a Track event. It holds details of the action, such as an order ID or an order value. Journeys can filter on properties with Only when. See Send customer events.
Reverse ETL
Section titled “Reverse ETL”A tool, such as Hightouch, that syncs rows from your warehouse to other systems. With JustAI, Hightouch sends warehouse rows to the Identify and Track APIs. See Hightouch.
One person’s pass through a journey. A run starts when the person enters and ends when they finish the steps or meet the exit conditions. When a message step can’t send, the run shows Not sent with the reason. See Troubleshooting.
S3 file import
Section titled “S3 file import”A customer-specific import to discuss with your JustAI team before exporting files. Confirm availability, format, access, and acceptance checks for your requirements. See Amazon S3 file import.
Segment (audience)
Section titled “Segment (audience)”A saved group of people under Users > Segments. An auto-updating segment uses rules on profile attributes. A fixed-list segment holds the people you pick or upload. An audience segment isn’t the Segment CDP. See Send customer profiles.
Segment (CDP)
Section titled “Segment (CDP)”A customer data platform. JustAI receives Segment’s Identify and Track calls through the Webhooks (Actions) destination. See Segment.
Sending profile
Section titled “Sending profile”The Iterable sender and campaign setup that journeys send through. An email sending profile sets the From email, sender name, reply-to address, and message type. An SMS or push sending profile sets the message type. JustAI creates a matching template and triggered campaign in Iterable, named JustAI · <profile name>. A journey can use a sending profile only after it’s Verified. A sending profile isn’t a customer profile. See Create a sending profile.
Suppression
Section titled “Suppression”A block on email to one person in JustAI, for example after you turn off Email subscription under Edit user. Users shows the person as Email suppressed, and JustAI doesn’t send them email. Confirm with your JustAI team how Iterable unsubscribes are synchronized, and verify subscription and suppression states in both systems before launch. See Identity and consent.
System webhook
Section titled “System webhook”The webhook in your Iterable project that reports sends, skipped sends, bounces, opens, clicks, and unsubscribes back to JustAI. JustAI writes an authentication header into it when you select Set header. See Set up the system webhook.
System webhook header
Section titled “System webhook header”The authentication header that JustAI writes into your system webhook when you select Set header. JustAI rejects webhook calls that don’t carry it. You never copy it. If someone edits or removes it in Iterable, send and engagement events stop reaching JustAI. See Credentials.
Test email
Section titled “Test email”The email you send from a sending profile’s Verify setup card. Its subject is “Confirm your JustAI sending profile”. When you select Click here to confirm while signed in to JustAI, the profile becomes Verified. See Create a sending profile.
Track API
Section titled “Track API”The endpoint that records one customer event: POST https://ingest.justwords.ai/api/track/{org_slug}. It returns 202 when JustAI accepts the event. See Track API.
A fact about a person, such as plan or email, sent in the traits object of an Identify call. Identify merges traits by top-level key and never removes one. The app calls traits attributes. See Send customer profiles.
Triggered campaign
Section titled “Triggered campaign”An Iterable campaign that sends when an API call triggers it. JustAI creates one for each sending profile and triggers it to send each message. See Create a sending profile.
Triggered send and blast send
Section titled “Triggered send and blast send”Iterable’s names for send events in a system webhook. Triggered send reports sends from triggered campaigns, and Blast send reports sends from Iterable blast campaigns. JustAI sends email through triggered campaigns, so your system webhook needs Triggered send turned on for email. Iterable’s blast sends aren’t related to blasts in JustAI. See Events to enable.
User ID
Section titled “User ID”The userId field, your stable ID for a person, sent as a string. Use the same value in Identify calls, Track calls, and file imports. JustAI links events to profiles by user ID. See Identity and consent.
The page in the left sidebar that lists the people in the current environment. Search by email, user ID, or attribute, then open a person to see their attributes, segments, and activity. See Test your connection.
Verified
Section titled “Verified”The status of a sending profile after its test is confirmed. For email, you confirm with the link in the test email. For SMS and push, you confirm with the 6-digit code. Before that, the profile shows Setup needed. See Create a sending profile.
Wait until
Section titled “Wait until”A journey step that holds each person until a profile field matches or one of your events arrives. People who already match skip the wait. See Send customer events.
Next steps
Section titled “Next steps”- Read Key concepts to see how these pieces fit together.
- Look up a problem in Troubleshooting.
