Testing two versions of a message to determine which performs better in Customer.io campaigns.
Tasks performed within a campaign, such as sending an email, push notification, or SMS.
The default 10-second interval at which Customer.io checks for new in-app messages when a user has active messages in the queue.
Segments synced with advertising platforms like Facebook and Google Ads for targeted marketing.
A method to merge two identities, allowing Customer.io to combine data from different sources for the same user.
A custom sender name (e.g., a brand name) used instead of a phone number for sending SMS through Twilio. Not supported in all countries, including the USA.
Adding Customer.io's IPs to a firewall to ensure secure data transfer when using webhooks.
A feature that enables storing and retrieving Customer.io data via Amazon S3.
Actions performed by unidentified users before they are recognized in Customer.io.
Events triggered by users who haven't been identified yet.
In-app messages sent to unidentified users before they are recognized.
Users who have interacted with a Customer.io-tracked touchpoint but are not yet identified.
A method that allows external applications to communicate with Customer.io for data exchange and automation.
The maximum number of API requests allowed within a set time period to prevent excessive load on Customer.io's servers.
Messages sent to a large audience based on an API call, often used for announcements or updates.
An API designed for app-based integrations with Customer.io, enabling mobile apps to send and receive data.
The service used to send push notifications to iOS devices through Customer.io.
A certificate required to authenticate Customer.io when sending push notifications via Apple Push Notification Service.
User details (e.g., name, email, preferences) stored in Customer.io to personalize messaging.
A Twilio authentication credential required to integrate SMS messaging with Customer.io.
Handling multiple users at once instead of processing them individually, improving efficiency in Customer.io workflows.
Information about user actions collected in Customer.io, used for segmentation, targeting, and personalization.
Sending messages based on user interactions, such as page visits, purchases, or abandoned carts, to enhance engagement.
The authorization level required for Customer.io to send messages in Slack, enabling it to act as a bot within a workspace.
One-time messages sent to a segment of users, such as newsletters, announcements, or promotions.
The process of setting up a broadcast in Customer.io, including selecting recipients, defining content, and setting campaign goals.
Sending the same message to a large audience at once, often used for promotions or system-wide notifications.
Events or conditions that start a marketing campaign in Customer.io.
Automated workflows in Customer.io that send messages based on user actions and behaviors.
The sequence of actions within a Customer.io campaign, including messages, data updates, and delays.
The rules that determine when a user should leave a campaign early in Customer.io.
Data tracking how users move through a campaign, including entries, exits, and conversions.
The status of a Customer.io campaign, such as active, paused, or archived.
Labels applied to campaigns for better organization and filtering within Customer.io.
Data tracking the performance of campaigns in Customer.io, including conversions and engagement rates.
The process of choosing a Slack channel during integration in Customer.io. The selected channel isn't used for messages; instead, message channels are set per campaign.
The percentage of customers who stop using a product or service over a given period, often tracked in Customer.io campaigns.
Strategies implemented in Customer.io to keep users engaged and prevent drop-off.
The percentage of users who clicked a link within an email after opening it, measured in Customer.io email reporting.
A method of integrating Customer.io by running JavaScript in the browser to track user activity and identify people in real time.
A DNS record used to set up link tracking for email messages sent through Customer.io.
Groups of related objects used in Customer.io to organize data efficiently.
Standardized fields in Customer.io that provide additional context to debug issues or add special handling in actions.
Rules in Customer.io that determine whether an action should be performed based on user attributes or behaviors.
A tracking feature in Customer.io that marks a campaign as converted if a user performs a specified action.
Monitoring in Customer.io to determine if users complete desired actions, such as purchases or sign-ups.
A setting in Customer.io that allows webhook actions to be counted toward campaign conversion metrics.
A request header in Customer.io webhooks that defines the format of data being sent, such as JSON or XML.
A segmentation option in Customer.io that includes current users and automatically adds new users who meet the set criteria.
A tool for automating and personalizing customer interactions, such as Customer.io.
The default email sending option in Customer.io that uses a shared IP pool and built-in authentication.
The complete experience a user has with a product or brand, often mapped in Customer.io campaigns.
Detailed user information stored in Customer.io for segmentation and personalization.
A platform for sending automated messages based on user behavior, enabling businesses to improve engagement and retention.
A tool in Customer.io to create automated workflows for messaging and engagement.
Platforms that collect, manage, and activate customer data from multiple sources to provide a unified view of each customer, which can integrate with Customer.io.
A prediction of the total revenue a customer will generate throughout their relationship with a business, often tracked in Customer.io analytics.
Grouping users in Customer.io based on shared traits, behaviors, or attributes for targeted messaging.
A feature in Customer.io that allows you to define and track non-person entities, such as accounts, courses, or teams, and relate them to users.
Data formatted in a specific structure when sending webhooks or API requests in Customer.io.
Push notifications in Customer.io that include images, deep links, sounds, or other interactive elements beyond a simple title and body.
Uploading user or event data into Customer.io using CSV files for bulk updates or segmentation.
Adding more details to user profiles in Customer.io to enhance personalization and targeting.
Methods for importing data into Customer.io, such as APIs, integrations, and CSV uploads.
A tool in Customer.io that allows users to view and manage data attributes and events available in their workspace.
The process of matching data fields from one source to another to ensure accurate data integration within Customer.io.
Methods for exporting data from Customer.io to external platforms, such as analytics tools or CRMs.
A feature in Customer.io that enables businesses to send information from websites, apps, and other sources into various destinations without writing custom integrations.
A centralized storage system used for large-scale data analysis, often integrated with Customer.io for reporting and insights.
Customer.io segments that update automatically based on user behavior and predefined conditions.
Reprocessing past data in Customer.io to simulate events or campaigns, often used for testing and optimization.
A workspace-level overview of key performance indicators in Customer.io, such as segment changes, test results, and message engagement rates.
Links within push notifications that direct users to a specific page inside an app instead of opening the homepage, supported in Customer.io campaigns.
Exclusive IP addresses used in Customer.io for sending email campaigns, improving deliverability and sender reputation.
A process in Customer.io that prevents multiple messages from being sent to the same email address when duplicate emails exist in a workspace.
Pauses between actions in a Customer.io workflow, helping to space out messages and optimize campaign timing.
A unique identifier assigned to each message sent from Customer.io, useful for tracking, troubleshooting, and analytics.
An HTTP request type used in Customer.io webhooks to remove an existing record from an external system, such as unsubscribing users or deleting data.
The percentage of messages that successfully reach users' inboxes in a Customer.io email campaign.
External tools where Customer.io sends data for analysis, such as analytics platforms, CRMs, and data warehouses.
A unique identifier assigned to a device for receiving push notifications. It must be registered in Customer.io for successful message delivery.
A setting in Customer.io that cancels all outstanding in-app messages and prevents future in-app messages from being sent.
The process of verifying and authenticating a domain in Customer.io to improve email deliverability and prevent spoofing.
External tools or services that receive data from Customer.io, such as email analytics or reporting platforms.
Message content in Customer.io that changes dynamically based on user attributes, behavior, or other conditions.
The international standard for phone numbers required by Twilio, formatted as [+][country code][subscriber number] (e.g., +14155552671 for a US number) when sending SMS through Customer.io.
The success rate of emails reaching inboxes, a key performance metric in Customer.io's email campaigns.
Customer.io's built-in system for tracking spam complaints, denylistings, and sender reputation to improve email success rates.
Using email to nurture, engage, and convert customers through Customer.io's automated messaging workflows.
Customizing emails in Customer.io with user details like names, purchase history, or preferences to enhance engagement.
The ability to connect external email service providers like Mailgun, SendGrid, and Amazon SES to Customer.io for improved email sending flexibility.
A measure in Customer.io that evaluates how much users interact with messages, helping optimize targeting and content.
Automated messages in Customer.io that are sent when users perform specific actions, such as making a purchase or abandoning a cart.
Events in Customer.io that start automated campaigns when a user completes a predefined action, like signing up or completing a checkout.
Actions performed by users that are tracked in Customer.io, such as signing up, making a purchase, or clicking a link.
Information passed along with an event in Customer.io, such as product name, price, or location, used for personalization and segmentation.
Data fields within an event in Customer.io that provide additional context, such as purchase amount, signup date, or referral source.
The monitoring and recording of user activities or behaviors in Customer.io, which can trigger automated messages or actions.
The process of downloading user or event information from Customer.io for external analysis or reporting.
The conditions in Customer.io under which a user exits a workflow, stopping further automated actions in a campaign.
Messages in Customer.io that weren't successfully delivered due to issues like invalid email addresses, network problems, or authentication errors.
Default content in Customer.io that displays when personalized data is missing or unavailable, ensuring messages remain coherent.
Rules in Customer.io that determine which users receive specific messages based on their attributes or behaviors.
Actions tracked in Customer.io when a user performs them for the first time, often used to trigger welcome or onboarding campaigns.
A feature in Customer.io that limits how often messages are sent to users to prevent overwhelming them.
A method of implementing Customer.io that combines both server-side and client-side tracking for comprehensive user data collection.
A feature in Customer.io that automatically adds users to segments when they meet the defined criteria, even after the segment is created.
An HTTP request type used in Customer.io webhooks to retrieve data from an external source without modifying it.
A feature in Customer.io that tracks whether recipients perform a specific action (such as making a purchase) after receiving a newsletter.
A temporary pause in a Customer.io journey that allows users to rematch campaign conditions before continuing.
An API call in Customer.io that associates a user with a group, such as a company or team, enabling group-based messaging and analytics.
A method in Customer.io to associate a person with a group, like a company or organization, helping to manage group-level data.
Ensuring user data protection in Customer.io under healthcare regulations, particularly for handling sensitive personal information.
Connecting Customer.io with HubSpot to enable seamless marketing automation, data syncing, and customer engagement workflows.
The five supported request types for webhooks in Customer.io: GET (retrieve data), POST (send data), PUT (update data), DELETE (remove data), and PATCH (partially update data).
The process in Customer.io of linking anonymous activity to a known user by assigning a unique identifier.
API calls used in Customer.io to capture information about users and their traits, enabling personalized communication.
Unique data points (such as email addresses or user IDs) used in Customer.io to track and recognize users.
The API method in Customer.io used to add or update a person's attributes, ensuring accurate user data.
A requirement in Customer.io that users must be logged in or identified before they can receive push notifications.
A unique key included in Customer.io webhook requests to prevent duplicate actions from being processed multiple times.
A workflow automation tool that connects Customer.io with other apps and services to trigger actions based on conditions.
The process of bringing external user or event data into Customer.io for segmentation, personalization, and automation.
Notifications sent directly inside a mobile or web app through Customer.io, appearing as pop-ups, banners, or modals.
The feature in Customer.io that enables sending messages within an app to engage users in real-time.
The 60-second interval at which Customer.io checks for new in-app messages when a user has received a message in the last 30 days but has no active messages in the queue.
Persistent in-app messages in Customer.io that function as banners or UI elements rather than disappearing after user interaction.
A holding system in Customer.io where in-app messages wait until a user opens the app or website.
Mechanisms in Customer.io that allow external services to trigger campaigns or send data by making HTTP requests to designated endpoints.
The process of connecting Customer.io with external tools such as CRMs, analytics platforms, and data warehouses.
Various approaches supported by Customer.io for data integration, including client-side JavaScript, mobile SDKs, reverse ETL, and partnerships with Customer Data Platforms.
The process of adding users and their event data to Customer.io directly from a database instead of using client-side or server-side methods.
A requirement in Customer.io where users must manually invite the Customer.io bot using the /invite @Customer.io command before it can post messages in a private Slack channel.
Making a request to Customer.io's API to perform an action, such as adding or updating a user.
The process in Customer.io of gradually increasing email sending volume to establish a positive sender reputation and avoid spam filters.
A security measure in Customer.io that permits access requests only from specified IP addresses, enhancing data protection.
A Customer.io library used to track and identify people on a website using JavaScript, enabling real-time data collection.
A code block added to a website to enable in-app messaging in Customer.io and track user interactions.
Automated workflows in Customer.io that guide users through a sequence of messages based on their behavior and attributes.
Data points in Customer.io that track a user's progress through a campaign, including triggered, started, in progress, completed, exited early, and converted.
The recommended format for sending structured data via Customer.io webhooks, ensuring seamless integration with external systems.
Data structured in JavaScript Object Notation (JSON) format within Customer.io, commonly used for API requests, event tracking, and message personalization.
The process of building relationships with potential customers through automated messaging in Customer.io.
Messaging users at different stages of their journey in Customer.io to guide them from onboarding to retention.
A setting in Customer.io that controls the speed at which messages are delivered to prevent server overload or spamming users.
Tracking user engagement in Customer.io by analyzing clicks on URLs within messages.
A Customer.io feature that records clicks on email links by setting up a CNAME record to ensure accurate engagement reporting.
The process in Customer.io of removing inactive or incorrect email addresses to maintain a high deliverability rate.
A templating language used in Customer.io for dynamic message personalization based on user attributes and event data.
The use of Liquid templating in Customer.io to dynamically customize campaign messages based on user behavior and profile data.
A dynamic variable (e.g., {{customer.channel}}) used in Customer.io to personalize the Slack channel where messages are posted.
A tool in Customer.io for embedding dynamic content in messages to personalize user interactions.
A method in Customer.io for customizing messages using simple code that dynamically adjusts content based on user data.
A Customer.io method for dynamically selecting a phone number attribute (e.g., primary_phone, cell_phone) when sending messages.
The 180-second interval at which Customer.io checks for new in-app messages when a user has not received any messages in the last 30 days.
The choice in Customer.io between sending emails via its shared infrastructure or using a custom SMTP provider for more control.
User-created groups in Customer.io based on specific criteria for targeted messaging.
Uploading a CSV or Google Sheet in Customer.io to manually add people to a segment for campaign targeting.
The process in Customer.io of manually removing a person from an active campaign before it completes.
The ability in Customer.io to trigger webhooks manually from the People page without requiring an automated campaign.
Using Customer.io's software to send targeted messages automatically based on user behavior and data.
A cloud-based email service provider that integrates with Customer.io for sending and tracking emails.
An email platform that allows businesses to send marketing and transactional emails, supported as an external provider in Customer.io.
A transactional email API for Mailchimp users, designed for sending one-to-one emails and compatible with Customer.io email workflows.
The ability in Customer.io to tag Slack users in messages using their unique Slack Member ID format: <@U012AB3CD>.
Combining actions from unidentified users with their Customer.io profiles once they are recognized.
A Twilio-supported message type that includes images (PNG, JPEG, GIF) and supports up to 1,600 characters, usable in Customer.io SMS campaigns.
Different communication methods in Customer.io, including email, SMS, push notifications, and in-app messages.
A filter in Customer.io that determines recipients based on their previous interactions with messages (e.g., opened an email, clicked a link).
A set of analytics in Customer.io that evaluate message effectiveness, including delivery, open, click, unsubscribe, and spam rates.
A system in Customer.io that manages the order and timing of message delivery.
Automatically sending messages in Customer.io based on user actions or pre-defined schedules.
Data in Customer.io that tracks message performance, including delivery, open, and engagement rates.
Tools in Customer.io for analyzing message performance and campaign effectiveness.
A set of tools provided by Customer.io to simplify the integration of push notifications into mobile apps.
Marketing efforts in Customer.io that span multiple platforms, such as email, SMS, and push notifications.
The process of sending messages in Customer.io through multiple communication methods, including email, SMS, in-app, and push notifications.
One-time messages sent in Customer.io to a list of subscribers, often used for updates or promotions.
The specific set of message performance metrics in Customer.io that apply to newsletters, as they are single-send broadcasts rather than ongoing campaigns.
A metric in Customer.io that measures customer satisfaction and loyalty based on their likelihood to recommend a product or service.
User settings in Customer.io that allow individuals to choose which messages they want to receive.
A series of automated messages in Customer.io designed to keep users engaged over time and encourage retention.
Non-person entities in Customer.io, such as a company, account, or subscription, that can be associated with users.
The ability in Customer.io to trigger campaigns based on object data, such as notifying account admins about plan upgrades.
Campaigns in Customer.io that begin when an object (such as an account or subscription) is created or updated.
Using Liquid templating in Customer.io to reference object attributes dynamically in messages for personalization.
Categories of non-person entities in Customer.io, such as products, plans, or subscriptions, used in campaigns.
Associations in Customer.io between people and objects, such as an employee's link to a company or a student's enrollment in a course.
An event in Customer.io triggered when a custom object (like a subscription or product) is modified.
The process in Customer.io of guiding new users through their journey to help them understand and effectively use a product.
A cloud-based email and DNS provider used for delivering transactional and marketing emails through Customer.io.
A feature in Customer.io that enables real-time data transmission to external services or endpoints as part of campaigns or event triggers.
An API call in Customer.io that records a user viewing a web page, useful for tracking page views and user navigation patterns.
Events in Customer.io that track visits to specific web pages and can be used for segmentation and triggering in-app messages.
Conditions in Customer.io set to trigger actions when users visit specific website pages.
A feature in Customer.io that allows users to temporarily stop sending a newsletter and resume it later without modifying the recipient list.
An HTTP request type in Customer.io webhooks that partially updates an existing record without replacing the full dataset.
Contacts or users stored in Customer.io for messaging and segmentation.
The section in Customer.io where users are listed, along with their attributes, segments, and event history.
Tailoring messages in Customer.io based on user attributes and behaviors for improved engagement.
Attributes in Customer.io assigned to a user, such as name, email, and preferences, used for segmentation and targeting.
Data fields in Customer.io (e.g., name, location) used to dynamically customize messages.
The process in Customer.io of customizing messages using user data to make them more relevant and engaging.
The stored phone number data for each user in Customer.io, used for sending SMS messages.
An HTTP request type in Customer.io webhooks that sends data to create a new record in an external system, such as submitting form data or adding new users.
The interval at which Customer.io checks for new in-app messages, adjusted based on user activity.
Advanced third-party connections available in Customer.io for expanded functionality.
The default phone number in Customer.io used for SMS messaging, which can be modified dynamically using Liquid.
Messages sent through Customer.io that appear on a user's mobile or desktop screen for real-time engagement.
Authentication details (e.g., APNs .p8 certificate, FCM JSON key) that authorize Customer.io to send push notifications on behalf of an app.
An HTTP request type in Customer.io webhooks used to update an existing record in an external system, such as modifying user data or updating settings.
Live user activity and event tracking in Customer.io, enabling immediate updates and insights for automation.
Sending messages in Customer.io the moment a specific event or trigger occurs, ensuring timely engagement.
The set of users in Customer.io who will receive a broadcast or newsletter, defined by segment conditions or manual import.
Associations in Customer.io between people and objects, such as users linked to accounts, products, or teams.
An event in Customer.io logged when a relationship between objects (e.g., a user and a subscription) is created or modified.
The process in Customer.io of associating objects like accounts, memberships, or purchases with individuals for personalized messaging and segmentation.
Webhooks in Customer.io used to send campaign performance metrics and data to external platforms for analysis.
The feature in Customer.io that helps identify and merge multiple profiles representing the same user.
The percentage of users in Customer.io who continue engaging with a product or service over a given period, measured to assess user stickiness.
A set of methods in Customer.io designed to keep users engaged, reduce churn, and increase long-term customer value.
Linking Customer.io messages to revenue generation by tracking how marketing campaigns influence purchases and conversions.
A process in Customer.io that extracts data from a data warehouse and loads it into operational tools for better customer engagement and automation.
The endpoint where webhook data is sent from Customer.io, often requiring authentication for secure data transfer.
Data returned by a webhook request in Customer.io that can be stored as customer attributes for segmentation and personalization.
Push messages in Customer.io that contain multimedia elements such as images, videos, and buttons for enhanced engagement.
Syncing Customer.io with Salesforce CRM to enable seamless data sharing and automated workflows.
A security header in Customer.io that uses HMAC-SHA256 encryption to verify that incoming webhooks are legitimate.
An option in Customer.io that allows sending critical updates to unsubscribed users while ensuring compliance with email laws.
The Twilio number used in Customer.io to send SMS/MMS, which can be a short code, toll-free number, or alphanumeric ID.
A feature in Customer.io that allows users to manually send a newsletter to a single recipient after it has already been sent.
A workflow action in Customer.io that triggers webhooks for external data exchange.
The process in Customer.io of grouping users based on attributes or behaviors to target specific audiences effectively.
Automated campaigns in Customer.io that start when a user enters a specified segment.
Data in Customer.io that tracks how the number of users in a segment changes over time.
An API call in Customer.io that records a user viewing a screen in a mobile app, aiding in tracking in-app behavior.
Events in Customer.io that track visits to specific screens in a mobile app, similar to page views for websites.
Tools provided by Customer.io for developers to integrate features into mobile or web applications.
A toolset in Customer.io required for integrating in-app messaging into mobile apps, including SDKs for iOS, Android, React Native, Expo, and Flutter.
Finding specific user profiles in Customer.io based on attributes or behavioral data.
Groups of users in Customer.io categorized by shared behaviors or attributes for better targeting.
The rules in Customer.io that determine which users belong to a specific segment.
Conditions in Customer.io used to group users dynamically based on their interactions and attributes.
Events in Customer.io that represent user actions in meaningful terms, such as "Added to Cart" or "Completed Purchase."
A cloud-based email delivery service that integrates with Customer.io for sending transactional and marketing emails.
A feature in Customer.io that determines and sends messages at the best time for each user based on engagement data.
A method in Customer.io where user data and events are sent from a backend system rather than the client's browser for improved security and accuracy.
The process in Customer.io of connecting with other platforms to automatically add people and track their events.
A 5-6 digit number used for high-volume SMS sending in Customer.io to improve deliverability and recognition.
The interface within Customer.io where users create and format Slack messages, including mentions, links, and custom Liquid variables.
A method of sending emails through an external mail provider while still using Customer.io for automation and reporting.
Predefined keywords (e.g., STOP, UNSUBSCRIBE) that allow users to opt out of receiving SMS messages in Customer.io.
An enterprise-grade email API service that integrates with Customer.io for sending bulk and transactional emails.
A feature in Customer.io that compares two versions of a message or campaign to determine which performs better.
Non-dynamic lists of users in Customer.io that do not update automatically, commonly used for manual segmentation.
The process in Customer.io of saving data in JSON format within user attributes or events for structured storage and retrieval.
A setting in Customer.io that determines whether users receive marketing or transactional emails based on their opt-in status.
A feature in Customer.io that allows businesses to collect user feedback through in-app messages.
Predefined user groups in Customer.io recommended based on common attributes or behaviors.
The process in Customer.io of updating sender phone numbers after changes in Twilio to ensure SMS and MMS deliverability.
The process in Customer.io of comparing different versions of a newsletter or message to determine which performs best before sending to the full audience.
A unique device token in Customer.io used for testing push notifications to ensure proper delivery and formatting.
A feature in Customer.io that allows users to send a real test message before activating a campaign to verify formatting and channel selection.
Criteria in Customer.io based on specific dates and times, used to segment users or trigger actions at the right moment.
The practice in Customer.io of limiting the number of messages sent over a specific period to manage server load and avoid overwhelming recipients.
A system in Customer.io that retries webhook requests up to 10 times with exponential backoff if they fail due to network issues or errors.
A method in Customer.io to record events representing user actions, such as "Signed Up" or "Purchased," along with associated properties.
An API in Customer.io that records customer events and attributes, facilitating the creation of personalized and automated messaging based on user behavior.
System-driven emails in Customer.io, such as order confirmations or password resets, that are essential for user communication.
A Customer.io feature that monitors whether users open emails or click links for engagement tracking and campaign optimization.
Actions in Customer.io that start an automated message, such as a user joining a segment or completing an event.
The rules in Customer.io that determine when a user enters a campaign, based on segment changes, events, or object updates.
A unique identifier for a Twilio account, required for SMS and push notification integration with Customer.io.
A limitation in Customer.io that only supports Twilio credentials from the US region for SMS and push notification services.
A free Twilio account used for initial setup and testing in Customer.io before switching to a paid plan.
User details stored in Customer.io, such as name, email, and preferences, used for personalization and segmentation.
A method in Customer.io that dynamically selects a sender ID based on customer attributes to personalize messages.
Special tracking parameters in Customer.io used to identify the source, medium, and campaign of incoming traffic.
A method in Customer.io for manually importing users by uploading a CSV file to update or add new contacts.
A domain that has been authenticated in Customer.io for sending emails, ensuring improved deliverability, preventing spoofing, and enhancing inbox placement.
A Customer.io feature that sends real-time data to external apps or services in response to specific events or triggers.
Actions within Customer.io workflows that send data to external services or APIs, enabling seamless integration with other platforms.
A feature in Customer.io that allows users to manually trigger webhooks for a person without running a full campaign.
A secret key in Customer.io used to authenticate and verify webhook requests for secure data transfer.
A feature in Customer.io that provides detailed logs of webhook requests, including response status, request payload, and timestamps for troubleshooting and tracking.
Automated sequences of actions in Customer.io triggered by user behavior, designed to streamline messaging and engagement.
The process in Customer.io of setting up automatic message sequences to engage users based on their actions.
An individual environment within Customer.io where teams can manage data, campaigns, and integrations separately from other projects.