https://docs.customer.io/Recent content on Customer.io DocsHugo -- gohugo.ioen-ushttps://docs.customer.io/integrations/directory/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/directory/contenthttps://docs.customer.io/journeys/message-channels/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/message-channels/ This section is about messages If you want to know about campaigns, broadcasts, or transactional messages—the mechanisms in Customer.io that actually trigger workflows and messages—you should go here. Channel Campaigns API-Triggered Broadcasts Newsletters Transactional Email Push In-app Inbox messages SMS WhatsApp Slack Webhooks Email Our most common and customizable platform. We support several email service providers (ESP), or you can use your own, custom SMTP server. You can send email through any workflow or trigger type in Customer.https://docs.customer.io/journeys/objects-start/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/objects-start/This page covers object types and objects. Object types are the kinds of non-people things that you want to track in Customer.io—like companies, online classes, accounts, etc. An object is an individual thing—a single company, online class, or account—that you want to relate to one or more people.  Check out our plans and how we bill to learn more about object pricing. How it works Objects let you group and relate data to people in your workspace, like accounts that people belong to, flights they’ve booked, or online courses they’ve enrolled in.https://docs.customer.io/journeys/subscriptions-overview/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/subscriptions-overview/Native unsubscribe links for emails, SMS, WhatsApp, and push In Customer.io, you can use our default global unsubscribe functionality or set up a subscription center to manage which messages your customers receive. We recommend you create a subscription center to give your customers the option to receive messages they’re interested in without opting-out of all of your messages. flowchart LR c{Is unsubscribed true?} c-....->|yes|f[Person is only eligible for in-app or Slack messages] c-->|no|g{Is the subscriptionhttps://docs.customer.io/journeys/getting-started-objects-collections/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/getting-started-objects-collections/How it works Customer.io revolves around people. You identify people, set their attributes, and send events representing the things that they do on your websites or in your apps. But you might want to maintain some data independently of people and associate this data with people later. Maybe you manage multiple accounts, and people can belong to one or more accounts; or people in your environment can enroll in educational courses; or you might manage recreational sports leagues that people can join.https://docs.customer.io/journeys/using-liquid/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/using-liquid/ New to liquid? Check out our tutorial for marketers! Our tutorial can help you understand the fundamentals of message personalization and how to use your data to send engaging messages that increase conversion rates. When you’re ready, you can find examples of liquid for a variety of use cases in Liquid recipes. How it works Liquid lets you use variables and other logical statements in messages to personalize content. These can be customer attributesA key-value pair that you associate with a person or an object—like a person’s name, the date they were created in your workspace, or a company’s billing date etc.https://docs.customer.io/integrations/getting-started/quick-start-guide/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/getting-started/quick-start-guide/1. Set up your JavaScript integration Our JavaScript client feeds data from your website into Customer.io. You’ll add *data inAn integration that feeds data into Customer.io. integrations for every system or touchpoint you want to collect data from. Go to Data & Integrations > Integrations and click Add Integration. Select our JavaScript integration. Enter a Name for the integration and click Submit. You should give your integration a name that helps you and your teammates understand the resource you’re capturing data from—like “company website” or “community forums.https://docs.customer.io/journeys/components-overview/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/components-overview/In Design Studio, you can use our out-of-the-box Standard Components and create your own Custom Components. Standard components Standard components are pre-built blocks that help you build beautiful, engaging messages as quickly as possible. They are the backbone of Design Studio messages — headings, paragraphs, buttons, sections, and more. You’ll see a list of available standard components in the insert menu of the visual editor. Once you’ve dragged a component onto the canvas, you can style it by adjusting the component’s properties.https://docs.customer.io/journeys/custom-comp-syntax/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/custom-comp-syntax/ Use our Design Studio GPT to create a custom component! Learn how to best utilize our GPT to create code for reusable, custom content. Required top-level syntax You must include both <script> and <template> tags in your custom component file. The <script> tag handles logic, properties, and configuration for the component. In the <script> tag, you can: Write JavaScript logic to help render your <template> HTML. It supports the full JavaScript run-time.https://docs.customer.io/journeys/design-studio-overview/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/design-studio-overview/In Design Studio, you can: Build emails with our visual, block-based editor. You can also modify the HTML/CSS as you see fit by switching to the code editor! Build emails using reusable blocks. We offer out-of-the-box blocks called standard componentsA pre-built block that helps you build beautiful, engaging messages as quickly as possible in Design Studio.. You can also create your own reusable blocks called custom componentsA custom block of code with content and properties you can reuse across messages made in Design Studio.https://docs.customer.io/journeys/workflow-builder/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/workflow-builder/Campaign settings: edit the name, goal, exit conditions, and message settings. Build menu: drag and drop message and action blocks onto the canvas to create your workflow. Canvas: drag blocks here to add them to your workflow. The canvas flows top to bottom. Builder features: open/close the build menu, zoom in or out, add a sticky note for your teammates, export an image of your workflow, or review keyboard shortcuts.https://docs.customer.io/integrations/sdk/flutter/whats-new/4.0.0-upgrade/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/flutter/whats-new/4.0.0-upgrade/What changed? Version 4.0.0 of the Flutter SDK adds Swift Package Manager (SPM) support as an alternative iOS dependency manager. SPM is Apple’s built-in package manager with native Xcode integration, so you don’t need to manage a separate Podfile for Customer.io dependencies. When SPM is enabled, the SDK is automatically resolved - no manual Xcode package setup needed for the main app. CocoaPods continues to work. If you want to stay on CocoaPods, you don’t need to change anything.https://docs.customer.io/integrations/sdk/react-native/whats-new/6.4.0-upgrade/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/whats-new/6.4.0-upgrade/What changed? Version 6.4.0 adds support for App Groups, which improves the reliability of push delivery metric tracking on iOS. This update is additive—your existing integration continues to work without changes. However, to take advantage of App Groups, you’ll need to update your Xcode project configuration and regenerate provisioning profiles if you use manual signing. Why App Groups? When you send a push notification, the SDK tracks delivery metrics in your Notification Service Extension (NSE).https://docs.customer.io/journeys/insert-components/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/insert-components/Insert components You can add standard or custom components to your message by dragging them onto the canvas from the visual editor’s Insert menu. Standard Components appear at the top of the menu. Collapse the folder and you’ll see Custom Components immediately below. If you haven’t created custom components, you’ll only have the option to drag in standard components. Click and hold any component then drag and drop it onto the center canvas.https://docs.customer.io/journeys/campaign-changes/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/campaign-changes/Both trigger and filter conditions must be met for people to start moving through your campaign’s workflow. Some campaigns types — event, form, important date, legacy segment, and attribute or segment — have a frequency setting which controls how many times the same person can enter a campaign. By default, it’s once.  If you edit a trigger or filter and expect people to re-enter a campaign, make sure you check your frequency setting.https://docs.customer.io/journeys/keyboard-shortcuts/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/keyboard-shortcuts/There are a number of keyboard shortcuts you can use to access Design Studio functionality. You can see a full list of shortcuts at any time by clicking the Shortcuts button in the bottom right corner of the code editor. Any shortcut that uses CMD on Mac will use CTRL on Windows (and vice versa). General Name Shortcut Toggle Preferences CMD/CTRL , Toggle Sidebar CMD/CTRL SHIFT B Editors Editor management Name Shortcut Close current editor OPTION W Formatting Name Shortcut Wrap Bold CMD/CTRL B Wrap Italics CMD/CTRL I Wrap Underline CMD/CTRL U Basic editing Name Shortcut Cut line CMD/CTRL X Copy line CMD/CTRL C Paste line CMD/CTRL V Move line up OPTION ↑ Move line down OPTION ↓ Basic editing - Code editor only Name Shortcut Copy line up SHIFT OPTION ↑ Copy line down SHIFT OPTION ↓ Delete line CMD/CTRL SHIFT K Indent line CMD/CTRL ] Outdent line CMD/CTRL [ Toggle line comment CMD/CTRL / Fold current region CMD/CTRL K CMD/CTRL [ Unfold current region CMD/CTRL K CMD/CTRL ] Preview - Code editor only Name Shortcut Toggle Preview CMD/CTRL SHIFT D Toggle Inspect Element CMD/CTRL SHIFT C Toggle Focus Mode CMD/CTRL SHIFT M Find & replace - Code editor only Name Shortcut Find CMD/CTRL F Replace CMD/CTRL OPTION F Find Next CMD/CTRL G Find Previous CMD/CTRL SHIFT G Select all matches OPTION Enter Multi-cursor & selection - Code editor only Name Shortcut Insert cursor OPTION + Click Insert cursor above CMD/CTRL OPTION ↑ Insert cursor below CMD/CTRL OPTION ↓ Select current line CMD/CTRL Lhttps://docs.customer.io/integrations/data-in/connections/cdps/segment/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/cdps/segment/ Do you have a standard Segment destination? This page helps you use Customer.io with Segment’s “destination actions” feature. If you’re using Segment’s classic integration with Customer.io, and you don’t want to upgrade, see the Segment Destination (classic) page. Unlike our standard Segment Destination integration, the Destination Actions integration supports anonymous events. Segment’s Destination Actions feature lets you filter the events that you send to Customer.io, helping you determine exactly what data you want to send to your destination.https://docs.customer.io/integrations/sdk/flutter/whats-new/3.5.0-upgrade/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/flutter/whats-new/3.5.0-upgrade/What changed? Version 3.5.0 adds support for App Groups, which improves the reliability of push delivery metric tracking on iOS. This update is additive—your existing integration continues to work without changes. However, to take advantage of App Groups, you’ll need to update your Xcode project configuration and regenerate provisioning profiles if you use manual signing. Why app groups? When you send a push notification, the SDK tracks delivery metrics in your Notification Service Extension (NSE).https://docs.customer.io/integrations/sdk/react-native/whats-new/6.x-upgrade/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/whats-new/6.x-upgrade/What changed? Version 6.0.0 removes support for React Native’s legacy architecture. This aligns with React Native’s move to exclusively support their new architecture. You must migrate your app to use React Native’s new architecture to use this and future versions of the SDK. Do you need to update to this version? We recommend updating to the latest SDK version. However, if your app uses the old React Native architecture and you’re not ready to migrate, you can continue using version 5.https://docs.customer.io/journeys/file-manager/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/file-manager/Overview To access your dashboard, click Design Studio from the left navigation. From there, you can: Switch between your message files and global styles at the top. Create, edit, or delete your emails, templates, and components. Search and filter for existing files. To manage assets, like logos and images, go to Content > Assets. Learn more about managing your assets and what file types and sizes we support. You can also upload and optimize images from a Design Studio email.https://docs.customer.io/journeys/objects-video-tutorials/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/objects-video-tutorials/Introduction to objects Overview of objects in your workspace Using objects for SaaS/B2B use cases In this example, our Product Manager Cam shows you how to message admins when a new member joins their accounts. Cam created a campaign that triggers each time a person joins an account (i.e. for each new relationship). The person who joins the account is different from the people who should receive the campaign, which applies to many other use cases, like:https://docs.customer.io/journeys/set-styles/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/set-styles/You’ll add global styles—your colors, fonts, spacing, and radii—then assign them to standard elements—headings, paragraphs, links, and buttons. This way, your components will default to styles that best support your brand, making it easy to keep your messages consistent no matter the content, or how many people are making edits.  Global styles now apply to in-app messages! Styles apply differently to in-app messages than they do to emails, so make sure you check out our article on using global styles with in-app messages.https://docs.customer.io/journeys/goal-changes/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/goal-changes/Changing conversion criteria does not change past conversion data If you change conversion criteria, we do not retroactively count conversions. Conversion metrics only include people who convert after you add or change conversion criteria. Updating conversion criteria will not change your conversion metrics for messages that were previously marked as converted. Change the underlying configuration of a campaign’s conversion-criteria segment People currently in your campaign who already matched the new goal conditions will not be retroactively marked as converted.https://docs.customer.io/integrations/sdk/flutter/whats-new/3.x-upgrade/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/flutter/whats-new/3.x-upgrade/What changed? Version 3.x introduces a Firebase wrapper that improves compatibility with Firebase Cloud Messaging (FCM). What needs to change? You need to add the CioFirebaseWrapper import to your Swift files that use CioMessagingPushFCM. Add the Firebase wrapper import to your AppDelegate.swift file: import UIKit import Flutter import CioMessagingPushFCM import CioFirebaseWrapper // Add this import for FCM users import FirebaseMessaging import FirebaseCore @main class AppDelegateWithCioIntegration: CioAppDelegateWrapper<AppDelegate> {} Troubleshooting If you see build errors related to Firebase after upgrading:https://docs.customer.io/integrations/sdk/react-native/5.x/whats-new/5.x-upgrade/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/5.x/whats-new/5.x-upgrade/What changed? Version 5.x introduces a Firebase wrapper that improves compatibility with Firebase Cloud Messaging (FCM) and other Firebase services in your app. Do you need to update to this version? You need to update to this version if you use FCM (Firebase Cloud Messaging) for push notifications Update process Add the CioFirebaseWrapper import to your Swift files that use CioMessagingPushFCM. Add the Firebase wrapper import to your AppDelegate.swift file:https://docs.customer.io/integrations/sdk/react-native/whats-new/5.x-upgrade/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/whats-new/5.x-upgrade/What changed? Version 5.x introduces a Firebase wrapper that improves compatibility with Firebase Cloud Messaging (FCM) and other Firebase services in your app. Do you need to update to this version? You need to update to this version if you use FCM (Firebase Cloud Messaging) for push notifications Update process Add the CioFirebaseWrapper import to your Swift files that use CioMessagingPushFCM. Add the Firebase wrapper import to your AppDelegate.swift file:https://docs.customer.io/journeys/directives/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/directives/ Use our Design Studio GPT to create a custom component! Learn how to best utilize our GPT to create code for reusable, custom content. Use directives in HTML, standard components, custom component templates and our optional, top-level elements of your email to set attributes dynamically and conditionally add/remove them. Every directive begins with #. For instance, you can use #if, #else-if, and #else for conditionally displaying these tags: <script> const useExternal = true; </script> <link #if="useExternal" rel="stylesheet" href="https://example.https://docs.customer.io/journeys/dark-mode/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/dark-mode/Why set dark mode styles? Dark mode is increasingly the default setting across devices and email clients. As customer expectations shift toward modern design standards, supporting dark mode helps: Reduce broken email experiences by providing intentional styling Increase readability with properly contrasted colors designed for dark backgrounds Meet accessibility standards and user preferences Reduce support complaints about poor email rendering in dark mode Where to set dark mode styles You can set default, global dark mode styles in Styles.https://docs.customer.io/journeys/code-editor-overview/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/code-editor-overview/This guide gives you a tour of the code editor so you can navigate the workspace, write and structure your message, and use built-in tools to validate and troubleshoot your work. The code editor has three main areas: File Manager: navigate between messages, templates, and components Editor: write your HTML, plain text, AMP, and transformer logic Preview: render your message and access developer tools for testing Navigate between your files To the left of the code editor, you’ll find the File Manager.https://docs.customer.io/journeys/visual-editor-overview/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/visual-editor-overview/Here’s a quick guide to what’s available in the visual editor, and how each part helps you build your message. It has four key areas—the Insert menu, Layers menu, Canvas, and Properties menu. Together, they enable you to add and style content without code. For more on previewing your message for accessibility and responsiveness, check out Preview email in Design Studio. If you get stuck, reach out to our agent! Click at the top of your workspace to get started.https://docs.customer.io/journeys/unsubscribes/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/unsubscribes/ Check out our subscription center! This article covers global unsubscribes. Visit our subscription center documentation to learn how to give customers more granular control over the messages they receive. Our subscription functionality doesn’t apply to in-app messages; rather, you’ll want to learn how to target the right people with in-app messages. Learn more about how people can unsubscribe from SMS, WhatsApp, or push notifications as channels. How it works In your emails, you need to add liquidA syntax that supports variables, letting you personalize messages for your audience.https://docs.customer.io/journeys/segments/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/segments/Overview Here’s an overview of segments in Customer.io: And here’s a more interactive look at creating a manual segment and data-driven segment: Segments are named groups of people who share characteristics or behaviors. A Segment can have many people and a person can belong to many segments. You can use segments as recipient lists, campaign triggers, filters, conversion criteria and more. Whenever you need to reference a subset of the people in your workspace, you’ll use a segment.https://docs.customer.io/accounts-and-workspaces/intro-account-access/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/accounts-and-workspaces/intro-account-access/Overview In Account Settings > Team Members, you can add team members to collaborate on campaigns, help with integrations, and more across your workspaces. Customer.io does not charge for team members, so feel free to grant access to anyone that you need! Only Account Admins can add team members. And each account can have up to 300 team members across all workspaces. For each team member, you’ll need to decide the level of access they should have to your account and to each of your workspaces.https://docs.customer.io/journeys/collaborate/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/collaborate/Overview Design Studio offers you and your teammates many tools for collaborating on your messages—you can share, export, or capture a screenshot of your work, create rounds of feedback, and access version history. You can also send a test to see how the message looks in your inboxes.  Only one person can edit a Design Studio message at a time. Design Studio doesn’t offer live, cross-team collaboration. If someone else is working on a message when you enter the visual or code editor, you’ll be prompted to Take over Editing or View Only.https://docs.customer.io/journeys/create-custom-component/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/create-custom-component/Overview You can create a custom component to reuse across emails in a few ways: Create and save a component from the visual editor Prompt our GPT to generate your component Create one from scratch using our templating language Save a component from the visual editor Create and save custom components from the visual editor to reuse in subsequent emails. This way you can create things like headers and footers once, without having to write HTML/CSS!https://docs.customer.io/journeys/liquid-upgrade/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/liquid-upgrade/ What liquid version are you on? If your Customer.io account was created on or after Nov 28, 2023, you are using the latest liquid version for all messages. If your Customer.io account was created before Nov 28, 2023, see Changing your liquid version for more info. See below for the differences between the two versions. How to check your liquid version Within any message editor, hover over the last saved date at the top to see the liquid version you’re using.https://docs.customer.io/journeys/llm-actions/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/llm-actions/ Not seeing this AI feature? Make sure “Customer.io AI” is enabled in Privacy, Data, & AI settings. Reach out to an Account Admin if you can’t edit the toggle. How it works LLM actions let you prompt an AI model as a part of a campaign and store the output as attributes so you can use them later in the campaign. You can personalize messages, enrich data, and create conditions to help you reach the right audience.https://docs.customer.io/journeys/transformer-mjml/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/transformer-mjml/Add MJML to code editor To use MJML in your message: Go to Transformers > Framework and turn on MJML Or, append your message file with a .mjml extension. If you create a message from scratch ending with .mjml, the editor will auto-populate this template to help you get started: <mjml lang="en"> <mj-head> <mj-title>Subject goes here</mj-title> <mj-preview>Preview text goes here</mj-preview> </mj-head> <mj-body> <!-- Content goes here --> </mj-body> </mjml> Add HTML to MJML ending tags Ending tags, like <mj-raw>, let you add HTML inside an MJML block.https://docs.customer.io/journeys/getting-started-with-json/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/getting-started-with-json/How it works JSON stands for JavaScript Object Notation. It’s a common format to send and store data over the internet, and the way in which you’ll send, store, and reference data in Customer.io! If you’re a Customer.io user, you’re already using JSON—even if you don’t know it! For example, when you send an eventSomething that a person in your workspace did. Events can trigger campaigns, add people to segments, etc, and you can use properties from events to personalize messages.https://docs.customer.io/journeys/standard-components/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/standard-components/We also offer some standard components behind the scenes to help you structure your email, enhance accessibility, style imported emails, and import Google fonts. How styling works Standard components pull from your global styles so you can create a consistent brand across your messages, but you can individually overwrite these styles too. To style a standard component, click the component on the canvas of the visual editor to open the Properties panel.https://docs.customer.io/journeys/troubleshoot-campaign-entrance/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/troubleshoot-campaign-entrance/Note that people who are unsubscribed from topics or from all messages can still trigger a campaign; they just won’t receive messages from that campaign. See issues with messages for more information. 1. Check if the campaign is live If no one is entering your campaign, check that it’s live first. You’ll see “Running” next to the campaign title. If it’s still in a “Starting” state, people may not be able to trigger the campaign yet.https://docs.customer.io/journeys/segment-builder/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/segment-builder/How it works Our agent uses publicly available data about your company and data from your workspace to suggest conditions for targeting specific audiences. Provide a brief prompt to generate segments that align with your goals. You can build a segment from any page using the agent. Click to get started. We prioritize your data privacy Our AI-powered segment suggestions are based solely on attribute names from your workspace, such as profile and event attributes, but never the values.https://docs.customer.io/journeys/data-driven-segments/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/data-driven-segments/Create a data-driven segment This process explains how to create a segment on the Segments page, but can also create a segmentA group of people who match a series of conditions. People enter and exit the segment automatically when they match or stop matching conditions. when you create a campaign (using the They meet conditions option). The same basic steps apply there as well. If you create a new segment when working on a campaign, you may want to check your segment before you start the campaign just to make sure that your conditions match the right people for your campaign.https://docs.customer.io/journeys/workflow-changes/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/workflow-changes/Change or delete delays Shorten a delay If you shorten a delay, like from 7 days to 5 days, all people waiting in that particular delay are re-evaluated. You will see a processing circle while this is happening. People who have already waited for more than the new delay (in our case, more than 5 days) will immediately move to the next action. Everyone else continues waiting in the delay for the required period.https://docs.customer.io/accounts-and-workspaces/account-verification/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/accounts-and-workspaces/account-verification/The result of this process is that you get great deliverability and peace of mind, while we maintain our standard of high quality and integrity as an email service provider.  Emails send to your test delivery address before you’re verified You can activate a campaign or send a broadcast, but emails will send to your test delivery address, not your audience, before your account is verified. All other message types will send normally.https://docs.customer.io/journeys/component-loops/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/component-loops/ Use our Design Studio GPT to create a custom component! Learn how to best utilize our GPT to create code for reusable, custom content. Loop through numbers Numerical iteration is 0 indexed - the first number is 0. <template> <ul> <li #each="n in 10">${n}</li> </ul> </template> Using this component in an email: <html> <body> A simple email <my-first-component></my-first-component> </body> </html> The output source becomes: <html> <body> A simple email <ul> <li>0</li> <li>1</li> <li>2</li> <li>3</li> <li>4</li> <li>5</li> <li>6</li> <li>7</li> <li>8</li> <li>9</li> </ul> </body> </html> Loop through arrays You can loop through an array to dynamically generate repeated elements—like list items—based on your data.https://docs.customer.io/integrations/data-in/connections/classic-api/journeys-sources/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/classic-api/journeys-sources/ Just getting started? Use our newer source integrations instead! This page is about our Track API and integration sources that rely on the Track API. If you’re new to Customer.io, you should integrate with our newer API or native integrations instead. Our newer API and integrations support batching, retry logic, and are where we’re focusing our development efforts. To send data from the Journeys Track API, or integrations based on the Track API, to a destination outside of Customer.https://docs.customer.io/journeys/anonymous-people/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/anonymous-people/How it works Most of the things you do in Customer.io revolve around people you know: they log into your service, make purchases, sign up for your newsletters, and so on. And, because you know who they are—you have their email addresses, names, and other information—you can send them messages. But what about people you don’t know? Plenty of people visit your website or open your app without logging in or otherwise providing identifying information.https://docs.customer.io/accounts-and-workspaces/audit-logs/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/accounts-and-workspaces/audit-logs/To track changes to your workspace data, like updates to people or custom objects, go to your Activity Logs. Overview As an Account Admin, you have access to two audit logs: Go to Account settings > Audit logs to see Account-level audit logs. These provide security-related information like team member session data, changes in permissions, and deletion of API keys. Go to Workspace settings > Audit logs to see Workspace-level audit logs.https://docs.customer.io/integrations/data-in/connections/http-api/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/http-api/With the Pipelines API (shown in the UI as the Customer.io API source), you can send data from anywhere directly to Customer.io and other downstream integrations without using an SDK. See our API documentation for more information about the Pipelines APIs.  Examples on this page use our US region If you’re in our EU region, you’ll use endpoints beginning with https://cdp-eu.customer.io/v1/ instead. Connect a Customer.io Pipelines API source Go to Data & Integrations > Integrations and click Add Integration.https://docs.customer.io/integrations/data-in/connections/cio-journeys/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/cio-journeys/How it works Customer.io automatically captures events relating to message activity—the messages you send, whether or not people open them, when people click them, and so on. So when you look at your integrations, you’ll see Customer.io (Workspaces) as a data source that you can connect to other services. Treating incoming metrics as a source lets you send data to destinations that help you aggregate and analyze audience data, so you follow and chart how your audience reacts to different message channels in your marketing stack.https://docs.customer.io/integrations/data-in/connections/mobile/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/mobile/How mobile SDKs work When you integrate our mobile SDK into your app, you’ll gain support for push notifications, in-app messages, and the ability to send your app data to both Customer.io and downstream integrations like your analytics platform. We currently have SDKs for iOS (Swift), Android, React Native, Expo, and Flutter. flowchart LR a(Your app)-->|User activity (identify, track, etc)|b((Customer.io)) b-.->d(Your analytics platform) b-.->e(Your CRM) Minimum versions Our SDKs became “integration sources” in fairly recent releases.https://docs.customer.io/integrations/sdk/android/quick-start-guide/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/android/quick-start-guide/ Our MCP server can help you get started Our MCP server includes SDK-installation tools that can help you get integrated quickly with Customer.io and troubleshoot any issues you might have. See Set up an MCP server to get started. Setup Process Overview For native Android apps, our Android SDK sets you up to send push notifications and track user activity. You’ll need to add Customer.io SDK to your project, configure it with your API key, and set up push notification handling.https://docs.customer.io/integrations/sdk/flutter/2.x/quick-start-guide/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/flutter/2.x/quick-start-guide/ Our MCP server can help you get started Our MCP server includes SDK-installation tools that can help you get integrated quickly with Customer.io and troubleshoot any issues you might have. See Set up an MCP server to get started. Setup process overview Flutter lets you build native mobile apps using Dart. Our Flutter SDK helps you integrate Customer.io to identify people, track their activity, and send both push notifications and in-app messages.https://docs.customer.io/integrations/sdk/flutter/quick-start-guide/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/flutter/quick-start-guide/ Our MCP server can help you get started Our MCP server includes SDK-installation tools that can help you get integrated quickly with Customer.io and troubleshoot any issues you might have. See Set up an MCP server to get started. Setup process overview Flutter lets you build native mobile apps using Dart. Our Flutter SDK helps you integrate Customer.io to identify people, track their activity, and send both push notifications and in-app messages.https://docs.customer.io/integrations/sdk/ios/3.x/quick-start-guide/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/3.x/quick-start-guide/ Our MCP server can help you get started Our MCP server includes SDK-installation tools that can help you get integrated quickly with Customer.io and troubleshoot any issues you might have. See Set up an MCP server to get started. Setup process overview Our SDK lets you build native mobile apps for iOS. When you’re done, you’ll be able to identify people, track their activity, and send both push notifications and in-app messages.https://docs.customer.io/integrations/sdk/ios/quick-start-guide/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/quick-start-guide/ Our MCP server can help you get started Our MCP server includes SDK-installation tools that can help you get integrated quickly with Customer.io and troubleshoot any issues you might have. See Set up an MCP server to get started. Setup process overview Our SDK lets you build native mobile apps for iOS. When you’re done, you’ll be able to identify people, track their activity, and send both push notifications and in-app messages.https://docs.customer.io/integrations/sdk/react-native/4.x/quick-start-guide/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/4.x/quick-start-guide/ Our MCP server can help you get started Our MCP server includes SDK-installation tools that can help you get integrated quickly with Customer.io and troubleshoot any issues you might have. See Set up an MCP server to get started. Setup process overview React Native lets you build native mobile apps with JavaScript. Our React Native SDK helps you integrate Customer.io to identify people, track their activity, and send both push notifications and in-app messages.https://docs.customer.io/integrations/sdk/react-native/5.x/quick-start-guide/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/5.x/quick-start-guide/ Our MCP server can help you get started Our MCP server includes SDK-installation tools that can help you get integrated quickly with Customer.io and troubleshoot any issues you might have. See Set up an MCP server to get started. Setup process overview React Native lets you build native mobile apps with JavaScript. Our React Native SDK helps you integrate Customer.io to identify people, track their activity, and send both push notifications and in-app messages.https://docs.customer.io/integrations/sdk/react-native/quick-start-guide/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/quick-start-guide/ Our MCP server can help you get started Our MCP server includes SDK-installation tools that can help you get integrated quickly with Customer.io and troubleshoot any issues you might have. See Set up an MCP server to get started. Setup process overview React Native lets you build native mobile apps with JavaScript. Our React Native SDK helps you integrate Customer.io to identify people, track their activity, and send both push notifications and in-app messages.https://docs.customer.io/get-started/welcome/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/get-started/welcome/How Customer.io Works In Customer.io, you’ll spend most of your time setting up campaigns to send messages to people. But you’ll get the most out of Customer.io when you integrate your data with Customer.io and make us a central part of your martech/messaging stack. By getting your data into Customer.io, enriching it, and sending it out to other places where you activate it, you can focus on your messaging strategy without having to jump from platform to platform.https://docs.customer.io/integrations/sdk/flutter/2.x/whats-new/2.2-upgrade/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/flutter/2.x/whats-new/2.2-upgrade/Key Changes The primary change in version 2.2 is the introduction of the wrapper pattern for handling push notifications on iOS. This change: Eliminates method swizzling: No more automatic method replacement Simplifies setup: Less boilerplate code required Improves reliability: More predictable behavior See the instructions below to update your Flutter app’s iOS configuration. Upgrading to SDK 2.2 Update your dependencies: Update your pubspec.yaml file: dependencies: customer_io: ^2.2.0 Run dependency update:https://docs.customer.io/integrations/sdk/flutter/whats-new/2.2-upgrade/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/flutter/whats-new/2.2-upgrade/Key Changes The primary change in version 2.2 is the introduction of the wrapper pattern for handling push notifications on iOS. This change: Eliminates method swizzling: No more automatic method replacement Simplifies setup: Less boilerplate code required Improves reliability: More predictable behavior See the instructions below to update your Flutter app’s iOS configuration. Upgrading to SDK 2.2 Update your dependencies: Update your pubspec.yaml file: dependencies: customer_io: ^2.2.0 Run dependency update:https://docs.customer.io/integrations/sdk/ios/3.x/whats-new/3.13.0-upgrade/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/3.x/whats-new/3.13.0-upgrade/What changed? The changes are mainly to align our SDK APIs across different platforms. No functional changes to be expected. Upgrade process Attributes profileAttributes property is deprecated Getter has no replacement, the mobile SDK doesn’t expose the user’s profile attributes Setter is replaced with setProfileAttributes(attributes: [String: Any]) deviceAttributes property is deprecated Getter has no replacement, the mobile SDK doesn’t expose the user’s device attributes Setter is replaced with setDeviceAttributes(attributes: [String: Any]) Tracking Identifying a userhttps://docs.customer.io/integrations/sdk/expo/whats-new/3.3-upgrade/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/expo/whats-new/3.3-upgrade/What changed? Version 3.3 introduces the appGroupId configuration option, which enables App Groups for reliable push delivery metric tracking on iOS. This update also requires customerio-reactnative version 6.4.0 or later as a peer dependency. Do you need to update to this version? This update is additive—your existing integration works without changes. We recommend updating if you want to improve the reliability of push delivery metric tracking on iOS. Update process 1.https://docs.customer.io/integrations/sdk/react-native/4.x/whats-new/4.3-upgrade/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/4.x/whats-new/4.3-upgrade/Key Changes The primary change in version 4.3 is the introduction of the wrapper pattern for handling push notifications on iOS. This change: Eliminates method swizzling: No more automatic method replacement Simplifies setup: Less boilerplate code required Improves reliability: More predictable behavior See the instructions below to update your app depending on whether you send push notifications with APN or FCM and whether you use UIKit or SwiftUI. Update with APN (Apple Push Notification service) UIKit Update your AppDelegate.https://docs.customer.io/integrations/sdk/react-native/5.x/whats-new/4.3-upgrade/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/5.x/whats-new/4.3-upgrade/Key Changes The primary change in version 4.3 is the introduction of the wrapper pattern for handling push notifications on iOS. This change: Eliminates method swizzling: No more automatic method replacement Simplifies setup: Less boilerplate code required Improves reliability: More predictable behavior See the instructions below to update your app depending on whether you send push notifications with APN or FCM and whether you use UIKit or SwiftUI. Update with APN (Apple Push Notification service) UIKit Update your AppDelegate.https://docs.customer.io/integrations/sdk/react-native/whats-new/4.3-upgrade/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/whats-new/4.3-upgrade/Key Changes The primary change in version 4.3 is the introduction of the wrapper pattern for handling push notifications on iOS. This change: Eliminates method swizzling: No more automatic method replacement Simplifies setup: Less boilerplate code required Improves reliability: More predictable behavior See the instructions below to update your app depending on whether you send push notifications with APN or FCM and whether you use UIKit or SwiftUI. Update with APN (Apple Push Notification service) UIKit Update your AppDelegate.https://docs.customer.io/integrations/data-in/connections/reverse-etl/about-reverse-etl/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/reverse-etl/about-reverse-etl/How it works Our data warehouse and database “reverse ETL” (Extract, Transform, Load) integrations extract data from a data warehouse so you can take advantage of your data in Customer.io and other services downstream. These integrations help you leverage your big data storage in Customer.io. For example, you might write a query representing track events so you can sync records from Snowflake to Mixpanel. When you set up a reverse ETL integration, you’ll set up one or more syncs.https://docs.customer.io/integrations/data-out/connections/salesforce/salesforce-intro/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/salesforce/salesforce-intro/ Do you want to capture data from Salesforce? Check out our Salesforce Source. With the Salesforce data-in and data-out integrations, you can set up a complete, end-to-end integration! Getting started Go to Data & Integrations > Integrations and select the About this integration entry in the Directory tab. (Optional) Select the data sources that you want to connect to your outbound integration. You can always connect data sources later. We’ll only show you data sources that work with your integration.https://docs.customer.io/integrations/data-out/connections/actable-predictive/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/actable-predictive/Getting started Go to Data & Integrations > Integrations and select the Actable Predictive entry in the Directory tab. (Optional) Select the data sources that you want to connect to your outbound integration. You can always connect data sources later. We’ll only show you data sources that work with your integration. Configure your integration. Client Id: Your Actable-supplied Client ID. Client Secret: Your Actable-supplied Client Secret. Click Enable Destination. Actions When you’re done setting things up, you can go to the Actions tab to see how we map incoming data to your integration.https://docs.customer.io/integrations/data-out/connections/adobe-target/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/adobe-target/Getting started: Web integration The Adobe Target “Web” integration loads Adobe’s at.js script alongside our JavaScript client source so that you can upsert user profiles, trigger views, and track events. Go to Data & Integrations > Integrations and select the Adobe Target entry in the Directory tab. (Optional) Select the data sources that you want to connect to your outbound integration. You can always connect data sources later. We’ll only show you data sources that work with your integration.https://docs.customer.io/integrations/data-out/connections/algolia-insights/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/algolia-insights/Getting started Go to Data & Integrations > Integrations and select the Algolia Insights entry in the Directory tab. (Optional) Select the data sources that you want to connect to your outbound integration. You can always connect data sources later. We’ll only show you data sources that work with your integration. Configure your integration. App Id: Your Algolia Application ID. Api Key: An API key which has write permissions to the Algolia Insights APIhttps://docs.customer.io/integrations/data-in/connections/reverse-etl/amazon-redshift/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/reverse-etl/amazon-redshift/Best Practices Before you add a Reverse ETL source, you should take some measures to ensure the security of your customers’ data and limit performance impacts to your database and Customer.io workspace. Create a new database user/service account. Implement a database user with minimal privileges specifically for Customer.io import/sync operations. This person only requires read permissions with access limited to the tables you want to sync from. Avoid using your main database instance.https://docs.customer.io/integrations/data-out/connections/amazon-redshift-data-out/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/amazon-redshift-data-out/ We have two integrations! This integration uses Customer.io as a source, and syncs data from your Customer.io workspace to your data warehouse, including campaign information. Our other integration sends data from multiple sources to your data warehouse. While the other integration captures data from multiple sources, even if those sources don’t send data to your workspace, it cannot capture some data from within Customer.io like campaign information. How it works This integration exports individual parquet files for Deliveries, Metrics, Subjects, Outputs, Content, People, and Attributes to your storage bucket.https://docs.customer.io/integrations/data-out/connections/amazon-redshift/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/amazon-redshift/How it works This integration sends CSV, JSON, or parquet files containing your data to your Amazon Redshift (Advanced) bucket. Then you can ingest the files in your storage bucket to your data warehouse of choice. We write files for each type of incoming call to your storage bucket every 10 minutes. So you’ll have files for identify calls, track calls, and so on. Files are named with an incrementing number, so it’s easy to determine the sequence of files, and the order of incoming calls.https://docs.customer.io/integrations/data-out/connections/amazon-s3-data-out/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/amazon-s3-data-out/ We have two integrations! This integration uses Customer.io as a source, and syncs data from your Customer.io workspace to your data warehouse, including campaign information. Our other integration sends data from multiple sources to your data warehouse. While the other integration captures data from multiple sources, even if those sources don’t send data to your workspace, it cannot capture some data from within Customer.io like campaign information. How it works This integration exports individual parquet files for Deliveries, Metrics, Subjects, Outputs, Content, People, and Attributes to your storage bucket.https://docs.customer.io/integrations/data-out/connections/amazon-simple-storage-service/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/amazon-simple-storage-service/How it works This integration sends CSV, JSON, or parquet files containing your data to your Amazon S3 (Advanced) bucket. Then you can ingest the files in your storage bucket to your data warehouse of choice. We write files for each type of incoming call to your storage bucket every 10 minutes. So you’ll have files for identify calls, track calls, and so on. Files are named with an incrementing number, so it’s easy to determine the sequence of files, and the order of incoming calls.https://docs.customer.io/integrations/data-out/connections/amplitude/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/amplitude/ We use Amplitude’s v2 API While we show the schemas that we map data to below, you’ll need to check out Amplitude’s documentation to learn more about their API. Getting started Go to Data & Integrations > Integrations and select the Amplitude entry in the Directory tab. (Optional) Select the data sources that you want to connect to your outbound integration. You can always connect data sources later. We’ll only show you data sources that work with your integration.https://docs.customer.io/integrations/data-out/connections/amplitude-metrics/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/amplitude-metrics/How it works This integration sends your audience engagement data—also available as reporting webhooks—to Amplitude, where you can use it alongside your other user and analytics data to gain insight into your audience’s behaviors. Because Amplitude generally expects a unique, immutable user_id in events, we only send events to Amplitude when they represent a person with an id or a the event contains a device_id. We do not send events to Amplitude for people who do not have an id or aren’t represented by a device_id.https://docs.customer.io/ai/agent/get-started/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/ai/agent/get-started/Click Agent in the sidebar or click Ask Agent in the bottom right to open a fresh conversation. You can ask it to do just about anything that you can do in Customer.io. Give it a prompt like: “Create a segment with people that opened an email in the last 90 days.” “What’s the click-to-open rate for my birthday campaign?” “Of my onboarding and welcome campaigns, which had the lowest deliverability this month?https://docs.customer.io/accounts-and-workspaces/assign-standard-roles/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/accounts-and-workspaces/assign-standard-roles/Overview You can assign standard roles to team members from Workspace Settings or from Account Settings > Team Members. A workspace-level role controls the set of permissions a team member has in a single workspace. We offer three standard roles: Workspace Admin (full access) Author (partial access) Viewer (view-only access) When you assign Author or Viewer roles, you choose whether to limit their access to sensitive data. This helps you keep your account as secure as possible.https://docs.customer.io/integrations/data-out/connections/attio/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/attio/Our Attio destination creates or updates records for people, users, companies, and workspaces in Attio. This integration helps you keep your Attio workspace up-to-date with the latest information about your customers. Getting started Go to Data & Integrations > Integrations and select the Attio entry in the Directory tab. (Optional) Select the data sources that you want to connect to your outbound integration. You can always connect data sources later. We’ll only show you data sources that work with your integration.https://docs.customer.io/integrations/data-out/connections/ms-azure-data-out/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/ms-azure-data-out/ We have two integrations! This integration uses Customer.io as a source, and syncs data from your Customer.io workspace to your data warehouse, including campaign information. Our other integration sends data from multiple sources to your data warehouse. While the other integration captures data from multiple sources, even if those sources don’t send data to your workspace, it cannot capture some data from within Customer.io like campaign information. How it works This integration exports individual parquet files for Deliveries, Metrics, Subjects, Outputs, Content, People, and Attributes to your storage bucket.https://docs.customer.io/integrations/data-out/connections/bing-ads/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/bing-ads/Getting started Before you can track conversions or target audiences, you need to create a UET tag in Bing Ads and then add it to the destination settings. Follow the steps within the Bing Ads documentation to create a UET tag. You’ll only be able to include one Tag ID per source so make sure to associate conversion criteria to the correct Tag ID that is included in your settings.https://docs.customer.io/integrations/data-out/connections/braze/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/braze/Web only mode You can set up this integration in “web” mode. When set up this way, our JavaScript client will load the Braze SDK and send data directly to Braze, bypassing Customer.io entirely. We don’t typically recommend setting things up this way, because: You won’t capture data in Customer.io. As the name suggests, you cannot use this mode with other sources of data (mobile SDKs, server-side libraries, and so on).https://docs.customer.io/integrations/data-out/connections/braze-cohorts/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/braze-cohorts/Getting started Go to Data & Integrations > Integrations and select the Braze Cohorts entry in the Directory tab. (Optional) Select the data sources that you want to connect to your outbound integration. You can always connect data sources later. We’ll only show you data sources that work with your integration. Configure your integration. Client Secret: Data Import Key for the client whose cohort this belongs to. Also known as customer key.https://docs.customer.io/journeys/campaigns-in-customerio/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/campaigns-in-customerio/If you’re new to Customer.io, checkout campaigns, broadcasts, and transactional messages to make sure you’re creating the right kind of automation. How it works A campaign is a workflow to send messages and manipulate data in Customer.io. It consists of four major components: Trigger: this determines who enters your campaign (trigger and filter conditions) and when (frequency setting). Filters are optional. Goals: the outcome you want your customers to achieve through the campaign.https://docs.customer.io/integrations/data-out/connections/clevertap/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/clevertap/Getting started Go to Data & Integrations > Integrations and select the Clevertap entry in the Directory tab. (Optional) Select the data sources that you want to connect to your outbound integration. You can always connect data sources later. We’ll only show you data sources that work with your integration. Configure your integration. Clevertap Account Id: CleverTap Account Id. This can be found under Settings Page. Clevertap Passcode: CleverTap Passcode. This can be found under Settings Page.https://docs.customer.io/integrations/data-out/connections/close/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/close/Getting started Go to Data & Integrations > Integrations and select the Close entry in the Directory tab. (Optional) Select the data sources that you want to connect to your outbound integration. You can always connect data sources later. We’ll only show you data sources that work with your integration. Configure your integration. Api Key: Your Close API key. Lead Custom Field Id For Company Id: Enter the ID of a Lead Custom Field that'll be used to store Company ID.https://docs.customer.io/integrations/data-out/connections/commandbar/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/commandbar/Getting started Go to Data & Integrations > Integrations and select the CommandBar entry in the Directory tab. (Optional) Select the data sources that you want to connect to your outbound integration. You can always connect data sources later. We’ll only show you data sources that work with your integration. Configure your integration. Org Id: The ID of your CommandBar organization. Deploy: If enabled, CommandBar will be deployed to your site automatically and you can remove the snippet from your source code.https://docs.customer.io/integrations/data-out/connections/cordial/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/cordial/Getting started Go to Data & Integrations > Integrations and select the Cordial entry in the Directory tab. (Optional) Select the data sources that you want to connect to your outbound integration. You can always connect data sources later. We’ll only show you data sources that work with your integration. Configure your integration. Api Key: Your Cordial API Key Endpoint: Cordial API endpoint. Leave default, unless you've been provided with another one.https://docs.customer.io/journeys/code-custom-component/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/code-custom-component/ New to custom components? If you’re new to custom components, check out how to build them using visual blocks or our GPT. This may save you some time! Understand the structure There are two required tags when setting up a component: <script> and <template>. The <script> tag is where you define properties for styles, slots for modifiable content, and other JavaScript logic. The <template> tag is where you create your content and reference variables and slots.https://docs.customer.io/journeys/component-styling/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/component-styling/ Use our Design Studio GPT to create a custom component! Learn how to best utilize our GPT to create code for reusable, custom content. We’ve shown you have to define properties with JavaScript in the <script> tag of your custom component, but you may also want to define styles in a stylesheet. In the <style> element, you can define branding, hover styles, responsive styles, dark mode, and more through CSS or by passing in properties defined in the <script> tag.https://docs.customer.io/integrations/data-out/connections/criteo-audiences/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/criteo-audiences/Getting started Before you can setup your Criteo Audiences destination, you need to create a Criteo API Marketing Solutions app to generate your app credentials. Follow Criteo’s Developer Portal checklist to generate your credentials. You also need your Criteo Advertiser ID. Talk to your Criteo Account Strategist if you don’t know your Advertiser ID. Go to Data & Integrations > Integrations and select the Criteo Audiences entry in the Directory tab.https://docs.customer.io/journeys/transformer-css-inlining/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/transformer-css-inlining/ Only use CSS inlining for emails made with standard HTML Enabling this transformer on emails with our standard components will not work well and will likely lead to unintended styles. Click Transformers > CSS Inlining then turn on Inline CSS. Once enabled, you can customize what styling should be converted or preserved. The state of those toggles will be saved if you deactivate and later reactivate the transformer.  CSS inlining does not convert all styles in Design Studiohttps://docs.customer.io/integrations/data-out/connections/customerio/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/customerio/Getting started Go to Data & Integrations > Integrations and select the Customer.io entry in the Directory tab. (Optional) Select the data sources that you want to connect to your outbound integration. You can always connect data sources later. We’ll only show you data sources that work with your integration. Configure your integration. Site Id: Customer.io site ID. This can be found on your API Credentials page. Api Key: Customer.io API key.https://docs.customer.io/integrations/api/customerio-apis/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/api/customerio-apis/ Use one of our libraries or SDKs! We have ready-made libraries and SDKs that make it easy to use our APIs and provide other features like in-app messaging, retry logic, and so on. While our APIs can help you get started—and our API documentation includes examples for some of our libraries—you’ll almost always do better with a library or SDK. Check out our integration directory for more information. Just getting started?https://docs.customer.io/journeys/events/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/events/How does it work? Where an attributeA key-value pair that you associate with a person or an object—like a person’s name, the date they were created in your workspace, or a company’s billing date etc. Use attributes to target people and personalize messages. represents something you know about a person, an event represents point-in-time data about something a person did. Throughout Customer.io’s APIs and SDKs, you’ll use the track command to send events.https://docs.customer.io/integrations/data-out/connections/facebook-conversions-api/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/facebook-conversions-api/Getting started To set up the Facebook Conversions API destination, you’ll need a Facebook user access token from your business account. See the section below for help creating or getting a token. Go to Data & Integrations > Integrations and select the Facebook Conversions API entry in the Directory tab. (Optional) Select the data sources that you want to connect to your outbound integration. You can always connect data sources later.https://docs.customer.io/integrations/data-out/connections/friendbuy/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/friendbuy/There are two versions of this integration You’ll see two entries for Friendbuy in our integration catalog, with one labeled Web. We typically recommend that you use the standard integration, the one not labeled “Web” when possible. The web version of this integration only works with our JavaScript client and does not pass data through Customer.io’s servers, which can make it hard to debug your integration, capture a history of events sent to the integration, and so on.https://docs.customer.io/integrations/data-out/connections/fullstory/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/fullstory/Getting started Go to Data & Integrations > Integrations and select the FullStory entry in the Directory tab. (Optional) Select the data sources that you want to connect to your outbound integration. You can always connect data sources later. We’ll only show you data sources that work with your integration. Configure your integration. Api Key: FullStory API key Click Enable Destination. Actions When you’re done setting things up, you can go to the Actions tab to see how we map incoming data to your integration.https://docs.customer.io/integrations/data-out/connections/gainsight-px-cloud-action/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/gainsight-px-cloud-action/Getting started Go to Data & Integrations > Integrations and select the Gainsight PX entry in the Directory tab. (Optional) Select the data sources that you want to connect to your outbound integration. You can always connect data sources later. We’ll only show you data sources that work with your integration. Configure your integration. Api Key: Gainsight PX API key. You can find this key in the "Administration/Products" screen. Data Center: The PX data center where your PX subscription is hosted.https://docs.customer.io/integrations/data-in/connections/forms/connected-forms/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/forms/connected-forms/How it works Our form integrations identifyThe Customer.io operation that adds or updates a person. When you identify a person, Customer.io either adds a person if they don’t exist in your workspace, or updates them if they do. Before you identify someone (by their email address or an ID), you can track them anonymously. the form submitter and assign them attributesA key-value pair that you associate with a person or an object—like a person’s name, the date they were created in your workspace, or a company’s billing date etc.https://docs.customer.io/integrations/data-in/connections/javascript/legacy-js/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/javascript/legacy-js/getting-started/ New here? Try out our newer JavaScript client! This page is for our JavaScript snippet, which is older and doesn’t support some newer features in our JavaScript client library. If you’re just getting started with Customer.io, you should use the newer JavaScript client instead! How it works Our web SDK is a JavaScript snippet that helps you identify, send events for, and send in-app messages to people who visit your website(s) or use your web app(s).https://docs.customer.io/journeys/in-app-getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/in-app-getting-started/What is an in-app message? An in-app message is a message sent to a user inside your app or on your website. It’s distinct from a push notification in that a user must be in your app or on your website to receive it. They can’t get your message if they don’t open your app or log in to your site. While we refer to in-app messages as messages, you can make them persistent and use them as banners or other UI elements.https://docs.customer.io/integrations/sdk/android/2.x/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/android/2.x/getting-started/This page is part of an introductory series to help you get started with the essential features of our SDK. The highlighted step(s) below are covered on this page. Before you continue, make sure you've implemented previous features—i.e. you can't identify people before you initialize the SDK! graph LR getting-started(Install SDK) -->B(Initialize SDK) B --> identify(identify people) identify -.-> track-events(Send events) identify -.-> push(Receive push) identify -.-> rich-push(Receive Rich Push) track-events --> test-support(Write tests) push --> test-support rich-push --> test-support identify -.https://docs.customer.io/integrations/sdk/android/3.x/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/android/3.x/getting-started/This page is part of an introductory series to help you get started with the essential features of our SDK. The highlighted step(s) below are covered on this page. Before you continue, make sure you've implemented previous features—i.e. you can't identify people before you initialize the SDK! graph LR getting-started(Install SDK) -->B(Initialize SDK) B --> identify(identify people) identify -.-> track-events(Send events) identify -.-> push(Receive push) identify -.-> rich-push(Receive Rich Push) track-events --> test-support(Write tests) push --> test-support rich-push --> test-support identify -.https://docs.customer.io/integrations/sdk/expo/1.x/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/expo/1.x/getting-started/This page is part of an introductory series to help you get started with the essential features of our SDK. The highlighted step(s) below are covered on this page. Before you continue, make sure you've implemented previous features—i.e. you can't identify people before you initialize the SDK! graph LR getting-started(Install SDK) -->B(Initialize SDK) B --> identify(identify people) identify -.-> track-events(Send events) identify -.-> push(Receive push) identify -.-> in-app(Receive in-app) click getting-started href "https://docs.customer.io/integrations/sdk/flutter/1.x/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/flutter/1.x/getting-started/This page is part of an introductory series to help you get started with the essential features of our SDK. The highlighted step(s) below are covered on this page. Before you continue, make sure you've implemented previous features—i.e. you can't identify people before you initialize the SDK! graph LR getting-started(Install SDK) -->B(Initialize SDK) B --> identify(identify people) identify -.-> track-events(Send events) identify -.-> push(Receive push) identify -.-> in-app(Receive in-app) click getting-started href "https://docs.customer.io/integrations/sdk/ios/1.x/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/1.x/getting-started/This page is part of an introductory series to help you get started with the essential features of our SDK. The highlighted step(s) below are covered on this page. Before you continue, make sure you've implemented previous features—i.e. you can't identify people before you initialize the SDK! graph LR getting-started(Install SDK) -->B(Initialize SDK) B --> identify(identify people) identify -.-> track-events(Send events) identify -.-> register-token(Register Device Token) register-token -.-> push(Receive push) register-token -.https://docs.customer.io/integrations/sdk/ios/2.x/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/2.x/getting-started/This page is part of an introductory series to help you get started with the essential features of our SDK. The highlighted step(s) below are covered on this page. Before you continue, make sure you've implemented previous features—i.e. you can't identify people before you initialize the SDK! graph LR getting-started(Install SDK) -->B(Initialize SDK) B --> identify(identify people) identify -.-> track-events(Send events) identify -.-> register-token(Register Device Token) register-token -.-> push(Receive push) register-token -.https://docs.customer.io/integrations/sdk/react-native/2.x/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/2.x/getting-started/This page is part of an introductory series to help you get started with the essential features of our SDK. The highlighted step(s) below are covered on this page. Before you continue, make sure you've implemented previous features—i.e. you can't identify people before you initialize the SDK! graph LR getting-started(Install SDK) -->B(Initialize SDK) B --> identify(identify people) identify -.-> track-events(Send events) identify -.-> push(Receive push) identify -.-> in-app(Receive in-app) click getting-started href "https://docs.customer.io/integrations/sdk/react-native/3.x/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/3.x/getting-started/This page is part of an introductory series to help you get started with the essential features of our SDK. The highlighted step(s) below are covered on this page. Before you continue, make sure you've implemented previous features—i.e. you can't identify people before you initialize the SDK! graph LR getting-started(Install SDK) -->B(Initialize SDK) B --> identify(identify people) identify -.-> track-events(Send events) identify -.-> push(Receive push) identify -.-> in-app(Receive in-app) click getting-started href "https://docs.customer.io/journeys/line-get-started/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/line-get-started/Set up LINE Before you connect LINE to Customer.io, you need: A LINE Official Account with the Messaging API enabled A Messaging API channel in the LINE Developers Console If you haven’t done these things yet, follow LINE’s getting started guide to create an account and enable their Messaging API. Get your channel access token To connect LINE to Customer.io, you’ll need your LINE API key. This is the channel access token for your Messaging API channel.https://docs.customer.io/journeys/sms-get-started/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/sms-get-started/How it works While you’ll send SMS messages through Customer.io, SMS setup can be a bit complicated. If you send exclusively to people in the US or Canada, you might be able to setup SMS sending—including procuring your sender phone numbers—entirely through Customer.io. If you send messages to people outside of the US or Canada, you’ll need to set up a Twilio account and connect it to Customer.io—which is still very straightforward.https://docs.customer.io/journeys/whatsapp-get-started/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/whatsapp-get-started/How it works WhatsApp is similar to SMS in that you can send messages to your audience using their phone numbers. But you’ll need WhatsApp-approved phone numbers to send messages; these are separate from the phone numbers you use to send SMS messages. After you’ve enabled WhatsApp support, you’ll set up templates for your messages. Unlike SMS and other channels, you won’t write message content directly in Customer.io; WhatsApp messages are based on templates that you create in WhatsApp (or through Twilio), and then populate in Customer.https://docs.customer.io/journeys/get-a-phone-number/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/get-a-phone-number/Before you can get a phone number and send SMS messages, you’ll need to register as a sender, which includes several steps—including making sure that your privacy policy and terms and conditions are updated to reflect your SMS-use case. We’ll help you register as a sender, but it can take 1-2 weeks for carriers to review and approve or deny your request. You need to do the following things before we submit your request to Twilio and respective carriers—so you can register for phone numbers and start sending SMS as quickly as possible.https://docs.customer.io/journeys/inbound-sms/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/inbound-sms/How it works SMS messages frequently include keywords that trigger downstream actions—like STOP to opt-out of messages or HELP to understand the things people can do through SMS replies. Customer.io handles these replies, helping you trigger campaigns and segment your audience based on replies to your messages. For example, you might ask people to reply to a message with a keyword if they want updates for a particular event or product.https://docs.customer.io/integrations/data-in/connections/hubspot/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/hubspot/getting-started/How it works This integration sends data from HubSpot to Customer.io on regular intervals called syncs. You’ll set up syncs for each kind of data you want to use in Customer.io. As you set up syncs, you’ll map your HubSpot data to Customer.io. These will be the attributesA key-value pair that you associate with a person or an object—like a person’s name, the date they were created in your workspace, or a company’s billing date etc.https://docs.customer.io/integrations/data-in/connections/javascript/js-source/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/javascript/js-source/ Are you already integrated with our classic JavaScript snippet? If you’re already integrated with Customer.io, and your calls are prefixed with _cio, you’re using our classic JavaScript snippet. We recommend that you update to the JavaScript client integration described on this page, so that you can take advantage of our latest features. But, if you don’t want to update, you’ll find documentation for our classic JavaScript snippet here. How it works Our JavaScript client library helps you send data from your website to Customer.https://docs.customer.io/integrations/data-in/connections/salesforce/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/salesforce/getting-started/Quick start video Here’s a quick overview of the setup process for our incoming Salesforce integration. In this video, we set up Salesforce to send Contacts and Accounts to Customer.io. Before you begin Before you begin, you should ask yourself how you want to use your Salesforce data. The data that you send to Customer.io—as People, Events, Custom Objects, or Relationships between people and objects—may depend on what you want to do with your data in Customer.https://docs.customer.io/integrations/data-out/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/getting-started/How it works Data-out integrations let you send data to platforms outside of Customer.io, like analytics platforms, CRMs, support tools, advertising platforms, messaging platforms, and more. Most of our data-out integrations support all your sources of data. In these cases, data travels into Customer.io and then to your destination. Some data-out integrations, clearly marked with Web in our integration directory, only support data our JavaScript client. In these cases, data travels directly from your website to the destination, bypassing Customer.https://docs.customer.io/journeys/transactional-api/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/transactional-api/How it works Transactional messages are messages that your audience implicitly opts into—like purchase receipts, password reset requests, shipping updates, two-factor authentication codes, etc. Your audience expects to receive these messages even if they’ve opted out of marketing messages. That makes transactional different from marketing messages, which require explicit opt-in. And this difference isn’t just limited to Customer.io; it’s governed by laws like the CAN-SPAM Act and GDPR! When someone does something that requires a transactional message, you’ll call our transactional API to send them a message—like when they request a password reset or need a receipt for a purchase.https://docs.customer.io/integrations/data-out/connections/google-enhanced-conversions/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/google-enhanced-conversions/Getting started Go to Data & Integrations > Integrations and select the Google Ad Conversions entry in the Directory tab. (Optional) Select the data sources that you want to connect to your outbound integration. You can always connect data sources later. We’ll only show you data sources that work with your integration. Configure your integration. Customer Id: ID of your Google Ads Account. This should be 10-digits and in XXX-XXX-XXXX format.https://docs.customer.io/integrations/data-out/connections/google-ads/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/google-ads/ Don’t use this destination if you use Google Tag Manager You should only use this destination if your Google Ads account is using Gtag. If you’re using Google Tag Manager, don’t add the global site tag (gtag.js) in your GTM containers, otherwise you’ll end up duplicating Gtag on your site—once through your Customer.io integration and again through Google Tag Manager. Getting started This destination maps .page() and .track() calls from your website or app to Page Load Conversions and Click Conversions respectively.https://docs.customer.io/integrations/data-out/connections/google-analytics-4/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/google-analytics-4/Getting started Go to the Data Pipelines tab and click Connections. Click Add New under Destinations. Select the Google Analytics destination. (Optional) Select the sources that you want to connect to this destination. You can always connect sources to your destination later. We’ll only show you sources that you can use with your destination. Configure your destination. Measurement Id: The Measurement ID associated with a stream. Found in the Google Analytics UI under: Admin > Data Streams > choose your stream > Measurement ID.https://docs.customer.io/integrations/data-in/connections/reverse-etl/google-bigquery/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/reverse-etl/google-bigquery/Best Practices Before you add a Reverse ETL source, you should take some measures to ensure the security of your customers’ data and limit performance impacts to your database and Customer.io workspace. Create a new database user/service account. Implement a database user with minimal privileges specifically for Customer.io import/sync operations. This person only requires read permissions with access limited to the tables you want to sync from. Avoid using your main database instance.https://docs.customer.io/integrations/data-out/connections/google-bigquery-data-out/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/google-bigquery-data-out/ We have two integrations! This integration uses Customer.io as a source, and syncs data from your Customer.io workspace to your data warehouse, including campaign information. Our other integration sends data from multiple sources to your data warehouse. While the other integration captures data from multiple sources, even if those sources don’t send data to your workspace, it cannot capture some data from within Customer.io like campaign information. How it works This integration exports individual parquet files for Deliveries, Metrics, Subjects, Outputs, Content, People, and Attributes to your storage bucket.https://docs.customer.io/integrations/data-out/connections/google-bigquery/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/google-bigquery/How it works This integration sends CSV, JSON, or parquet files containing your data to your Google BigQuery (Advanced) bucket. Then you can ingest the files in your storage bucket to your data warehouse of choice. We write files for each type of incoming call to your storage bucket every 10 minutes. So you’ll have files for identify calls, track calls, and so on. Files are named with an incrementing number, so it’s easy to determine the sequence of files, and the order of incoming calls.https://docs.customer.io/integrations/data-out/connections/gcs-data-out/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/gcs-data-out/ We have two integrations! This integration uses Customer.io as a source, and syncs data from your Customer.io workspace to your data warehouse, including campaign information. Our other integration sends data from multiple sources to your data warehouse. While the other integration captures data from multiple sources, even if those sources don’t send data to your workspace, it cannot capture some data from within Customer.io like campaign information. How it works This integration exports individual parquet files for Deliveries, Metrics, Subjects, Outputs, Content, People, and Attributes to your storage bucket.https://docs.customer.io/integrations/data-out/connections/google-cloud-storage/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/google-cloud-storage/How it works This integration sends CSV, JSON, or parquet files containing your data to your Google Cloud Storage (Advanced) bucket. Then you can ingest the files in your storage bucket to your data warehouse of choice. We write files for each type of incoming call to your storage bucket every 10 minutes. So you’ll have files for identify calls, track calls, and so on. Files are named with an incrementing number, so it’s easy to determine the sequence of files, and the order of incoming calls.https://docs.customer.io/integrations/data-out/connections/google-sheets-non-etl/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/google-sheets-non-etl/Getting started Go to Data & Integrations > Integrations and select the Google Sheets entry in the Directory tab. (Optional) Select the data sources that you want to connect to your outbound integration. You can always connect data sources later. We’ll only show you data sources that work with your integration. Configure your integration. Click Enable Destination. Connect your Google Account to Customer.io Before you can use the Google Sheets destination, you need to grant us access to your sheets.https://docs.customer.io/integrations/data-out/connections/google-tag-manager/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/google-tag-manager/ Don’t use both the GTAG and GTM destinations Using both the Google Tag Manager and Google Ads (GTAG) destinations on the same page, with the same pixel ID, will likely result in duplicate events. Getting started Go to Data & Integrations > Integrations and select the Google Tag Manager (GTM) entry in the Directory tab. (Optional) Select the data sources that you want to connect to your outbound integration. You can always connect data sources later.https://docs.customer.io/integrations/data-out/connections/heap/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/heap/There are two versions of this integration You’ll see two entries for Heap in our integration catalog, with one labeled Web. We typically recommend that you use the standard integration, the one not labeled “Web” when possible. The web version of this integration only works with our JavaScript client and does not pass data through Customer.io’s servers, which can make it hard to debug your integration, capture a history of events sent to the integration, and so on.https://docs.customer.io/integrations/sdk/android/getting-started/how-it-works/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/android/getting-started/how-it-works/Our SDKs provide a ready-made integration to identify people who use mobile devices and send them notifications. Before you start using the SDK, you should understand a bit about how the SDK works with Customer.io. sequenceDiagram participant A as Mobile User participant B as SDK participant C as Customer.io A-->>B: Anonymous User activity B-->>C:   A->>B: Logs in (identify method) rect rgb(229, 254, 249) Note over A,C: Now you can Send events and receive messages B-->>C: Person added/updated in CIO C-->>C: Associate anonymoushttps://docs.customer.io/integrations/sdk/expo/getting-started/how-it-works/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/expo/getting-started/how-it-works/Our SDKs provide a ready-made integration to identify people who use mobile devices and send them notifications. Before you start using the SDK, you should understand a bit about how the SDK works with Customer.io. sequenceDiagram participant A as Mobile User participant B as SDK participant C as Customer.io A-->>B: Anonymous User activity B-->>C:   A->>B: Logs in (identify method) rect rgb(229, 254, 249) Note over A,C: Now you can Send events and receive messages B-->>C: Person added/updated in CIO C-->>C: Associate anonymoushttps://docs.customer.io/integrations/sdk/flutter/2.x/getting-started/how-it-works/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/flutter/2.x/getting-started/how-it-works/Our SDKs provide a ready-made integration to identify people who use mobile devices and send them notifications. Before you start using the SDK, you should understand a bit about how the SDK works with Customer.io. sequenceDiagram participant A as Mobile User participant B as SDK participant C as Customer.io A-->>B: Anonymous User activity B-->>C:   A->>B: Logs in (identify method) rect rgb(229, 254, 249) Note over A,C: Now you can Send events and receive messages B-->>C: Person added/updated in CIO C-->>C: Associate anonymoushttps://docs.customer.io/integrations/sdk/flutter/getting-started/how-it-works/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/flutter/getting-started/how-it-works/Our SDKs provide a ready-made integration to identify people who use mobile devices and send them notifications. Before you start using the SDK, you should understand a bit about how the SDK works with Customer.io. sequenceDiagram participant A as Mobile User participant B as SDK participant C as Customer.io A-->>B: Anonymous User activity B-->>C:   A->>B: Logs in (identify method) rect rgb(229, 254, 249) Note over A,C: Now you can Send events and receive messages B-->>C: Person added/updated in CIO C-->>C: Associate anonymoushttps://docs.customer.io/integrations/sdk/ios/3.x/getting-started/how-it-works/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/3.x/getting-started/how-it-works/Our SDKs provide a ready-made integration to identify people who use mobile devices and send them notifications. Before you start using the SDK, you should understand a bit about how the SDK works with Customer.io. sequenceDiagram participant A as Mobile User participant B as SDK participant C as Customer.io A-->>B: Anonymous User activity B-->>C:   A->>B: Logs in (identify method) rect rgb(229, 254, 249) Note over A,C: Now you can Send events and receive messages B-->>C: Person added/updated in CIO C-->>C: Associate anonymoushttps://docs.customer.io/integrations/sdk/ios/getting-started/how-it-works/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/getting-started/how-it-works/Our SDKs provide a ready-made integration to identify people who use mobile devices and send them notifications. Before you start using the SDK, you should understand a bit about how the SDK works with Customer.io. sequenceDiagram participant A as Mobile User participant B as SDK participant C as Customer.io A-->>B: Anonymous User activity B-->>C:   A->>B: Logs in (identify method) rect rgb(229, 254, 249) Note over A,C: Now you can Send events and receive messages B-->>C: Person added/updated in CIO C-->>C: Associate anonymoushttps://docs.customer.io/integrations/sdk/react-native/4.x/getting-started/how-it-works/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/4.x/getting-started/how-it-works/Our SDKs provide a ready-made integration to identify people who use mobile devices and send them notifications. Before you start using the SDK, you should understand a bit about how the SDK works with Customer.io. sequenceDiagram participant A as Mobile User participant B as SDK participant C as Customer.io A-->>B: Anonymous User activity B-->>C:   A->>B: Logs in (identify method) rect rgb(229, 254, 249) Note over A,C: Now you can Send events and receive messages B-->>C: Person added/updated in CIO C-->>C: Associate anonymoushttps://docs.customer.io/integrations/sdk/react-native/5.x/getting-started/how-it-works/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/5.x/getting-started/how-it-works/Our SDKs provide a ready-made integration to identify people who use mobile devices and send them notifications. Before you start using the SDK, you should understand a bit about how the SDK works with Customer.io. sequenceDiagram participant A as Mobile User participant B as SDK participant C as Customer.io A-->>B: Anonymous User activity B-->>C:   A->>B: Logs in (identify method) rect rgb(229, 254, 249) Note over A,C: Now you can Send events and receive messages B-->>C: Person added/updated in CIO C-->>C: Associate anonymoushttps://docs.customer.io/integrations/sdk/react-native/getting-started/how-it-works/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/getting-started/how-it-works/Our SDKs provide a ready-made integration to identify people who use mobile devices and send them notifications. Before you start using the SDK, you should understand a bit about how the SDK works with Customer.io. sequenceDiagram participant A as Mobile User participant B as SDK participant C as Customer.io A-->>B: Anonymous User activity B-->>C:   A->>B: Logs in (identify method) rect rgb(229, 254, 249) Note over A,C: Now you can Send events and receive messages B-->>C: Person added/updated in CIO C-->>C: Associate anonymoushttps://docs.customer.io/integrations/data-out/connections/hubspot/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/hubspot/There are two versions of this integration You’ll see two entries for HubSpot in our integration catalog, with one labeled Web. We typically recommend that you use the standard integration, the one not labeled “Web” when possible. The web version of this integration only works with our JavaScript client and does not pass data through Customer.io’s servers, which can make it hard to debug your integration, capture a history of events sent to the integration, and so on.https://docs.customer.io/integrations/sdk/android/2.x/identify/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/android/2.x/identify/You must have have the Tracking SDK to use this feature. implementation 'io.customer.android:tracking:<version-here>' This page is part of a setup flow for the SDK. Before you continue, make sure you've implemented previous features—i.e. you can't identify people before you initialize the SDK! graph LR getting-started(Install SDK) -->B(Initialize SDK) B --> identify(identify people) identify -.-> track-events(Send events) identify -.-> push(Receive push) identify -.-> rich-push(Receive Rich Push) track-events --> test-support(Write tests) push --> test-support rich-push --> test-support identify -.https://docs.customer.io/integrations/sdk/android/3.x/identify/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/android/3.x/identify/You must have have the Tracking SDK to use this feature. implementation 'io.customer.android:tracking:3.11.1' This page is part of a setup flow for the SDK. Before you continue, make sure you've implemented previous features—i.e. you can't identify people before you initialize the SDK! graph LR getting-started(Install SDK) -->B(Initialize SDK) B --> identify(identify people) identify -.-> track-events(Send events) identify -.-> push(Receive push) identify -.-> rich-push(Receive Rich Push) track-events --> test-support(Write tests) push --> test-support rich-push --> test-support identify -.https://docs.customer.io/integrations/sdk/android/tracking/identify/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/android/tracking/identify/Identify a person Identifying a person: Adds or updates the person in your workspace. This is basically the same as an identify call to our server-side API. Saves the person’s information on the device. Future calls to the SDK reference the identified person. For example, after you identify a person, any events that you track are automatically associated with that person. Associates the current device token with the the person.https://docs.customer.io/integrations/sdk/expo/1.x/identify/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/expo/1.x/identify/This page is part of a setup flow for the SDK. Before you continue, make sure you've implemented previous features—i.e. you can't identify people before you initialize the SDK! graph LR getting-started(Install SDK) -->B(Initialize SDK) B --> identify(identify people) identify -.-> track-events(Send events) identify -.-> push(Receive push) identify -.-> in-app(Receive in-app) click getting-started href "/integrations/sdk/expo/getting-started/#install" click B href "/integrations/sdk/expo/getting-started/#initialize-the-sdk" click identify href "/integrations/sdk/expo/identify" click track-events href "/integrations/sdk/expo/track-events/" click register-token href "https://docs.customer.io/integrations/sdk/expo/tracking/identify/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/expo/tracking/identify/Identify a person Identifying a person: Adds or updates the person in your workspace. This is basically the same as an identify call to our server-side API. Saves the person’s information on the device. Future calls to the SDK reference the identified person. For example, after you identify a person, any events that you track are automatically associated with that person. Associates the current device token with the the person.https://docs.customer.io/integrations/sdk/flutter/1.x/identify/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/flutter/1.x/identify/This page is part of a setup flow for the SDK. Before you continue, make sure you've implemented previous features—i.e. you can't identify people before you initialize the SDK! graph LR getting-started(Install SDK) -->B(Initialize SDK) B --> identify(identify people) identify -.-> track-events(Send events) identify -.-> push(Receive push) identify -.-> in-app(Receive in-app) click getting-started href "/integrations/sdk/flutter/getting-started/#install" click B href "/integrations/sdk/flutter/getting-started/#initialize-the-sdk" click identify href "/integrations/sdk/flutter/identify" click track-events href "/integrations/sdk/flutter/track-events/" click register-token href "https://docs.customer.io/integrations/sdk/flutter/2.x/tracking/identify/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/flutter/2.x/tracking/identify/This page is part of a setup flow for the SDK. Before you continue, make sure you've implemented previous features—i.e. you can't identify people before you initialize the SDK! graph LR getting-started(Install SDK) -->B(Initialize SDK) B --> identify(identify people) identify -.-> track-events(Send events) identify -.-> push(Receive push) identify -.-> in-app(Receive in-app) click getting-started href "/integrations/sdk/flutter/getting-started/#install" click B href "/integrations/sdk/flutter/getting-started/#initialize-the-sdk" click identify href "/integrations/sdk/flutter/identify" click track-events href "/integrations/sdk/flutter/track-events/" click register-token href "https://docs.customer.io/integrations/sdk/flutter/tracking/identify/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/flutter/tracking/identify/This page is part of a setup flow for the SDK. Before you continue, make sure you've implemented previous features—i.e. you can't identify people before you initialize the SDK! graph LR getting-started(Install SDK) -->B(Initialize SDK) B --> identify(identify people) identify -.-> track-events(Send events) identify -.-> push(Receive push) identify -.-> in-app(Receive in-app) click getting-started href "/integrations/sdk/flutter/getting-started/#install" click B href "/integrations/sdk/flutter/getting-started/#initialize-the-sdk" click identify href "/integrations/sdk/flutter/identify" click track-events href "/integrations/sdk/flutter/track-events/" click register-token href "https://docs.customer.io/integrations/sdk/ios/1.x/identify/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/1.x/identify/This page is part of a setup flow for the SDK. Before you continue, make sure you've implemented previous features—i.e. you can't identify people before you initialize the SDK! graph LR getting-started(Install SDK) -->B(Initialize SDK) B --> identify(identify people) identify -.-> track-events(Send events) identify -.-> register-token(Register Device Token) register-token -.-> push(Receive push) register-token -.-> rich-push(Receive Rich Push) track-events --> test-support(Write tests) push --> test-support rich-push --> test-support identify -.-> in-app(Receive in-app) in-app --> test-support click getting-started href "https://docs.customer.io/integrations/sdk/ios/2.x/identify/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/2.x/identify/This page is part of a setup flow for the SDK. Before you continue, make sure you've implemented previous features—i.e. you can't identify people before you initialize the SDK! graph LR getting-started(Install SDK) -->B(Initialize SDK) B --> identify(identify people) identify -.-> track-events(Send events) identify -.-> register-token(Register Device Token) register-token -.-> push(Receive push) register-token -.-> rich-push(Receive Rich Push) track-events --> test-support(Write tests) push --> test-support rich-push --> test-support identify -.-> in-app(Receive in-app) in-app --> test-support click getting-started href "https://docs.customer.io/integrations/sdk/ios/3.x/tracking/identify/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/3.x/tracking/identify/Identify a person Identifying a person: Adds or updates the person in your workspace. This is basically the same as an identify call to our server-side API. Saves the person’s information on the device. Future calls to the SDK reference the identified person. For example, after you identify a person, any events that you track are automatically associated with that person. If you already registered a device token, identifying a person automatically associates the token with the identified person.https://docs.customer.io/integrations/sdk/ios/tracking/identify/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/tracking/identify/Identify a person Identifying a person: Adds or updates the person in your workspace. This is basically the same as an identify call to our server-side API. Saves the person’s information on the device. Future calls to the SDK reference the identified person. For example, after you identify a person, any events that you track are automatically associated with that person. If you already registered a device token, identifying a person automatically associates the token with the identified person.https://docs.customer.io/integrations/sdk/react-native/2.x/identify/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/2.x/identify/This page is part of a setup flow for the SDK. Before you continue, make sure you've implemented previous features—i.e. you can't identify people before you initialize the SDK! graph LR getting-started(Install SDK) -->B(Initialize SDK) B --> identify(identify people) identify -.-> track-events(Send events) identify -.-> push(Receive push) identify -.-> in-app(Receive in-app) click getting-started href "/integrations/sdk/react-native/getting-started/#install" click B href "/integrations/sdk/react-native/getting-started/#initialize-the-sdk" click identify href "/integrations/sdk/react-native/identify" click track-events href "/integrations/sdk/react-native/track-events/" click register-token href "https://docs.customer.io/integrations/sdk/react-native/3.x/identify/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/3.x/identify/This page is part of a setup flow for the SDK. Before you continue, make sure you've implemented previous features—i.e. you can't identify people before you initialize the SDK! graph LR getting-started(Install SDK) -->B(Initialize SDK) B --> identify(identify people) identify -.-> track-events(Send events) identify -.-> push(Receive push) identify -.-> in-app(Receive in-app) click getting-started href "/integrations/sdk/react-native/getting-started/#install" click B href "/integrations/sdk/react-native/getting-started/#initialize-the-sdk" click identify href "/integrations/sdk/react-native/identify" click track-events href "/integrations/sdk/react-native/track-events/" click register-token href "https://docs.customer.io/integrations/sdk/react-native/4.x/tracking/identify/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/4.x/tracking/identify/Identify a person Identifying a person: Adds or updates the person in your workspace. This is basically the same as an identify call to our server-side API. Saves the person’s information on the device. Future calls to the SDK reference the identified person. For example, after you identify a person, any events that you track are automatically associated with that person. Associates the current device token with the the person.https://docs.customer.io/integrations/sdk/react-native/5.x/tracking/identify/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/5.x/tracking/identify/Identify a person Identifying a person: Adds or updates the person in your workspace. This is basically the same as an identify call to our server-side API. Saves the person’s information on the device. Future calls to the SDK reference the identified person. For example, after you identify a person, any events that you track are automatically associated with that person. Associates the current device token with the the person.https://docs.customer.io/integrations/sdk/react-native/tracking/identify/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/tracking/identify/Identify a person Identifying a person: Adds or updates the person in your workspace. This is basically the same as an identify call to our server-side API. Saves the person’s information on the device. Future calls to the SDK reference the identified person. For example, after you identify a person, any events that you track are automatically associated with that person. Associates the current device token with the the person.https://docs.customer.io/integrations/sdk/android/in-app/in-app/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/android/in-app/in-app/How it works An in-app message is a message that people see within the app. To set up in app messaging, install and initialize the tracking and messaging-in-app packages. People won’t see your in-app messages until they open your app. If you set an expiry period for your message, and that time elapses before someone opens your app, they won’t see your message. You can also set page rules to display your in-app messages when people visit specific pages in your app.https://docs.customer.io/integrations/sdk/flutter/2.x/in-app-messages/in-app/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/flutter/2.x/in-app-messages/in-app/How it works An in-app message is a message that people see in your app. People won’t see your in-app messages until they open your app. If you set an expiry period for your message, and that time elapses before someone opens your app, they won’t see your message. You can also set page rules to display your in-app messages when people visit specific pages in your app. However, to take advantage of page rules, you need to use screen tracking features.https://docs.customer.io/integrations/sdk/flutter/in-app-messages/in-app/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/flutter/in-app-messages/in-app/How it works An in-app message is a message that people see in your app. People won’t see your in-app messages until they open your app. If you set an expiry period for your message, and that time elapses before someone opens your app, they won’t see your message. You can also set page rules to display your in-app messages when people visit specific pages in your app. However, to take advantage of page rules, you need to use screen tracking features.https://docs.customer.io/journeys/inbound-metrics/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/inbound-metrics/ Have you set up inbound messaging? You need to set up inbound messaging to see inbound metrics and activities. See Getting started for more information. The Replied status Most messages have statuses like sent, opened, clicked, and so on. For SMS and MMS messages, we also track replied. While sometimes your call to action might be for users to click a link, SMS lets you set an action item as a reply to a message with a particular keyword.https://docs.customer.io/integrations/data-out/connections/intercom/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/intercom/There are two versions of this integration You’ll see two entries for Intercom in our integration catalog, with one labeled Web. We typically recommend that you use the standard integration, the one not labeled “Web” when possible. The web version of this integration only works with our JavaScript client and does not pass data through Customer.io’s servers, which can make it hard to debug your integration, capture a history of events sent to the integration, and so on.https://docs.customer.io/integrations/data-in/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/getting-started/What is a data-in integration? A data-in integration is a website, mobile app, database, or service that you want to capture data from—it’s a “source” of data! These integrations help you collect data from your various customer touchpoints so you can route it to Customer.io and other outgoing integrations, so you can maintain an unbroken chain of customer data throughout your stack. You’ll add a different data-in integrations for each website or app you want to collect data from.https://docs.customer.io/integrations/data-out/data-warehouses/data-warehouse-intro/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/data-warehouses/data-warehouse-intro/How database and data warehouse integrations work Rather than streaming data to your warehouse in real time, like with most outbound integrations, our database and data warehouse integrations send data to your storage buckets in bulk at regular intervals. Then you’ll ingest those files into the data warehouse or database of your choice. These integrations only create new files in your storage bucket; they’ll never overwrite or append an existing file, so you can delete or remove files from your storage bucket after you ingest them into their ultimate integration—your data warehouse or database.https://docs.customer.io/journeys/broadcasts-in-customerio/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/broadcasts-in-customerio/If you’re new to Customer.io, checkout Campaigns, broadcasts, and transactional messages to make sure you’re creating the right kind of automation. How it works A broadcast is a message or workflow that you trigger (or schedule) for a group of people. It’s not “active” like a campaign: you’ll send, schedule, or trigger your broadcast for a group of people. Anybody outside that group won’t get the broadcast unless you send it again.https://docs.customer.io/journeys/3-layouts-and-customerio/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/3-layouts-and-customerio/What are layouts?  Layouts are only available in our rich text or code editors. You cannot use layouts with Design Studio or our drag and drop editor; instead, start from a template. Or learn more about the reusable content features available in Design Studio (components) and the drag and drop editor (saved rows, snippets). When using our Rich Text and Code editors to design your email templates, there are two parts to emails: the content and the layout.https://docs.customer.io/journeys/journeys-overview/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/journeys-overview/Journeys incorporates data from your customer touchpoints, helping you customize campaigns and send sophisticated, personalized messages that support and engage your audience.  New here? Check out our Quick Start Guide This section provides an overview of Journeys. But we recommend using our Quick Start Guide if you’re ready to jump in and start using Customer.io. How it all works The image below illustrates what a well-rounded integration with Customer.io looks like.https://docs.customer.io/integrations/data-out/connections/koala/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/koala/Getting started Go to Data & Integrations > Integrations and select the Koala entry in the Directory tab. (Optional) Select the data sources that you want to connect to your outbound integration. You can always connect data sources later. We’ll only show you data sources that work with your integration. Configure your integration. Project Slug: Please enter your Public API Key found in your Koala workspace settings. Click Enable Destination.https://docs.customer.io/integrations/data-out/connections/launchdarkly/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/launchdarkly/Getting started Go to Data & Integrations > Integrations and select the LaunchDarkly entry in the Directory tab. (Optional) Select the data sources that you want to connect to your outbound integration. You can always connect data sources later. We’ll only show you data sources that work with your integration. Configure your integration. Client Id: Find and copy the client-side ID in the LaunchDarkly account settings page. Click Enable Destination.https://docs.customer.io/journeys/link-tracking/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/link-tracking/We track the number and percentage of recipients who clicked links in your messages: We also track which links they clicked: You can view clicked links on a person’s profile through the Activity tab by expanding a Clicked action entry:  Your links must include the protocol—HTTP or HTTPS We can’t track links if you don’t include the protocol. To generate secure HTTPS links, visit HTTPS Link Tracking. Emails For campaigns and API-triggered broadcasts, link tracking is enabled for emails in your workflows by default.https://docs.customer.io/journeys/liquid-tag-list/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/liquid-tag-list/https://docs.customer.io/integrations/data-out/connections/livelike-cloud/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/livelike-cloud/Getting started Go to Data & Integrations > Integrations and select the LiveLike entry in the Directory tab. (Optional) Select the data sources that you want to connect to your outbound integration. You can always connect data sources later. We’ll only show you data sources that work with your integration. Configure your integration. Client Id: Your LiveLike Application Client ID. Producer Token: Your LiveLike Producer token. Click Enable Destination. Actions When you’re done setting things up, you can go to the Actions tab to see how we map incoming data to your integration.https://docs.customer.io/integrations/data-out/connections/logrocket/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/logrocket/Getting started Go to Data & Integrations > Integrations and select the LogRocket entry in the Directory tab. (Optional) Select the data sources that you want to connect to your outbound integration. You can always connect data sources later. We’ll only show you data sources that work with your integration. Configure your integration. App ID: The LogRocket app ID. Network Sanitization: Sanitize all network request and response bodies from session recordings.https://docs.customer.io/integrations/data-in/connections/hubspot/mapping-to-customerio/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/hubspot/mapping-to-customerio/In most cases when you map a type of HubSpot data to Customer.io, you should use our default settings and focus only on the Fields that you want to bring into Customer.io. But if the default settings don’t quite work for your use case, you can update mappings in a few different ways: The primary identifiers for the data you bring into Customer.io (its id in HubSpot, email address for contacts, or another field).https://docs.customer.io/integrations/data-in/connections/salesforce/mapping-to-customerio/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/salesforce/mapping-to-customerio/You’ll set up a sync for each kind of data you want to send through your pipeline. In most cases, you’ll want to follow our typical mappings. But the way you map your data to Customer.io depends on what you want to do with it—send messages, use it to trigger messages, or manage relationships! Typical mappings Remember, you’ll convert your Salesforce data to people, events, custom objectsAn object is a non-person entity that you can associate with one or more people—like a company, account, or online course.https://docs.customer.io/integrations/data-out/connections/meta-pixel/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/meta-pixel/Getting started Go to Data & Integrations > Integrations and select the Meta (Facebook) Pixel entry in the Directory tab. (Optional) Select the data sources that you want to connect to your outbound integration. You can always connect data sources later. We’ll only show you data sources that work with your integration. Configure your integration. Pixel ID: Your Pixel ID from the snippet created on the Facebook Pixel creation page.https://docs.customer.io/integrations/data-out/connections/metronome/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/metronome/Getting started Go to Data & Integrations > Integrations and select the Metronome entry in the Directory tab. (Optional) Select the data sources that you want to connect to your outbound integration. You can always connect data sources later. We’ll only show you data sources that work with your integration. Configure your integration. Api Token: Your Metronome API Token Click Enable Destination. Actions When you’re done setting things up, you can go to the Actions tab to see how we map incoming data to your integration.https://docs.customer.io/integrations/data-in/connections/reverse-etl/microsoft-sql/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/reverse-etl/microsoft-sql/Best Practices Before you add a Reverse ETL source, you should take some measures to ensure the security of your customers’ data and limit performance impacts to your database and Customer.io workspace. Create a new database user/service account. Implement a database user with minimal privileges specifically for Customer.io import/sync operations. This person only requires read permissions with access limited to the tables you want to sync from. Avoid using your main database instance.https://docs.customer.io/integrations/data-out/connections/mixpanel/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/mixpanel/Getting started Go to Data & Integrations > Integrations and select the Mixpanel entry in the Directory tab. (Optional) Select the data sources that you want to connect to your outbound integration. You can always connect data sources later. We’ll only show you data sources that work with your integration. Configure your integration. Project Token: Mixpanel project token. Api Secret: Mixpanel project secret. Api Region: Learn about EU data residencyhttps://docs.customer.io/integrations/data-out/connections/mixpanel-legacy/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/mixpanel-legacy/How it works This integration sends audience engagement data—also available as reporting webhooks—to Mixpanel, where you can use it alongside your other user and analytics data to gain insight into your audience’s behaviors. The events we send are both based on things that happen in Customer.io and your customer activity. For example, an email sent event indicates that we’ve sent an email to a person, but an email clicked event lets you know that your audience clicked a link in your email.https://docs.customer.io/integrations/data-out/connections/moengage/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/moengage/Getting started Go to Data & Integrations > Integrations and select the Moengage entry in the Directory tab. (Optional) Select the data sources that you want to connect to your outbound integration. You can always connect data sources later. We’ll only show you data sources that work with your integration. Configure your integration. Api Id: Your Moengage API Id Api Key: Your Moengage API Key Region: The region to send your data.https://docs.customer.io/integrations/data-out/connections/azure-blob-storage/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/azure-blob-storage/How it works This integration sends CSV, JSON, or parquet files containing your data to your MS Azure Blob Storage (Advanced) bucket. Then you can ingest the files in your storage bucket to your data warehouse of choice. We write files for each type of incoming call to your storage bucket every 10 minutes. So you’ll have files for identify calls, track calls, and so on. Files are named with an incrementing number, so it’s easy to determine the sequence of files, and the order of incoming calls.https://docs.customer.io/integrations/data-in/connections/reverse-etl/mysql/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/reverse-etl/mysql/Best Practices Before you add a Reverse ETL source, you should take some measures to ensure the security of your customers’ data and limit performance impacts to your database and Customer.io workspace. Create a new database user/service account. Implement a database user with minimal privileges specifically for Customer.io import/sync operations. This person only requires read permissions with access limited to the tables you want to sync from. Avoid using your main database instance.https://docs.customer.io/integrations/data-in/connections/servers/node/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/servers/node/How it works Our Node.js library helps you record source events from your node-side code. Requests from your Node.js server go to our servers, and we route your data to your destinations. This library uses an internal queue so that your identify and track calls are fast and non-blocking. It also batches requests and flushes asynchronously to Customer.io’s servers. Like our other libraries, you can log anonymous activity—track and page events—with an anonymousId.https://docs.customer.io/journeys/object-types/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/object-types/An object type defines the kind of one-to-many relationship you want to set, like Accounts, Employers, or Job Postings. The first three types appear in the side nav under People. If you have more than three, we’ll nest all of your object types under Custom Objects. Depending on your plan type, you can create 2 or more object types. In our API, we identify object types as integers starting at 1.https://docs.customer.io/journeys/recipes/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/recipes/Recipes typically have some Ingredients that we’ll tell you about: a few things that need to be in place to use the recipe. These are things like attributesA key-value pair that you associate with a person or an object—like a person’s name, the date they were created in your workspace, or a company’s billing date etc. Use attributes to target people and personalize messages. or eventsSomething that a person in your workspace did.https://docs.customer.io/journeys/people-overview/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/people-overview/When you go to the People page, you’ll see a list of people you’ve identifiedThe Customer.io operation that adds or updates a person. When you identify a person, Customer.io either adds a person if they don’t exist in your workspace, or updates them if they do. Before you identify someone (by their email address or an ID), you can track them anonymously.. From here, you can click on any individual person to see their profile—all the data that you have about a person.https://docs.customer.io/integrations/data-out/connections/pinterest-conversions/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/pinterest-conversions/Getting started Go to Data & Integrations > Integrations and select the Pinterest Conversions entry in the Directory tab. (Optional) Select the data sources that you want to connect to your outbound integration. You can always connect data sources later. We’ll only show you data sources that work with your integration. Configure your integration. Ad Account Id: Unique identifier of an ad account. This can be found in the Pinterest UI by following the steps mentioned here.https://docs.customer.io/integrations/data-out/connections/pipedrive/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/pipedrive/Getting started Go to Data & Integrations > Integrations and select the Pipedrive entry in the Directory tab. (Optional) Select the data sources that you want to connect to your outbound integration. You can always connect data sources later. We’ll only show you data sources that work with your integration. Configure your integration. Domain: Pipedrive domain. This is found in Pipedrive in Settings > Company settings > Company domain. Api Token: Pipedrive API token.https://docs.customer.io/integrations/data-out/connections/playerzero/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/playerzero/Getting started Go to Data & Integrations > Integrations and select the PlayerZero entry in the Directory tab. (Optional) Select the data sources that you want to connect to your outbound integration. You can always connect data sources later. We’ll only show you data sources that work with your integration. Configure your integration. Project Id: The Project ID where you want to send data. You can find this ID on the Project Data Collection page.https://docs.customer.io/integrations/data-in/connections/reverse-etl/postgresql/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/reverse-etl/postgresql/Best Practices Before you add a Reverse ETL source, you should take some measures to ensure the security of your customers’ data and limit performance impacts to your database and Customer.io workspace. Create a new database user/service account. Implement a database user with minimal privileges specifically for Customer.io import/sync operations. This person only requires read permissions with access limited to the tables you want to sync from. Avoid using your main database instance.https://docs.customer.io/integrations/data-in/connections/servers/python/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/servers/python/How it works Our python library helps you record source events from your node-side code. Requests from your python app go to our servers, and we route your data to your destinations. This library uses an internal queue so that your identify and track calls are non-blocking and fast. It also batches requests and flushes asynchronously to Customer.io’s servers. Like our other libraries, you can log anonymous activity—track and page events—with an anonymousId.https://docs.customer.io/integrations/data-out/connections/qualtrics/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/qualtrics/Getting started Go to Data & Integrations > Integrations and select the Qualtrics entry in the Directory tab. (Optional) Select the data sources that you want to connect to your outbound integration. You can always connect data sources later. We’ll only show you data sources that work with your integration. Configure your integration. Api Token: Qualtrics API token found in your Qualtrics account under "Account settings" -> "Qualtrics IDs." Datacenter: Qualtrics datacenter id that identifies where your qualtrics instance is located.https://docs.customer.io/get-started/quick-start-guide/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/get-started/quick-start-guide/Get started This guide is designed to walk you through the most common parts of the setup path and introduce you to the major parts of our platform. When you start setting up Customer.io, we provide you with a Setup List on your Workspace’s Dashboard. You don’t have to do everything on the list, but you must do the following things before you can really take advantage of Customer.io: Create an account and a workspace.https://docs.customer.io/integrations/sdk/expo/quick-start-guide/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/expo/quick-start-guide/ Our MCP server can help you get started Our MCP server includes SDK-installation tools that can help you get integrated quickly with Customer.io and troubleshoot any issues you might have. See Set up an MCP server to get started. Setup process overview Expo provides a managed framework to help you build React Native mobile apps. Our Expo plugin relies on our React Native SDK. When you run the prebuild, we’ll generate the native files you’ll need to integrate Customer.https://docs.customer.io/integrations/data-out/connections/webhooks/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/webhooks/You can find information about each individual event type on our Reporting Webhooks API documentation.  Looking to send a custom webhook to a specific API via your workflow? Check out Webhook Actions, instead. Setup Log in and go to Data & Integrations > Integrations. Find and select Reporting Webhooks. Click Add Reporting Webhook. Enter the Webhook Endpoint URL where you want to receive events. While the endpoint URL can be either HTTP or HTTPs, we recommend HTTPS to protect customer information.https://docs.customer.io/journeys/inbound-campaigns/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/inbound-campaigns/How it works We treat inbound messages like events in Customer.io: they can trigger campaignsCampaigns are automated workflows you set up to send people messages and perform other actions when they meet your criteria. and add people to segmentsA segment is a group of people in your workspace. Use segments to trigger campaigns, track membership over time, or fine-tune your audience. There are two types of segments: data-driven and manual.https://docs.customer.io/integrations/data-out/connections/ripe/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/ripe/There are two versions of this integration You’ll see two entries for Ripe in our integration catalog, with one labeled Web. We typically recommend that you use the standard integration, the one not labeled “Web” when possible. The web version of this integration only works with our JavaScript client and does not pass data through Customer.io’s servers, which can make it hard to debug your integration, capture a history of events sent to the integration, and so on.https://docs.customer.io/integrations/data-out/connections/rudderstack-legacy/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/rudderstack-legacy/How it works Rudderstack takes advantage of reporting webhooks when using Customer.io as a source. Rudderstack converts our webhooks to their event format. A person’s customer_id (a legacy identifier for id) in Customer.io becomes their userId in Rudderstack. If a person doesn’t have an id, Rudderstack sets a person’s email address as an anonymousId. { "event_id": "01E4C4CT6YDC7Y5M7FE1GWWPQJ", "object_type": "email", "timestamp": 1613063089, "metric": "opened", "data": { "trigger_id": 1, "customer_id": "42", "delivery_id": "ZAIAAVTJVG0QcCok0-0ZKj6yiQ==", "action_id": 96, "broadcast_id": 2, "journey_id": "01GW20GXAAXBKZD8J96M8FNV3R", "parent_action_id": 1, "identifiers": { "id": "42", "email": "test@example.https://docs.customer.io/integrations/data-out/connections/saleswings/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/saleswings/Getting started Go to Data & Integrations > Integrations and select the SalesWings entry in the Directory tab. (Optional) Select the data sources that you want to connect to your outbound integration. You can always connect data sources later. We’ll only show you data sources that work with your integration. Configure your integration. Api Key: API key for your SalesWings project. Environment: SalesWings environment this destination is connected with. Click Enable Destination.https://docs.customer.io/search/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/search/https://docs.customer.io/integrations/data-out/connections/segment/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/segment/Getting started Go to Data & Integrations > Integrations and select the Segment entry in the Directory tab. (Optional) Select the data sources that you want to connect to your outbound integration. You can always connect data sources later. We’ll only show you data sources that work with your integration. Configure your integration. Source Write Key: The Write Key of a Segment source. Endpoint: The region to send your data.https://docs.customer.io/integrations/data-out/connections/segment-legacy/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/segment-legacy/ Disable and re-enable this integration to gain access to new features! We updated this integration in May of 2022. If you enabled your Segment Source integration before then, disable the integration and re-enable it to gain access to new events and settings. Enable Customer.io as a Segment source To enable Customer.io as a Segment source, you need both a Customer.io and a Segment.com account. If you are creating a new Segment account, enter “Customer.https://docs.customer.io/journeys/webhooks-action/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/webhooks-action/Here’s James, a Senior Solutions Architect at Customer.io, with a quick explanation to help you understand webhook actions and how you can use them to personalize messages for your audience.  You can trigger webhooks without a campaign Our shortcuts feature lets you manually trigger external APIs for anybody on your People page without entering that person into a campaign. You might do this to manually activate or deactivate a person’s account, to open a help desk ticket, etc.https://docs.customer.io/journeys/line-send-messages/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/line-send-messages/Send a LINE message As a part of your campaign or broadcast workflow: Drag LINE into your workflow. Click the message and click Add Content. If you store your audience’s LINE ID in an attribute other than line_id, set the correct attribute in the To field. Add text and image content to your message. Click Save Changes. What kinds of messages can I send? While LINE supports a variety of message types, we support basic text and image messages.https://docs.customer.io/integrations/data-out/connections/sendgrid/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/sendgrid/Getting started Go to Data & Integrations > Integrations and select the SendGrid Marketing Campaigns entry in the Directory tab. (Optional) Select the data sources that you want to connect to your outbound integration. You can always connect data sources later. We’ll only show you data sources that work with your integration. Configure your integration. Send Grid Api Key: The Api key for your SendGrid account. Click Enable Destination. Actions When you’re done setting things up, you can go to the Actions tab to see how we map incoming data to your integration.https://docs.customer.io/accounts-and-workspaces/login-session/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/accounts-and-workspaces/login-session/How it works We manage your session in Customer.io using a secure HTTP-only cookie. The cookie can only be read by the browser, protecting your session from unauthorized access and malicious cross-site scripting (XSS) attacks. By default, our session cookies last for 14 days. But, as an administrator, you can set the duration of sessions for everybody on your team to fit your security policy—down to 1 hour. If a session expires while a person is logged in, they’ll be prompted to re-authenticate, but they won’t lose their work.https://docs.customer.io/journeys/transactional-email/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/transactional-email/ New to transactional messaging? Check out our getting started section to learn more about transactional concepts and how our transactional API works. Before you begin Before you can send transactional emails, you need to: Confirm your registration email and verify your account. Authenticate your sending domain. If you configured a custom SMTP server, contact us to manually authenticate your sending domain. Get your app API key. This is the bearer token that you’ll use when calling the transactional API.https://docs.customer.io/integrations/sdk/react-native/4.x/in-app-messages/set-up-in-app/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/4.x/in-app-messages/set-up-in-app/How it works An in-app message is a message that people see within the app. People won’t see your in-app messages until they open your app. If you set an expiry period for your message, and that time elapses before someone opens your app, they won’t see your message. You can also set page rules to display your in-app messages when people visit specific pages in your app. However, to take advantage of page rules, you need to use screen tracking features.https://docs.customer.io/integrations/sdk/react-native/5.x/in-app-messages/set-up-in-app/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/5.x/in-app-messages/set-up-in-app/How it works An in-app message is a message that people see within the app. People won’t see your in-app messages until they open your app. If you set an expiry period for your message, and that time elapses before someone opens your app, they won’t see your message. You can also set page rules to display your in-app messages when people visit specific pages in your app. However, to take advantage of page rules, you need to use screen tracking features.https://docs.customer.io/integrations/sdk/react-native/in-app-messages/set-up-in-app/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/in-app-messages/set-up-in-app/How it works An in-app message is a message that people see within the app. People won’t see your in-app messages until they open your app. If you set an expiry period for your message, and that time elapses before someone opens your app, they won’t see your message. You can also set page rules to display your in-app messages when people visit specific pages in your app. However, to take advantage of page rules, you need to use screen tracking features.https://docs.customer.io/integrations/sdk/flutter/2.x/push-notifications/push-setup/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/flutter/2.x/push-notifications/push-setup/How it works If you’ve followed our getting started instructions, you’re already set up to send push notifications to your Android audience. But you’ll need to add a bit of code to support your iOS users. Remember that a device/user can’t receive a push notification until you: (iOS) Register a device token for the device; code samples on this page help you do that. Identify a person. This associates a token with the person; you can’t send push notifications to a device until you identify the recipient.https://docs.customer.io/integrations/sdk/flutter/push-notifications/push-setup/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/flutter/push-notifications/push-setup/How it works If you’ve followed our getting started instructions, you’re already set up to send push notifications to your Android audience. But you’ll need to add a bit of code to support your iOS users. Remember that a device/user can’t receive a push notification until you: (iOS) Register a device token for the device; code samples on this page help you do that. Identify a person. This associates a token with the person; you can’t send push notifications to a device until you identify the recipient.https://docs.customer.io/integrations/sdk/ios/3.x/push/push-setup/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/3.x/push/push-setup/Before you begin This page explains how to register for push notifications using our SDK. But, before you can send push notifications, you need to add your push service credentials to Customer.io. See our push service certificates to learn more. If you haven’t already, you’ll need to install the push package for the push service you use—APNs or FCM—and enable the Push Notifications capability in XCode. See our quick start guide page for installation instructions.https://docs.customer.io/integrations/sdk/ios/push/push-setup/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/push/push-setup/Before you begin This page explains how to register for push notifications using our SDK. But, before you can send push notifications, you need to add your push service credentials to Customer.io. See our push service certificates to learn more. If you haven’t already, you’ll need to install the push package for the push service you use—APNs or FCM—and enable the Push Notifications capability in XCode. For FCM users, you’ll also need to install the CioFirebaseWrapper dependency.https://docs.customer.io/journeys/inbox-setup/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/inbox-setup/The notification inbox lets you send messages to your audience that they can access at their leisure.  We’re actively working on this feature We’re just getting started with inbox messaging. For now, the feature requires some extra work on your part to build your own inbox, style messages in your client, and listen for events. We’re working on features to make this all easier. How it works Inbox messages aren’t displayed immediately (or along our normal prioritization settings for in-app messages), but rather are displayed through a custom inbox UI.https://docs.customer.io/journeys/in-app-web/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/in-app-web/How it works While we call some messages “in-app” messages, they’re not limited to mobile apps! You can use “in-app” messages to send things like banners and modal messages that appear on your website. These are great ways to alert your users about new features, send promotions, ask for feedback using surveys, and so on. To get set up with in-app messages, you’ll copy our JavaScript source snippet to your website.https://docs.customer.io/integrations/data-out/connections/slack/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/slack/Getting started Setting up your Slack integration is trivial. To take advantage of it, you’ll have to set up the Post Message action. Go to Data & Integrations > Integrations and select the Slack entry in the Directory tab. (Optional) Select the data sources that you want to connect to your outbound integration. You can always connect data sources later. We’ll only show you data sources that work with your integration.https://docs.customer.io/integrations/data-in/connections/reverse-etl/snowflake/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/reverse-etl/snowflake/Best Practices Before you add a Reverse ETL source, you should take some measures to ensure the security of your customers’ data and limit performance impacts to your database and Customer.io workspace. Create a new database user/service account. Implement a database user with minimal privileges specifically for Customer.io import/sync operations. This person only requires read permissions with access limited to the tables you want to sync from. Avoid using your main database instance.https://docs.customer.io/integrations/data-out/connections/snowflake-data-out/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/snowflake-data-out/ We have two integrations! This integration uses Customer.io as a source, and syncs data from your Customer.io workspace to your data warehouse, including campaign information. Our other integration sends data from multiple sources to your data warehouse. While the other integration captures data from multiple sources, even if those sources don’t send data to your workspace, it cannot capture some data from within Customer.io like campaign information. How it works This integration exports individual parquet files for Deliveries, Metrics, Subjects, Outputs, Content, People, and Attributes to your storage bucket.https://docs.customer.io/integrations/data-out/connections/snowflake/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/snowflake/How it works This integration sends CSV, JSON, or parquet files containing your data to your Snowflake (Advanced) bucket. Then you can ingest the files in your storage bucket to your data warehouse of choice. We write files for each type of incoming call to your storage bucket every 10 minutes. So you’ll have files for identify calls, track calls, and so on. Files are named with an incrementing number, so it’s easy to determine the sequence of files, and the order of incoming calls.https://docs.customer.io/integrations/data-out/connections/sprig/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/sprig/Getting started Go to Data & Integrations > Integrations and select the Sprig entry in the Directory tab. (Optional) Select the data sources that you want to connect to your outbound integration. You can always connect data sources later. We’ll only show you data sources that work with your integration. Configure your integration. Env Id: Your environment ID (production or development). Debug Mode: Enable debug mode for testing purposes. Click Enable Destination.https://docs.customer.io/integrations/data-out/data-warehouses/data-warehouses-intro/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/data-warehouses/data-warehouses-intro/You can find our data warehouse integrations by going to Data & Integrations > Integrations and selecting the Databases option. From here, you can select your data warehouse or storage bucket. If your data warehouse appears twice in this list, pick the Data out integration. Check out the specific documentation for your data warehouse for help setting up your integration. How it works This integration exports individual parquet files for Deliveries, Metrics, Subjects, Outputs, Content, People, and Attributes to your storage bucket.https://docs.customer.io/journeys/feedback/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/feedback/Get feedback Feedback allows other team members to leave comments, annotations, and approvals on your email. To create and share a feedback version: Click the dropdown next to your filename and choose Feedback. Or, click Share, then select Get Feedback. Name your feedback version. Add a description to explain what changed or what kind of feedback you’re looking for. Click Get Feedback to open the feedback page. In the sidebar, click Share to copy the link to your feedback page.https://docs.customer.io/integrations/data-out/connections/talon-one/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/talon-one/Getting started Go to Data & Integrations > Integrations and select the Talon.One entry in the Directory tab. (Optional) Select the data sources that you want to connect to your outbound integration. You can always connect data sources later. We’ll only show you data sources that work with your integration. Configure your integration. Api Key: Created under Developer Settings in the Talon.One Campaign Manager. Deployment: The base URL of your Talon.https://docs.customer.io/accounts-and-workspaces/workspace-tasks/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/accounts-and-workspaces/workspace-tasks/Access tasks In your workspace’s top navigation bar, click and then choose Tasks. You’ll see your latest background tasks and their status. Click See all tasks to drill in further. From the Tasks page, you can find more information on each task by clicking . Check when the task started, how long it was queued for, and how long it took to complete. How we process priority levels You’ll also see a priority within the details of a task.https://docs.customer.io/journeys/subscription-center/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/subscription-center/If you’re looking for information on global subscriptions or the unsubscribed attribute, check out our overview on subscription options. How it works The subscription center lets people manage what messages they get through topicsA category of message, set within your workspace’s subscription center, that people can subscribe to or unsubscribe from. Topics let your audience determine the kinds of messages they want to get from you. (content types) and channel preferences (delivery methods).https://docs.customer.io/integrations/data-out/connections/tiktok-conversions/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/tiktok-conversions/Before you get started The TikTok Conversions destination uses the TikTok Events API. To use the Events API, you’ll need to generate a TikTok Pixel Code and Access Token: Create a TikTok For Business account. Create a TikTok Pixel in Developer Mode to obtain a Pixel Code. For more information about Developer Mode, see TikTok’s developer documentation. Follow instructions for Authorization and generate a long term Access Token. Getting started Go to Data & Integrations > Integrations and select the TikTok Conversions entry in the Directory tab.https://docs.customer.io/journeys/localization-getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/localization-getting-started/How it works To localize messages, you’ll follow this process: Set a language attribute for your workspace so we know how to determine a recipient’s language preference. Create messages with language variants. When you add or update people, you can set an attributeA key-value pair that you associate with a person or an object—like a person’s name, the date they were created in your workspace, or a company’s billing date etc.https://docs.customer.io/accounts-and-workspaces/login-trouble/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/accounts-and-workspaces/login-trouble/Help, Customer.io isn’t loading! If you see a perpetual loading spinner when you try to log in to Customer.io, you have trouble logging in, or you find the interface to be a little sluggish, you might have a problem with your web browser. Here’s the typical troubleshooting path for browser-related issues in Customer.io: Update your browser. Clear your browser cache. Try disabling your ad blocker or using Customer.io in incognito mode.https://docs.customer.io/integrations/data-out/connections/twilio/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/twilio/Getting started Go to Data & Integrations > Integrations and select the Twilio entry in the Directory tab. (Optional) Select the data sources that you want to connect to your outbound integration. You can always connect data sources later. We’ll only show you data sources that work with your integration. Configure your integration. Account Id: Your Twilio Account Id Token: Your Twilio Token. Phone Number: Your Twilio Phone Number with Country Code.https://docs.customer.io/integrations/data-out/connections/engage-messaging-twilio/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/engage-messaging-twilio/Getting started Go to Data & Integrations > Integrations and select the Twilio Engage Messaging entry in the Directory tab. (Optional) Select the data sources that you want to connect to your outbound integration. You can always connect data sources later. We’ll only show you data sources that work with your integration. Configure your integration. Twilio Account SID: Twilio Account SID Twilio Api Key SID: Twilio API Key SID Twilio Api Key Secret: Twilio API Key Secrethttps://docs.customer.io/integrations/data-out/connections/twilio-studio/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/twilio-studio/Getting started Go to Data & Integrations > Integrations and select the Twilio Studio entry in the Directory tab. (Optional) Select the data sources that you want to connect to your outbound integration. You can always connect data sources later. We’ll only show you data sources that work with your integration. Configure your integration. Account Sid: Your Twilio Account SID, starting with AC. You can find this in the Account Info section of your dashboard in the Twilio Console.https://docs.customer.io/integrations/data-out/connections/twitter-pixel/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/twitter-pixel/Getting started Go to Data & Integrations > Integrations and select the Twitter Pixel entry in the Directory tab. (Optional) Select the data sources that you want to connect to your outbound integration. You can always connect data sources later. We’ll only show you data sources that work with your integration. Configure your integration. Pixel ID: The Pixel ID is a unique identifier for your Twitter Pixel installation. It can be found in the "Tools" -> "Events Manager" section of your Twitter Ads account.https://docs.customer.io/journeys/branches/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/branches/Flow controls and branches Branches help you personalize campaigns or test different messages in a campaign. When people reach a flow-control block in your workflow, we’ll evaluate criteria to determine which path to send them down. We offer three types of branching flow controls that you can place anywhere in your workflows: True/False Branches: Send people go down one path if they match a condition, or down the other path if they don’t.https://docs.customer.io/integrations/data-in/source-spec/incoming-data/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/source-spec/incoming-data/How it works When you send data into Customer.io, it only takes a few different shapes—identify, track, and so on. But the services you connect your data to have different requirements and use your data in different ways! So we map incoming data to the places where you use it with what we call Actions. Actions are the things your incoming data will do when it reaches its destination, like creating people, updating people, tracking custom events, etc.https://docs.customer.io/integrations/getting-started/how-it-works/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/getting-started/how-it-works/Why integrate with Customer.io? While you can add people manually, upload CSV files, and get data into and out of Customer.io other ways, integrating with Customer.io unlocks the ability to respond to your audiences in near real-time. For example, imagine that you want to remind people to complete their purchases when they abandon their carts. Integrating with Customer.io makes this easy: your integration sends events to Customer.io when people add items to their carts, which you can then use to send messages to your audience if they don’t complete their purchases within a certain amount of time.https://docs.customer.io/integrations/data-in/semantic-events/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/semantic-events/getting-started/Many of the actionsThe source event and data that triggers an API call to your destination. For example, an incoming identify event from your sources adds or updates a person in our Customer.io Journeys destination. for outbound integrations are based on the name of the event you send. With these semantic events, we expect a certain set of properties that we use to map to multiple integration destinations. While you can send any properties and events that you want, taking advantage of our pre-defined semantic events can save you time and effort, helping you take advantage of our default actions—so it’s easier to set up data-out integrations.https://docs.customer.io/journeys/upsell-users/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/upsell-users/Business-to-business (B2B) companies often need to track and drive growth across both individual users of their product and the account or company they work for. In Customer.io, objectsAn object is a non-person entity that you can associate with one or more people—like a company, account, or online course. help you do this. For this recipe, imagine you work at a design platform, Sketcher.io, which offers graphic design and product design tools.https://docs.customer.io/ai/cio-with-llms/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/ai/cio-with-llms/ Check out our roadmap to see what’s coming next We’re always working on new features. Take a peek at our roadmap to see what’s in store for the future. Our current functionality powered by AI Our current AI tools include: 🎉New AI agent: The agent is your AI coworker in Customer.io. You’ll prompt it to help you do things in your workspace, like creating segments, drafting messages, and so on—so you can focus on important parts of your job and not the ins-and-outs of Customer.https://docs.customer.io/journeys/developer-tools/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/developer-tools/Click the caret to expand or collapse the panel. Inspect element Find the HTML source for any element in the preview using Inspect Element. Click the Inspect Element button in toolbar or enter Cmd/Ctrl + Shift + C. Click the element in the preview panel and the corresponding code will be highlighted in the editor. When you’re done, click the button (or keyboard shortcut) again to deactivate inspect mode. Focus mode Focus mode keeps the preview aligned with the code you’re working on.https://docs.customer.io/integrations/data-out/connections/vwo/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/vwo/There are two versions of this integration You’ll see two entries for Visual Website Optimizer (VWO) in our integration catalog, with one labeled Web. We typically recommend that you use the standard integration, the one not labeled “Web” when possible. The web version of this integration only works with our JavaScript client and does not pass data through Customer.io’s servers, which can make it hard to debug your integration, capture a history of events sent to the integration, and so on.https://docs.customer.io/journeys/webhook-triggered-campaigns/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/webhook-triggered-campaigns/How it works Normally, you trigger campaigns when a person performs an event or meets some criteria you set. This type of campaign lets you use webhooks to trigger workflows when you receive data from an external source. This video helps explain how it works: When you set up a webhook-triggered campaign, Customer.io generates a Webhook URL. You’ll provide this URL to the service or platform that you capture data from and set up rules determining when that service or platform will call your webhook, sending data to Customer.https://docs.customer.io/integrations/data-out/connections/webhook/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/webhook/Getting started Our webhook destination lets you transform and send data to any URL you maintain. It’s basically a custom destination, letting you handle source data however you want. Go to Data & Integrations > Integrations and select the Webhooks entry in the Directory tab. (Optional) Select the data sources that you want to connect to your outbound integration. You can always connect data sources later. We’ll only show you data sources that work with your integration.https://docs.customer.io/journeys/messages-not-sending/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/messages-not-sending/Note that people who are unsubscribed from topics or from all messages can still trigger a campaign; they just won’t receive messages from that campaign. Check your message’s settings Select the message block to get started. Check your message’s sending behavior Select Settings to check your message’s sending behavior. By default, messages are set to queue as drafts in your campaigns. Update them to send automatically then send any drafts manually to ensure all of your campaign’s audience receives the messages.https://docs.customer.io/integrations/data-out/connections/wisepops/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/wisepops/Getting started Go to Data & Integrations > Integrations and select the Wisepops entry in the Directory tab. (Optional) Select the data sources that you want to connect to your outbound integration. You can always connect data sources later. We’ll only show you data sources that work with your integration. Configure your integration. Website Id: The identifier of your Wisepops' website. You can find it in your setup code on Wisepops.https://docs.customer.io/accounts-and-workspaces/workspaces/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/accounts-and-workspaces/workspaces/Manage workspaces  To create, edit, or delete a workspace, you must be an Account Admin. Click your workspace in the upper left corner and then click Manage all workspaces to see a list of your workspaces. From here you can add, edit or delete workspaces (if you have more than one). Add a workspace By default, new workspaces use both email and id as identifiersThe attributes you use to add, modify, and target people.https://docs.customer.io/integrations/data-out/connections/yandex-data-out/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/yandex-data-out/ We have two integrations! This integration uses Customer.io as a source, and syncs data from your Customer.io workspace to your data warehouse, including campaign information. Our other integration sends data from multiple sources to your data warehouse. While the other integration captures data from multiple sources, even if those sources don’t send data to your workspace, it cannot capture some data from within Customer.io like campaign information. How it works This integration exports individual parquet files for Deliveries, Metrics, Subjects, Outputs, Content, People, and Attributes to your storage bucket.https://docs.customer.io/integrations/data-out/connections/zendesk/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/zendesk/Getting started Go to Data & Integrations > Integrations and select the Zendesk entry in the Directory tab. (Optional) Select the data sources that you want to connect to your outbound integration. You can always connect data sources later. We’ll only show you data sources that work with your integration. Configure your integration. Subdomain: The subdomain of your Zendesk instance. For example, if your Zendesk URL is https://example.zendesk.com, your subdomain is example.https://docs.customer.io/journeys/anonymous-activity/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/anonymous-activity/How it works When a person visits your site or app, they get an anonymous_id. You can track events against this ID—the pages they visit, things they click, and so on. For the most part, this activity isn’t very useful by itself. But when you identify people, we’ll merge people’s anonymous activity with their profiles, so you can respond to the things people did before you identified them! That’s where anonymous activity really shines.https://docs.customer.io/integrations/sdk/android/getting-started/auth/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/android/getting-started/auth/To get your SDK keys and send data to the right places, you’ll need to set up your app as a data inAn integration that feeds data into Customer.io. integration in Customer.io, and route it to your workspace. The SDK lets you route data to any number of destinations, but you must connect it to your workspace destination to send data, like the people you identify, the events you track, and so on, to Customer.https://docs.customer.io/integrations/sdk/expo/getting-started/auth/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/expo/getting-started/auth/These keys come from different places in Customer.io! CDP API Key: You’ll get this key when you set up your mobile app as a data-in integration in Customer.io. Site ID: This key tells the SDK which workspace your in-app messages come from. You’ll use it to support inApp messages. If you’re upgrading from a previous version of the Customer.io SDK, it also serves as the migrationSiteId. Get your CDP API Key You’ll use your write key to initialize the SDK and send data to Customer.https://docs.customer.io/integrations/sdk/flutter/2.x/getting-started/auth/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/flutter/2.x/getting-started/auth/Get your CDP API Key You’ll use a CDP API Key to initialize the SDK and send data to Customer.io. You’ll get this key when you set up your mobile app as a data inAn integration that feeds data into Customer.io. integration in Customer.io. If you haven’t already set up your integration in Customer.io, you’ll need to do that first. Go to Data & Integrations > Integrations. Select your Flutter integration in the Overview tab.https://docs.customer.io/integrations/sdk/flutter/getting-started/auth/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/flutter/getting-started/auth/Get your CDP API Key You’ll use a CDP API Key to initialize the SDK and send data to Customer.io. You’ll get this key when you set up your mobile app as a data inAn integration that feeds data into Customer.io. integration in Customer.io. If you haven’t already set up your integration in Customer.io, you’ll need to do that first. Go to Data & Integrations > Integrations. Select your Flutter integration in the Overview tab.https://docs.customer.io/integrations/sdk/ios/3.x/getting-started/auth/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/3.x/getting-started/auth/To get your SDK keys and send data to the right places, you’ll need to set up your app as a data inAn integration that feeds data into Customer.io. integration in Customer.io, and route it to your workspace. The SDK lets you route data to any number of destinations, but you must connect it to your workspace destination to send data, like the people you identify, the events you track, and so on, to Customer.https://docs.customer.io/integrations/sdk/ios/getting-started/auth/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/getting-started/auth/To get your SDK keys and send data to the right places, you’ll need to set up your app as a data inAn integration that feeds data into Customer.io. integration in Customer.io, and route it to your workspace. The SDK lets you route data to any number of destinations, but you must connect it to your workspace destination to send data, like the people you identify, the events you track, and so on, to Customer.https://docs.customer.io/integrations/sdk/react-native/4.x/getting-started/auth/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/4.x/getting-started/auth/These keys come from different places in Customer.io! CDP API Key: You’ll get this key when you set up your mobile app as a data-in integration in Customer.io. Site ID: This key tells the SDK which workspace your in-app messages come from. You’ll use it to support inApp messages. If you’re upgrading from a previous version of the Customer.io SDK, it also serves as the migrationSiteId. Get your CDP API Key You’ll use your write key to initialize the SDK and send data to Customer.https://docs.customer.io/integrations/sdk/react-native/5.x/getting-started/auth/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/5.x/getting-started/auth/These keys come from different places in Customer.io! CDP API Key: You’ll get this key when you set up your mobile app as a data-in integration in Customer.io. Site ID: This key tells the SDK which workspace your in-app messages come from. You’ll use it to support inApp messages. If you’re upgrading from a previous version of the Customer.io SDK, it also serves as the migrationSiteId. Get your CDP API Key You’ll use your write key to initialize the SDK and send data to Customer.https://docs.customer.io/integrations/sdk/react-native/getting-started/auth/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/getting-started/auth/These keys come from different places in Customer.io! CDP API Key: You’ll get this key when you set up your mobile app as a data-in integration in Customer.io. Site ID: This key tells the SDK which workspace your in-app messages come from. You’ll use it to support inApp messages. If you’re upgrading from a previous version of the Customer.io SDK, it also serves as the migrationSiteId. Get your CDP API Key You’ll use your write key to initialize the SDK and send data to Customer.https://docs.customer.io/journeys/subscription-center-branding/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/subscription-center-branding/You can add your own Logo and set a primary Brand Color so that your subscription pages look more like a native part of your website or app. Set up branding Global unsubscribes You can set the branding for your global unsubscribe page as long as you have not created subscription topics. Go to Workspace Settings > Subscription Center and click Settings. Then select Edit next to Branding. Select your Logo.https://docs.customer.io/accounts-and-workspaces/create-a-har-file-for-help-troubleshooting/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/accounts-and-workspaces/create-a-har-file-for-help-troubleshooting/ CAUTION HAR files contain sensitive data and potentially personally identifiable information. It includes the content of the pages you accessed while recording the file as well as your cookies. This could include things like email addresses, phone numbers, usernames, passwords, credit card numbers, etc. Please handle the resulting file with the same caution you would any other sensitive information. We offer a tool so you can sanitize your Customer.io credentials - see the instructions below for more info.https://docs.customer.io/integrations/data-in/connections/salesforce/mapping-data/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/salesforce/mapping-data/ Is Customer.io where you’re using your Salesforce data? Do you want to send messages? Check out Salesforce with Customer.io page for help connecting your Salesforce data to Customer.io, so you can send messages. This page is meant to help you send Salesforce data to places outside of Customer.io. How it works Unlike most platforms, Salesforce doesn’t have generic concepts like People and Groups—or things that map easily to those terms.https://docs.customer.io/integrations/data-in/connections/classic-api/journeys-track-mappings/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/classic-api/journeys-track-mappings/How it works When we receive traffic from some integrations, like the Track API, we translate them to our newer and more generic Pipelines format to better support downstream, data outAn integration that sends data out of Customer.io. integrations. This might be a little confusing when you send data in to Customer.io with one format, and then see the resulting Data Out calls in a different format! This page explains how we map the Track API to our Pipelines API for data out integrations, to help you understand how your data transforms as we send it out of Customer.https://docs.customer.io/journeys/responsive-styles/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/responsive-styles/How to set responsive styles You can set responsive styles in the visual editor or by writing your own CSS. Set responsive styles in Design Studio You can set responsive styles for your brand and for individual emails. Our responsive styles have a breakpoint of 600px. To set responsive styles globally, go to Styles. To modify mobile vs desktop styles in the visual editor, click a component and locate properties with .https://docs.customer.io/integrations/data-in/connections/reverse-etl/database-sync/reverse-etl/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/reverse-etl/database-sync/reverse-etl/ These are legacy integrations If you’re new to Customer.io, you won’t see the integrations in this directory. You’ll use our newer Reverse ETL integrations instead. A "reverse ETL" integration extracts, transforms, and loads data from your database to your workspace. With this integration, you can automatically add or update people, objects, and their relationships in Customer.io from your database on a recurring interval. When you set up your integration, you can import people or objects—you cannot import both with the same query.https://docs.customer.io/integrations/data-in/connections/cdps/segment-destination-classic/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/cdps/segment-destination-classic/Set up a Segment Destination integration  This integration is in maintenance mode Segment no longer actively maintains this integration. If you’re just getting started, we suggest that you use the newer Segment Destination Actions integration integration, which supports anonymous events and lets you filter the events that you send to Customer.io. Go to Settings > Integrations and click the Segment Destination integration. Click Configure Segment. Pick the Workspace and Source you want to associate your integration with, and then click Allow.https://docs.customer.io/journeys/send-inbox/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/send-inbox/Set up a message Before you try to send an inbox message, make sure you’ve set up your inbox. When you set up a message, you’re essentially determining the id or name of the message you want to send. You’ll use one of these values to send and populate your message when you’re ready to send it. In your campaign or broadcast workflow, drag an Inbox message block into your workflow.https://docs.customer.io/journeys/sms-send-messages/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/sms-send-messages/Learn how to send smsShort Message Service: a text message, typically up to 160 characters, sent through a mobile carrier to a phone. and mmsMultimedia Message Service: a message sent through a mobile carrier to a phone that includes a picture or video. messages using Customer.io. Add SMS/MMS messages to your workflow Before you can send messages, you need to set up your Twilio account and enable SMS in your workspace.https://docs.customer.io/integrations/data-out/connections/salesforce/tasks-in-sf/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/salesforce/tasks-in-sf/How it works The Task for Message Delivery action records message events from Customer.io as completed tasks in Salesforce. This makes it easy for you to see the messages you’ve sent, whether people have interacted with them, and so on—all in Salesforce. This helps you make your Salesforce environment a reliable source of truth. To take advantage of this action, you need to make sure that you sync people from Salesforce to Customer.https://docs.customer.io/integrations/sdk/ios/3.x/in-app/set-up-in-app/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/3.x/in-app/set-up-in-app/How it works An in-app message is a message that people see within the app; people won’t see your message until they open your app. To set up in app messaging, install and initialize the CioDataPipelines and CioMessagingInApp packages. You can also set page rules to display your in-app messages when people visit specific pages in your app. However, to take advantage of page rules, you need to use screen tracking features.https://docs.customer.io/integrations/sdk/ios/in-app/set-up-in-app/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/in-app/set-up-in-app/How it works An in-app message is a message that people see within the app; people won’t see your message until they open your app. To set up in app messaging, install and initialize the CioDataPipelines and CioMessagingInApp packages. You can also set page rules to display your in-app messages when people visit specific pages in your app. However, to take advantage of page rules, you need to use screen tracking features.https://docs.customer.io/integrations/sdk/ios/3.x/tracking/track-events/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/3.x/tracking/track-events/Track an event The track method helps you send events representing your audience’s activities to Customer.io. When you send events, you can include event properties—information about the person or the event that they performed. In Customer.io, you can use events to trigger campaigns and broadcasts. Those campaigns might send someone a push notification or manipulate information associated with the person in your workspace. Events include the following: name: the name of the event.https://docs.customer.io/integrations/sdk/ios/tracking/track-events/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/tracking/track-events/Track an event The track method helps you send events representing your audience’s activities to Customer.io. When you send events, you can include event properties—information about the person or the event that they performed. In Customer.io, you can use events to trigger campaigns and broadcasts. Those campaigns might send someone a push notification or manipulate information associated with the person in your workspace. Events include the following: name: the name of the event.https://docs.customer.io/integrations/sdk/react-native/4.x/tracking/track-events/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/4.x/tracking/track-events/Track an event The track method helps you send events representing your audience’s activities to Customer.io. When you send events, you can include event properties—information about the person or the event that they performed. In Customer.io, you can use events to trigger campaigns and broadcasts. Those campaigns might send someone a push notification or manipulate information associated with the person in your workspace. Events include the following: name: the name of the event.https://docs.customer.io/integrations/sdk/react-native/5.x/tracking/track-events/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/5.x/tracking/track-events/Track an event The track method helps you send events representing your audience’s activities to Customer.io. When you send events, you can include event properties—information about the person or the event that they performed. In Customer.io, you can use events to trigger campaigns and broadcasts. Those campaigns might send someone a push notification or manipulate information associated with the person in your workspace. Events include the following: name: the name of the event.https://docs.customer.io/integrations/sdk/react-native/tracking/track-events/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/tracking/track-events/Track an event The track method helps you send events representing your audience’s activities to Customer.io. When you send events, you can include event properties—information about the person or the event that they performed. In Customer.io, you can use events to trigger campaigns and broadcasts. Those campaigns might send someone a push notification or manipulate information associated with the person in your workspace. Events include the following: name: the name of the event.https://docs.customer.io/integrations/data-in/connections/reverse-etl/database-sync/redshift-reverse-etl/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/reverse-etl/database-sync/redshift-reverse-etl/ This is a legacy integration If you’re new to Customer.io, you won’t see this integration in your integrations directory. You’ll use our newer Amazon Redshift integration. A "reverse ETL" integration extracts, transforms, and loads data from your Amazon Redshift database to your workspace. With this integration, you can automatically add or update people, objects, and their relationships in Customer.io from your database on a recurring interval. When you set up your integration, you can import people or objects—you cannot import both with the same query.https://docs.customer.io/integrations/sdk/flutter/2.x/getting-started/packages-options/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/flutter/2.x/getting-started/packages-options/You’ll call configuration options before you initialize the SDK with CustomerIOConfig. When you initialize the SDK, you can pass configuration options. In most cases, you’ll want to stick with the defaults, but you might do things like change the logLevel when testing updates to your app. CustomerIO.initialize( config: CustomerIOConfig( cdpApiKey: "YOUR_CDP_API_KEY", // Required migrationSiteId: "YOUR_SITE_ID", // Required to migrate from a previous version autoTrackDeviceAttributes: true, region: Region.us, logLevel: CioLogLevel.error ) ); Option Type Default Description cdpApiKey string Required: the key you'll use to initialize the SDK and send data to Customer.https://docs.customer.io/integrations/sdk/flutter/getting-started/packages-options/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/flutter/getting-started/packages-options/You’ll call configuration options before you initialize the SDK with CustomerIOConfig. When you initialize the SDK, you can pass configuration options. In most cases, you’ll want to stick with the defaults, but you might do things like change the logLevel when testing updates to your app. CustomerIO.initialize( config: CustomerIOConfig( cdpApiKey: "YOUR_CDP_API_KEY", // Required migrationSiteId: "YOUR_SITE_ID", // Required to migrate from a previous version autoTrackDeviceAttributes: true, region: Region.us, logLevel: CioLogLevel.error ) ); Option Type Default Description cdpApiKey string Required: the key you'll use to initialize the SDK and send data to Customer.https://docs.customer.io/journeys/component-slots/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/component-slots/ Use our Design Studio GPT to create a custom component! Learn how to best utilize our GPT to create code for reusable, custom content. How to create a slot To create a slot, define the type of slot in <script> and insert <slot> tags in the <template> where you want users to insert or edit content. You can also add placeholder text to guide your team when they’re working in the visual editor.https://docs.customer.io/integrations/data-out/connections/salesforce/salesforce-faq/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/connections/salesforce/salesforce-faq/Salesforce OAuth connection limits You should not create more than five Salesforce connections (between data-in and data-out) per user. Salesforce enforces a limit of five connections per OAuth-enabled Connected Application, per user. When you hit this limit, Salesforce revokes the oldest connection. This limit is not configurable and Customer.io is not notified when Salesforce revokes a connection. Because this limit is per user, you can circumvent the limit by creating multiple Salesforce integration users and carefully managing their connections—no more than five connections per user.https://docs.customer.io/integrations/data-in/connections/reverse-etl/database-sync/bigquery-reverse-etl/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/reverse-etl/database-sync/bigquery-reverse-etl/ This is a legacy integration If you’re new to Customer.io, you won’t see this integration in your integrations directory. You’ll use our newer Google BigQuery integration. A "reverse ETL" integration extracts, transforms, and loads data from your BigQuery database to your workspace. With this integration, you can automatically add or update people, objects, and their relationships in Customer.io from your database on a recurring interval. When you set up your integration, you can import people or objects—you cannot import both with the same query.https://docs.customer.io/journeys/merge-anonymous/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/merge-anonymous/How it works When you identifyThe Customer.io operation that adds or updates a person. When you identify a person, Customer.io either adds a person if they don’t exist in your workspace, or updates them if they do. Before you identify someone (by their email address or an ID), you can track them anonymously. a person, Customer.io will associate anonymous events with the person. You can use a person’s previously anonymous activity to add them to segments, trigger campaigns, and personalize their experiences.https://docs.customer.io/integrations/data-in/connections/reverse-etl/database-sync/ms-sql-reverse-etl/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/reverse-etl/database-sync/ms-sql-reverse-etl/ This is a legacy integration If you’re new to Customer.io, you won’t see this integration in your integrations directory. You’ll use our newer Microsoft SQL integration. A "reverse ETL" integration extracts, transforms, and loads data from your Microsoft SQL database to your workspace. With this integration, you can automatically add or update people, objects, and their relationships in Customer.io from your database on a recurring interval. When you set up your integration, you can import people or objects—you cannot import both with the same query.https://docs.customer.io/integrations/data-in/connections/reverse-etl/database-sync/sql-reverse-etl/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/reverse-etl/database-sync/sql-reverse-etl/ This is a legacy integration If you’re new to Customer.io, you won’t see this integration in your integrations directory. You’ll use our newer MySQL integration. How it works A "reverse ETL" integration extracts, transforms, and loads data from your MySQL database to your workspace. With this integration, you can automatically add or update people, objects, and their relationships in Customer.io from your database on a recurring interval. When you set up your integration, you can import people or objects—you cannot import both with the same query.https://docs.customer.io/integrations/sdk/android/getting-started/packages-options/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/android/getting-started/packages-options/SDK packages To minimize our SDK’s impact on your app’s size, we’ve split the SDK into packages. You can limit your install to the packages that you need for your project. But, in most cases, you’ll want to install all the packages to get the most value out of Customer.io. You must install the datapipelines package. It lets you identify people, which you must do before you can send them messages, etc.https://docs.customer.io/integrations/sdk/expo/getting-started/packages-options/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/expo/getting-started/packages-options/How it works With our Expo plugin, you can configure the SDK in two ways: Auto-initialization (Expo 53+): Configure everything in your app.json file using the config object. The SDK will automatically initialize without requiring CustomerIO.initialize() in your app code. Manual initialization: Configure native settings in app.json and SDK runtime settings in your React Native app code using CustomerIO.initialize(). Both approaches require configuration in your app.json or app.config.js files that affect the native files we generate when you run the prebuild.https://docs.customer.io/integrations/sdk/ios/3.x/getting-started/packages-options/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/3.x/getting-started/packages-options/SDK packages To minimize our SDK’s impact on your app’s size, we’ve split the SDK into packages. You can limit your install to the packages that you need for your project. You must install the CioDataPipelines package. It lets you identify people, which you must do before you can send them messages, track their events, etc. Package Product Required? Description CioDataPipelines ✅ identify people and track events CioMessagingPushAPN Receive push notifications over Apple’s Push Notification Service (APNs) CioMessagingPushFCM Receive push notifications over Google Firebase Cloud Messaging (FCM) CioFirebaseWrapper Required for FCM push notifications.https://docs.customer.io/integrations/sdk/ios/getting-started/packages-options/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/getting-started/packages-options/SDK packages To minimize our SDK’s impact on your app’s size, we’ve split the SDK into packages. You can limit your install to the packages that you need for your project. You must install the CioDataPipelines package. It lets you identify people, which you must do before you can send them messages, track their events, etc. Package Product Required? Description CioDataPipelines ✅ identify people and track events CioMessagingPushAPN Receive push notifications over Apple’s Push Notification Service (APNs) CioMessagingPushFCM Receive push notifications over Google Firebase Cloud Messaging (FCM) CioFirebaseWrapper Required for FCM push notifications.https://docs.customer.io/integrations/sdk/react-native/4.x/getting-started/packages-options/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/4.x/getting-started/packages-options/SDK packages The SDK consists of a few packages. You must use the CioConfig and CustomerIO packages to configure and initialize the SDK. Package Product Required? Description CustomerIO ✅ The main SDK package. Used to initialize the SDK and call the SDK’s methods. CioConfig ✅ Configure the SDK including in-app messaging support. CioRegion Used inside the CioConfig.region option to declare your region—EU or US. CioLogLevel Used inside the CioConfig.logLevel option to set the level of logs you can view from the SDK.https://docs.customer.io/integrations/sdk/react-native/5.x/getting-started/packages-options/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/5.x/getting-started/packages-options/SDK packages The SDK consists of a few packages. You must use the CioConfig and CustomerIO packages to configure and initialize the SDK. Package Product Required? Description CustomerIO ✅ The main SDK package. Used to initialize the SDK and call the SDK’s methods. CioConfig ✅ Configure the SDK including in-app messaging support. CioRegion Used inside the CioConfig.region option to declare your region—EU or US. CioLogLevel Used inside the CioConfig.logLevel option to set the level of logs you can view from the SDK.https://docs.customer.io/integrations/sdk/react-native/getting-started/packages-options/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/getting-started/packages-options/SDK packages The SDK consists of a few packages. You must use the CioConfig and CustomerIO packages to configure and initialize the SDK. Package Product Required? Description CustomerIO ✅ The main SDK package. Used to initialize the SDK and call the SDK’s methods. CioConfig ✅ Configure the SDK including in-app messaging support. CioRegion Used inside the CioConfig.region option to declare your region—EU or US. CioLogLevel Used inside the CioConfig.logLevel option to set the level of logs you can view from the SDK.https://docs.customer.io/integrations/data-in/connections/reverse-etl/database-sync/postgres-reverse-etl/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/reverse-etl/database-sync/postgres-reverse-etl/ This is a legacy integration If you’re new to Customer.io, you won’t see this integration in your integrations directory. You’ll use our newer PostgreSQL integration. A "reverse ETL" integration extracts, transforms, and loads data from your Postgres database to your workspace. With this integration, you can automatically add or update people, objects, and their relationships in Customer.io from your database on a recurring interval. When you set up your integration, you can import people or objects—you cannot import both with the same query.https://docs.customer.io/journeys/preview-email-in-design-studio/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/preview-email-in-design-studio/Preview liquid Check out Add & preview liquid for more information on personalizing your messages with liquid data. Review links Click Review Links to make sure all links in your email work. You’ll see a list of valid links and those that need attention under “errors” and “warnings”. Access preview settings In the visual editor, you can preview a few settings while you edit: Desktop vs mobile views Light vs dark modes Content hidden based on screen size A more in-depth preview is available when you turn on Preview in the canvas toolbar.https://docs.customer.io/integrations/data-in/connections/cdps/rudderstack-in/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/cdps/rudderstack-in/ You can find the open-source transformer code for this destination in Rudderstack’s GitHub repository. How it works When you set up Customer.io as a Rudderstack Destination, Rudderstack adds, updates, and sends events representing people to Customer.io from one or more sources. Rudderstack supports the same set of calls as our Pipelines API, with similar payload structures. This page provides some examples of source calls you can make to forward data to Customer.https://docs.customer.io/integrations/data-in/connections/salesforce/syncs/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/salesforce/syncs/We pull data from Salesforce on a regular interval (that you set) called a sync. sequenceDiagram participant a as Salesforce participant b as Customer.io participant c as Destination service note over a, c: Sync Data: occurs on a schedule a->>a:Changes happen in Salesforce b->>a: Query for changes a->>b: Send changeset b->>b: Convert to people, events, objects b->>c: Send to destination While you can see incoming data in the Data In tab, syncs also show in the Imports tab.https://docs.customer.io/integrations/sdk/ios/push/rich-push/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/push/rich-push/1. Add a service extension to your project Add a Service App Extension to your project in Xcode. You should now see a new file added to your Xcode project. The file is probably named NotificationService and looks similar to this. import UserNotifications class NotificationService: UNNotificationServiceExtension { override func didReceive( _ request: UNNotificationRequest, withContentHandler contentHandler: @escaping (UNNotificationContent) -> Void ) { } override func serviceExtensionTimeWillExpire() { } } 2. Update the service extension  Xcode 16.https://docs.customer.io/journeys/localization-attribute/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/localization-attribute/How it works To set up your workspace to send translated messages, you’ll follow these steps: Store your audience’s language preferences as an attribute on their profiles. Assign this attribute in your language settings. You’ll indicate which attributeA key-value pair that you associate with a person or an object—like a person’s name, the date they were created in your workspace, or a company’s billing date etc. Use attributes to target people and personalize messages.https://docs.customer.io/integrations/data-in/connections/reverse-etl/database-sync/snowflake-reverse-etl/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/reverse-etl/database-sync/snowflake-reverse-etl/ This is a legacy integration If you’re new to Customer.io, you won’t see this integration in your integrations directory. You’ll use our newer Snowflake integration. A "reverse ETL" integration extracts, transforms, and loads data from your Snowflake database to your workspace. With this integration, you can automatically add or update people, objects, and their relationships in Customer.io from your database on a recurring interval. When you set up your integration, you can import people or objects—you cannot import both with the same query.https://docs.customer.io/journeys/unsubscribe-faqs/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/unsubscribe-faqs/What messages will someone stop receiving after unsubscribing? By default, if a customer is globally unsubscribed, we will not send them emails, push or SMS for any campaign or broadcast. If a customer is unsubscribed from a topic in your subscription center, we also stop sending email, push and SMS, but only for that topic. If you use channel preferences, people can also opt out of specific messaging channels. For example, if someone unsubscribes from the push channel, they won’t receive push notifications for any topic—even if they’re still subscribed to those topics.https://docs.customer.io/ai/agent/how-it-works/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/ai/agent/how-it-works/When you ask the agent to do something, it works through a series of steps behind the scenes. Along the way, you might see it doing things that look technical—reading files, writing code, running commands. This is all part of the agent’s process. Where you work in a user interface, clicking and typing, the agent works by reading and writing code. Skills If you see the agent reading a skill, it’s just loading instructions for how to work with a specific part of Customer.https://docs.customer.io/ai/agent/routines/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/ai/agent/routines/How it works Routines are recurring tasks that the agent runs automatically on a schedule. You tell the agent what to check and how often, and it delivers a summary by email each time it runs. You can use routines to automate the kinds of checks you’d otherwise do manually—monitoring deliverability, auditing segments, comparing broadcast performance, or tracking goal conversions. Routines run in safe mode—the agent can read your workspace data and analyze it, but it can’t make changes to your campaigns, segments, or other resources.https://docs.customer.io/integrations/sdk/android/tracking/screen-events/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/android/tracking/screen-events/Screen views are events that record the pages that your audience visits in your app. They have a type property set to screen, and a name representing the title of the screen or page that a person visited in your app. Screen view events let you trigger campaignsCampaigns are automated workflows you set up to send people messages and perform other actions when they meet your criteria. or add people to segmentsA group of people who match a series of conditions.https://docs.customer.io/integrations/sdk/ios/3.x/tracking/screen-events/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/3.x/tracking/screen-events/Screen views are events that record the pages that your audience visits in your app. They have a type property set to screen, and a title representing the title of the screen or page that a person visited in your app. Screen view events let you trigger campaignsCampaigns are automated workflows you set up to send people messages and perform other actions when they meet your criteria. or add people to segmentsA group of people who match a series of conditions.https://docs.customer.io/integrations/sdk/ios/tracking/screen-events/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/tracking/screen-events/Screen views are events that record the pages that your audience visits in your app. They have a type property set to screen, and a title representing the title of the screen or page that a person visited in your app. Screen view events let you trigger campaignsCampaigns are automated workflows you set up to send people messages and perform other actions when they meet your criteria. or add people to segmentsA group of people who match a series of conditions.https://docs.customer.io/integrations/sdk/react-native/4.x/tracking/screen-events/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/4.x/tracking/screen-events/Screen views are events that record the pages that your audience visits in your app. They have a type property set to screen, and a name representing the title of the screen or page that a person visited in your app. Screen view events let you trigger campaignsCampaigns are automated workflows you set up to send people messages and perform other actions when they meet your criteria. or add people to segmentsA group of people who match a series of conditions.https://docs.customer.io/integrations/sdk/react-native/5.x/tracking/screen-events/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/5.x/tracking/screen-events/Screen views are events that record the pages that your audience visits in your app. They have a type property set to screen, and a name representing the title of the screen or page that a person visited in your app. Screen view events let you trigger campaignsCampaigns are automated workflows you set up to send people messages and perform other actions when they meet your criteria. or add people to segmentsA group of people who match a series of conditions.https://docs.customer.io/integrations/sdk/react-native/tracking/screen-events/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/tracking/screen-events/Screen views are events that record the pages that your audience visits in your app. They have a type property set to screen, and a name representing the title of the screen or page that a person visited in your app. Screen view events let you trigger campaignsCampaigns are automated workflows you set up to send people messages and perform other actions when they meet your criteria. or add people to segmentsA group of people who match a series of conditions.https://docs.customer.io/journeys/component-properties/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/component-properties/To create responsive custom components or enable dark mode, check out Responsive Styles and Dark Mode.  Use our Design Studio GPT to create a custom component! Learn how to best utilize our GPT to create code for reusable, custom content. Define properties To declare properties, export a variable like props so the property can be set in the visual editor. Then set this equal to the Component.defineProps object of your <script>.https://docs.customer.io/journeys/delete-component/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/delete-component/Delete a custom component On your Design Studio dashboard, click Components. Click next to your component. Click Find Component References to see if your component is used in your messages. Remove the component from all messages where it’s referenced.  Publish changes to connected messages After you remove component references from messages, publish your changes so your messages and automations are in sync. Click Delete. If you delete a component file before removing its references from messages, you’ll see an error in the visual editor.https://docs.customer.io/journeys/localization-metrics/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/localization-metrics/To learn more about metrics, check out Campaign and newsletter metrics. Campaign metrics When you look at a running campaign, the Overview and Metrics tabs both show aggregated metrics for your messages, including all the languages they contain. The Metrics tab shows stats for each language under the name of the message block. Beside the message block name, you’ll see metrics aggregated across all languages. Newsletter metrics In the Overview tab of a newsletter, you’ll see metrics for each language.https://docs.customer.io/journeys/your-privacy-policy/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/your-privacy-policy/ This section contains recommendations and examples, but it does not constitute legal advice. Contact your legal team to ensure that you’re compliant with all applicable laws and regulations before you make changes to your privacy policy or terms and conditions. Update your privacy policy Before you request a sender phone number, you need to update your privacy policy to include information about how you’ll message your audience and use their phone numbers.https://docs.customer.io/integrations/sdk/ios/whats-new/4.4.0-upgrade/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/whats-new/4.4.0-upgrade/What changed? Version 4.4.0 adds support for App Groups, which improves the reliability of push delivery metric tracking. This update is additive—your existing integration continues to work without changes. However, to take advantage of App Groups, you’ll need to update your Xcode project configuration and regenerate provisioning profiles if you use manual signing. Why App Groups? When you send a push notification, the SDK tracks delivery metrics in your Notification Service Extension (NSE).https://docs.customer.io/journeys/manually-adding-or-updating-people/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/manually-adding-or-updating-people/Add a person via the UI Go to People. Click Add People. Scroll to the bottom of the modal and click Add a single person. Under Identifiers, you’ll see id and/or email as options. The identifiers you see depend on the identifiers you’ve allowed in workspace settings. You only need to set one identifier to create a person. Learn more in How to identify people. Add other data you want to store on this person’s profile.https://docs.customer.io/integrations/sdk/flutter/push-notifications/app-groups/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/flutter/push-notifications/app-groups/You need App Groups for reliable push delivery tracking on iOS. Without this setup, delivery metrics may be lost if iOS terminates the Notification Service Extension before the tracking request completes. With App Groups configured, the SDK automatically recovers any lost metrics on the next app launch. Before you begin Before you configure App Groups, make sure you’ve completed the following: Set up push notifications in your app, including the Notification Service Extension (NSE) 1.https://docs.customer.io/integrations/sdk/ios/push/app-groups/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/push/app-groups/App Groups are required for reliable push delivery tracking. Without this setup, delivery metrics may be lost if iOS terminates the Notification Service Extension before the tracking request completes. With App Groups configured, the SDK automatically recovers any lost metrics on the next app launch. Before you begin Before you configure App Groups, make sure you’ve completed the following: Set up push notifications in your app Set up rich push with a Notification Service Extension (NSE) 1.https://docs.customer.io/journeys/campaign-journeys/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/campaign-journeys/View and troubleshoot journeys Journeys help you track people’s current or historical pathway through your campaign. This makes it very useful for troubleshooting issues like people not proceeding in your workflow or exiting campaigns when you’d expect. To access individual journeys, go to the Journeys tab of Campaigns or a person’s profile. In this campaign, you can see this person entered the campaign at 4:51pm and left it at 4:58pm, a short journey!https://docs.customer.io/journeys/link-checking/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/link-checking/Checking Link Status in the Composer When composing your message, you may notice the “Review Links” button: When you click it, you’ll see a modal with all of your link information. You’ll see your link text, the URL, whether it is tracked or untracked, its UTM tags, and any errors associated with the link.  Note: If you use a link protocol other than http, https, ftp, mailto or tel you may see a message stating that your protocol is not supported.https://docs.customer.io/journeys/webhook-manager/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/webhook-manager/Overview In Workspace Settings, you can configure webhooks to reuse them across your campaigns and API-triggered broadcasts. Use them to reduce friction across your workflows: Less repetitive work & fewer errors. Define your webhook URL, headers, and auth details once, and reference them in any campaign. Updates at scale. When an API endpoint or auth header changes, update the configuration in one place and all referencing campaigns pick up the change automatically.https://docs.customer.io/journeys/add-email-to-automation/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/add-email-to-automation/ You can only connect a Design Studio message to one automation. You can connect an email made in Design Studio to any campaign, broadcast, or transactional message, but only one. If you’d like to connect the same email to multiple automations, you can duplicate the email. Connect your message How you connect your Design Studio message depends on the type of automation you’re working with. Campaigns and API-triggered broadcasts Open your campaign or API-triggered broadcast.https://docs.customer.io/accounts-and-workspaces/create-roles/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/accounts-and-workspaces/create-roles/Overview Customer.io has two types of workspace-level roles: standard roles and custom roles. Standard roles come with a predefined set of permissions, while custom roles allow you to specify your own set of permissions across content, integrations, and more. Account Admins can create custom roles in Account Settings > Roles. You can create roles from scratch or start from an existing role. A few things to keep in mind: Custom roles must minimally have all view permissions.https://docs.customer.io/journeys/create-a-campaign/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/create-a-campaign/ New to campaigns? Check out campaign concepts & settings to get started. Here’s a brief video showing the main components of our campaign builder. And here’s a walkthrough on creating an onboarding campaign! Before you begin Before you begin, determine the purpose of your campaign. This will help you define the trigger and goal of your campaign. Are you trying to reach people who have just signed up? Are you interested in notifying people about changes to accounts they manage?https://docs.customer.io/journeys/transformer-formatting/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/transformer-formatting/Click Transformers > Formatting to get started. Format your source code Click Prettify to make your code easy to read. Clicking this unlocks further preferences you can enable: Indent with spaces or tabs Wrap HTML attributes We remember the state of those toggles if you deactivate and later reactivate them. To format the code in your editor, click Format Document at the top of the editor. Reduce the size of your email Click Minify to reduce the size of your source code when it sends.https://docs.customer.io/journeys/uploading-people/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/uploading-people/How it works You can upload CSVs or Google Sheets to add people, update people, and send events to Customer.io outside your normal integration path. When you upload a CSV of people or events, each row in your CSV represents a person or an event respectively; each column in your CSV represents an attribute or event property respectively. When you go to upload a CSV, you’ll select People or Events.https://docs.customer.io/integrations/data-in/connections/javascript/frameworks/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/javascript/frameworks/Client-side vs. server-side The instructions on this page are for client-side implementations. In general, we prefer the client-side library to support things like in-app messaging and automatic page tracking. But, if you need to use a server-side implementation, see our Node.js library. Feature Browser Library Node.js Library Package @customerio/cdp-analytics-browser @customerio/cdp-analytics-node Page context Automatic: captured from DOM Manual: you must provide URL, path, etc. Identity persistence Automatic: stored in cookies/localStorage Manual: you must pass userId or anonymousId on every call In-app message support Use for Client-side tracking, single page applications (SPAs), in-app messages Server-side tracking, API routes, background jobs React For React-based applications, you’ll want to create a singleton instance of the analytics client that you can import throughout your app.https://docs.customer.io/journeys/manage-subscription-preferences/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/manage-subscription-preferences/After you set up your subscription center, you can manage people’s subscription preferences in several ways. Set subscription preferences Beyond people unsubscribing themselves from messages, you can also: manually set subscription preferences in your workspace migrate people’s existing preferences from another service send out a campaign requesting they update their preferences track their preferences outside of the subscription center You have the option to set preferences for some subscription topics or channels, while preserving those set for others, using JSON dot notation.https://docs.customer.io/journeys/version-history/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/version-history/Save a version Versions capture your message, settings, assets, and components at a specific point in time. You can save a version from several places: In the visual or code editors, click and select Save Current Version. On a Feedback page, click New Version. Give your version a name and (optionally) a description.  You can only save a version if something has changed since the last one. If nothing’s changed, you’ll see a message that the version wasn’t saved.https://docs.customer.io/integrations/sdk/android/tracking/lifecycle-events/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/android/tracking/lifecycle-events/By default, we track the following lifecycle events: Application Installed: A user installed your app. Application Updated: A user updated your app. Application Opened: A user opened your app. Application Foregrounded: A user switched back to your app. Application Backgrounded: A user backgrounded your app or switched to another app. You might also want to send your own lifecycle events, like Application Crashed or Application Updated. You can do this using the track method.https://docs.customer.io/integrations/sdk/flutter/2.x/tracking/lifecycle-events/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/flutter/2.x/tracking/lifecycle-events/By default, we track the following lifecycle events: Application Installed: A user installed your app. Application Updated: A user updated your app. Application Opened: A user opened your app. Application Foregrounded: A user switched back to your app. Application Backgrounded: A user backgrounded your app or switched to another app. You might also want to send your own lifecycle events, like Application Crashed or Application Updated. You can do this using the track call.https://docs.customer.io/integrations/sdk/flutter/tracking/lifecycle-events/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/flutter/tracking/lifecycle-events/By default, we track the following lifecycle events: Application Installed: A user installed your app. Application Updated: A user updated your app. Application Opened: A user opened your app. Application Foregrounded: A user switched back to your app. Application Backgrounded: A user backgrounded your app or switched to another app. You might also want to send your own lifecycle events, like Application Crashed or Application Updated. You can do this using the track call.https://docs.customer.io/integrations/sdk/ios/3.x/tracking/lifecycle-events/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/3.x/tracking/lifecycle-events/By default, we track the following lifecycle events: Application Installed: A user installed your app. Application Updated: A user updated your app. Application Opened: A user opened your app. Application Foregrounded: A user switched back to your app. Application Backgrounded: A user backgrounded your app or switched to another app. You might also want to send your own lifecycle events, like Application Crashed or Application Updated. You can do this using the track call.https://docs.customer.io/integrations/sdk/ios/tracking/lifecycle-events/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/tracking/lifecycle-events/By default, we track the following lifecycle events: Application Installed: A user installed your app. Application Updated: A user updated your app. Application Opened: A user opened your app. Application Foregrounded: A user switched back to your app. Application Backgrounded: A user backgrounded your app or switched to another app. You might also want to send your own lifecycle events, like Application Crashed or Application Updated. You can do this using the track call.https://docs.customer.io/integrations/sdk/react-native/4.x/tracking/lifecycle-events/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/4.x/tracking/lifecycle-events/By default, we track the following lifecycle events: Application Installed: A user installed your app. Application Updated: A user updated your app. Application Opened: A user opened your app. Application Foregrounded: A user switched back to your app. Application Backgrounded: A user backgrounded your app or switched to another app. You might also want to send your own lifecycle events, like Application Crashed or Application Updated. You can do this using the track method.https://docs.customer.io/integrations/sdk/react-native/5.x/tracking/lifecycle-events/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/5.x/tracking/lifecycle-events/By default, we track the following lifecycle events: Application Installed: A user installed your app. Application Updated: A user updated your app. Application Opened: A user opened your app. Application Foregrounded: A user switched back to your app. Application Backgrounded: A user backgrounded your app or switched to another app. You might also want to send your own lifecycle events, like Application Crashed or Application Updated. You can do this using the track method.https://docs.customer.io/integrations/sdk/react-native/tracking/lifecycle-events/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/tracking/lifecycle-events/By default, we track the following lifecycle events: Application Installed: A user installed your app. Application Updated: A user updated your app. Application Opened: A user opened your app. Application Foregrounded: A user switched back to your app. Application Backgrounded: A user backgrounded your app or switched to another app. You might also want to send your own lifecycle events, like Application Crashed or Application Updated. You can do this using the track method.https://docs.customer.io/journeys/newsletters/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/newsletters/How it works A Newsletter is a single message that you want to send to a group of people. You can schedule a newsletter or send it immediately. Newsletters provide a simple way to broadcast a message to your audience without setting up a complex campaign. You might send a newsletter to alert your audience to changes in your terms of service, or to a group of people when you onboard people belonging to an account.https://docs.customer.io/journeys/opt-in-and-out-flow/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/opt-in-and-out-flow/You must preview your opt-in and out flow before you register as an SMS sender You do not need to have completed your opt-in and out flow before you contact Customer.io to register as an SMS sender—in part because you won’t be able to do it until you have a sender number! But you need to have designs or a preview to demonstrate your opt-in and out flow. Twilio and carriers evaluate your designs to make sure that you’re ready to send messages.https://docs.customer.io/ai/mcp-server/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/ai/mcp-server/How it works Our Model Context Protocol (MCP) Server helps you interact with Customer.io through your favorite AI tools—Claude, Cursor, and so on. Where you might be able to use our APIs to do some things, the MCP server is a layer of tools that includes features that aren’t possible with our APIs today. The MCP server is especially helpful if you want to integrate your mobile or web app with Customer.https://docs.customer.io/integrations/api/track-vs-cdp-api/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/api/track-vs-cdp-api/TL;DR: Which API should I use? We recommend that you use the Pipelines API unless you send data to Customer.io through a customer data platform (CDP) like Segment or Rudderstack. The Pipelines API is newer and includes support for newer Customer.io features like geolocation. General differences We have two APIs to help you get data into Customer.io: the Track API and the Pipelines API. If you’re new to Customer.io: most of our libraries and SDKs are based on the Pipelines API; it’s what you’ll use for most integrations.https://docs.customer.io/journeys/data-campaign-event-action/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/data-campaign-event-action/ You can send events from other kinds of campaigns too! You’re most likely to create events in webhook-triggered campaigns—that’s how you associate incoming data with a person. But now you can send events from any campaign, making it easy to trigger parallel campaigns. You can send an event for the current person or someone else entirely. How it works Webhook-triggered campaigns start with arbitrary data from an incoming webhook. This data isn’t associated with a person, and it can take any shape.https://docs.customer.io/journeys/event-action/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/event-action/An event consists of a name and a data object. The name is typically how you’ll select an event, and you can further filter people based on data in the event. You can use properties in the data object to personalize campaigns using liquidA syntax that supports variables, letting you personalize messages for your audience. For example, if you want to reference a person’s first name, you might use the variable {{customer.https://docs.customer.io/journeys/properties-menu/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/properties-menu/Global styles vs message styles By default, components pull from your Global Styles—like text, link, and button styles. If you want to change these for an individual message, you can override them in the Properties menu. To override styles for a group of standard componentsA pre-built block that helps you build beautiful, engaging messages as quickly as possible in Design Studio., add them to a container (like a section, box, or column) and modify the container’s styles—the components will inherit these.https://docs.customer.io/journeys/code-editor-emmet/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/code-editor-emmet/For example, type this (don’t copy/paste): div>div>table>tr*3>td>a Then hit tab and it expands to: <div> <div> <table> <tr> <td><a href=""></a></td> </tr> <tr> <td><a href=""></a></td> </tr> <tr> <td><a href=""></a></td> </tr> </table> </div> </div> You can learn more about abbreviations in the official Emmet documentation. Specify child tags with > table>tr>td Becomes… <table> <tr> <td></td> </tr> </table> Specify sibling tags with + a+a+a Becomes… <a href=""></a> <a href=""></a> <a href=""></a> Multiply tags with * table>tr*3>td*2 Becomes…https://docs.customer.io/integrations/sdk/android/tracking/anonymous-activity/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/android/tracking/anonymous-activity/In Customer.io, you’ll see anonymous activity in the Activity Log, but we don’t surface anonymous profilesAn instance of a person. Generally, a person is synonymous with their profile; there should be a one-to-one relationship between a real person and their profile in Customer.io. You reference a person’s profile attributes in liquid using customer—e.g. {{customer.email}}. in Customer.io. You won’t be able to find an “anonymous person” in your workspace, and an anonymous person can’t trigger campaigns or get messages (including push notifications) from Customer.https://docs.customer.io/integrations/sdk/flutter/2.x/tracking/anonymous-activity/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/flutter/2.x/tracking/anonymous-activity/In Customer.io, you’ll see anonymous activity in the Activity Log, but we don’t surface anonymous profilesAn instance of a person. Generally, a person is synonymous with their profile; there should be a one-to-one relationship between a real person and their profile in Customer.io. You reference a person’s profile attributes in liquid using customer—e.g. {{customer.email}}. in Customer.io. You won’t be able to find an “anonymous person” in your workspace, and an anonymous person can’t trigger campaigns or get messages (including push notifications) from Customer.https://docs.customer.io/integrations/sdk/flutter/tracking/anonymous-activity/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/flutter/tracking/anonymous-activity/In Customer.io, you’ll see anonymous activity in the Activity Log, but we don’t surface anonymous profilesAn instance of a person. Generally, a person is synonymous with their profile; there should be a one-to-one relationship between a real person and their profile in Customer.io. You reference a person’s profile attributes in liquid using customer—e.g. {{customer.email}}. in Customer.io. You won’t be able to find an “anonymous person” in your workspace, and an anonymous person can’t trigger campaigns or get messages (including push notifications) from Customer.https://docs.customer.io/integrations/sdk/ios/3.x/tracking/anonymous-activity/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/3.x/tracking/anonymous-activity/In Customer.io, you’ll see anonymous activity in the Activity Log, but we don’t surface anonymous profilesAn instance of a person. Generally, a person is synonymous with their profile; there should be a one-to-one relationship between a real person and their profile in Customer.io. You reference a person’s profile attributes in liquid using customer—e.g. {{customer.email}}. in Customer.io. You won’t be able to find an “anonymous person” in your workspace, and an anonymous person can’t trigger campaigns or get messages (including push notifications) from Customer.https://docs.customer.io/integrations/sdk/ios/tracking/anonymous-activity/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/tracking/anonymous-activity/In Customer.io, you’ll see anonymous activity in the Activity Log, but we don’t surface anonymous profilesAn instance of a person. Generally, a person is synonymous with their profile; there should be a one-to-one relationship between a real person and their profile in Customer.io. You reference a person’s profile attributes in liquid using customer—e.g. {{customer.email}}. in Customer.io. You won’t be able to find an “anonymous person” in your workspace, and an anonymous person can’t trigger campaigns or get messages (including push notifications) from Customer.https://docs.customer.io/integrations/sdk/react-native/4.x/tracking/anonymous-activity/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/4.x/tracking/anonymous-activity/In Customer.io, you’ll see anonymous activity in the Activity Log, but we don’t surface anonymous profilesAn instance of a person. Generally, a person is synonymous with their profile; there should be a one-to-one relationship between a real person and their profile in Customer.io. You reference a person’s profile attributes in liquid using customer—e.g. {{customer.email}}. in Customer.io. You won’t be able to find an “anonymous person” in your workspace, and an anonymous person can’t trigger campaigns or get messages (including push notifications) from Customer.https://docs.customer.io/integrations/sdk/react-native/5.x/tracking/anonymous-activity/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/5.x/tracking/anonymous-activity/In Customer.io, you’ll see anonymous activity in the Activity Log, but we don’t surface anonymous profilesAn instance of a person. Generally, a person is synonymous with their profile; there should be a one-to-one relationship between a real person and their profile in Customer.io. You reference a person’s profile attributes in liquid using customer—e.g. {{customer.email}}. in Customer.io. You won’t be able to find an “anonymous person” in your workspace, and an anonymous person can’t trigger campaigns or get messages (including push notifications) from Customer.https://docs.customer.io/integrations/sdk/react-native/tracking/anonymous-activity/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/tracking/anonymous-activity/In Customer.io, you’ll see anonymous activity in the Activity Log, but we don’t surface anonymous profilesAn instance of a person. Generally, a person is synonymous with their profile; there should be a one-to-one relationship between a real person and their profile in Customer.io. You reference a person’s profile attributes in liquid using customer—e.g. {{customer.email}}. in Customer.io. You won’t be able to find an “anonymous person” in your workspace, and an anonymous person can’t trigger campaigns or get messages (including push notifications) from Customer.https://docs.customer.io/journeys/sms-brand-campaign/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/sms-brand-campaign/How it works Brand and Campaign are regulatory terms for sending messages in the US and Canada. Before you can register for phone numbers, you have to declare who you are—your brand—and what kinds of messages you’ll send—your campaigns. We’ll help you register your brand and campaigns. If you want to get started right away, take a look at campaigns below. Before you contact Customer.io to help you register as an SMS sender, you’ll need to provide at least three example messages for each of your campaign use cases—each kind of message you want to send.https://docs.customer.io/journeys/subscription-metrics/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/subscription-metrics/You can track subscription preference changes across campaigns, broadcasts, and newsletters—and send subscription events to external systems through reporting webhooks and data warehouse integrations. Metrics for subscription preferences You can track unsubscribes from topics across campaigns and broadcasts within the Journeys UI or through reporting webhooks. Unsubscribed from topics counts each subscription topic that a user unsubscribed from through a delivered message. As such, you may see a percentage above 100; say you have 4 subscription topics and 5 messages are delivered to five users.https://docs.customer.io/journeys/phone-number-types/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/phone-number-types/Most of the guidance here is focused on the United States and Canada—the regions we typically support through Twilio. You can use international numbers, but you may need to work with Twilio to support them. Types of phone numbers You can send messages using three different kinds of phone numbers. In general, all three have similar regulatory requirements, but they have different daily sending limits. You’ll want to pick the type of number that best fits your business needs.https://docs.customer.io/journeys/send-in-app-message/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/send-in-app-message/Before you begin You’re welcome to try out our in-app message editor and set up campaigns with in-app messages before you integrate our SDKs. But your audience won’t be able to see your in-app messages until you integrate with our SDKs for your app or your website. How it works You can send in-app messages as a part of any campaign or broadcast workflow. In addition to creating your message, you’ll also determine when and where your message will show up for your audience:https://docs.customer.io/integrations/sdk/expo/whats-new/3.x-upgrade/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/expo/whats-new/3.x-upgrade/What changed? Version 3.0.0 removes support for React Native’s legacy architecture. This aligns with React Native’s move to exclusively support their new architecture. You must migrate your app to use React Native’s new architecture to use this and future versions of the plugin. Do you need to update to this version? We recommend updating to the latest plugin version. However, if your app uses the old React Native architecture and you’re not ready to migrate, you can continue using version 2.https://docs.customer.io/integrations/sdk/ios/3.x/whats-new/3.9.0-upgrade/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/3.x/whats-new/3.9.0-upgrade/Key Changes The primary change in version 3.9.0 is the introduction of the wrapper pattern for handling push notifications on iOS. This change: Eliminates method swizzling: No more automatic method replacement Simplifies setup: Less boilerplate code required Improves reliability: More predictable behavior See the instructions below to update your app depending on whether you send push notifications with APN or FCM and whether you use UIKit or SwiftUI. Update with APNs UIKit Update your AppDelegate.https://docs.customer.io/integrations/sdk/ios/whats-new/4.0.0-upgrade/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/whats-new/4.0.0-upgrade/What changed? Version 4.0.0 introduces a breaking change for users who utilize Firebase Cloud Messaging (FCM) for push notifications. The change improves the FCM integration by consolidating Firebase dependencies into a dedicated wrapper package. FCM Integration Changes New dependency required: CioFirebaseWrapper package is now required for FCM push notifications Import statement updated: Add import CioFirebaseWrapper wherever you use import CioMessagingPushFCM Initialize method unchanged: Continue using MessagingPushFCM.initialize() but it now comes from the new package Note: This change only affects users utilizing FCM for push notifications.https://docs.customer.io/integrations/sdk/android/whats-new/4.10-upgrade/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/android/whats-new/4.10-upgrade/What changed? The changes in this update are mainly to align our APIs across different platforms. You should not experience changes to functionality or features. Changes to initialization CustomerIOBuilder is deprecated. You should use CustomerIOConfigBuilder instead. Before CustomerIOBuilder( applicationContext = this, // new credentials cdpApiKey = "your_cdp_api_key" migrationSiteId = "your_site_id" ).apply { // If you're in the EU, set Region.EU region(Region.US) addCustomerIOModule( ModuleMessagingInApp( // the in-app module now has its own configuration config = MessagingInAppModuleConfig.https://docs.customer.io/integrations/data-in/semantic-events/a-b-test/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/semantic-events/a-b-test/How it works A/B tests help you determine how variations in your websites, apps, and services perform with your audience. We use this specification to support default actions—any we have now and ones we might add in the future. So, if you send A/B tests that conform to this specification, you’ll be ready to trigger downstream actions in outbound integrations that rely on an A/B testing framework. We refer to A/B tests as experiments.https://docs.customer.io/get-started/get-started-academy/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/get-started/get-started-academy/The Academy is a free resource where anybody with a Customer.io account can learn about Customer.io. Access the academy To access the Academy: Log into your account. Click Need help? at the top. Click Learn with Academy. From there, you can browse individual courses or complete a longer learning path composed of multiple courses. Learning paths are great for getting started with Customer.io! You can also filter by topic or use the search bar to find relevant learning material.https://docs.customer.io/journeys/liquid-visual-editor/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/liquid-visual-editor/Use the Personalization panel to add the data you want into your messages without having to memorize our syntax or remember all of your attributes. After you add your liquid, enter Preview mode to check that your data renders as you’d expect! Add liquid You can add liquid to text-based standard componentsA pre-built block that helps you build beautiful, engaging messages as quickly as possible in Design Studio. in three ways:https://docs.customer.io/integrations/data-out/add-destination/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/add-destination/How it works An outgoing integration is the place you want to send your data to—where you store data, use it to gather analytics, to power marketing automation (like Customer.io Journeys), and so on. You can send data from any number of incoming integrations to and outgoing integration, or you can do simple one-to-one mapping—whatever you need. However, in most cases, you’ll find that you typically want to aggregate data from multiple data sources to a single outgoing integration—so you can act on a holistic understanding of your audience.https://docs.customer.io/journeys/url-parameters/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/url-parameters/How it works While Customer.io supports link tracking, you might want to add URL parameters to links to track clicks from specific campaigns, messages, or other factors. You can manually add URL parameters to links in messages, but this can be tedious and error-prone. You probably have a repeatable set of parameters that you want to use for links in different messages. That’s where our URL parameters feature comes in. It makes it easy to automatically append a templated set of URL parameters to links in your messages.https://docs.customer.io/journeys/feature-adoption/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/feature-adoption/Business-to-business (B2B) companies often need to track and drive growth across both individual users of their product and the account or company they work for. In Customer.io, objectsAn object is a non-person entity that you can associate with one or more people—like a company, account, or online course. help you do this. For this recipe, imagine you work at a design platform, Sketcher.io, which offers graphic design and product design tools.https://docs.customer.io/integrations/data-in/connections/classic-api/cio-journeys-api/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/classic-api/cio-journeys-api/ Try using one of our SDKs or the Pipelines API instead Changing actionsA block in a campaign workflow—like a message, delay, or attribute change. for data coming into Customer.io can be complex. If you’re just getting started, we suggest that you format your data based on our default actions and don’t change them. These integrations are based on the Pipelines API already, and our libraries make it easier to understand and manage action mappings for destinations.https://docs.customer.io/journeys/api-triggered-broadcasts/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/api-triggered-broadcasts/How it works API-triggered broadcasts provide a way to send a one-to-many campaign on demand. It may help to think of API-triggered broadcasts like event-triggered campaigns, except the event comes from your backend integration and represents a group of people. For example, you might use an API-triggered broadcast to: Send news alerts to a group of people interested in a specific topic. Alert users interested in an event when tickets go on sale.https://docs.customer.io/journeys/batch-update-webhook-campaigns/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/batch-update-webhook-campaigns/How it works You can perform a batch update in any campaign, but you’re most likely to use it in a webhook-triggered campaign, which starts with arbitrary data from an incoming webhook. This data isn’t associated with anybody, and it can take any shape. A batch update lets you associate this data with one or more people—either as attributesA key-value pair that you associate with a person or an object—like a person’s name, the date they were created in your workspace, or a company’s billing date etc.https://docs.customer.io/journeys/batch-update/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/batch-update/How it works You can perform a batch update in any campaign. A batch update lets you associate this data with one or more people—either as attributesA key-value pair that you associate with a person or an object—like a person’s name, the date they were created in your workspace, or a company’s billing date etc. Use attributes to target people and personalize messages. or eventsSomething that a person in your workspace did.https://docs.customer.io/journeys/intro-to-campaigns/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/intro-to-campaigns/Click Campaigns in the left-hand menu to find a list of your campaigns. You can filter for your campaigns, change the default data you see, modify the state of your campaigns, or initiate creating one. Search for campaigns You can filter to find campaigns by: name description triggerA trigger determines who enters your campaign and when. status - whether your campaign is active (running) or not (draft, stopped) topic - the subscription preferenceCustomer.https://docs.customer.io/journeys/types-of-campaigns-and-broadcasts/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/types-of-campaigns-and-broadcasts/If you’re just getting started, checkout Start sending campaigns and workflows for a high-level overview. Campaigns Campaigns offer the most robust options for messaging automation. They offer the most flexible and specific options for triggering a campaign as well as the ability to automate messages over time, as opposed to sending messages all at once. Your campaign trigger determines who enters your campaign and when. Most triggers are based around people, like when they match certain criteria.https://docs.customer.io/journeys/whatsapp-content-templates/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/whatsapp-content-templates/How it works WhatsApp requires that you use templates to ensure that messages comply with their policies and to prevent spam. So, before you can send WhatsApp messages, you’ll need to create templates and have them approved by Meta/WhatsApp. The process to create and use templates depends on whether you connected your Facebook Business Account directly to Customer.io or set up WhatsApp support as a part of your SMS setup through Twilio.https://docs.customer.io/journeys/create-update-person/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/create-update-person/How it works You can use the Create or update person action in any campaign workflow. When you update the person currently in your campaign, you can set attributes from static values, the event that triggered your campaign, other profileAn instance of a person. Generally, a person is synonymous with their profile; there should be a one-to-one relationship between a real person and their profile in Customer.io. You reference a person’s profile attributes in liquid using customer—e.https://docs.customer.io/integrations/data-in/custom-events/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/custom-events/How it works Most of our API methods have a defined purpose: the identify call identifies users; page calls track pageviews. But the track call lets you send custom events, so that you can track the activities that are meaningful to you. Track calls take a name representing the name of the event you want to track and a set of custom properties. For example, when someone adds an item to their cart, you might send an added_to_cart event with properties representing the item that your customer added to their cart.https://docs.customer.io/integrations/data-in/semantic-events/cio-journeys/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/semantic-events/cio-journeys/How it works Your workspace supports a number of actions that aren’t immediately apparent from the API. For example, I can add a person using the identify function, but what if I want to remove a person? That’s what semantic events are for: they let you send track calls with a specific event name to perform actions in Customer.io. In general, the event names map directly to the thing you want to do: like Create Device or Delete Person.https://docs.customer.io/journeys/customizing-layout-starters/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/customizing-layout-starters/ Layouts are only available in our rich text or code editors. You cannot use layouts with Design Studio or our drag and drop editor; instead, start from a template. Or learn more about the reusable content features available in Design Studio (components) and the drag and drop editor (saved rows, snippets). Our Layout Starters are built using a framework called Foundation for Emails. This framework ensures that our starter email layouts are generally supported across clients, while still letting you to customize the look and feel of your emails.https://docs.customer.io/integrations/data-in/semantic-events/ecommerce/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/semantic-events/ecommerce/How it works Ecommerce track events typically contain the same information across platforms—products, brands, orders, cart information, etc. However, each place you send this data to might map this information differently. Our ecommerce specification helps you send events in a uniform format that maps to the actionsThe source event and data that triggers an API call to your destination. For example, an incoming identify event from your sources adds or updates a person in our Customer.https://docs.customer.io/journeys/publish-changes/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/publish-changes/ You’ll need to publish changes not just when you update the message in the editor, but also when you update a custom componentA custom block of code with content and properties you can reuse across messages made in Design Studio. file or global style used in the message. Edit your message Access the message from either the connected automation or directly in Design Studio. In either case, you’ll have full access to editing and previewing your message.https://docs.customer.io/journeys/email-deliverability-best-practices/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/email-deliverability-best-practices/What is email deliverability? Email deliverability is whether or not the emails you are sending are reaching the inbox of your recipients. There are a number of factors that can directly influence whether or not your emails arrive in the inbox. All of these best practice guidelines should be addressed to ensure maximum deliverability. Deliverability factors Technical Setup Configuring your MX, DKIM and SPF records is the most important step in letting inbox providers know that Customer.https://docs.customer.io/integrations/data-in/semantic-events/email/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/semantic-events/email/How it works Email service providers and other platforms produce events that help you track the lifecycles of your emails—whether emails are delivered, opened, etc. If you send email events into Customer.io, we recommend that you follow the specifications on this page. See Email Events if you want to download the specification or try out email events. We use this specification to support default actions—any we have now and ones we might add in the future.https://docs.customer.io/journeys/email-getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/email-getting-started/How it works When you get started with Customer.io or create a new workspace, you can choose how you want to send emails: Through Customer.io as your managed provider Through your own provider/SMTP server In most cases, the choice is simple: if you already have your own provider, you can use them. If you don’t, it’s probably easiest to use Customer.io. In either case, you’ll need to verify your domain to send email.https://docs.customer.io/journeys/satismeter-data-campaign/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/satismeter-data-campaign/As a part of this guide, you’ll: Set up a webhook-triggered campaign, capturing a response from Satismeter when someone fills out your survey and converting it to an event. Set up an event-triggered campaign (using the Satismeter event) to message people based on their net promoter score (NPS). sequenceDiagram participant A as Customer participant B as Satismeter participant C as Customer.io A->>B: Customer gives NPS rating B->>C: Webhook forwards response C->>C: Convert to event C->>A: Email customer with response Before you begin You’ll need access to your Satismeter account and your Customer.https://docs.customer.io/journeys/in-app-forms/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/in-app-forms/ We’re adding to this feature! Today, forms support text input, but we’re working on support for more input types—like checkboxes and radio buttons. How it works In-app messages—sent to your mobile app or website—can include form components to collect text-based feedback from recipients. When you add a Form or form-styled components to your message like Long Text or Short Text, we add a Form element to your message. Whenever someone submits the form, we’ll:https://docs.customer.io/integrations/data-in/connections/forms/formstack/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/forms/formstack/How it works Formstack is a form builder that lets you create forms and add them to your website. This integration lets you identifyThe Customer.io operation that adds or updates a person. When you identify a person, Customer.io either adds a person if they don’t exist in your workspace, or updates them if they do. Before you identify someone (by their email address or an ID), you can track them anonymously.https://docs.customer.io/journeys/push-getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/push-getting-started/Before you begin Setting up push notifications requires development work in your mobile app, access to your push provider, and then you’ll need to compose messages in Customer.io. This may mean that you’ll need to coordinate work across a few different people in your organization to get up and running! Your path in the setup process might change depending on whether you’re a developer integrating with Customer.io or a marketer who wants to send messages.https://docs.customer.io/journeys/slack/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/slack/What you need to get started It’s very easy to set up Slack in Customer.io. All you’ll need are your Slack login details, if you’re not logged into your team already. Enable Slack in Customer.io Before you can send Slack messages, you need to enable the Slack action in Customer.io—essentially inviting Customer.io to your Slack workspace as a bot. When you configure Slack in Customer.io, you need to provide Slack credentials with the “bot” scope, letting Customer.https://docs.customer.io/journeys/global-styles-in-app/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/global-styles-in-app/How Design Studio works Design Studio is a flexible editor that helps you create beautiful, responsive messages faster than ever before. Use it to set branding across emails made in Design Studio and in-app messages. If you’re new to Design Studio, this is the core of what you need to know: You continue to create an in-app message in a workflow, like a campaign or broadcast. By default, new messages use the styles set in Design Studio.https://docs.customer.io/integrations/data-in/connections/servers/go/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/servers/go/How it works Our Go library helps you record source events from your server-side code. This lets your Go-based app send requests to our servers, and we route your data to your cloud-mode destinations. Like our other libraries, you can log anonymous activity with an anonymousId. When you identify a person, you can pass the anonymousId and we’ll associate the anonymous activity with the identified person. This library uses a configurable buffer to batch messages, optimized to reduce network activity.https://docs.customer.io/journeys/identifying-people/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/identifying-people/How it works You can identify people using values that are unique for each person, like an email address or a user id. You add and update people based on their identifiers. To identify people, you need to first understand your workspace settings. Then you can add or update people based on the allowed identifiers: email: A person’s email address. You may want to use this identifier to track leads before they become customers.https://docs.customer.io/accounts-and-workspaces/how-we-bill/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/accounts-and-workspaces/how-we-bill/How it works When you sign up for Customer.io, you choose a plan—essentials, premium, or enterprise. Your plan determines how many emails and profilesThe representation of a person or group in Customer.io. People and custom objects both have their own profiles, but we bill based on the total number of profiles in your account. you’re entitled to. Profiles are the peopleAn instance of a person. Generally, a person is synonymous with their profile; there should be a one-to-one relationship between a real person and their profile in Customer.https://docs.customer.io/integrations/data-in/source-spec/identify-spec/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/source-spec/identify-spec/ See our API documentation for code samples This page can help you better understand when and how to use this API method. But, if you already know how it works and are ready to get started, you can go straight to our API documentation and start writing code. How it works The Identify method helps you represent a user and their traits — the things you know about them, like their name, email address, and so on.https://docs.customer.io/integrations/data-in/connections/javascript/legacy-js/identify/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/javascript/legacy-js/identify/How it works Identifying people adds them to, or updates them in, your workspace, and makes them eligible to receive in-app messages. After you identify someone, calls to the SDK will automatically reference the identified person until you identify someone else or send a reset call. Before you identify someone, we’ll attribute their activity on your website—page and track events—to an anonymous user. When you identify a person, we’ll automatically associate their anonymous activities with their profile in your workspace.https://docs.customer.io/integrations/sdk/android/in-app/in-app-event-listeners/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/android/in-app/in-app-event-listeners/Handle responses to messages (event listeners) You can set up event listeners to handle your audience’s response to your messages. For example, you might run different code in your app when your audience taps a button in your message or when they dismiss the message without tapping a button. You can listen for four different events: messageShown: a message is “sent” and appears to a user messageDismissed: the user closes the message (by tapping an element that uses the close action) errorWithMessage: the message itself produces an error—this probably prevents the message from appearing to the user messageActionTaken: the user performs an action in the message.https://docs.customer.io/integrations/sdk/android/in-app/inline-in-app/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/android/in-app/inline-in-app/How it works An inline message targets a specific view in your app. Basically, you’ll create an empty placeholder view in your app’s UI, and we’ll fill it with the content of your message. This makes it easy to show dynamic content in your app without development effort. You don’t need to force an update every time you want to talk to your audience. And, unlike push notifications, banners, toasts, and so on, in-line messages can look like natural parts of your app.https://docs.customer.io/integrations/sdk/expo/in-app-messages/inline-in-app/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/expo/in-app-messages/inline-in-app/How it works An inline message targets a specific view in your app. Basically, you’ll create an empty placeholder view in your app’s UI, and we’ll fill it with the content of your message. This makes it easy to show dynamic content in your app without development effort. You don’t need to force an update every time you want to talk to your audience. And, unlike push notifications, banners, toasts, and so on, in-line messages can look like natural parts of your app.https://docs.customer.io/integrations/sdk/flutter/2.x/in-app-messages/inline-in-app/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/flutter/2.x/in-app-messages/inline-in-app/How it works An inline message targets a specific widget in your app. You create a placeholder InlineInAppMessageView in your UI, and the SDK fills it with the content of your message. Inline messages let you show dynamic content without releasing a new version of your app. Unlike push notifications, banners, or modal in-app messages, an inline message looks and feels like part of your interface. 1. Add View to your app UI to support inline messages Add InlineInAppMessageView anywhere you want to display inline messages.https://docs.customer.io/integrations/sdk/flutter/in-app-messages/inline-in-app/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/flutter/in-app-messages/inline-in-app/How it works An inline message targets a specific widget in your app. You create a placeholder InlineInAppMessageView in your UI, and the SDK fills it with the content of your message. Inline messages let you show dynamic content without releasing a new version of your app. Unlike push notifications, banners, or modal in-app messages, an inline message looks and feels like part of your interface. 1. Add View to your app UI to support inline messages Add InlineInAppMessageView anywhere you want to display inline messages.https://docs.customer.io/integrations/sdk/ios/3.x/in-app/inline-in-app/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/3.x/in-app/inline-in-app/How it works An inline message targets a specific view in your app. Basically, you’ll create an empty placeholder view in your app’s UI, and we’ll fill it with the content of your message. This makes it easy to show dynamic content in your app without development effort. You don’t need to force an update every time you want to talk to your audience. And, unlike push notifications, banners, toasts, and so on, in-line messages can look like natural parts of your app.https://docs.customer.io/integrations/sdk/ios/in-app/inline-in-app/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/in-app/inline-in-app/How it works An inline message targets a specific view in your app. Basically, you’ll create an empty placeholder view in your app’s UI, and we’ll fill it with the content of your message. This makes it easy to show dynamic content in your app without development effort. You don’t need to force an update every time you want to talk to your audience. And, unlike push notifications, banners, toasts, and so on, in-line messages can look like natural parts of your app.https://docs.customer.io/integrations/sdk/react-native/4.x/in-app-messages/inline-in-app/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/4.x/in-app-messages/inline-in-app/How it works An inline message targets a specific view in your app. Basically, you’ll create an empty placeholder view in your app’s UI, and we’ll fill it with the content of your message. This makes it easy to show dynamic content in your app without development effort. You don’t need to force an update every time you want to talk to your audience. And, unlike push notifications, banners, toasts, and so on, in-line messages can look like natural parts of your app.https://docs.customer.io/integrations/sdk/react-native/5.x/in-app-messages/inline-in-app/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/5.x/in-app-messages/inline-in-app/How it works An inline message targets a specific view in your app. Basically, you’ll create an empty placeholder view in your app’s UI, and we’ll fill it with the content of your message. This makes it easy to show dynamic content in your app without development effort. You don’t need to force an update every time you want to talk to your audience. And, unlike push notifications, banners, toasts, and so on, in-line messages can look like natural parts of your app.https://docs.customer.io/integrations/sdk/react-native/in-app-messages/inline-in-app/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/in-app-messages/inline-in-app/How it works An inline message targets a specific view in your app. Basically, you’ll create an empty placeholder view in your app’s UI, and we’ll fill it with the content of your message. This makes it easy to show dynamic content in your app without development effort. You don’t need to force an update every time you want to talk to your audience. And, unlike push notifications, banners, toasts, and so on, in-line messages can look like natural parts of your app.https://docs.customer.io/integrations/api/integrate-with-ds/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/api/integrate-with-ds/To upload or update assets like images and PDFs, you’ll use a different set of endpoints: the Assets endpoints. Both the Assets and Design Studio endpoints are part of our App API and use the same bearer token for authentication. How it works Regardless of which external editor you use, the process for preparing and integrating your email with Customer.io follows the same pattern: Design your email in your preferred tool.https://docs.customer.io/journeys/push-developer-guide/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/push-developer-guide/When you integrate with us, you have some choices depending on the push platform you use (APNs, FCM) and whether or not you want to use our SDKs—though we strongly recommend that you use our SDKs if possible to simplify your integration process. But, before you can send and receive push notifications with Customer.io, you must: Generate and add certificates for your push service, Apple Push Notification service (APNs) and/or Firebase Cloud Messaging (FCM).https://docs.customer.io/integrations/data-in/connections/forms/jotform/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/forms/jotform/How it works When you set up a Jotform integration, we’ll give you a personalized Webhook URL. You’ll provide this webhook URL to Jotform. Whenever someone submits your form, Jotform calls this webhook to send the form submission data to Customer.io. The form submission creates a person in your workspace if they do not already exist, or updates them if they do. In both cases, we map form fields to attributesA key-value pair that you associate with a person or an object—like a person’s name, the date they were created in your workspace, or a company’s billing date etc.https://docs.customer.io/journeys/in-app-lead-form/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/in-app-lead-form/How it works The Lead Form component is a form containing Name and Email fields. When people submit the form, we’ll add the person to your workspace so you can send them messages and convert them to a customer or user. This component helps you capture leads from anonymous messages. For example, you might send an anonymous message with a Lead Form that offers people coupons when they sign up with their email addresses.https://docs.customer.io/journeys/line-metrics/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/line-metrics/LINE message metrics The following metrics apply to LINE messages. Note that metrics like Delivered depend on the webhook you set up in your LINE account. Metric Description Attempted We’re trying to send the message to LINE. You may see this status if we need to retry your message. Sent The message left Customer.io and was passed to LINE. Delivered LINE confirmed that the message reached the recipient, reported through your LINE webhook.https://docs.customer.io/journeys/sms-link-shortening/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/sms-link-shortening/How it works In Workspace settings > SMS, you’ll see a toggle for Shorten links. When this is enabled, we automatically shorten links in your SMS/MMS messages. When someone clicks a shortened link, the link directs them to Customer.io, where we’ll resolve the link and then send your audience to the ultimate destination. Shortened links are especially helpful with link tracking. By default, we track the links that people click in your SMS or WhatsApp messages, but tracked links won’t reliably fit inside a 160 character SMS message; shortened links fix that!https://docs.customer.io/integrations/data-in/semantic-events/live-chat/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/semantic-events/live-chat/How it works If you send live chat events into Data Customer.io, you should shape incoming events using the formats on this page. We use this specification to support default actions—any we have now and ones we might add in the future. If you send live chat events that conform to this specification, you’ll be ready to trigger downstream actions in integrations that rely on an live chat events. See Live Chat Events if you want to download the specification or try out live chat events.https://docs.customer.io/integrations/data-in/connections/javascript/method-reference/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/javascript/method-reference/Identify The identify method is how you link your users, and their actions, to a recognizable userId and traits. The Identify method follows the format below and includes the following options. cioanalytics.identify([userId], [traits], [options], [callback]); // A typical identify call without options or callback cioanalytics.identify('f4ca124298', { email: 'cool.person@example.com', first_name: 'cool', last_name: 'person' }); Argument Optional/Required Type Description userId optional String The database ID for the user. If you don't know who the user is yet, you can omit the userId and just record traits.https://docs.customer.io/journeys/analytics/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/analytics/What does Customer.io measure? We primarily focus on two kinds of metrics. You may find a combination of both of these things on the Home dashboard, Analysis, and Campaign Overview pages. While they often correspond, it’s important to note that we measure two different things. Campaign journeyTypically, a person’s path through your campaign. If the campaign is triggered by a webhook, then a journey captures the webhook’s path, not a person’s.https://docs.customer.io/journeys/migrate-comp-from-parcel/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/migrate-comp-from-parcel/Keep the following in mind as you migrate: Make sure the component tag name matches the content value in the script element. If this is the child of another component, make sure you also add the parent components to Design Studio or remove the allowedParents array. If you run into other issues, try troubleshooting with our GPT designed for creating custom components!https://docs.customer.io/journeys/push-migration/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/push-migration/How it works While you can export your audience from your old provider, push notification delivery is still dependent on the SDK(s) in your app. You can’t send a push from Customer.io to someone using a version of your app that doesn’t use Customer.io! So, when you move to Customer.io from another push provider, you’ll need to import your audience and help them upgrade to a version of your app that uses Customer.https://docs.customer.io/integrations/data-in/connections/javascript/js-migration/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/javascript/js-migration/Migrating from Segment Our calls are nearly identical to Segment’s. In most cases, you can simply replace your Segment script with our JavaScript client, and you’re all set. However, Segment supports a wider range of integration destinations than we do. Before you make the switch, check that we support the services you integrate with and the actionsThe source event and data that triggers an API call to your destination. For example, an incoming identify event from your sources adds or updates a person in our Customer.https://docs.customer.io/integrations/data-in/semantic-events/mobile-app/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/semantic-events/mobile-app/How it works Our Mobile App Lifecycle Event specification helps you send events in a uniform format that automatically maps data to the integrations we support. Following this spec makes it easier to use data from your mobile apps without having to re-map your incoming data each time you set up a new integration. These events typically contain information about your app version and build. If you use our SDKs, we capture some of the following events automatically.https://docs.customer.io/journeys/objects-create/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/objects-create/ Before you can create an object, you must create an object type. Create an object Remember that an object type is the kind of non-people grouping that you want to track in Customer.io—like Companies, Online classes, or Accounts. An object is an individual thing—a single company, online class, or account—that you want to relate to one or more people. You can create objects programmatically by integrating your systems with your Customer.https://docs.customer.io/journeys/device-tokens/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/device-tokens/What is a device token? Device tokens—sometimes known as push tokens in other products or push services—are unique, anonymous identifiers for the app-device combination that are issued by push notification services: they’re basically device addresses, so you can send push notifications to your app’s users. If a person doesn’t have a device token, they can’t receive push notifications and their device won’t appear in Customer.io. In Customer.io, we reflect device tokens as devices (or device_id in our APIs and SDKs).https://docs.customer.io/ai/agent/ai-segment-builder/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/ai/agent/ai-segment-builder/How it works Segment conditions typically require you to break your audience down into if this, then that style statements—but the logic can become complex when you have narrow or especially dense conditions. To help you build these conditions, you can use our agent. Describe the segment or ask for suggestions based on your target audience. You can ask the agent to build a segment at any time. Or, when you go to create a segmentA group of people who match a series of conditions.https://docs.customer.io/journeys/send-test/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/send-test/You can send a test message before or after connecting a Design Studio message to an automation. Open the message in Design Studio or the connected automation. Click Send test. Add up to 25 email addresses or choose an email group. Your email address is added by default. Click Send. Prevent threading adds a unique subject line so your inbox won’t group test emails together. If you don’t want this, uncheck the box.https://docs.customer.io/journeys/send-a-welcome-email/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/send-a-welcome-email/Introduction The way you make customers feel in the first few days after they’ve signed up for your site or service can influence their level of engagement with your company long-term. This moment of first impression is a crucial moment. In this tutorial, we’ll walk you through creating your welcome email in Customer.io (and also assumes that you’ve completed your integration). Ingredients Every customer in your Customer.io account must have a created_at attributeA key-value pair that you associate with a person or an object—like a person’s name, the date they were created in your workspace, or a company’s billing date etc.https://docs.customer.io/journeys/send-whatsapp/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/send-whatsapp/Set up your WhatsApp message  If you created your WhatsApp template in Design Studio, check out our Design Studio docs! The process for sending a WhatsApp message made with Design Studio is simpler than with other templates. Learn more. Add a WhatsApp message block to your campaign or broadcast workflow. Click Add Content. Select a WhatsApp approved sender in the From field. If you only have one sender phone number, it’s already selected for you.https://docs.customer.io/journeys/in-app-message-webhooks/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/in-app-message-webhooks/An in-app message is a message that targets a person currently using your app or website. In-app messages reach people after they open your app, helping you communicate with engaged members of your audience without bombarding them with notifications outside your app.  We have our own in-app solution! Check out our in-app documentation to learn more about sending in-app messages from Customer.io without a third party service. If you already use another service, you might use webhooks as a transitional solution while you migrate to Customer.https://docs.customer.io/journeys/transactional-push/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/transactional-push/Before you begin Before you can send transactional push notifications you need to: Enable Push Notifications in your workspace for Android and/or iOS. Set up your app to receive push notifications from Customer.io. We strongly recommend that you use our SDKs. If this isn’t an option, you can follow the instructions here to configure push without our SDKs. Create a transactional push notification  Try our Postman collection! You can use our Postman collection and associated environment to get started with the Customer.https://docs.customer.io/integrations/sdk/ios/3.x/push/rich-push/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/3.x/push/rich-push/1. Add a service extension to your project Add a Service App Extension to your project in Xcode. You should now see a new file added to your Xcode project. The file is probably named NotificationService and looks similar to this. import UserNotifications class NotificationService: UNNotificationServiceExtension { override func didReceive( _ request: UNNotificationRequest, withContentHandler contentHandler: @escaping (UNNotificationContent) -> Void ) { } override func serviceExtensionTimeWillExpire() { } } 2. Update the service extension Modify your new NotificationService extension by selecting the push package you want to import and calling the appropriate Customer.https://docs.customer.io/journeys/transformer-url-parameters/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/transformer-url-parameters/You can define URL parameters in two ways: Across all messages in Workspace Settings For a single email made in Design Studio This article shows you how to add URL parameters to a single message made in Design Studio. If you set URL parameters in workspace settings and in a single message, we append all parameters to your links. One does not override the other, so make sure you don’t duplicate URL parameters across these locations.https://docs.customer.io/integrations/data-in/connections/forms/squarespace/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/forms/squarespace/How it works Squarespace is a website builder that lets you create websites and add forms to your site. This integration lets you identifyThe Customer.io operation that adds or updates a person. When you identify a person, Customer.io either adds a person if they don’t exist in your workspace, or updates them if they do. Before you identify someone (by their email address or an ID), you can track them anonymously.https://docs.customer.io/integrations/sdk/ios/getting-started/swift-six/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/getting-started/swift-six/General Swift 6 was introduced in 2024 with Xcode 16. It includes language updates focused on safer, more predictable code, including macro improvements, stronger C++ interoperability, and stronger data-race detection through Strict Concurrency. Strict Concurrency helps you catch concurrency issues at compile time by enforcing actor isolation, Sendable requirements, and safer async boundaries. Many iOS apps are still migrating to Swift 6, while others have already completed the transition and run Swift 6 in production.https://docs.customer.io/journeys/delivery-window/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/delivery-window/This video shows each of our delay options. Click to fast forward to the Time Window section. How to set up a time window Within your campaign workflow, the Time Window option will be available to drag and drop into your workflow builder from the sidebar. If there are already other items in your workflow you’ll need to choose where you want to place your Time Window. Then, you can customize when you’d like the user to advance to the next step in the workflow.https://docs.customer.io/integrations/sdk/expo/tracking/track-events/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/expo/tracking/track-events/Track an event The track method helps you send events representing your audience’s activities to Customer.io. When you send events, you can include event properties—information about the person or the event that they performed. In Customer.io, you can use events to trigger campaigns and broadcasts. Those campaigns might send someone a push notification or manipulate information associated with the person in your workspace. Events include the following: name: the name of the event.https://docs.customer.io/journeys/deliverability-getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/deliverability-getting-started/What is a sender identity? Your sending identity, sometimes called a sender “fingerprint,” is comprised of: Sending domain Sending IP Other non-public fingerprints Every inbox provider tracks your sender identity differently. The goal of establishing sender fingerprints is to properly identify senders and calibrate their reputation and anti-spam systems based on historical behavior and performance. When you move to a new sending platform, some aspects of your sender identity will change.https://docs.customer.io/journeys/send-inbox-txnl/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/send-inbox-txnl/How it works You can leverage our transactional messaging feature to send inbox messages immediately from your backend without triggering a campaign or broadcast. This gives you a way to send one-to-one messages using Customer.io without having your message-sending logic inside Customer.io. flowchart LR a{Did user perform behavior that triggers an inbox message?} a-->|yes|b(Trigger inbox_message) a-.....->|no|c(Message not sent) b-->d{Is the recipient on your website or app?} d-->|no, wait for user to returnhttps://docs.customer.io/integrations/data-in/connections/forms/typeform/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/forms/typeform/How it works When you set up a Typeform integration, we’ll give you a personalized Webhook URL. You’ll provide this webhook URL to Typeform. Whenever someone submits your form, Typeform sends the form submission data to Customer.io. The form submission creates a person in your workspace if they do not already exist, or updates them if they do. In both cases, we map form fields to attributes for each person.https://docs.customer.io/integrations/data-in/connections/forms/unbounce/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/forms/unbounce/How it works Unbounce is a website builder that lets you create websites and add forms to your site. This integration lets you identifyThe Customer.io operation that adds or updates a person. When you identify a person, Customer.io either adds a person if they don’t exist in your workspace, or updates them if they do. Before you identify someone (by their email address or an ID), you can track them anonymously.https://docs.customer.io/journeys/code-editor-mso/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/code-editor-mso/Add conditional logic for Outlook You can add conditional logic that’s only parsed by Outlook through MSO comments. Syntax highlighting We visually distinguish MSO comments from regular comments to help you scan your email. For example, the following comment: <!--[if true]> <table role="presentation" width="100%" align="center" style="background:#EEE"> <tr> <td></td> <td style="width:600px;background:#ffffff;padding:24px;"> <![endif]--> becomes Disable syntax highlighting You can disable syntax highlighting for MSO comments in your editor preferences. Click Cmd/Ctrl + , then turn off the toggle.https://docs.customer.io/journeys/use-your-smtp-server/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/use-your-smtp-server/Upsides to doing this You’re in full control. You can send as many emails as you want: emails sent through your custom SMTP server don’t count against your billing plan’s allotted email count. We’ll still handle your open and click tracking. We’ll keep a full copy of your sent emails associated with the recipient. Downsides to doing this Customer.io won’t have a feedback loop for data from your email service provider.https://docs.customer.io/integrations/data-in/connections/webhooks/zapier-legacy-api/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/webhooks/zapier-legacy-api/Each Zap has one app as the Trigger, where your information comes from and which causes one or more Actions in other apps, where your data gets sent automatically. What Customer.io Actions and Triggers are Supported? Supported Actions Create or Update Customer - Creates a new customer. If the customer already exists, it will be updated. Create Event - Creates an event for a specific customer. Create Anonymous Event - Creates an event for an anonymous profile.https://docs.customer.io/integrations/data-in/semantic-events/video/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/semantic-events/video/How it works Video events help you observe and report how customers engage with your videos and ad content. Using the specification outlined on this page will help you take advantage of out-of-the-box actions for integrations that rely on video playback events. See Video Playback Events if you want to download the specification or try out video playback events. Playback events occur in three areas: Video: this represents the complete movie, program, or video that a person watches.https://docs.customer.io/integrations/data-in/connections/forms/webflow/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/forms/webflow/How it works Webflow is a website builder that lets you create websites and add forms to your site. This integration lets you identifyThe Customer.io operation that adds or updates a person. When you identify a person, Customer.io either adds a person if they don’t exist in your workspace, or updates them if they do. Before you identify someone (by their email address or an ID), you can track them anonymously.https://docs.customer.io/integrations/data-in/connections/forms/wordpress-with-wpforms/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/forms/wordpress-with-wpforms/How it works This integration lets you identifyThe Customer.io operation that adds or updates a person. When you identify a person, Customer.io either adds a person if they don’t exist in your workspace, or updates them if they do. Before you identify someone (by their email address or an ID), you can track them anonymously., update, and trigger events for people who submit your forms on your Wordpress site using the WPForms plugin.https://docs.customer.io/journeys/anonymous-in-app/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/anonymous-in-app/How it works With anonymous in-app messages, you can show messages to people who visit your website or use your app but haven’t been identified—people who haven’t logged in, provided their email address, and so on. These messages specifically exclude people you’ve identified. You can determine the pages where your message will appear, and any unidentified people who visit the page will see your message! That way you can show visitors a banner, pop-up, or even present them with a survey to learn what brought them to your website.https://docs.customer.io/accounts-and-workspaces/sms-billing/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/accounts-and-workspaces/sms-billing/ This page is for accounts billed for SMS activity through Customer.io Most users currently have their own Twilio account and manage their phone numbers and bill directly with Twilio. If this is the case for your account, you should see Twilio’s billing information instead. How it works SMS billing is mostly concerned with message “segments,” where each segment is up to 160 characters—what you might sometimes see as a single chat bubble in traditional SMS applications.https://docs.customer.io/ai/content-analysis/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/ai/content-analysis/ Not seeing this AI feature? Make sure “Customer.io AI” is enabled in Privacy, Data, & AI settings. Reach out to an Account Admin if you can’t edit the toggle. How it works When you work on an email in your campaign, broadcast, or newsletter, you can click Analyze Email Content to review your email and highlight ways you can improve deliverability so your message gets to the audience you want to build relationships with.https://docs.customer.io/journeys/attributes/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/attributes/What are customer attributes? Customer attributes are data points about people in your audience: things like first_name, email or product_interests—any information that is important for your marketing workflows. Every attribute has a name and a value. The name is how you reference the attribute whenever you want to get or set the value. When you want to personalize messages with customer data or group people by shared characteristics, you’ll use the attribute name.https://docs.customer.io/journeys/tagging-campaigns/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/tagging-campaigns/Manage tags You can create, edit, and delete tags from Campaigns, Broadcasts, Transactional messages, Segments, and your Data Index. No matter where you create them, you can assign that tag to any other automation, segment, or attribute moving forward. However, you can only assign tags on individual campaigns, segments, etc. From landing pages Select the tags filter at the top of pages like Campaigns, Segments, etc. Click Manage. Here you can create, edit or delete tags and check their usage.https://docs.customer.io/accounts-and-workspaces/whatsapp-billing/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/accounts-and-workspaces/whatsapp-billing/Meta’s pricing Meta, WhatsApp’s parent company, charges for WhatsApp messaging on a per-message basis. Pricing varies by template category and the recipient’s country. They also offer volume-based pricing tiers. For example, a message based on a “utility” template to a recipient in the United States costs $0.0034 per message. See Meta’s WhatsApp pricing page for the full list of rates for templates, countries, and message volume tiers. Template categories include:https://docs.customer.io/journeys/liquid-recipes/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/liquid-recipes/You can find our available tags, keys, and filters in our Liquid syntax list, and you can learn more about how to use liquid in Personalize messages with liquid. Countdown to an event If your customers subscribe to an event—a webinar, they buy tickets to a movie or concert, etc—you can include a countdown to an event or specific date and time that your audience is interested in! The timer produces an animated GIF that counts down to the event.https://docs.customer.io/journeys/manual-segments/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/manual-segments/Create a manual segment You have the opportunity to create manual segments when you import people by CSV and import people from a database. Otherwise, you can create a manual segment first, and then add people to it later. Go to Segments. Click Create Segment. Enter a Name and Description for the segment. These help you find the segment—both in the list of segments, and when selecting the segment in a campaign, broadcast, etc.https://docs.customer.io/accounts-and-workspaces/ai-credits/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/accounts-and-workspaces/ai-credits/How it works AI credits are the units that LLM actions consume when the action calls a Large Language Model (LLM). Each time a person uses an LLM action in your campaign, the LLM runs and uses credits based on the model and complexity of the request.  AI credits only apply to LLM actions Only LLM actions consume AI credits in your account. Other AI features—including the Agent, segment builder, content analysis, and in-app message suggestions—don’t use AI credits.https://docs.customer.io/journeys/device-segments/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/device-segments/How it works A person can have multiple devices. Each device has its own attributesA key-value pair that you associate with a person or an object—like a person’s name, the date they were created in your workspace, or a company’s billing date etc. Use attributes to target people and personalize messages.. You can use these attributes to create a segment of people whose devices match your criteria. Remember that your segment matches people.https://docs.customer.io/journeys/transformer-css-cleanup/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/transformer-css-cleanup/Remove unused CSS Enable this transformer and we’ll automatically find embedded CSS classes or ids that aren’t in use and remove them. This only affects selectors with at least one class or id. If the selector only has attributes and tags (i.e. a[x-apple-data-detectors]), it will not be affected. In this code, the class i-never-get-used will be removed since no HTML tags use that particular class. <html> <head> <style> .i-am-used { background: blue; } .https://docs.customer.io/integrations/data-in/connections/forms/javascript-form-integrations/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/forms/javascript-form-integrations/How it works When someone submits your form, we’ll identifyThe Customer.io operation that adds or updates a person. When you identify a person, Customer.io either adds a person if they don’t exist in your workspace, or updates them if they do. Before you identify someone (by their email address or an ID), you can track them anonymously. the form submitter and assign them attributesA key-value pair that you associate with a person or an object—like a person’s name, the date they were created in your workspace, or a company’s billing date etc.https://docs.customer.io/journeys/disconnect-from-automation/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/disconnect-from-automation/You can also duplicate the message to use it in another automation. Disconnect message from an automation To disconnect a Design Studio message from a campaign or API-triggered broadcast, delete the email block from your workflow. To disconnect a Design Studio message from a newsletter or transactional message, you can either switch to another message type (then back to “Email” if you want a different email connected) or delete the automation and start over.https://docs.customer.io/journeys/authentication/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/authentication/Why we require domain authentication Creating great copy means nothing if your messages don’t make it to the People you’re trying to reach. Although it’s just one piece of the deliverability puzzle (along with your copy and overall reputation), authenticating your email domains helps your messages reach your users. Check out our post on Email Deliverability to know more about how it works. In addition to improving email deliverability, authenticating your sending domains in Customer.https://docs.customer.io/journeys/goals/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/goals/How it works From the Goals page, you can define a business outcome—like starting a paid plan or completing onboarding—and attribute campaignsCampaigns are automated workflows you set up to send people messages and perform other actions when they meet your criteria. and broadcastsA message sent to a group of people at the same time. Unlike campaigns, where individuals can enter campaigns and receive messages on their own time, you’ll trigger a broadcast for everybody meeting your criteria at once.https://docs.customer.io/journeys/subscription-center-translation/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/subscription-center-translation/To translate custom copy on your subscription preferences page, like topics and a custom header and headline, you first need to add a topic and, optionally, customize your heading. You can localize your subscription preferences page before and after enabling your subscription center. We currently support 29 languages. Please let us know if you need support for another one! Factors that influence how translations render for your audience The following factors influence which languages your users will see on their subscription preferences page in this order:https://docs.customer.io/journeys/js-in-actions/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/js-in-actions/How it works In our Create Event and Create or Update Person actions, you can select the JavaScript option to return a specific value from your Trigger data. JavaScript might be easier to use than Liquid when you want to modify incoming JSON. If you use the JSON editor in the JavaScript mode, you can return an object representing the data object for your event. These are properties you can reference in messages or other campaigns using liquidA syntax that supports variables, letting you personalize messages for your audience.https://docs.customer.io/journeys/relationships/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/relationships/Create relationships between objects and people to segment users based on the groups they belong to and to personalize messages with object data. You can create and remove relationships between objects and people through: object and people pages in the UI our Track API our web sdk reverse ETL integrations our Segment integration While you can relate objects to people, you can’t relate objects to objects. If this is functionality you need, please share your use case with us.https://docs.customer.io/journeys/set-journey-attributes/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/set-journey-attributes/Unlike customer attributes, journey attributes don’t persist on a person’s profile—they automatically expire when the person exits the campaign. This keeps your workspace data clean while still letting you use data for personalization, conditions, and branching within a workflow. How it works You can set journey attributes in three ways: Method Use case Set journey attributes action Set values directly based on profile attributes, trigger data, liquid, or JavaScript. For instance, you might do this to temporarily store a discount code while a person is actively in a campaign.https://docs.customer.io/journeys/delete-domain/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/delete-domain/Go to Workspace Settings > Email. Click Show Records to the right of the domain you want to delete. Click Delete domain. Confirm your action. The domain will no longer appear in settings and the corresponding From addresses will not be available for emails. Remove a domain from messages If any email uses the From address for the domain you want to delete, you won’t be able to delete the domain.https://docs.customer.io/integrations/data-out/actions/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/actions/Here’s a quick demonstration showing how actions work and how easy it is to change data structures to fit your needs. How it works Customer.io knows how to use the data you send in identify calls and track events. But your outbound integrations don’t all work the same way Customer.io does! So we have to reshape the data you send to Customer.io to fit the kinds of requests and data your outgoing integration expects.https://docs.customer.io/integrations/data-out/action-trigger-syntax/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/action-trigger-syntax/How it works On any action, click Code mode to see the FQL trigger for that action. You can set or edit the trigger conditions to determine when we send data to your integration. This can be especially helpful if you need to set up complex trigger logic with nested and/or conditions—which you can’t do with the simple visual editor. Standard view Code mode You’ll apply criteria that evaluates to true or false based on the contents of incoming requests.https://docs.customer.io/integrations/data-in/importing-old-data/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/importing-old-data/Backfill people and attributes You can backfill people and their attributesA key-value pair that you associate with a person or an object—like a person’s name, the date they were created in your workspace, or a company’s billing date etc. Use attributes to target people and personalize messages. in your Customer.io account through our integrations or manually in your workspace. You might do this to store all your data within Customer.io so you can create segmentsA segment is a group of people in your workspace.https://docs.customer.io/journeys/sending-behavior/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/sending-behavior/Defaults In campaigns and API-triggered broadcasts, messages are set to queue, not send automatically. All campaigns and API-triggerd broadcasts have the setting “Track opens and link clicks” on. Messages inherit a campaign or broadcast’s subscription preference setting. You can, however, override this setting on each message. If you use our global unsubscribe functionality (this is our out-of-the-box option), we send to all subscribed by default. If you use our subscription center, you must choose to send to people subscribed to a specific topic or all subscribed AND unsubscribed.https://docs.customer.io/integrations/data-in/connections/hubspot/filter-incoming-data/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/hubspot/filter-incoming-data/How it works When you sync data from an integration like HubSpot to Customer.io, we re-shape it to match Customer.io’s data model through Actions. By default, your Journeys Workspace Actions are set up to process and use all of the data you sync to Customer.io. This works for most integrations. But what do you do if you want to filter out certain requests from HubSpot? You’d create a new Customer.io Journeys (Workspace) instance to handle data from these integrations independently from default settings!https://docs.customer.io/integrations/data-in/proxying-requests/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/proxying-requests/Proxying requests through your backend server lets you keep your Customer.io credentials secure while maintaining control over data collection. Instead of sending data directly from client applications to Customer.io, your SDKs send data to a server you control, which then forwards the requests to Customer.io. Why proxy requests? There are several reasons you might want to proxy requests through your backend: Security: Keep your Customer.io credentials secure on your backend instead of embedding them in client applications.https://docs.customer.io/get-started/create-workspace/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/get-started/create-workspace/Create your account and workspace After you create your account, you’ll follow the on-screen steps to make a workspace. If you’re new to Customer.io, we encourage you to use the default settings. They support most use cases and you can change them later! When you create your account, you’re considered an administrator. You can add other users to your account and determine their roles within your account and workspaces. Adding additional workspaces You can always set up extra workspaces when you go to Settings > Account-settings > Workspaces and click Add Workspace.https://docs.customer.io/integrations/sdk/expo/whats-new/2.x-upgrade/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/expo/whats-new/2.x-upgrade/What changed? While this represents a significant change “under the hood,” we’ve tried to make it as seamless as possible for you; much of your implementation remains the same. This move also adds two additional features: Support for anonymous tracking: you can send events and other activity for anonymous users, and we’ll reconcile that activity with a person when you identify them. Built-in lifecycle events: the SDK now automatically captures events like “Application Installed” and “Application Updated” for you.https://docs.customer.io/get-started/set-up-messages/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/get-started/set-up-messages/Before you begin Before you can send messages, you need to configure the types of messages you want to send. If your workspace is new, you can follow the onscreen setup guide, but you can always add channels later under ** Settings > Workspace settings. Some message channels take more time and effort to set up than others. Most require access to resources outside of Customer.io. You might need to work with your development team or other teams in your organization to set up your message channels.https://docs.customer.io/integrations/sdk/ios/3.x/whats-new/3.x-upgrade/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/3.x/whats-new/3.x-upgrade/What changed? This update provides native support for our new integrations framework. While this represents a significant change “under the hood,” we’ve tried to make it as seamless as possible for you; much of your implementation remains the same. This move also adds two additional features: Support for anonymous tracking: you can send events and other activity for anonymous users, and we’ll reconcile that activity with a person when you identify them.https://docs.customer.io/get-started/integrate/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/get-started/integrate/How it works While you can add people manually or upload CSVs, you’ll get the most out of Customer.io when you integrate with us, adding people and tracking the events they perform programmatically. You can integrate different data sources with Customer.io—your website, mobile apps, databases, and so on. flowchart LR d{Where does your data come from?} d-->|Website|a d--->|Mobile App|f(Integrate with a mobile SDK) d--->|Database or Data Warehouse|g(Reverse ETL Integration) a{Will you sendhttps://docs.customer.io/integrations/sdk/react-native/4.x/whats-new/4.x-upgrade/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/4.x/whats-new/4.x-upgrade/What changed? This update provides native support for our new integrations framework. While this represents a significant change “under the hood,” we’ve tried to make it as seamless as possible for you; much of your implementation remains the same. This move also adds two additional features: Support for anonymous tracking: you can send events and other activity for anonymous users, and we’ll reconcile that activity with a person when you identify them.https://docs.customer.io/integrations/sdk/react-native/5.x/whats-new/4.x-upgrade/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/5.x/whats-new/4.x-upgrade/What changed? This update provides native support for our new integrations framework. While this represents a significant change “under the hood,” we’ve tried to make it as seamless as possible for you; much of your implementation remains the same. This move also adds two additional features: Support for anonymous tracking: you can send events and other activity for anonymous users, and we’ll reconcile that activity with a person when you identify them.https://docs.customer.io/integrations/sdk/react-native/whats-new/4.x-upgrade/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/whats-new/4.x-upgrade/What changed? This update provides native support for our new integrations framework. While this represents a significant change “under the hood,” we’ve tried to make it as seamless as possible for you; much of your implementation remains the same. This move also adds two additional features: Support for anonymous tracking: you can send events and other activity for anonymous users, and we’ll reconcile that activity with a person when you identify them.https://docs.customer.io/integrations/sdk/ios/whats-new/3.13.0-upgrade/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/whats-new/3.13.0-upgrade/What changed? The changes are mainly to align our SDK APIs across different platforms. No functional changes to be expected. Upgrade process Attributes profileAttributes property is deprecated Getter has no replacement, the mobile SDK doesn’t expose the user’s profile attributes Setter is replaced with setProfileAttributes(attributes: [String: Any]) deviceAttributes property is deprecated Getter has no replacement, the mobile SDK doesn’t expose the user’s device attributes Setter is replaced with setDeviceAttributes(attributes: [String: Any]) Tracking Identifying a userhttps://docs.customer.io/integrations/sdk/android/whats-new/4.x-upgrade/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/android/whats-new/4.x-upgrade/What changed? This update provides native support for our new integrations framework. While this represents a significant change “under the hood,” we’ve tried to make it as seamless as possible for you; much of your implementation remains the same. This move also adds two additional features: Support for anonymous tracking: you can send events and other activity for anonymous users, and we’ll reconcile that activity with a person when you identify them.https://docs.customer.io/get-started/add-people/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/get-started/add-people/How it works Customer.io Journeys revolve around your audience of people. And the data you store in your workspace typically represents people and the things they do. To really take advantage of Journeys, you’ll add people and their events to Customer.io. Because we represent people with data, a “person” consists of a few things—all of which you can use to group people into segmentsA segment is a group of people in your workspace.https://docs.customer.io/get-started/segments-and-people-data/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/get-started/segments-and-people-data/How it works People have data associated with them—the attributesA key-value pair that you associate with a person or an object—like a person’s name, the date they were created in your workspace, or a company’s billing date etc. Use attributes to target people and personalize messages. you know about them and the eventsSomething that a person in your workspace did. Events can trigger campaigns, add people to segments, etc, and you can use properties from events to personalize messages.https://docs.customer.io/get-started/send-messages/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/get-started/send-messages/ Want to send your first message right away? Check out our quick start guide to send your first message and jump right in. How it works A message is what you want to send. But before you send a message, you have to determine who to send your message to and when to send it. You answer these questions when you set up a campaign, broadcast, newsletter, or transactional message.https://docs.customer.io/journeys/ad-audiences-sync/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/ad-audiences-sync/What are Ad Audiences? In Ad Networks, such as Google, Facebook, and Instagram Ads, you can target your advertising in several ways. One way is to import a list of known users (“known” meaning you have some personally identifiable information on them - such as an email address) and use that list for targeting. Now, you can programmatically send your Customer.io segments into Ad Networks as audiences. This eliminates the historically manual process of importing custom lists - as well as ensure parity in the people you reach in Customer.https://docs.customer.io/integrations/data-out/data-warehouses/data-warehouses-cdp/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/data-warehouses/data-warehouses-cdp/ Want information from your workspace, including campaign journeys? Try our standard Data Warehouse integration to get data from your workspace, including campaign journeys. How it works This integration forwards incoming data from data sources to your storage bucket independently of your workspace. This means that you can send data to your storage bucket even if you don’t store that data in Customer.io. It also means that this integration does not have access to campaign, broadcast, or journey information from your workspace.https://docs.customer.io/journeys/archiving-layouts/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/archiving-layouts/We don’t let you delete Layouts that you’re using in active campaigns or newsletters. But what if you don’t want to use that Layout anymore going forward? Simple: archive it! How to archive Archiving a Layout is simple. When you hover over that Layout in the Layouts menu, you’ll see a button to archive. The option will also be available on the individual Layout’s page. …and how to unarchive If you’d like to use the Layout in emails once more, head over to the ‘Archived’ tag, find the Layout you’d like to use again, and Unarchive it either from the Layouts listing, or the individual page:https://docs.customer.io/journeys/awareness-announce-events/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/awareness-announce-events/Business-to-business (B2B) companies often need to track and drive growth across both individual users of their product and non-people entities like the company they work for or webinars they want to attend. In Customer.io, objectsAn object is a non-person entity that you can associate with one or more people—like a company, account, or online course. help you do this. For this recipe, imagine you work at a design platform, Sketcher.io, which offers graphic design and product design tools.https://docs.customer.io/journeys/campaign-metrics/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/campaign-metrics/This page focuses on your Campaign Metrics, which provides a complete overview of the journeyTypically, a person’s path through your campaign. If the campaign is triggered by a webhook, then a journey captures the webhook’s path, not a person’s. and messageThe instance of a message sent to a person. When you set up a message, you determine an audience for your message. Each individual “send”—the version of a message sent to a single member of your audience—is a delivery.https://docs.customer.io/journeys/transformer-css-variables/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/transformer-css-variables/CSS variables (also known as CSS custom properties) help you define reusable styles and reduce duplication across your stylesheets. However, most email clients don’t support them. The CSS Variables transformer solves this by inserting the values of the variables. Statically insert :root CSS variables Enable this transformer to convert your CSS variables into styles that are compatible with more email clients.  Define CSS variables on the :root element in a <style> taghttps://docs.customer.io/journeys/domain-warming/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/domain-warming/ Automate your warm-up with Daily ramp for newsletters! If you use newsletters to warm up your sending domain, add a rate limit and set a daily ramp period to get your system up and running. This eliminates the need to create multiple newsletters or messages for your warm-up schedule! Overview Think of warming up your domain like introducing yourself to email providers (like Gmail, Yahoo, etc.) and saying, “Hi, I’m trustworthy and send relevant, valuable emails.https://docs.customer.io/accounts-and-workspaces/editing-account-information/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/accounts-and-workspaces/editing-account-information/ To edit this information, you must be an Account Admin or Member with the account-level permission, “Access billing & account info.” All of these items can be edited in your Account Information. Uploading a logo In your Account Settings, click Edit Account Information. Under Basic information, you can add, replace, or delete a logo: Please note that the file must be more than 200x200 pixels. The logo image will be automatically cropped to a square.https://docs.customer.io/integrations/data-in/connections/forms/facebook-lead-ads/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/forms/facebook-lead-ads/Overview To set up a Facebook lead ads integration, you connect a page in your Facebook business account to Customer.io, activate the forms you want to capture leads from, and map fields from your forms to attributes. When a person fills out your Facebook lead ad, Customer.io receives a form_submit event containing the Facebook lead form ID, the form name, and values representing the form submission. This form_submit event adds a person to, or updates a person in, your workspace.https://docs.customer.io/integrations/data-out/action-mapping/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/action-mapping/How it works Each data-out integration has a list of available actions. An action is how we map incoming data to your outgoing integration. In most cases, the defaults are all you’ll ever need. But you might want to add additional action filters or change the values we map to various events to change when we send data out or to fine-tune the data that we send with each action.https://docs.customer.io/journeys/how-to-use-attribute-updates-to-fix-typos-in-your-data/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/how-to-use-attribute-updates-to-fix-typos-in-your-data/In this example, let’s say you have an attribute called frist_name that should be first_name instead. 1. Create a segment to capture the misspelled attribute Create a new segment that captures people with the misspelled attribute. In this case, we’re looking for people with a frist_name attribute. 2. Create a campaign using your segment Use that segment as the trigger condition in a new campaign. If misspelled data is still coming into your workspace, make sure that your campaign is re-enterable, so that you fix the typo whenever it reoccurs.https://docs.customer.io/integrations/data-in/source-spec/group-spec/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/source-spec/group-spec/ See our API documentation for code samples This page can help you better understand when and how to use this API method. But, if you already know how it works and are ready to get started, you can go straight to our API documentation and start writing code. How it works The group method is how you’ll associate a person with a group, like the company they work for or the school they attend.https://docs.customer.io/journeys/import-objects/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/import-objects/How it works You can upload CSVs or Google Sheets to add or update objects and relationships outside your normal integration path. When you upload a CSV of objects, each row in your CSV represents an object, and each column represents an object attribute. When you upload a CSV of relationships, each row is a relationship between an object and person, and each column (besides object_type_id, object_id, and the identifier of the person) is an attribute on the relationship.https://docs.customer.io/ai/in-app-suggestions/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/ai/in-app-suggestions/ Not seeing this AI feature? Make sure “Customer.io AI” is enabled in Privacy, Data, & AI settings. Reach out to an Account Admin if you can’t edit the toggle. How it works When you drag an in-app message into your campaign and click it, you’ll see a section that says Add Content. Just below that, you’ll see Suggested with AI. Here we’ll provide some starter messages based on your campaign and message objectives.https://docs.customer.io/ai/in-app-survey-analysis/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/ai/in-app-survey-analysis/ Not seeing this AI feature? Make sure “Customer.io AI” is enabled in Privacy, Data, & AI settings. Reach out to an Account Admin if you can’t edit the toggle. How it works When you create an in-app survey, you’ll add buttons with Tracked Name parameters. When someone interacts with the button, you’ll see the results in Tracked Responses on the Metrics tab of your campaign or API-triggered broadcast. The Analyze Survey feature observes the responses to your survey (or any set of in-app messages with multiple buttons) and provides you with insights based on responses to your messages.https://docs.customer.io/journeys/inbox-metrics/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/inbox-metrics/Inbox messages follow a similar delivery patterns as regular in-app messages. This means that messages are sent but not displayed until the recipient returns to your website or app. The major difference is that inbox messages aren’t “delivered” in the traditional sense. Rather, you’ll fetch and display messages to your audience when they open your notification inbox. When you mark a message as opened, we’ll report that it’s delivered as well.https://docs.customer.io/journeys/inline-in-app/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/inline-in-app/How it works Unlike traditional in-app messages, which appear on top of your app or website, inline in-app messages act like a part of the content on your page. They let you dynamically populate parts of your app and talk to your customers without interrupting their experience. To support inline messages, you need to add empty elements to your website or views to your app to contain your inline messages. Then, when you send an inline message, you’ll specify the Position ID of the for your inline message—the empty element or view where you want to display your message.https://docs.customer.io/journeys/2-email-basics/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/2-email-basics/ Check out Design Studio! Design Studio is our newest, most flexible email editor. Use components to create a block-based email from scratch, and set global styles to create a consistent brand across your messages made in Design Studio. No longer do you have to decide between a visual or code-based editor; you can use both! Writing your message You can use one of four editors to create your email copy: Design Studio, drag-and-drop, rich text, or code.https://docs.customer.io/integrations/data-in/connections/servers/rails-customerio/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/servers/rails-customerio/Add the customer.io gem to your Gemfile gem 'customerio', :git => 'https://github.com/customerio/customerio-ruby' Run bundle install to install the gem then we’ll set up the configuration. Configuration We’ll add your Customer.io Site ID and API Key. We can do this in an initializer to save time and make sure we don’t accidentally commit sensitive data into source control. config/initializers/customerio.rb Rails.configuration.customerio = { :site_id => ENV['CIO_SITE_ID'], :api_key => ENV['CIO_API_KEY'] } $customerio = Customerio::Client.https://docs.customer.io/journeys/managing-customer-mobile-devices/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/managing-customer-mobile-devices/You’ll find a person’s devices by going to the People page, selecting a person, and going to their Devices tab. For each device, we show the device platform platform, token, and when the device was “last used”. Last used indicates the last time you identified a device—something you typically do when someone logs into your app, or opens your app and is already logged in! You can hover over the truncated token to see the full string and copy it to your clipboard.https://docs.customer.io/integrations/data-in/connections/javascript/js-source-identities/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/javascript/js-source-identities/How it works Our JavaScript client manages the identities of your audience, first as an anonymousId. Then, when you identify them, you know them by their userId. Then we remove those values when a person logs out and you call cioanalytics.reset();. We store user identity information in cookies and local storage. You can retrieve or override this information as necessary to support your integrations. This page provides information about the values we store, where we store them, and how to get or override them.https://docs.customer.io/journeys/migrate-subscription-prefs/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/migrate-subscription-prefs/ These steps will not affect your audience’s global subscription status This page is about migrating subscription preferences—the topics and channels a person wants (or does not want) to receive messages for. These steps will not affect your audience’s unsubscribed attribute—which indicates whether a person has opted out of messages. How it works If you used to manage subscription preferences outside our subscription center feature, or you set up new “opt-in” topics or channels, you’ll want to apply people’s current preferences to the cio_subscription_preferences attribute.https://docs.customer.io/journeys/multi-split/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/multi-split/How it works A multi-split branch sends people down different paths based on one or more conditions: Profile attributes Segment membership Events objectAn object is a non-person entity that you can associate with one or more people—like a company, account, or online course. attributes relationshipThe connection between an object and a person in your workspace. For instance, if you have Account objects, people could have relationships to an Account if they’re admins.https://docs.customer.io/journeys/multi-step/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/multi-step/How it works You can add multiple steps to your in-app message, where users progress through each step as they interact with your message—click a button; go to the next step within the in-app message. You might do this to walk new users through an onboarding flow, showcase new features in your app, immediately respond to surveys, and so on. Each step has its own settings including display, position, and content.https://docs.customer.io/integrations/data-in/source-spec/page-spec/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/source-spec/page-spec/How it works The page method represents pageviews. It helps you record the pages that people visit on your website. By recording page events, you can better understand the parts of your website that people use. You might even follow up with people who’ve visited particular pages to see if they’re still interested in a product, online class, and so on. Our JavaScript client automatically captures page events on load, but you’ll need to invoke page calls manually if you use our server-side libraries, you have a single page app, or you want to augment the call with special properties.https://docs.customer.io/integrations/sdk/android/in-app/target-in-app-messages/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/android/in-app/target-in-app-messages/You can set page rules when you create in-app messages. These rules determine the pages that your audience must visit in your app to see each message. Before you can take advantage of page rules, you need to: Track screens in your app. You can add autoTrackActivityScreens(true) to your CustomerIO configuration to automatically track screens or you can track screens manually. If you use Jetpack Compose you should turn off automatic screen tracking and track screens manually.https://docs.customer.io/integrations/sdk/ios/3.x/in-app/target-in-app-messages/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/3.x/in-app/target-in-app-messages/You can set page rules when you create in-app messages. These rules determine the pages that your audience must visit in your app to see each message. Before you can take advantage of page rules, you need to: Track screens in your app. You can add $0.autoTrackScreenViews = true to your CustomerIO.config to automatically track screens or you can track screens manually. Provide page names to whomever sets up in-app messages in fly.https://docs.customer.io/integrations/sdk/ios/in-app/target-in-app-messages/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/in-app/target-in-app-messages/You can set page rules when you create in-app messages. These rules determine the pages that your audience must visit in your app to see each message. Before you can take advantage of page rules, you need to: Track screens in your app. You can add $0.autoTrackScreenViews = true to your CustomerIO.config to automatically track screens or you can track screens manually. Provide page names to whomever sets up in-app messages in fly.https://docs.customer.io/journeys/previewing-broadcast-data/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/previewing-broadcast-data/How it works When you trigger a broadcast, you can provide additional data in your trigger that you can use to personalize your broadcast with liquidA syntax that supports variables, letting you personalize messages for your audience. For example, if you want to reference a person’s first name, you might use the variable {{customer.first_name}}.. This is very similar to the way you’d personalize event-triggered campaigns. But, in this case, you’ll reference your data using {{trigger.https://docs.customer.io/journeys/random-cohort/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/random-cohort/How it works A Random Cohort action randomly distributes people across up to 20 different paths in your workflow. It provides a way to test different messages or actions in a campaign. If you use custom objectsAn object is a non-person entity that you can associate with one or more people—like a company, account, or online course. in your workspace, pay attention to the Cohort by setting. By default, we add people to random cohorts.https://docs.customer.io/accounts-and-workspaces/reduce-billing-overages/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/accounts-and-workspaces/reduce-billing-overages/You should develop a cadence to delete unnecessary people and objects from your account to reduce overages and keep your billing predictable. Regularly deleting unused or defunct profiles can help you control your costs. This is probably something you should do monthly or every few months, rather than once or twice a year! 1. Review your integrations Overall, we recommend you review your integrations and ensure that you only add people and objects that provide value to your company/organization.https://docs.customer.io/journeys/snippets/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/snippets/Creating Snippets You can create snippets through our API or in the Customer.io UI. To simplify things, let’s create your first snippet in the UI. Go to Content > Snippets. Click Create New Snippet. Enter a Name and Value for the snippet. The liquid tag you’ll use to reference the snippet automatically updates as you enter name and value.  Avoid spaces in snippet names While snippet names can contain spaces, we recommend using underscores or hyphens to separate words, so they’re easier to use in messages and less prone to errors.https://docs.customer.io/integrations/data-in/source-spec/screen-spec/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/source-spec/screen-spec/How it works The screen method represents screenviews in your mobile apps—like a page call, but specifically for apps. It helps you record the screens that people visit as they use your app. By recording screen events, you can better understand the parts of your app that people use. You might even follow up with people who’ve visited particular screens to see if they’re still interested in a product, need help with something, and so on.https://docs.customer.io/integrations/sdk/expo/tracking/screen-events/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/expo/tracking/screen-events/Screen views are events that record the pages that your audience visits in your app. They have a type property set to screen, and a name representing the title of the screen or page that a person visited in your app. Screen view events let you trigger campaignsCampaigns are automated workflows you set up to send people messages and perform other actions when they meet your criteria. or add people to segmentsA group of people who match a series of conditions.https://docs.customer.io/integrations/sdk/flutter/2.x/tracking/screen-events/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/flutter/2.x/tracking/screen-events/Screen views are events that record the pages that your audience visits in your app. They have a type property set to screen, and a title representing the title of the screen or page that a person visited in your app. Screen view events let you trigger campaignsCampaigns are automated workflows you set up to send people messages and perform other actions when they meet your criteria. or add people to segmentsA group of people who match a series of conditions.https://docs.customer.io/integrations/sdk/flutter/tracking/screen-events/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/flutter/tracking/screen-events/Screen views are events that record the pages that your audience visits in your app. They have a type property set to screen, and a title representing the title of the screen or page that a person visited in your app. Screen view events let you trigger campaignsCampaigns are automated workflows you set up to send people messages and perform other actions when they meet your criteria. or add people to segmentsA group of people who match a series of conditions.https://docs.customer.io/journeys/sender-phone-numbers/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/sender-phone-numbers/Syncing Phone Numbers (Senders) to Customer.io If you add or change any of your sender identities in your Twilio account, you’ll need to re-sync them in Customer.io before you’ll see your changes in Customer.io. Go to > Workspace Settings > SMS and click Sync from Twilio. Using a Manual Sender ID You’ll see Manual Sender IDs in your Twilio Settings. You can add an Alphanumeric Sender ID, a Message Service ID, or provide some Liquid that dynamically determines the Sender ID for each message here.https://docs.customer.io/journeys/queue-draft/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/queue-draft/How it works By default, we set messages to “Queue Draft.” This means we generate drafts, but don’t automatically send them to your audience. This is meant to be temporary; you should update your messages to “Send Automatically” when you’re confident your messages are ready to go. With “Queue Draft” you can see a campaign in action before you actually send messages to your audience. Queueing drafts allows your complex workflow to run - matching recipients, rendering content, and emulating the campaign’s behavior - without any content being sent.https://docs.customer.io/journeys/transactional-sms/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/transactional-sms/ New to transactional messaging? Check out our getting started section to learn more about transactional concepts and how our transactional API works. Before you begin Before you can send transactional SMS messages, you need to: Set up your Twilio account and enable SMS in your workspace. Get your app API key. This is the bearer token that you’ll use when you call the transactional API to trigger a message. We also recommend that you use different phone numbers for transactional and marketing SMS messages.https://docs.customer.io/journeys/in-app-surveys/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/in-app-surveys/How it works You can use our in-app feature to send a message with an arrangement of buttons to solicit feedback from your audience—for net promoter score (NPS), customer satisfaction (CSAT), and other kinds of microsurveys. We track the buttons that people click or tap in your messages, so you can see how your audience feels about your products, features, and so on. You can even use responses to follow-up with people based on their feedback.https://docs.customer.io/journeys/stripe-data-campaign/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/stripe-data-campaign/Customer.io is great for tracking leads and sending people messages. Stripe is great for managing customer and purchase data. With this process, you’ll capture Stripe’s customer.created event in Customer.io to represent people who have become customers. From here you might do things like thank people for making their first purchase or offer them coupons!  This process works for other Stripe events This tutorial is based on customer events, but after you sync customer data between Stripe and Customer.https://docs.customer.io/journeys/testing-emails/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/testing-emails/ Are you using Design Studio to create your email? You can send tests from both the email editor and the connected automation.  Are you on a trial? If you’re on a trial, you’re allowed a limited number of test emails per day. From any workflow (campaign, broadcast, or transactional message), you can send test messages to make sure your emails look right in your inbox. Select the email block, and then click Edit Content.https://docs.customer.io/journeys/new-in-app-editor/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/new-in-app-editor/ We’re actively developing this feature! This feature is new, and we’re continuing to improve on it. If you run into a problem or have feedback for us, please get in touch so that we can build the best possible feature for you! How it works Our in-app editor lets you drag-and-drop components like text, media, and buttons to build in-app-messages. You can style each component so that your message looks and feels like a part of your app or website.https://docs.customer.io/integrations/data-in/source-spec/track-spec/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/source-spec/track-spec/How it works The track method helps you record events: the things your users do on your site, in your app, and so on. Each track call records a single event. Each event has a name and properties. For example, if you send a track call when someone starts a video on your website, the name of the event might be Video Started, and the properties might include the title of the video, the length of the video, and so on.https://docs.customer.io/integrations/data-in/connections/javascript/legacy-js/events/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/javascript/legacy-js/events/How it works You can send events representing the things people do, and the pages people visit, on your website. The events that you capture with our web SDK can trigger campaigns and supplament user information. You can send events before you identify a person. We call these “anonymous” events. When you identify your web visitor, we’ll automatically associate anonymous events with the person you identify. flowchart LR a[anonymous personhttps://docs.customer.io/integrations/sdk/android/2.x/track-events/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/android/2.x/track-events/This page is part of a setup flow for the SDK. Before you continue, make sure you've implemented previous features—i.e. you can't send events before you identify people! graph LR getting-started(Install SDK) -->B(Initialize SDK) B --> identify(identify people) identify -.-> track-events(Send events) identify -.-> push(Receive push) identify -.-> rich-push(Receive Rich Push) track-events --> test-support(Write tests) push --> test-support rich-push --> test-support identify -.-> in-app(Receive in-app) in-app --> test-support click getting-started href "https://docs.customer.io/integrations/sdk/android/3.x/track-events/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/android/3.x/track-events/This page is part of a setup flow for the SDK. Before you continue, make sure you've implemented previous features—i.e. you can't send events before you identify people! graph LR getting-started(Install SDK) -->B(Initialize SDK) B --> identify(identify people) identify -.-> track-events(Send events) identify -.-> push(Receive push) identify -.-> rich-push(Receive Rich Push) track-events --> test-support(Write tests) push --> test-support rich-push --> test-support identify -.-> in-app(Receive in-app) in-app --> test-support click getting-started href "https://docs.customer.io/integrations/sdk/android/tracking/track-events/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/android/tracking/track-events/Track a custom event The track method helps you send events representing your audience’s activities to Customer.io. When you send events, you can include event properties—information about the person or the event that they performed. In Customer.io, you can use events to trigger campaigns and broadcasts. Those campaigns might send someone a push notification or manipulate information associated with the person in your workspace. Events include the following: name: the name of the event.https://docs.customer.io/integrations/sdk/expo/1.x/track-events/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/expo/1.x/track-events/This page is part of a setup flow for the SDK. Before you continue, make sure you've implemented previous features—i.e. you can't send events before you identify people! graph LR getting-started(Install SDK) -->B(Initialize SDK) B --> identify(identify people) identify -.-> track-events(Send events) identify -.-> push(Receive push) identify -.-> in-app(Receive in-app) click getting-started href "/integrations/sdk/expo/getting-started/#install" click B href "/integrations/sdk/expo/getting-started/#initialize-the-sdk" click identify href "/integrations/sdk/expo/identify" click track-events href "/integrations/sdk/expo/track-events/" click register-token href "https://docs.customer.io/integrations/sdk/flutter/1.x/track-events/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/flutter/1.x/track-events/This page is part of a setup flow for the SDK. Before you continue, make sure you've implemented previous features—i.e. you can't send events before you identify people! graph LR getting-started(Install SDK) -->B(Initialize SDK) B --> identify(identify people) identify -.-> track-events(Send events) identify -.-> push(Receive push) identify -.-> in-app(Receive in-app) click getting-started href "/integrations/sdk/flutter/getting-started/#install" click B href "/integrations/sdk/flutter/getting-started/#initialize-the-sdk" click identify href "/integrations/sdk/flutter/identify" click track-events href "/integrations/sdk/flutter/track-events/" click register-token href "https://docs.customer.io/integrations/sdk/flutter/2.x/tracking/track-events/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/flutter/2.x/tracking/track-events/Track an event The track method helps you send events representing your audience’s activities to Customer.io. When you send events, you can include event properties—information about the person or the event that they performed. In Customer.io, you can use events to trigger campaigns and broadcasts. Those campaigns might send someone a push notification or manipulate information associated with the person in your workspace. Events include the following: name (Required): The name of the event.https://docs.customer.io/integrations/sdk/flutter/tracking/track-events/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/flutter/tracking/track-events/Track an event The track method helps you send events representing your audience’s activities to Customer.io. When you send events, you can include event properties—information about the person or the event that they performed. In Customer.io, you can use events to trigger campaigns and broadcasts. Those campaigns might send someone a push notification or manipulate information associated with the person in your workspace. Events include the following: name (Required): The name of the event.https://docs.customer.io/integrations/sdk/ios/1.x/track-events/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/1.x/track-events/This page is part of a setup flow for the SDK. Before you continue, make sure you've implemented previous features—i.e. you can't send events before you identify people! graph LR getting-started(Install SDK) -->B(Initialize SDK) B --> identify(identify people) identify -.-> track-events(Send events) identify -.-> register-token(Register Device Token) register-token -.-> push(Receive push) register-token -.-> rich-push(Receive Rich Push) track-events --> test-support(Write tests) push --> test-support rich-push --> test-support identify -.-> in-app(Receive in-app) in-app --> test-support click getting-started href "https://docs.customer.io/integrations/sdk/ios/2.x/track-events/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/2.x/track-events/This page is part of a setup flow for the SDK. Before you continue, make sure you've implemented previous features—i.e. you can't send events before you identify people! graph LR getting-started(Install SDK) -->B(Initialize SDK) B --> identify(identify people) identify -.-> track-events(Send events) identify -.-> register-token(Register Device Token) register-token -.-> push(Receive push) register-token -.-> rich-push(Receive Rich Push) track-events --> test-support(Write tests) push --> test-support rich-push --> test-support identify -.-> in-app(Receive in-app) in-app --> test-support click getting-started href "https://docs.customer.io/integrations/sdk/react-native/2.x/track-events/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/2.x/track-events/This page is part of a setup flow for the SDK. Before you continue, make sure you've implemented previous features—i.e. you can't send events before you identify people! graph LR getting-started(Install SDK) -->B(Initialize SDK) B --> identify(identify people) identify -.-> track-events(Send events) identify -.-> push(Receive push) identify -.-> in-app(Receive in-app) click getting-started href "/integrations/sdk/react-native/getting-started/#install" click B href "/integrations/sdk/react-native/getting-started/#initialize-the-sdk" click identify href "/integrations/sdk/react-native/identify" click track-events href "/integrations/sdk/react-native/track-events/" click register-token href "https://docs.customer.io/integrations/sdk/react-native/3.x/track-events/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/3.x/track-events/This page is part of a setup flow for the SDK. Before you continue, make sure you've implemented previous features—i.e. you can't send events before you identify people! graph LR getting-started(Install SDK) -->B(Initialize SDK) B --> identify(identify people) identify -.-> track-events(Send events) identify -.-> push(Receive push) identify -.-> in-app(Receive in-app) click getting-started href "/integrations/sdk/react-native/getting-started/#install" click B href "/integrations/sdk/react-native/getting-started/#initialize-the-sdk" click identify href "/integrations/sdk/react-native/identify" click track-events href "/integrations/sdk/react-native/track-events/" click register-token href "https://docs.customer.io/journeys/universal-links/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/universal-links/ These instructions only apply to universal and app links in emails You can use universal links and app links in other message channels, but the manual tracking steps we describe in this article are only viable in emails. For in-app messages, our web and mobile SDKs automatically track links, but make sure your app is set up to resolve deep links. For push, use the Opened metric to track links, which is the push equivalent to Clicked.https://docs.customer.io/journeys/tracking-twilio-messages/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/tracking-twilio-messages/SMS/MMS delivery logs When you send an SMS or MMS message, you can view the delivery logs for that message in the campaign’s sent messages page. Here you can correct and retry failed messages. Message failures are sometimes related to problems with liquid in your message (missing attributes, etc). In delivery logs, you’ll see: The recipient The name of the message The status of the message (sent or failed) Date and time sent Conversions after receiving the message Create a segment based on SMS/MMS messages As with an email, you can create a segment for SMS’s that have been sent, converted, etc.https://docs.customer.io/journeys/transactional-api-examples/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/transactional-api-examples/Send an email using a transactional message template To send a message using a transactional message template, you need the following: transactional_message_id: This is found in the code examples when setting up a transactional message. It’s also the id listed in the URL of a transactional message. message_data: A list of data that you want to pass into your message using liquidA syntax that supports variables, letting you personalize messages for your audience.https://docs.customer.io/journeys/campaign-triggers/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/campaign-triggers/If you’re just getting started, we’ve created a quick video to help you understand what each campaign trigger does. To learn about object and relationship triggers, read on. How it works A campaign trigger determines who enters your campaign and when. You can set up filters to narrow your trigger criteria. People need to meet your trigger and filter criteria to enter your campaign. You can also set your exit conditions to make people exit your campaign when they quit matching your trigger and filter criteria, ensuring that your campaign is relevant to your audience.https://docs.customer.io/integrations/getting-started/troubleshooting/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/getting-started/troubleshooting/This page helps you check the various areas of your pipeline to find and solve problems. General troubleshooting tips Check your Data & Integrations > Integrations page to determine if an integration has a problem. You can hover over each integration to see if we’ve noticed a problem. Check your incoming integration’s Data In tab: are you sending the right calls to Customer.io? Check your outgoing integration’s Data Out tab: are you sending data to its ultimate destination?https://docs.customer.io/journeys/true-false/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/true-false/How it works A true/false branch sends your audience down different paths based on conditions. Customers matching the conditions go down one path; customers who don’t match the conditions go down the other. You can create a true/false branch based on: profile attributes segment membership events messages (like if a certain email has ever been clicked) objectAn object is a non-person entity that you can associate with one or more people—like a company, account, or online course.https://docs.customer.io/journeys/multiple-smtp-servers/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/multiple-smtp-servers/Getting started First, you need to configure your primary custom SMTP server. By default, all your emails will send from your first SMTP server, but you can change this as you add new servers. You can configure up to six servers. Customizing campaign delivery To customize the delivery settings by campaign type, you need to add your additional servers in the same manner as you added your first custom SMTP server.https://docs.customer.io/journeys/wait-until/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/wait-until/How it works You can set three different types of waits. Each wait type adds a new path in your workflow. A person progresses down the first path they meet conditions for. Conditions: Determine whether a person needs to achieve certain attributes, perform an event, join a segment, and so on before they can progress through the campaign. You can set multiple conditions. Event time (event-triggered campaigns only): Base your wait on a timestamp in your event data.https://docs.customer.io/journeys/web-push-webhooks/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/web-push-webhooks/Webhooks provide a way to access public APIs and services outside of Customer.io. We treat webhooks like messages: when someone reaches a webhook in your campaign, we’ll execute the webhook, sending a request to an external API. In this case, we’ll show you how to use webhooks to send web push messages.  Try our in-app message solution! Check to see if our in-app messages suit your needs before moving forward with web push with webhooks.https://docs.customer.io/journeys/welcome-email-copy/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/welcome-email-copy/General product / service welcome This is a basic welcome message from a business, app, or website that is sent after people sign up for an account. [greeting] Hi Bob!Welcome to Prioritizer! Thanks so much for joining us. You’re on your way to super-productivity and beyond! [who we are; our mission/ what we help you do; how it works] Prioritizer is a task management app that helps you focus on the important things in life by only allowing you to add 3 items a day.https://docs.customer.io/journeys/whatsapp-metrics/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/whatsapp-metrics/WhatsApp message metrics The following metrics apply to WhatsApp messages. Some metrics, like Opened, behave differently for WhatsApp than for email because they rely on WhatsApp-specific signals like read receipts. Metric Description Drafted We generated the message but haven’t sent it yet. The message requires manual action if you use Queue Draft. Sent The message left Customer.io and was passed to the delivery provider. Delivered The delivery provider confirmed that the message reached the recipient.https://docs.customer.io/journeys/anonymous-events/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/anonymous-events/An anonymous event is an event associated with a person you don’t recognize. The event bears an anonymous_id—a value representing the unknown person, like a cookie. We store these events for up to 30 days. The Anonymous event merge feature lets you associate these events with a person after you identify them. You can enable anonymous event merging in your workspace settings. If you use the JavaScript snippet (client-side): we automatically log anonymous events and associate them with people you identify.https://docs.customer.io/journeys/objects-export-many/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/objects-export-many/Export a single object and its relationships You can export data for a single objectAn object is a non-person entity that you can associate with one or more people—like a company, account, or online course. from an object’s detail page or the object list page. Select an object type from the left hand navigation. Click the name of the object you want to export. Click Options in the top right then choose “Export Object data.https://docs.customer.io/journeys/web-nps-survey/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/web-nps-survey/While we’ve provided instructions below, here’s a quick video explaining how to set up an NPS survey and conditional logic in your workflow to handle different responses. How it works If you want to gauge how people feel about your product, you can send them an NPS survey in your website to measure their satisfaction. Here, we’ll help you set up a web in-app message to survey your customers. In your campaign, we’ll help you group responses so you can follow-up with people depending on the rating they give you—detractors (0-6), passives (7-8), and promoters (9-10).https://docs.customer.io/journeys/web-promotion/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/web-promotion/Read on for instructions on how to build messages like this welcome offer. How it works In this recipe, we’ll broadcastA single broadcast sent to a group of people, all from the Customer.io user interface. Newsletters provide a simple way to send a message without having to set up a campaign workflow or send a call to the API to trigger your broadcast. You can also A/B test a newsletter. an in-app message telling people that we’re running a promotion.https://docs.customer.io/journeys/send-push/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/send-push/Create a Push Notification This process covers a basic push notification. If you set an image or a deep link, your app should either use our SDKs or handle payloads in the format we send. If you want to send more than images and links—like badges, sounds, etc—you can send a message using a Custom Push Payload. In your campaign, click and drag a Push Notification into your campaign from the sidebar.https://docs.customer.io/integrations/sdk/flutter/1.x/update/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/flutter/1.x/update/Assuming that you have followed the install instructions, this section covers the steps to take to successfully update the Customer.io Flutter SDK to the latest version. Inside of your pubspec.yaml, update the version of the Customer.io Flutter SDK (customer_io) to the latest version found here. If you followed the instructions for setting up push notifications on iOS and made modifications to your ios/Podfile, open your ios/Podfile file and make the following updates: # For every line of code that contains 'pod CustomerIO.https://docs.customer.io/integrations/sdk/flutter/2.x/whats-new/2.x-upgrade/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/flutter/2.x/whats-new/2.x-upgrade/What changed? This update provides native support for our new integrations framework. While this represents a significant change “under the hood,” we’ve tried to make it as seamless as possible for you; much of your implementation remains the same. This move also adds two additional features: You’ll use SDK methods from an instance: Support for anonymous tracking: you can send events and other activity for anonymous users, and we’ll reconcile that activity with a person when you identify them.https://docs.customer.io/integrations/sdk/flutter/whats-new/2.x-upgrade/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/flutter/whats-new/2.x-upgrade/What changed? This update provides native support for our new integrations framework. While this represents a significant change “under the hood,” we’ve tried to make it as seamless as possible for you; much of your implementation remains the same. This move also adds two additional features: You’ll use SDK methods from an instance: Support for anonymous tracking: you can send events and other activity for anonymous users, and we’ll reconcile that activity with a person when you identify them.https://docs.customer.io/journeys/link-tracking-custom-domain/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/link-tracking-custom-domain/Set up link tracking for your domain Customer.io provides link tracking by default, but you can also track links on your own subdomain. To use a custom subdomain for tracked links using HTTP in Customer.io, add a CNAME (Canonical Name) record to your DNS host that aliases our tracking subdomains. These are e.customeriomail.com or e-eu.customeriomail.com depending on your Customer.io account region. To use a custom subdomain for tracking links using HTTPS, you’ll need to take additional steps outside of Customer.https://docs.customer.io/journeys/transformer-accessibility-fixes/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/transformer-accessibility-fixes/Within Transformers > Accessibility fixes, enable the feature to set further preferences. You can customize how the Accessibility transformer behaves. For example, you can: Choose whether to autodetect the message language or define it manually. Automatically add lang and role attributes. Remove meta tags that prevent mobile users from zooming. These updates can make your message more accessible and reduce the need for manual fixes.https://docs.customer.io/journeys/mixpanel-data-campaign/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/mixpanel-data-campaign/In Mixpanel, you can organize users into cohorts, which are akin to segments in Customer.io. Mixpanel cohorts compile users based on criteria like what events they’ve performed. You can send cohort data from Mixpanel to Customer.io through webhooks, and you can trigger campaigns to update people, index events, and more. Visit Mixpanel’s documentation on webhooks for more info. Before you begin Mixpanel You must have a paid Mixpanel plan to create custom webhooks.https://docs.customer.io/journeys/ip-addresses/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/ip-addresses/Shared IP pool (default) By default, we add email domains to Customer.io’s shared IP address pool to send emails. We manage and monitor multiple IP pools and remove domains that perform poorly to maintain high deliverability. Send from transactional IP pool We also maintain a separate, transactional IP address pool. This pool has even higher standards—stricter bounce and spam thresholds—than our default, shared IP pool. This ensures that your transactional messages achieve the highest deliverability.https://docs.customer.io/journeys/object-and-relationship-campaigns/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/object-and-relationship-campaigns/Trigger campaigns based on objects or relationships You can trigger campaigns based on changes to objects or relationships. You can trigger a campaign when: an object is updated (like an Account’s name was changed). a relationship between an object and person is added. a relationship is changed (like a person is no longer associated with an Account). You can also narrow in on the audience for these campaigns. For both object and relationship-triggered campaigns, you can choose to send to:https://docs.customer.io/journeys/in-app-event-promotion/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/in-app-event-promotion/How it works This recipe expands on our recipe Create an email campaign to announce registration for events! It uses a feature of ours called objectsAn object is a non-person entity that you can associate with one or more people—like a company, account, or online course., which are non-people entities you can relate to people. In this case, objects are events that people want to register for. Below you’ll learn how to set up an in-app message to promote an upcoming event on your website.https://docs.customer.io/journeys/spamhaus-blocklist/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/spamhaus-blocklist/Spamhaus maintains one of the most widely used blocklists on the internet. When your domain is listed on the Spamhaus Domain Block List (DBL), it can’t be verified or used for sending in Customer.io until it’s removed — and delivery to most major email providers is blocked in the meantime. Listings can escalate quickly: a domain listing can lead to an IP listing, which can result in a broader network block.https://docs.customer.io/journeys/whatsapp-design-studio/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/whatsapp-design-studio/How it works To manage WhatsApp templates in Design Studio, you must integrate directly with your Facebook Business Account. Then you can create WhatsApp templates and submit them for approval from Design Studio, instead of having to leave your workspace to create them with Meta. The process goes like this: From Design Studio, create a WhatsApp message from scratch and add your content including any relevant liquid syntax. Submit it for approval from Meta.https://docs.customer.io/journeys/campaign-triggers-and-filters/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/campaign-triggers-and-filters/How it works Both triggers and filters are sets of conditions that determine who enter your campaigns. A trigger determines who’s eligible to enter a campaign and when. A filter is additional criteria that a person or triggering data must meet for people to enter or remain in the campaign. For example, you might want to send a message when someone views the pricing page (event trigger: page view) of your website, but only send that message to people who aren’t on a paid plan (filter: free plan).https://docs.customer.io/journeys/esp-suppression/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/esp-suppression/Email service providers (ESP) keep suppression lists to ensure they don’t send messages from servers that rejected them before or from people who explicitly do not want messages from you. A message experiences a hard bounce. This means that either the recipient email address does not exist or the recipient email server blocked delivery. A person lodges a spam complaint against a message. ESP suppression only prevents people from receiving emails.https://docs.customer.io/integrations/sdk/android/push/push/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/android/push/push/Before you begin This page explains how to receive rich push notifications using our SDK. However, before you can send push notifications to your audience, you need to enable Customer.io to send push notifications through Firebase Cloud Messaging (FCM). How it works Before a device can receive a push notification, you must: Set up FCM. Set up push. Identify a person. When someone starts the app, they automatically generate a device token.https://docs.customer.io/integrations/data-out/data-replay/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-out/data-replay/How it works Imagine that you’ve sent source data to an analytics platform for six months. Now you want to move to a new platform—it might have features you need or just aligns better with your business needs. Do you really have to start fresh in your new analytics platform? What happens to that six months of data? That’s what our Resend past data feature does: it lets you send data that you previously sent into Customer.https://docs.customer.io/integrations/sdk/ios/whats-new/3.9.0-upgrade/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/whats-new/3.9.0-upgrade/Key Changes The primary change in version 3.9.0 is the introduction of the wrapper pattern for handling push notifications on iOS. This change: Eliminates method swizzling: No more automatic method replacement Simplifies setup: Less boilerplate code required Improves reliability: More predictable behavior See the instructions below to update your app depending on whether you send push notifications with APN or FCM and whether you use UIKit or SwiftUI. Update with APNs UIKit Update your AppDelegate.https://docs.customer.io/integrations/data-in/source-spec/alias-spec/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/source-spec/alias-spec/ See our API documentation for code samples This page can help you better understand when and how to use this API method. But, if you already know how it works and are ready to get started, you can go straight to our API documentation and start writing code. How it works An alias call helps you merge two user profiles—a userId and a previousId. The userId inherits the traits and activity of the previousId, so you can track activity going forward against the canonical userId.https://docs.customer.io/journeys/birthday-and-anniversary-campaigns/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/birthday-and-anniversary-campaigns/Introduction Sending messages on birthdays, anniversaries, and other recurring dates is a great way of keeping customers engaged with your company throughout the year. Customer.io makes this simple. Let’s get started sending your customers a birthday discount, celebrating their time as a customer, or reminding them of something that reccurs on a long time scale. This recipe documents a yearly anniversary campaign, but the same steps work for any type of date.https://docs.customer.io/journeys/email-editors/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/email-editors/ Check out Design Studio! Design Studio is our newest, most flexible email editor. Use components to create a block-based email from scratch, and set global styles to create a consistent brand across your messages made in Design Studio. No longer do you have to decide between a visual or code-based editor; you can use both! Choose your editor While editing a campaign, broadcast, or transactional message, you can create and edit your emails.https://docs.customer.io/journeys/transactional-api-common-api-errors/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/transactional-api-common-api-errors/Successful requests A successful transactional API request returns a 200 OK and looks like this: status: 200 OK { "delivery_id": "A1C2E3jdieDks7zXdyz8XCFn1888", "queued_at": 1604977406 } status: 405 Method Not Allowed Possible misspelling of the request URI. The URI is https://api.customer.io/v1/send/email or https://api.customer.io/v1/send/push. status: 403 Forbidden You probably need to take some additional steps to ensure that you’re authorized to send transactional messages. Error Message Resolution Account owner’s email address is not confirmed.https://docs.customer.io/journeys/conversion-activate-waitlist/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/conversion-activate-waitlist/Business-to-business (B2B) companies often need to track and drive growth across both individual users of their product and non-people entities like the company they work for or webinars they want to attend. In Customer.io, objectsAn object is a non-person entity that you can associate with one or more people—like a company, account, or online course. help you do this. For this recipe, imagine you work at a design platform, Sketcher.io, which offers graphic design and product design tools.https://docs.customer.io/integrations/data-in/connections/javascript/js-source-cookies/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/javascript/js-source-cookies/How it works The JavaScript library stores some information in cookies and local storage on the client to manage user identity. By default, we store up to five cookies on the client. You can recall this information when you need to reuse it and change whether we persist data to protect your audience’s personal information. Cookie Contains ajs_anonymous_id A user’s anonymous ID, set automatically when someone visits your site. This value is used to track anonymous activity and associate anonymous activity with an identified person.https://docs.customer.io/journeys/push-custom-payloads/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/push-custom-payloads/Getting started with custom payloads Creating a custom payload for your push notification grants access to a greater range of push features, like images and deep links—provided that your app is set up to support those features. To enter a custom payload, click Custom Payload when composing your push notification. You can then write or paste your custom code into the editor. There are different tabs for Android and iOS so that you can send custom code for each platform separately but, if you are using Firebase Cloud Messaging, you can just use the Android tab to send custom code that will be used for both Android and iOS.https://docs.customer.io/integrations/sdk/android/push/deep-links/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/android/push/deep-links/Our SDK supports redirects for notification links registered in Android by default. You can customize this behavior using CustomerIOPushNotificationCallback. To register a deep link, you must first add intent filters in your AndroidManifest.xml file. <intent-filter android:label="deep_linking_filter"> <action android:name="android.intent.action.VIEW" /> <category android:name="android.intent.category.DEFAULT" /> <category android:name="android.intent.category.BROWSABLE" /> <!-- Accepts URIs that begin with "remote-habits://settings” --> <data android:host="settings" android:scheme="remote-habits" /> </intent-filter> CustomerIOPushNotificationCallback—a URL handler feature provided by the SDK. When configuring your CustomerIO instance, you can set the callback to handle notification behavior.https://docs.customer.io/integrations/sdk/ios/3.x/push/deep-links/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/3.x/push/deep-links/Deep links let you open a specific page in your app instead of opening the device’s web browser. Want to open a screen in your app or perform an action when a push notification or in-app button is clicked? Deep links work great for this! Setup deep linking in your app. There are two ways to do this; you can do both if you want. Universal Links: universal links let you open your mobile app instead of a web browser when someone interacts with a URL on your website.https://docs.customer.io/integrations/sdk/ios/push/deep-links/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/push/deep-links/Deep links let you open a specific page in your app instead of opening the device’s web browser. Want to open a screen in your app or perform an action when a push notification or in-app button is clicked? Deep links work great for this! Setup deep linking in your app. There are two ways to do this; you can do both if you want. Universal Links: universal links let you open your mobile app instead of a web browser when someone interacts with a URL on your website.https://docs.customer.io/integrations/data-in/connections/hubspot/delete/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/hubspot/delete/ This information is for services outside of Customer.io Customer.io automatically handles deleted HubSpot data. You only need to pay attention to the information on this page if you send your HubSpot data through Customer.io to other services. How it works We use Semantic Events, events with special meanings, to handle delete operations when you sync data from HubSpot to Customer.io. For example, if you delete a contact in HubSpot, we represent the deletion in Customer.https://docs.customer.io/integrations/data-in/connections/salesforce/delete/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/salesforce/delete/ Customer.io Journeys automatically handles deleted Salesforce data The information below is important if you want to handle deletions in services outside of Customer.io. But, if you don’t send your Salesforce data to anywhere other than Customer.io, then you don’t need to do anything to handle deleted data; we handle it for you. How it works You can delete data in Salesforce, but the API that Salesforce uses to ingest data from Salesforce doesn’t have Delete operations.https://docs.customer.io/journeys/email-attachments/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/email-attachments/ Try sending a transactional message Rather than trying to send links, or add attachments to events, you can send attachments as a part of our transactional message service. Why you shouldn’t send attachments Sending attachments can create problems for your deliverability. Here’s a non-exhaustive list of potential problems stemming from attachments: Email attachments are often used to hide viruses and malware, so they are more likely to end up in spam folders or flagged as potentially malicious.https://docs.customer.io/journeys/exit-blocks/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/exit-blocks/How it works Normally, people leave a campaign when they reach the end. But if you set up branches and flow controls, you may want to allow people to exit the campaign at different points along different paths. That’s what exit blocks are for! You can place exit blocks along different branches in your workflow, letting people gracefully exit the campaign along different paths in your workflow. For example, imagine that you have a multi-split branch configured to send messages to anyone whose favorite color is red or yellow, but you want to make sure that everyone else does not receive messages from this branch and leaves the campaign.https://docs.customer.io/journeys/api-triggered-data-format/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/api-triggered-data-format/Providing custom data You’ll send custom data using our API or our libraries. You can also see sample data in our Composer preview. Here’s a basic example of what some custom data might look like in your request. { "data": { "headline": "Roadrunner spotted in Albuquerque!", "date": "January 24, 2018", "text": "We've received reports of a roadrunner in your immediate area! Head to your dashboard to view more information!" } } Overriding Recipients You can set the audience for an API-triggered broadcast in the UI—which is useful when your audience always meets the same conditions.https://docs.customer.io/journeys/transactional-faq/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/transactional-faq/ Is your question not answered here? If you have any questions or feedback not covered on this page or in our transactional API documentation, let us know at product@customer.io! Does the transactional API cost extra? No! You can start sending transactional messages immediately alongside your other messages. When should I use the ‘disable message retention’ setting? You probably want to disable message retention to concealing sensitive content, like password reset tokens.https://docs.customer.io/journeys/faq-twilio/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/faq-twilio/Does Customer.io manage my Twilio account? No. While Customer.io partners with Twilio to send SMS messages, we can’t set up or manage your Twilio account for you. Your Twilio account includes your sender numbers and other things that we can’t manage on your behalf—so you can make changes to your senders, keywords, and so on without having to wait on us to make changes to your account. What countries can I send SMS messages to?https://docs.customer.io/journeys/faq-whatsapp/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/faq-whatsapp/How much does it cost to send WhatsApp messages? Customer.io doesn’t charge you for WhatsApp messages. However, both Meta and Twilio (if you use Twilio) charge for WhatsApp usage. See Billing for WhatsApp messages for more information. Meta charges per message using a tiered pricing model based on the template type (marketing, utility, authentication, or service), recipient country, and message volume. See Meta’s WhatsApp pricing page for details. Twilio As of February 2026, Twilio charges $0.https://docs.customer.io/journeys/gmail-promotions/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/gmail-promotions/Introduction Google has added annotation support for emails that appear in the Promotions tab of the Gmail app. This means that your promotional emails have more opportunities to make an impression beyond the subject and preheader. You can highlight incentives, share key information from your message, and stand out in the crowded inbox. 1. Choose your Annotations Supported annotations include images, your logo, promo codes, expiration dates on deals, and more.https://docs.customer.io/journeys/campaign-conversions/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/campaign-conversions/How goals work A goal is what you want your audience to accomplish during your campaign, like purchase a product, sign up, or subscribe. When you set up a goal, you define conversion criteria, which are the rules that determine when we mark a message or journey as “converted.” The conversion criteria can be one of (and only one of) the following things: an eventSomething that a person in your workspace did.https://docs.customer.io/journeys/google-postmaster-tools/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/google-postmaster-tools/If your recipient marks a message as spam and the email service provider sends that information back to Customer.io, we will automatically suppress that user profile so you can’t send to someone who clearly doesn’t want your messages in the future. However, Google does not send information about spam complaints back to Customer.io. Remember that when viewing your Customer.io dashboard, the spam information displayed does not include Gmail users! Google Postmaster Tools is the only place to view information about Gmail user-reported spam complaints.https://docs.customer.io/journeys/dashboard/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/dashboard/ Use the Agent to understand your workspace data and assist in managing your workflows. Click anytime to chat with your Agent, get help, and get started. Learn more in AI Features. Continue where you left off Under Ready to keep going, you’ll see a carousel of pages you last edited. If you haven’t made any changes in the last 90 days, you’ll see a list of actions you can take to get started.https://docs.customer.io/journeys/1-html-and-css/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/1-html-and-css/There are a couple of reasons for this: HTML and CSS work differently in emails and the web. Emails and how they’re laid out (Layouts) both work a little differently in Customer.io In this doc, we’ll try to explain reason #1, show how those differences manifest in emails, and hopefully give some good advice for how to move forward. (Here’s more info on reason #2.) Why does this happen? Coding for the web is code for browsers.https://docs.customer.io/integrations/data-in/connections/hubspot/forms/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/hubspot/forms/How it works You’ll set up a workflow in HubSpot that sends a webhook to Customer.io when someone submits your form. Then, in Customer.io, you can: Convert that webhook to an event that triggers downstream campaigns Store attributes on your audience’s profiles in Customer.io. These attributes can add people to segments, trigger campaigns, or personalize messages. flowchart LR subgraph HubSpot direction TB a(Person submits form)-->|Hubspot workflow|b(Generate webhook) end b-->c subgraph Customer.https://docs.customer.io/journeys/in-app-components/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/in-app-components/How it works In-app messages use an HTML-like syntax with components similar to HTML elements beginning with x-. In HTML, you typically pass CSS styles to components in a style attribute. You can still do that with our in-app code editor, but each component also exposes a number of top-level attributes that makes it easy to set things like fonts, colors, and so on. These attributes correspond to common CSS properties, like font-size and color, so all the styles should make sense to you if you’re familiar with CSS.https://docs.customer.io/integrations/sdk/ios/3.x/in-app/in-app-event-listeners/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/3.x/in-app/in-app-event-listeners/Handle responses to messages (event listeners) You can set up event listeners to handle your audience’s response to your messages. For example, you might run different code in your app when your audience taps a button in your message or when they dismiss the message without tapping a button. You can listen for four different events: messageShown: a message is “sent” and appears to a user messageDismissed: the user closes the message (by tapping an element that uses the close action) errorWithMessage: the message itself produces an error—this probably prevents the message from appearing to the user messageActionTaken: the user performs an action in the message.https://docs.customer.io/integrations/sdk/ios/in-app/in-app-event-listeners/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/in-app/in-app-event-listeners/Handle responses to messages (event listeners) You can set up event listeners to handle your audience’s response to your messages. For example, you might run different code in your app when your audience taps a button in your message or when they dismiss the message without tapping a button. You can listen for four different events: messageShown: a message is “sent” and appears to a user messageDismissed: the user closes the message (by tapping an element that uses the close action) errorWithMessage: the message itself produces an error—this probably prevents the message from appearing to the user messageActionTaken: the user performs an action in the message.https://docs.customer.io/journeys/in-app-metrics/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/in-app-metrics/How it works When you send a message to a person, Customer.io reports the status of your message until it’s Sent. After that, we rely on the device to tell us when a message is Opened. We aggregate these statuses as metrics, helping you determine how your message performed across your audience. However, we begin displaying metrics before your message expires. While metrics can always help you understand how your audience responds to your message, you should probably consider metrics incomplete until your message expires and your in-app message stops being sent.https://docs.customer.io/journeys/web-achievements/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/web-achievements/Consider what milestone or achievement you’d like to celebrate. In this recipe, we’ll create a campaign to notify customers of their one year anniversary using your product. How it works In this recipe, we’ll trigger a campaign based on the date a person started using your product. When they reach their one year anniversary, we’ll send them an in-app message to congratulate them and offer a discount code for their loyalty.https://docs.customer.io/integrations/sdk/expo/tracking/lifecycle-events/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/expo/tracking/lifecycle-events/By default, we track the following lifecycle events: Application Installed: A user installed your app. Application Updated: A user updated your app. Application Opened: A user opened your app. Application Foregrounded: A user switched back to your app. Application Backgrounded: A user backgrounded your app or switched to another app. You might also want to send your own lifecycle events, like Application Crashed or Application Updated. You can do this using the track method.https://docs.customer.io/integrations/sdk/ios/3.x/push/push-metrics/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/3.x/push/push-metrics/Customer.io supports device-side metrics that help you determine the efficacy of your push notifications: delivered when a push notification is received by the app and opened when a push notification is clicked. If you already configured rich push notifications, the SDK will automatically track opened and delivered events for push notifications originating from Customer.io. See section Automatic push handling below to learn more about this great feature and how to best take advantage of it.https://docs.customer.io/integrations/sdk/ios/push/push-metrics/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/push/push-metrics/Customer.io supports device-side metrics that help you determine the efficacy of your push notifications: delivered when a push notification is received by the app and opened when a push notification is clicked.  Improve delivery metric reliability Configure App Groups to make sure delivery metrics aren’t lost when iOS terminates the Notification Service Extension before the tracking request completes. With App Groups, the SDK automatically recovers any undelivered metrics on the next app launch.https://docs.customer.io/integrations/sdk/android/2.x/push/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/android/2.x/push/This page is part of a setup flow for the SDK. Before you continue, make sure you've implemented previous features—i.e. you can't receive push notifications before you identify people! graph LR getting-started(Install SDK) -->B(Initialize SDK) B --> identify(identify people) identify -.-> track-events(Send events) identify -.-> push(Receive push) identify -.-> rich-push(Receive Rich Push) track-events --> test-support(Write tests) push --> test-support rich-push --> test-support identify -.-> in-app(Receive in-app) in-app --> test-support click getting-started href "https://docs.customer.io/integrations/sdk/android/3.x/push/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/android/3.x/push/This page is part of a setup flow for the SDK. Before you continue, make sure you've implemented previous features—i.e. you can't receive push notifications before you identify people! graph LR getting-started(Install SDK) -->B(Initialize SDK) B --> identify(identify people) identify -.-> track-events(Send events) identify -.-> push(Receive push) identify -.-> rich-push(Receive Rich Push) track-events --> test-support(Write tests) push --> test-support rich-push --> test-support identify -.-> in-app(Receive in-app) in-app --> test-support click getting-started href "https://docs.customer.io/integrations/sdk/ios/1.x/push/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/1.x/push/This page is part of a setup flow for the SDK. Before you continue, make sure you've implemented previous features—i.e. you can't receive push notifications before you identify people! graph LR getting-started(Install SDK) -->B(Initialize SDK) B --> identify(identify people) identify -.-> track-events(Send events) identify -.-> register-token(Register Device Token) register-token -.-> push(Receive push) register-token -.-> rich-push(Receive Rich Push) track-events --> test-support(Write tests) push --> test-support rich-push --> test-support identify -.-> in-app(Receive in-app) in-app --> test-support click getting-started href "https://docs.customer.io/integrations/sdk/ios/2.x/push/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/2.x/push/This page is part of a setup flow for the SDK. Before you continue, make sure you've implemented previous features—i.e. you can't receive push notifications before you identify people! graph LR getting-started(Install SDK) -->B(Initialize SDK) B --> identify(identify people) identify -.-> track-events(Send events) identify -.-> register-token(Register Device Token) register-token -.-> push(Receive push) register-token -.-> rich-push(Receive Rich Push) track-events --> test-support(Write tests) push --> test-support rich-push --> test-support identify -.-> in-app(Receive in-app) in-app --> test-support click getting-started href "https://docs.customer.io/journeys/random-delay/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/random-delay/You can hold people in randomized time delays in campaigns. When journeys reach a Random Delay block, we hold them for a random amount of time between the minimum and maximum time you set using a flat distribution model. This can help you avoid overloading rate-limited API endpoints with webhook requests. Add a condition Like with other workflow blocks, you can add one or more conditions so only certain people wait in a random delay.https://docs.customer.io/journeys/how-to-use-attribute-updates-to-reformat-timestamps/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/how-to-use-attribute-updates-to-reformat-timestamps/1. Create a segment with the attribute you want to reformat When you create your segment, you can use the is not a timestamp condition. This makes sure that you only update attributes that aren’t formatted correctly. 2. Create a campaign using your new segment When you create your campaign make the campaign re-enterable, so you can reformat the timestamp whenever it appears. This campaign won’t send any messages, so you’ll want it to “send” to unsubscribed people as well.https://docs.customer.io/journeys/merge-people/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/merge-people/How merging people works You can merge people manually or automatically. When you merge two people, you pick a primary person and a secondary person. The primary person remains after the merge and the secondary is deleted. This process is permanent: you cannot recover the secondary person. Depending on the data type, the primary person may retain its data or inherit the data from the secondary person.  The primary person might enter new segments and campaignshttps://docs.customer.io/journeys/lob-webhook-integration/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/lob-webhook-integration/How it works Lob specializes in intelligent direct mail, so you can send personalized postcards, letters, and more to your customers. Using webhooks, you can send personalization data and trigger messages from your campaigns. This lets you send personalized physical mail to customers in response to the things they do on your website or in your app—like if a customer requests more information, or if you want to follow up with a physical coupon to retain customers.https://docs.customer.io/journeys/set-preferences-outside-center/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/set-preferences-outside-center/How it works Customer.io’s Subscription Center feature lets your audience set their subscription preferences when they click Unsubscribe or Manage your preferences in your messages. But you might want to let your audience proactively manage their preferences outside of messages—like as a part of your in-product settings or as a part of your sign-up flow. There are two ways to do this: Link to the hosted subscription center — Generate a signed URL that takes a person directly to your Customer.https://docs.customer.io/integrations/sdk/expo/1.x/push-notifications/push/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/expo/1.x/push-notifications/push/This page is part of a setup flow for the SDK. Before you continue, make sure you've implemented previous features—i.e. you can't receive push notifications before you identify people! graph LR getting-started(Install SDK) -->B(Initialize SDK) B --> identify(identify people) identify -.-> track-events(Send events) identify -.-> push(Receive push) identify -.-> in-app(Receive in-app) click getting-started href "/integrations/sdk/expo/getting-started/#install" click B href "/integrations/sdk/expo/getting-started/#initialize-the-sdk" click identify href "/integrations/sdk/expo/identify" click track-events href "/integrations/sdk/expo/track-events/" click register-token href "https://docs.customer.io/integrations/sdk/expo/push-notifications/push/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/expo/push-notifications/push/How it works When you use our Expo plugin, you’re already set up to support push notifications, including images and deep links. Before a device can receive a push notification, you must: Identify a person. This associates a token with the person; you can’t send push notifications to a device until you identify the recipient. (Optional) Set up your app to report push metrics back to Customer.io. Before you begin You need to enable Customer.https://docs.customer.io/integrations/sdk/flutter/1.x/push-notifications/push/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/flutter/1.x/push-notifications/push/This page is part of a setup flow for the SDK. Before you continue, make sure you've implemented previous features—i.e. you can't receive push notifications before you identify people! graph LR getting-started(Install SDK) -->B(Initialize SDK) B --> identify(identify people) identify -.-> track-events(Send events) identify -.-> push(Receive push) identify -.-> in-app(Receive in-app) click getting-started href "/integrations/sdk/flutter/getting-started/#install" click B href "/integrations/sdk/flutter/getting-started/#initialize-the-sdk" click identify href "/integrations/sdk/flutter/identify" click track-events href "/integrations/sdk/flutter/track-events/" click register-token href "https://docs.customer.io/integrations/sdk/react-native/2.x/push-notifications/push/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/2.x/push-notifications/push/This page is part of a setup flow for the SDK. Before you continue, make sure you've implemented previous features—i.e. you can't receive push notifications before you identify people! graph LR getting-started(Install SDK) -->B(Initialize SDK) B --> identify(identify people) identify -.-> track-events(Send events) identify -.-> push(Receive push) identify -.-> in-app(Receive in-app) click getting-started href "/integrations/sdk/react-native/getting-started/#install" click B href "/integrations/sdk/react-native/getting-started/#initialize-the-sdk" click identify href "/integrations/sdk/react-native/identify" click track-events href "/integrations/sdk/react-native/track-events/" click register-token href "https://docs.customer.io/integrations/sdk/react-native/3.x/push-notifications/push/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/3.x/push-notifications/push/This page is part of a setup flow for the SDK. Before you continue, make sure you've implemented previous features—i.e. you can't receive push notifications before you identify people! graph LR getting-started(Install SDK) -->B(Initialize SDK) B --> identify(identify people) identify -.-> track-events(Send events) identify -.-> push(Receive push) identify -.-> in-app(Receive in-app) click getting-started href "/integrations/sdk/react-native/getting-started/#install" click B href "/integrations/sdk/react-native/getting-started/#initialize-the-sdk" click identify href "/integrations/sdk/react-native/identify" click track-events href "/integrations/sdk/react-native/track-events/" click register-token href "https://docs.customer.io/integrations/sdk/react-native/4.x/push-notifications/push/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/4.x/push-notifications/push/How it works Under the hood, our React Native SDK takes advantage of our native Android and iOS SDKs. This helps us keep the React Native SDK up to date. But, for now, it also means you’ll need to add a bit of code to support your iOS users. For Android, you’re ready to go if you followed our getting started instructions. Before a device can receive a push notification, you must:https://docs.customer.io/integrations/sdk/react-native/5.x/push-notifications/push/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/5.x/push-notifications/push/How it works Under the hood, our React Native SDK takes advantage of our native Android and iOS SDKs. This helps us keep the React Native SDK up to date. But, for now, it also means you’ll need to add a bit of code to support your iOS users. For Android, you’re ready to go if you followed our getting started instructions. Before a device can receive a push notification, you must:https://docs.customer.io/integrations/sdk/react-native/push-notifications/push/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/push-notifications/push/How it works Under the hood, our React Native SDK takes advantage of our native Android and iOS SDKs. This helps us keep the React Native SDK up to date. But, for now, it also means you’ll need to add a bit of code to support your iOS users. For Android, you’re ready to go if you followed our getting started instructions. Before a device can receive a push notification, you must:https://docs.customer.io/journeys/zendesk-data-campaign/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/zendesk-data-campaign/As a part of this guide, you’ll set up a webhook in Zendesk to your Customer.io workspace when someone opens a high-priority ticket. You’ll use the webhook to trigger Slack notifications that alert your Support. Zendesk doesn’t support native Slack notifications when tickets are created, and this provides a handy way to help your Support team stay on top of tickets! sequenceDiagram participant A as Customer participant B as Zendesk participant C as Customer.https://docs.customer.io/integrations/sdk/ios/3.x/push/sound-in-push/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/3.x/push/sound-in-push/When you send a push notification to iOS devices that uses our SDK, you can opt to send the Default system sound or no sound at all. If your audience’s phone is set to vibrate, or they’ve disabled sound permissions for your app, the Default setting will cause the device to vibrate rather than playing a sound. In most cases, you should use the Default sound setting to make sure your audience hears (or feels) your message.https://docs.customer.io/integrations/sdk/ios/push/sound-in-push/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/push/sound-in-push/When you send a push notification to iOS devices that uses our SDK, you can opt to send the Default system sound or no sound at all. If your audience’s phone is set to vibrate, or they’ve disabled sound permissions for your app, the Default setting will cause the device to vibrate rather than playing a sound. In most cases, you should use the Default sound setting to make sure your audience hears (or feels) your message.https://docs.customer.io/journeys/test-in-app/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/test-in-app/There are different ways to test your in-app messages: Live preview: Preview your web message in real time on your actual website. Adjust display settings on the fly and see changes sync back to the editor automatically. Send a test message: Send a one-time test of your message to check that it shows up in the right place and behaves the way you expect. Send test Live preview How it works Sends a one-time test message Opens an interactive session Settings Uses editor settings Adjustable on the fly via preview bar Platforms Web and mobile Web only Duration One-time 30-minute session Preview your message on your website Live preview lets you see your in-app message on your actual website as you build it.https://docs.customer.io/journeys/segmentation-and-timestamp-rules/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/segmentation-and-timestamp-rules/When you created your Customer.io account, you likely saw a default segment called “Signed up” that uses the rule created_at is a timestamp. When you build your own segment, we have a variety of timestamp-based rules: This document will give some guidelines for how and when to use each. What does “is a timestamp” even mean? is a timestamp will evaluate to true as soon as the value is a valid UNIX timestamp.https://docs.customer.io/integrations/data-in/connections/forms/forms-in-campaigns/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/forms/forms-in-campaigns/How it works You can use form submissions to trigger campaigns and you can personalize messages using form submission data. This helps you talk to users who fill out your forms. Each form submission also comes into Customer.io as an event called form_submit. You can use this event to create segments or complex campaign conditions in campaigns that aren’t necessarily triggered by the original form submission. Trigger a campaign from a form Form submission events can trigger campaigns, so you can start a conversation with people and foster conversions immediately when they fill out your form.https://docs.customer.io/journeys/objects-in-liquid/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/objects-in-liquid/Reference trigger data You can trigger campaigns based on changes to objects and relationships, so we made it possible for you to use liquid that targets the trigger object or relationship data. You can reference trigger data for object and relationship-triggered campaigns using {{trigger.<object_type>.<attribute_name>}}. For instance, if you have an object type of “Online Classes” and set up a campaign to trigger when you update a class, you could craft an email like the following:https://docs.customer.io/ai/use-docs-with-ai/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/ai/use-docs-with-ai/How it works Large language models (LLMs) are great at reading markdown because, unlike HTML, there’s a lot less noise for them to parse. To make our documentation more accessible to AI, we’ve provided markdown-accessible versions of most of our documentation so you can reference it with your own AI tools. You can access plain-text markdown versions of our docs in a few ways: (Recommended) Our llms.txt file: This is an emerging standard and acts as a sort of LLM-friendly sitemap.https://docs.customer.io/journeys/triggered-lifecycle-email-with-mailgun/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/triggered-lifecycle-email-with-mailgun/You can use your Mailgun account to send email through Customer.io with no loss in functionality. To take advantage of Mailgun, you need to do two things: Point Mailgun’s webhooks at Customer.io. Configure Mailgun as a custom SMTP server in Customer.io. Point Mailgun’s webhooks at Customer.io Go to the Mailgun webhooks page. Enter the webhook URL that corresponds to your region for the events you want to forward to Customer.io.https://docs.customer.io/journeys/json-in-segments/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/json-in-segments/ New to JSON? JSON is a standard, simple way to organize and structure data. Check out our introduction to JSON and learn how you can take advantage of JSON in Customer.io. How it works Attributes and events can contain nested JSON (JavaScript Object Notation) values, and you can evaluate these values when you build a segmentA group of people who match a series of conditions. People enter and exit the segment automatically when they match or stop matching conditions.https://docs.customer.io/integrations/data-in/connections/javascript/utility-methods/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/javascript/utility-methods/How it works Our JavaScript client exposes the following utility methods to help you change how script loads on your page. Load Ready Debug On (Emitter) Timeout Reset (Logout) Load You can load a buffered version of our JavaScript that requires you call load explicitly before the script initiates any network activity. This is useful if you want to wait for user consent before you load the full compliment of integrations or send buffered events to Customer.https://docs.customer.io/journeys/last-visited/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/last-visited/You may have noticed that each person in your Customer.io account has a Last Visited field: If this field is blank in your account, there are several ways to set up and make use of it. Updating Last Visited with page views By default, the “Last Visited” attribute is updated based on page view activity. For profiles where page views exist, we will update “Last Visited” accordingly. Page views can be tracked using one of two options:https://docs.customer.io/integrations/data-in/connections/webhooks/integrating-with-zoho-crm/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/webhooks/integrating-with-zoho-crm/Configuring Zoho CRM in Zoho Flow To start, create a new flow from the My Flows page in Zoho Flow From there you’ll be asked to name and describe your new flow, sending you to the Zoho Flow Builder. Select ‘App’ as the trigger for your flow. Select Zoho CRM as your App Trigger. Here you are given several option for what action will trigger this workflow. You can find full descriptions for each option in Zoho Flow’s documentation.https://docs.customer.io/integrations/sdk/expo/push-notifications/app-groups/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/expo/push-notifications/app-groups/App Groups are required for reliable push delivery tracking on iOS. Without this setup, delivery metrics may be lost if iOS terminates the Notification Service Extension before the tracking request completes. With App Groups, the SDK automatically recovers these lost metrics on the next app launch. Before you begin Before you configure App Groups, make sure you’ve completed the following: Set up push notifications with useRichPush: true enabled Created an App Group identifier in the Apple Developer Portal.https://docs.customer.io/integrations/sdk/react-native/push-notifications/app-groups/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/push-notifications/app-groups/App Groups are required for reliable push delivery tracking on iOS. Without this setup, delivery metrics may be lost if iOS terminates the Notification Service Extension before the tracking request completes. With App Groups, the SDK automatically recovers these lost metrics on the next app launch. Before you begin Before you configure App Groups, make sure you’ve completed the following: Set up push notifications in your React Native app Added a Notification Service Extension as part of the push setup 1.https://docs.customer.io/journeys/custom-unsubscribe-links/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/custom-unsubscribe-links/How it works Google and Yahoo have added new requirements, allowing recipients to unsubscribe from your marketing messages with a single click. If you use our default unsubscribe functionality, you don’t need to do anything. But if you use a custom unsubscribe solution, you need to follow the instructions on this page to implement the new requirements before June 1st, 2024. The new requirement is RFC 8058 List-unsubscribe-post. It defines true one-click unsubscribe through an HTTPS URI POST that triggers an unsubscribe within 48 hours.https://docs.customer.io/integrations/sdk/flutter/2.x/push-notifications/deep-links/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/flutter/2.x/push-notifications/deep-links/How it works Deep links are the links that directs users to a specific location within a mobile app. When you set up your notification, you can set a “deep link.” When your audience taps the notification, the SDK will route users to the right place. Deep links help make your message meaningful, with a call to action that makes it easier, and more likely, for your audience to follow. For example, if you send a push notification about a sale, you can send a deep link that takes your audience directly to the sale page in your app.https://docs.customer.io/integrations/sdk/flutter/push-notifications/deep-links/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/flutter/push-notifications/deep-links/How it works Deep links are the links that directs users to a specific location within a mobile app. When you set up your notification, you can set a “deep link.” When your audience taps the notification, the SDK will route users to the right place. Deep links help make your message meaningful, with a call to action that makes it easier, and more likely, for your audience to follow. For example, if you send a push notification about a sale, you can send a deep link that takes your audience directly to the sale page in your app.https://docs.customer.io/integrations/sdk/expo/1.x/push-notifications/deep-links/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/expo/1.x/push-notifications/deep-links/How it works Deep links are the links that directs users to a specific location within a mobile app. When you set up your notification, you can set a “deep link.” When your audience taps the notification, the SDK will route users to the right place. Deep links help make your message meaningful, with a call to action that makes it easier, and more likely, for your audience to follow. For example, if you send a push notification about a sale, you can send a deep link that takes your audience directly to the sale page in your app.https://docs.customer.io/integrations/sdk/expo/push-notifications/deep-links/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/expo/push-notifications/deep-links/How it works Deep links are the links that directs users to a specific location within a mobile app. When you set up your notification, you can set a “deep link.” When your audience taps the notification, the SDK will route users to the right place. Deep links help make your message meaningful, with a call to action that makes it easier, and more likely, for your audience to follow. For example, if you send a push notification about a sale, you can send a deep link that takes your audience directly to the sale page in your app.https://docs.customer.io/integrations/sdk/flutter/1.x/push-notifications/deep-links/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/flutter/1.x/push-notifications/deep-links/How it works Deep links are the links that directs users to a specific location within a mobile app. When you set up your notification, you can set a “deep link.” When your audience taps the notification, the SDK will route users to the right place. Deep links help make your message meaningful, with a call to action that makes it easier, and more likely, for your audience to follow. For example, if you send a push notification about a sale, you can send a deep link that takes your audience directly to the sale page in your app.https://docs.customer.io/integrations/sdk/react-native/2.x/push-notifications/deep-links/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/2.x/push-notifications/deep-links/How it works Deep links are links that send a person from push notifications to pages in your app. When you set up your notification, you can set a “deep link.” When your audience taps the notification, the SDK will route users to the right place. Deep links help make your message meaningful, with a call to action that makes it easier, and more likely, for your audience to follow. For example, if you send a push notification about a sale, you can send a deep link that takes your audience directly to the sale page in your app.https://docs.customer.io/integrations/sdk/react-native/3.x/push-notifications/deep-links/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/3.x/push-notifications/deep-links/How it works Deep links are the links that directs users to a specific location within a mobile app. When you set up your notification, you can set a “deep link.” When your audience taps the notification, the SDK will route users to the right place. Deep links help make your message meaningful, with a call to action that makes it easier, and more likely, for your audience to follow. For example, if you send a push notification about a sale, you can send a deep link that takes your audience directly to the sale page in your app.https://docs.customer.io/integrations/sdk/react-native/4.x/push-notifications/deep-links/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/4.x/push-notifications/deep-links/How it works Deep links are the links that directs users to a specific location within a mobile app. When you set up your notification, you can set a “deep link.” When your audience taps the notification, the SDK will route users to the right place. Deep links help make your message meaningful, with a call to action that makes it easier, and more likely, for your audience to follow. For example, if you send a push notification about a sale, you can send a deep link that takes your audience directly to the sale page in your app.https://docs.customer.io/integrations/sdk/react-native/5.x/push-notifications/deep-links/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/5.x/push-notifications/deep-links/How it works Deep links are the links that directs users to a specific location within a mobile app. When you set up your notification, you can set a “deep link.” When your audience taps the notification, the SDK will route users to the right place. Deep links help make your message meaningful, with a call to action that makes it easier, and more likely, for your audience to follow. For example, if you send a push notification about a sale, you can send a deep link that takes your audience directly to the sale page in your app.https://docs.customer.io/integrations/sdk/react-native/push-notifications/deep-links/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/push-notifications/deep-links/How it works Deep links are the links that directs users to a specific location within a mobile app. When you set up your notification, you can set a “deep link.” When your audience taps the notification, the SDK will route users to the right place. Deep links help make your message meaningful, with a call to action that makes it easier, and more likely, for your audience to follow. For example, if you send a push notification about a sale, you can send a deep link that takes your audience directly to the sale page in your app.https://docs.customer.io/integrations/sdk/flutter/2.x/push-notifications/multiple-push-providers/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/flutter/2.x/push-notifications/multiple-push-providers/How to handle multiple push providers If you use another push service alongside our SDK (like FlutterFire), then that other service takes over push handling by default and prevents your app from receiving rich push notifications from Customer.io. There are two ways to solve this problem, but we typically recommend the first option, because it’s more flexible and lets you process notifications through another service. The second option causes our SDK to take over push handling entirely.https://docs.customer.io/integrations/sdk/flutter/push-notifications/multiple-push-providers/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/flutter/push-notifications/multiple-push-providers/How to handle multiple push providers If you use another push service alongside our SDK (like FlutterFire), then that other service takes over push handling by default and prevents your app from receiving rich push notifications from Customer.io. There are two ways to solve this problem, but we typically recommend the first option, because it’s more flexible and lets you process notifications through another service. The second option causes our SDK to take over push handling entirely.https://docs.customer.io/integrations/sdk/flutter/1.x/push-notifications/multiple-push-providers/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/flutter/1.x/push-notifications/multiple-push-providers/How to handle multiple push providers If you use another push service alongside our SDK (like FlutterFire), then that other service takes over push handling by default and prevents your app from receiving rich push notifications from Customer.io. There are two ways to solve this problem, but we typically recommend the first option, because it’s more flexible and lets you process notifications through another service. The second option causes our SDK to take over push handling entirely.https://docs.customer.io/integrations/sdk/react-native/2.x/push-notifications/multiple-push-providers/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/2.x/push-notifications/multiple-push-providers/How to handle multiple push providers If you use another push service alongside our SDK (like rnfirebase), it will take over push handling by default and prevent your app from receiving rich push notifications from Customer.io. You can solve this problem using one (and only one) of the methods below, but we typically recommend the first option, because it doesn’t require you to write native code! Option 1 (Recommended): Let Customer.https://docs.customer.io/integrations/sdk/react-native/3.x/push-notifications/multiple-push-providers/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/3.x/push-notifications/multiple-push-providers/How to handle multiple push providers If you use another module in your app that can display push notifications, like expo-notifications, react-native-push-notification, or rnfirebase, these modules may take over push handling by default and prevent your app from receiving push notifications from Customer.io. If Customer.io is the only SDK that you use in your app to display push notifications, then there is no more work that you need complete in your app.https://docs.customer.io/integrations/sdk/react-native/4.x/push-notifications/multiple-push-providers/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/4.x/push-notifications/multiple-push-providers/How to handle multiple push providers If Customer.io is the only SDK that you use in your app to display push notifications, then you don’t need to do anything special to display push notifications. But, if you use another module in your app that can display push notifications like expo-notifications, react-native-push-notification, or rnfirebase, these modules can take over push handling by default and prevent your app from receiving push notifications from Customer.https://docs.customer.io/integrations/sdk/react-native/5.x/push-notifications/multiple-push-providers/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/5.x/push-notifications/multiple-push-providers/How to handle multiple push providers If Customer.io is the only SDK that you use in your app to display push notifications, then you don’t need to do anything special to display push notifications. But, if you use another module in your app that can display push notifications like expo-notifications, react-native-push-notification, or rnfirebase, these modules can take over push handling by default and prevent your app from receiving push notifications from Customer.https://docs.customer.io/integrations/sdk/react-native/push-notifications/multiple-push-providers/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/push-notifications/multiple-push-providers/How to handle multiple push providers If Customer.io is the only SDK that you use in your app to display push notifications, then you don’t need to do anything special to display push notifications. But, if you use another module in your app that can display push notifications like expo-notifications, react-native-push-notification, or rnfirebase, these modules can take over push handling by default and prevent your app from receiving push notifications from Customer.https://docs.customer.io/integrations/data-in/connections/webhooks/integrating-with-hubspot/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/webhooks/integrating-with-hubspot/ This article covers sending data from Hubspot to Customer.io. Looking to send data to Hubspot? Use our Hubspot destination! If you need a way to sync Hubspot with Customer.io, this article is for you! While we don’t have an out-of-the-box integration for sending data from Hubspot to Customer.io, you can: create a webhook campaign to retrieve this data or use Zapier to connect Hubspot to Customer.io or check out our partners to see if one of their integrations could suit your needs Some other options include exporting your Hubspot contacts and importing them to Customer.https://docs.customer.io/accounts-and-workspaces/legacy-permissions/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/accounts-and-workspaces/legacy-permissions/ When creating authors or viewers, if you are able to check a box for Hide all attributes, you are using our legacy roles and permission system. We’re in the process of streamlining how you manage sensitive data in Customer.io. In the new system, all authors will have the same functionality regardless of whether sensitive data is hidden and you can control which profile attributes are hidden too. Otherwise, if you see a dropdown for Hide sensitive attributes you’re using our latest system and should go to Manage team members for up-to-date info.https://docs.customer.io/journeys/authenticating-for-apple-private-email-relay/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/authenticating-for-apple-private-email-relay/When a customer enables the Hide My Email option, Apple generates a unique and randomized email address at the @privaterelay.appleid.com domain that you can associate with that customer. After you pass these addresses into your Customer.io workspace, you need to do a few more things to ensure that your messages are delivered to the Apple Private Email Relay. To start, you need to log into your Apple Developer Portal and go to Certificates, Identifiers & Profiles > More > Sign in with Apple for Email Communication > Configure.https://docs.customer.io/integrations/sdk/flutter/2.x/push-notifications/push-metrics/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/flutter/2.x/push-notifications/push-metrics/Automatic push handling Customer.io supports device-side metrics that help you determine the efficacy of your push notifications: delivered when a push notification is received by the app and opened when a push notification is clicked. The SDK automatically tracks opened and delivered events for push notifications originating from Customer.io after you configure your app to receive push notifications. You don’t have to add any code to track opened push metrics or launch deep links.https://docs.customer.io/integrations/sdk/flutter/push-notifications/push-metrics/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/flutter/push-notifications/push-metrics/Automatic push handling Customer.io supports device-side metrics that help you determine the efficacy of your push notifications: delivered when a push notification is received by the app and opened when a push notification is clicked. The SDK automatically tracks opened and delivered events for push notifications originating from Customer.io after you configure your app to receive push notifications. You don’t have to add any code to track opened push metrics or launch deep links.https://docs.customer.io/integrations/sdk/expo/1.x/push-notifications/push-metrics/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/expo/1.x/push-notifications/push-metrics/How it works Customer.io supports device-side metrics that help you determine the efficacy of your push notifications: delivered when a push notification is received by the app and opened when a push notification is clicked. As of version 1.0.0-beta.14 of our Expo plugin, we track both opened and delivered metrics automatically for you. Beginning in version 1.0.0-beta.14 of our Expo plugin, the SDK automatically tracks opened and delivered events for push notifications originating from Customer.https://docs.customer.io/integrations/sdk/expo/push-notifications/push-metrics/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/expo/push-notifications/push-metrics/How it works Customer.io supports device-side metrics that help you determine the efficacy of your push notifications: delivered when a push notification is received by the app and opened when a push notification is clicked. By default, our SDK automatically tracks opened and delivered events for push notifications originating from Customer.io, but you can add (optional) custom handling to various push events. You might need a custom handler for push notifications that originate outside of Customer.https://docs.customer.io/integrations/sdk/flutter/1.x/push-notifications/push-metrics/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/flutter/1.x/push-notifications/push-metrics/ Upgrade iOS SDK! Beginning in version 2.11 of the native iOS SDK, the SDK automatically handles push notifications from Customer.io and tracks opened and delivered metrics for you. We recommend that you upgrade to simplify your code! Automatic push handling Customer.io supports device-side metrics that help you determine the efficacy of your push notifications: delivered when a push notification is received by the app and opened when a push notification is clicked.https://docs.customer.io/integrations/sdk/react-native/2.x/push-notifications/push-metrics/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/2.x/push-notifications/push-metrics/How it works Customer.io supports device-side metrics that help you determine the efficacy of your push notifications: delivered when a push notification is received by the app and opened when a push notification is clicked.  Update to version 3 for Javascript functions The React Native SDK version 3.0 introduced support for tracking push metrics using Javascript methods, eliminating the need for adding any native code. It’s recommended you update to the latest version to take advantage of this feature.https://docs.customer.io/integrations/sdk/react-native/3.x/push-notifications/push-metrics/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/3.x/push-notifications/push-metrics/ Upgrade to a version after 3.4.0! If you’re on a version of our SDK before 3.4.0, you’ll need to manually handle push notifications. Beginning in 3.4.0, the SDK automatically handles push notifications from Customer.io and tracks opened and delivered metrics for you. We recommend that you upgrade to simplify your code! Automatic push handling Customer.io supports device-side metrics that help you determine the efficacy of your push notifications: delivered when a push notification is received by the app and opened when a push notification is clicked.https://docs.customer.io/integrations/sdk/react-native/4.x/push-notifications/push-metrics/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/4.x/push-notifications/push-metrics/Automatic push handling Customer.io supports device-side metrics that help you determine the efficacy of your push notifications: delivered when a push notification is received by the app and opened when a push notification is clicked. The SDK automatically tracks opened and delivered events for push notifications originating from Customer.io after you configure your app to receive push notifications. You don’t have to add any code to track opened push metrics or launch deep links.https://docs.customer.io/integrations/sdk/react-native/5.x/push-notifications/push-metrics/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/5.x/push-notifications/push-metrics/Automatic push handling Customer.io supports device-side metrics that help you determine the efficacy of your push notifications: delivered when a push notification is received by the app and opened when a push notification is clicked. The SDK automatically tracks opened and delivered events for push notifications originating from Customer.io after you configure your app to receive push notifications. You don’t have to add any code to track opened push metrics or launch deep links.https://docs.customer.io/integrations/sdk/react-native/push-notifications/push-metrics/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/push-notifications/push-metrics/Automatic push handling Customer.io supports device-side metrics that help you determine the efficacy of your push notifications: delivered when a push notification is received by the app and opened when a push notification is clicked. The SDK automatically tracks opened and delivered events for push notifications originating from Customer.io after you configure your app to receive push notifications. You don’t have to add any code to track opened push metrics or launch deep links.https://docs.customer.io/journeys/transactional-campaign/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/transactional-campaign/How it works A transactional message is a message that your audience expects to receive even if they’ve opted out of marketing messages—like purchase receipts, password reset requests, shipping updates, etc. In most cases, we suggest that you use our transactional API to send transactional messages. But, if you need to send a transactional message over a channel other than email, SMS or push notifications, or you want to perform additional actions—like attribute changes, etc—you may need to set up a transactional campaign.https://docs.customer.io/journeys/collections/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/collections/What’s a Collection? A collection is a new type of data in Customer.io that’s separate from people or events in your account. They represent any set of “things” that exist in your business. For instance, a Collection could be a list of upcoming events, promotions/coupons, or available classes. You should store this data in Customer.io when it’s helpful to be able to sort through the Collection to identify a specific set of data that you want to include in a message, tailored to the data you know about each person.https://docs.customer.io/journeys/apitb-changes/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/apitb-changes/Change the recipient segment(s) in the UI Your updated segment(s) will be used the next time the broadcast is triggered. Keep in mind, if you set the recipients in the UI but end up triggering through an API call, any recipients defined in the API call will override the UI setting. Make changes while the broadcast is queued to send When a broadcast is triggered via API, it’s queued while sending to all recipients.https://docs.customer.io/integrations/data-in/connections/forms/forms-api/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/forms/forms-api/How it works When someone submits your form, we’ll identifyThe Customer.io operation that adds or updates a person. When you identify a person, Customer.io either adds a person if they don’t exist in your workspace, or updates them if they do. Before you identify someone (by their email address or an ID), you can track them anonymously. the form submitter and assign them attributesA key-value pair that you associate with a person or an object—like a person’s name, the date they were created in your workspace, or a company’s billing date etc.https://docs.customer.io/journeys/health/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/health/Click > Workspace performance to go to your dashboard. Start troubleshooting To start troubleshooting, review your Active issues on the Overview tab and dive into data or messaging metrics. Data metrics showcase info for data coming into your workspace. Messaging metrics showcase data for messages leaving your workspace. Check your Overview tab for Active issues. Review your daily metrics on the Data tab to help diagnose data ingress issues. Review your daily metrics on the Messaging tab to help diagnose messaging output and delivery issues.https://docs.customer.io/journeys/verify-email-deliverable-kickbox/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/verify-email-deliverable-kickbox/Introduction You don’t just want to know that email addresses are valid (i.e. they comply with RFC 5322); you want to know that addresses are deliverable. Sending messages to undeliverable email addresses can increase your bounce rate and impact your deliverability. If you’re not able to verify the deliverability of an email address before you add it to Customer.io, you can always leverage Webhook actions and a third-party verification service like Kickbox.https://docs.customer.io/integrations/sdk/ios/whats-new/3.x-upgrade/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/whats-new/3.x-upgrade/What changed? This update provides native support for our new integrations framework. While this represents a significant change “under the hood,” we’ve tried to make it as seamless as possible for you; much of your implementation remains the same. This move also adds two additional features: Support for anonymous tracking: you can send events and other activity for anonymous users, and we’ll reconcile that activity with a person when you identify them.https://docs.customer.io/accounts-and-workspaces/ip-addresses/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/accounts-and-workspaces/ip-addresses/If you have a custom SMTP server, use our webhooks, or have an outgoing data warehouse integration, you’ll need to allow the appropriate addresses below. Make sure you allow the appropriate addresses for your region! Email (Custom SMTP) and Webhook IP Addresses US RegionEU Region 35.188.196.183 34.76.143.229 104.198.177.219 34.78.91.47 104.154.232.87 34.77.94.252 130.211.229.195 35.187.188.242 104.198.221.24 34.78.122.90 104.197.27.15 35.195.137.235 35.194.9.154 130.211.108.156 104.154.144.51 104.199.50.18 104.197.210.12 34.78.44.80 35.225.6.73 35.205.31.154 35.192.215.166 34.170.204.100 Reverse ETL IP Addresses (data-in) 34.https://docs.customer.io/journeys/run-reports/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/run-reports/Reports let you retrieve data from Campaigns and Broadcasts based on common tags or naming conventions. With reports on the Analysis page, you might: Locate your top performing marketing campaigns. Analyze deliverability of all your transactional campaigns together. Compare journey volume and performance of two similar campaigns. Each report might take a few seconds to run and will automatically run again when you change the report criteria. After results are returned, however, you can toggle any of the display options you’d like without re-running the full report.https://docs.customer.io/integrations/sdk/expo/push-notifications/push-notification-channel/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/expo/push-notifications/push-notification-channel/🎉New in v2.4 Starting in Android 8.0, you can set up “notification channels,” which categorize notifications for your Android app. Every notification now belongs to a channel and the channel determines the behavior of notifications—whether they play sounds, appear as heads-up notifications, and so on. Channels also give users control over which channels they want to see notifications from. For example, if you had a news app, you might have different channels for sports, entertainment, and breaking news, giving users the ability to pick the channels they care about.https://docs.customer.io/integrations/sdk/flutter/2.x/push-notifications/push-notification-channel/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/flutter/2.x/push-notifications/push-notification-channel/🎉New in v2.4.0 Starting in Android 8.0, you can set up “notification channels,” which categorize notifications for your Android app. Every notification now belongs to a channel and the channel determines the behavior of notifications—whether they play sounds, appear as heads-up notifications, and so on. Channels also give users control over which channels they want to see notifications from. For example, if you had a news app, you might have different channels for sports, entertainment, and breaking news, giving users the ability to pick the channels they care about.https://docs.customer.io/integrations/sdk/flutter/push-notifications/push-notification-channel/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/flutter/push-notifications/push-notification-channel/🎉New in v2.4.0 Starting in Android 8.0, you can set up “notification channels,” which categorize notifications for your Android app. Every notification now belongs to a channel and the channel determines the behavior of notifications—whether they play sounds, appear as heads-up notifications, and so on. Channels also give users control over which channels they want to see notifications from. For example, if you had a news app, you might have different channels for sports, entertainment, and breaking news, giving users the ability to pick the channels they care about.https://docs.customer.io/integrations/sdk/react-native/4.x/push-notifications/push-notification-channel/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/4.x/push-notifications/push-notification-channel/🎉New in v4.5.0 Starting in Android 8.0, you can set up “notification channels,” which categorize notifications for your Android app. Every notification now belongs to a channel and the channel determines the behavior of notifications—whether they play sounds, appear as heads-up notifications, and so on. Channels also give users control over which channels they want to see notifications from. For example, if you had a news app, you might have different channels for sports, entertainment, and breaking news, giving users the ability to pick the channels they care about.https://docs.customer.io/integrations/sdk/react-native/5.x/push-notifications/push-notification-channel/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/5.x/push-notifications/push-notification-channel/🎉New in v4.5.0 Starting in Android 8.0, you can set up “notification channels,” which categorize notifications for your Android app. Every notification now belongs to a channel and the channel determines the behavior of notifications—whether they play sounds, appear as heads-up notifications, and so on. Channels also give users control over which channels they want to see notifications from. For example, if you had a news app, you might have different channels for sports, entertainment, and breaking news, giving users the ability to pick the channels they care about.https://docs.customer.io/integrations/sdk/react-native/push-notifications/push-notification-channel/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/push-notifications/push-notification-channel/🎉New in v4.5.0 Starting in Android 8.0, you can set up “notification channels,” which categorize notifications for your Android app. Every notification now belongs to a channel and the channel determines the behavior of notifications—whether they play sounds, appear as heads-up notifications, and so on. Channels also give users control over which channels they want to see notifications from. For example, if you had a news app, you might have different channels for sports, entertainment, and breaking news, giving users the ability to pick the channels they care about.https://docs.customer.io/integrations/sdk/expo/tracking/anonymous-activity/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/expo/tracking/anonymous-activity/In Customer.io, you’ll see anonymous activity in the Activity Log, but we don’t surface anonymous profilesAn instance of a person. Generally, a person is synonymous with their profile; there should be a one-to-one relationship between a real person and their profile in Customer.io. You reference a person’s profile attributes in liquid using customer—e.g. {{customer.email}}. in Customer.io. You won’t be able to find an “anonymous person” in your workspace, and an anonymous person can’t trigger campaigns or get messages (including push notifications) from Customer.https://docs.customer.io/journeys/cart-abandonment/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/cart-abandonment/How it works For this recipe, we’ll send emails to customers who have abandoned their carts after a certain amount of time. We offer two methods through event-triggered or segment-triggered campaignsCampaigns are automated workflows you set up to send people messages and perform other actions when they meet your criteria.. We recommend using event-triggered campaigns when possible as you’ll have more flexibility for targeting information related to carts than if the information were stored on a person’s profile (segment-triggered campaign).https://docs.customer.io/integrations/sdk/android/push/push-notification-channel/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/android/push/push-notification-channel/🎉New in v4.7.0 Starting in Android 8.0, you can set up “notification channels,” which categorize notifications for your Android app. Every notification now belongs to a channel and the channel determines the behavior of notifications—whether they play sounds, appear as heads-up notifications, and so on. Channels also give users control over which channels they want to see notifications from. For example, if you had a news app, you might have different channels for sports, entertainment, and breaking news, giving users the ability to pick the channels they care about.https://docs.customer.io/journeys/api-triggered-errors/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/api-triggered-errors/Method Not Allowed You might have misspelled the request URI. The URI should look like the following (with the broadcast/trigger :id): US region: https://api.customer.io/v1/api/campaigns/:id/triggers EU region: https://api-eu.customer.io/v1/api/campaigns/:id/triggers “status”:“400” { "errors":[ { "detail":"bad request (reference 01C4MWXZPAR1SHBSZT4ZMZ6KZV)", "status":"400" } ] } Reason: Issues with the JSON formatting of the request. This could be mismatched opening or closing brackets, missing commas or quotes, etc. “status”:“401” You’ve provided an incorrect or invalid bearer token. Check that your token provides access to the workspace containing your broadcast and has sufficient permissions to trigger a broadcast.https://docs.customer.io/journeys/composer-errors/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/composer-errors/If you click it, the Review Errors modal will let you know what’s wrong. Inside this modal, there can be a variety of outputs. This is a run-down of the most common ones, when you see them, and what you can do to fix them! Variable is missing!  Error found in From Variable ‘customer.eemail’ is missing And it happens when the variable you’re trying to use in your email doesn’t exist for the customer whose sample data you’re using.https://docs.customer.io/journeys/css-pre-processing/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/css-pre-processing/What’s CSS pre-processing? CSS pre-processing converts your CSS styles to inline attributes in your emails. This can make your email more compatible with email clients. Why disable CSS pre-processing? You may want to disable CSS pre-processing if your HTML has already been processed. For instance, if you copy/pasted a custom email template with styles already inlined, repeating CSS pre-processing may cause issues with your layout. This most frequently happens with responsive email templates on mobile devices.https://docs.customer.io/accounts-and-workspaces/gdpr-faq/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/accounts-and-workspaces/gdpr-faq/ Read the text in full! We’d encourage you to read the text in full and consult with your legal counsel for the most complete understanding of the GDPR. Customer.io helps you use customer data to help send personalized messaging. We understand the power of this capability, and with it the importance of helping you protect that data. We’ve stated our public commitment to the regulation and, as part of that, have either built new features for the product, or made them more accessible.https://docs.customer.io/integrations/getting-started/data-compliance/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/getting-started/data-compliance/GDPR and regulatory compliance GDPR is the EU’s General Data Protection Regulation, and provides rules for handling customer data within the EU. But, even if you don’t have customers in the EU, you may want to abide by these rules—more or less—to prepare for data privacy rules in other locations and to respect your audience’s privacy. To help you maintain GDPR compliance, we: Store and transfer data securely. Information in our North America data center does not leave North America unless you send it to a service outside the US.https://docs.customer.io/journeys/deleting-users/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/deleting-users/If you are honoring a person’s request to be forgotten, or simply want to prevent an identifier from being added to your Customer.io workspace in the future, you can suppress that identifier when deleting people. Types of suppressions Suppressions can mean a few different things: In Customer.io, you can suppress a deleted person’s identifiers so they can’t ever be readded to your workspace (good for GDPR compliance). Email service providers (ESP) suppress an email address to help you maintain good deliverability.https://docs.customer.io/journeys/drag-and-drop/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/drag-and-drop/ Check out Design Studio! Design Studio is our newest, most flexible email editor. Use components to create a block-based email from scratch, and set global styles to create a consistent brand across your messages made in Design Studio. No longer do you have to decide between a visual or code-based editor; you can use both! Settings The Settings tab contains general settings for your whole message: background color, default typeface, link color, etc.https://docs.customer.io/integrations/data-in/connections/forms/edit-disconnect/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/forms/edit-disconnect/How it works You can edit a form at any time to add, remove, or re-map form fields. But changing form fields does not affect form submissions you’ve already received. If you want to keep attributesA key-value pair that you associate with a person or an object—like a person’s name, the date they were created in your workspace, or a company’s billing date etc. Use attributes to target people and personalize messages.https://docs.customer.io/journeys/deliverability-metrics/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/deliverability-metrics/The Deliverability tab in the Analysis section of your workspace shows key email metrics by provider. These metrics represent all outbound emails from your workspace over a timeframe you select. This data can help you identify providers you’re performing poorly with so that you can take action to improve deliverability and engagement with your emails. Metrics The Provider column shows the provider or provider group name: the email services that your recipients use.https://docs.customer.io/journeys/campaign-exit-conditions/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/campaign-exit-conditions/By default, a person continues through a campaign until they stop matching the campaign filter criteria. (For an attribute or segment-triggered campaign, people will exit when they stop matching the trigger conditions by default.) To view or modify your exit criteria, click the upper-left menu while editing a campaign. Then click Manage under Exit. These are your options for exit conditions: They match the conversion criteria: This setting causes people to exit your campaign after they perform the conversion action (your audience performs an event, enters a segment, or leaves a segment).https://docs.customer.io/journeys/web-adoption/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/web-adoption/How it works In this recipe, we’ll trigger a campaign based on a segment of users who use your product regularly. We’ll send them an in-app message about the new feature and how to get started. We’ll also set up our message so that it only appears on relevant pages and in the right spot. For example, we don’t want our message to block an Add to Cart button. Before you begin This recipe assumes you’ve already set up your website to identify people and receive in-app messages.https://docs.customer.io/journeys/hipaa-standards/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/hipaa-standards/HIPAA compliance requirements The Health Insurance Portability and Accountability Act (HIPAA) is a United States law that ensures organizations handling individuals’ digital health information keep it secure and confidential. The information protected under HIPAA is referred to as Protected Health Information (PHI). PHI includes not only medical details, like test outcomes and treatment records, but also personal identifiers connected to those records like a patient’s name, contact details, account numbers, demographic data, and related identifiers.https://docs.customer.io/accounts-and-workspaces/managing-credentials/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/accounts-and-workspaces/managing-credentials/ To access your credentials, you must be an Account Admin or Member with the account-level permission, “Manage API credentials.” Track API Keys vs App API Keys There are two types of API keys in each account. Track API Keys Track API keys are used to send behavioral tracking activity (/events and attribute updates) into your workspace. API requests using the https://track.customer.io/api/v1/ endpoint use these tracking API keys. App API Keys App API keys are used to trigger messages and broadcasts, or programmatically retrieve data from your workspace for analysis, troubleshooting, or reporting.https://docs.customer.io/integrations/sdk/expo/push-notifications/multiple-push-providers/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/expo/push-notifications/multiple-push-providers/Use React Native Firebase with the Customer.io SDK If you use react-native-firebase with the Customer.io SDK, you’ll need to make sure that your app.json or app.config.js file doesn’t include the ios.pushNotification.googleServicesFile option. This ensures that you properly capture metrics for push notifications sent through Customer.io and any notifications you receive using react-native-firebase. { "expo": { "ios": { // include plist file here "googleServicesFile": "./GoogleService-Info.plist" }, "plugins": [ [ "customerio-expo-plugin", { "android": { "googleServicesFile": ".https://docs.customer.io/accounts-and-workspaces/payment-problems/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/accounts-and-workspaces/payment-problems/If your payment fails: If your account payment fails repeatedly, our billing team will try to reach out to your team to talk about the issue. It’s important you keep your invoice contact up to date so that these messages reach the right person. We’ll also display a banner in-app to let you know there’s a problem. If you see this, don’t panic! Reach out to our billing team on billing@customer.https://docs.customer.io/integrations/sdk/ios/3.x/push/provisional/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/3.x/push/provisional/Provisional push support is available for iOS 15 and above. Customer.io doesn’t have a specific “provisional push” feature. This is just something that iOS supports out of the box with iOS 15+. See Apple’s provisional authorization documentation to learn more. When you request authorization for push notifications, you can include the .provisional option in the requestAuthorization call. class NotificationUtil: NotificationUtility { func showPromptForPushPermission(completionHandler: @escaping (Bool) -> Void) { UNUserNotificationCenter.current().requestAuthorization(options: [.alert, .https://docs.customer.io/integrations/sdk/ios/push/provisional/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/push/provisional/Provisional push support is available for iOS 15 and above. Customer.io doesn’t have a specific “provisional push” feature. This is just something that iOS supports out of the box with iOS 15+. See Apple’s provisional authorization documentation to learn more. When you request authorization for push notifications, you can include the .provisional option in the requestAuthorization call. class NotificationUtil: NotificationUtility { func showPromptForPushPermission(completionHandler: @escaping (Bool) -> Void) { UNUserNotificationCenter.current().requestAuthorization(options: [.alert, .https://docs.customer.io/integrations/sdk/android/push/push-certificates/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/android/push/push-certificates/Upload your push certificate If you don’t already have your FCM .JSON file, you’ll need to get it before you can finish this process and send push notifications. In Customer.io, go to Settings > Workspace Settings and click Settings next to Push. For iOS, click Enable, and select the Firebase Cloud Messaging (FCM) option. Get your .JSON file for FCM Before you can get a push certificate for Firebase Cloud Messaging, make sure that the FCM API is enabled for your project.https://docs.customer.io/integrations/sdk/ios/3.x/push/push-certificates/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/3.x/push/push-certificates/You can send push notifications to iOS devices using either Apple’s Push Notification service (APNs) or Google’s Firebase Cloud Messaging (FCM) service. To authorize your Customer.io workspace to send notifications through APNs, you’ll need to upload your APNs .p8 certificate and provide your credentials or upload your .JSON to iOS devices over Apple’s Push Notification service, you’ll need to upload your APNs .p8 certificate and enter your Apple Developer Key ID, Team ID, and Bundle ID.https://docs.customer.io/integrations/sdk/ios/push/push-certificates/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/push/push-certificates/You can send push notifications to iOS devices using either Apple’s Push Notification service (APNs) or Google’s Firebase Cloud Messaging (FCM) service. To authorize your Customer.io workspace to send notifications through APNs, you’ll need to upload your APNs .p8 certificate and provide your credentials or upload your .JSON to iOS devices over Apple’s Push Notification service, you’ll need to upload your APNs .p8 certificate and enter your Apple Developer Key ID, Team ID, and Bundle ID.https://docs.customer.io/integrations/sdk/android/2.x/rich-push/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/android/2.x/rich-push/This page is part of a setup flow for the SDK. Before you continue, make sure you've implemented previous features—i.e. you can't receive in-app notifications before you identify people! graph LR getting-started(Install SDK) -->B(Initialize SDK) B --> identify(identify people) identify -.-> track-events(Send events) identify -.-> push(Receive push) identify -.-> rich-push(Receive Rich Push) track-events --> test-support(Write tests) push --> test-support rich-push --> test-support identify -.-> in-app(Receive in-app) in-app --> test-support click getting-started href "https://docs.customer.io/integrations/sdk/ios/1.x/rich-push/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/1.x/rich-push/This page is part of a setup flow for the SDK. Before you continue, make sure you've implemented previous features—i.e. you can't receive in-app notifications before you identify people! graph LR getting-started(Install SDK) -->B(Initialize SDK) B --> identify(identify people) identify -.-> track-events(Send events) identify -.-> register-token(Register Device Token) register-token -.-> push(Receive push) register-token -.-> rich-push(Receive Rich Push) track-events --> test-support(Write tests) push --> test-support rich-push --> test-support identify -.-> in-app(Receive in-app) in-app --> test-support click getting-started href "https://docs.customer.io/journeys/bcc-salesforce-or-your-crm/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/bcc-salesforce-or-your-crm/For each email you want to BCC to your CRM, head into the Composer: Add your CRM’s dropbox address in the BCC field Uncheck the “Fake BCC option” What does “Fake BCC” do? If this option is checked, instead of sending a true BCC, we’ll send you a separate copy of the email (with a modified subject line containing the user’s email address). This allows you to be copied on emails, open them and click links without worrying about affecting the user’s history.https://docs.customer.io/integrations/sdk/react-native/2.x/in-app-messages/set-up-in-app/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/2.x/in-app-messages/set-up-in-app/This page is part of a setup flow for the SDK. Before you continue, make sure you've implemented previous features—i.e. you can't receive in-app notifications before you identify people! graph LR getting-started(Install SDK) -->B(Initialize SDK) B --> identify(identify people) identify -.-> track-events(Send events) identify -.-> push(Receive push) identify -.-> in-app(Receive in-app) click getting-started href "/integrations/sdk/react-native/getting-started/#install" click B href "/integrations/sdk/react-native/getting-started/#initialize-the-sdk" click identify href "/integrations/sdk/react-native/identify" click track-events href "/integrations/sdk/react-native/track-events/" click register-token href "https://docs.customer.io/integrations/sdk/react-native/3.x/in-app-messages/set-up-in-app/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/3.x/in-app-messages/set-up-in-app/This page is part of a setup flow for the SDK. Before you continue, make sure you've implemented previous features—i.e. you can't receive in-app notifications before you identify people! graph LR getting-started(Install SDK) -->B(Initialize SDK) B --> identify(identify people) identify -.-> track-events(Send events) identify -.-> push(Receive push) identify -.-> in-app(Receive in-app) click getting-started href "/integrations/sdk/react-native/getting-started/#install" click B href "/integrations/sdk/react-native/getting-started/#initialize-the-sdk" click identify href "/integrations/sdk/react-native/identify" click track-events href "/integrations/sdk/react-native/track-events/" click register-token href "https://docs.customer.io/journeys/sms-character-encoding/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/sms-character-encoding/How it works By default, SMS messages use the GSM 7-bit character set, which supports up to 160 characters. Going over the character limit will cause your message to split into multiple messages—which may not be a great experience for your customers and each message (called a segment or a credit depending on your plan) is counted towards your bill! While the default character set covers roughly 128 common symbols, it doesn’t cover all languages or symbols you might use in text messages.https://docs.customer.io/integrations/sdk/android/push/test-push/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/android/push/test-push/This is what the payload looks like on our end. If you’ve set up your app to use other data—custom keys outside the scope of our SDK—you can use our Custom Payload Editor; you’re welcome to place custom keys inside the message.data object, but you’ll need to do additional development to support keys beyond our standard title, body, link, and image. { "message": { "data": { "title": "string", //(optional) The title of the notification.https://docs.customer.io/integrations/sdk/ios/3.x/push/test-push/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/3.x/push/test-push/After you set up push notifications, you should send some test messages. You can send messages through the Customer.io push composer. If your app is set up to send more than the standard title, body, image, and link, you’ll need to send a custom payload. The payloads below represent what your app can expect to receive from Customer.io. If you use a custom payload, you’ll need to use the format(s) below to make sure that the SDK receives your message properly.https://docs.customer.io/integrations/sdk/ios/push/test-push/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/push/test-push/After you set up push notifications, you should send some test messages. You can send messages through the Customer.io push composer. If your app is set up to send more than the standard title, body, image, and link, you’ll need to send a custom payload. The payloads below represent what your app can expect to receive from Customer.io. If you use a custom payload, you’ll need to use the format(s) below to make sure that the SDK receives your message properly.https://docs.customer.io/journeys/faq-timestamps/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/faq-timestamps/Why don’t people match my Signed Up segment even after I sent in created_at timestamps? In order for any timestamp rule to work, you need to send the timestamps in unix (seconds since epoch) format. If you are sending timestamps in milliseconds or if you’re using a different timestamp format like ISO 8601, your users will not match. Unsupported timestamp values We support timestamp values in seconds since epoch. We don’t support timestamps between 0 and 100000000, values in milliseconds, or negative timestamp values.https://docs.customer.io/ai/agent/troubleshooting/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/ai/agent/troubleshooting/Verify AI-generated results AI suggestions and generated content are designed to help you, but they’re not a substitute for your expertise. AI can make mistakes, potentially leading to unintended consequences. You should not rely on AI-powered features as a singular source of truth, especially when it comes to features that can impact your audience—like segments that trigger campaigns or updating messages in live campaigns. When you work with AI-powered search results, you should review the cited sources from our documentation to verify the accuracy of the information.https://docs.customer.io/journeys/understanding-ab-results/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/understanding-ab-results/Note: the information in this document only applies to testing campaign messages. See A/B Testing Newsletters for more on testing newsletters. What does ‘Chance to Beat Original’ mean? Chance to beat original (CTBO) is the likelihood that the variation will outperform the original. It determines statistical significance by answering the question: Is the difference observed between the original and variation greater than a difference due to random chance? What does a CTBO of 50% mean?https://docs.customer.io/journeys/triggered-lifecycle-email-with-mailjet/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/triggered-lifecycle-email-with-mailjet/You can use your Mailjet account to send email through Customer.io with no loss in functionality. To take advantage of Mailjet, you need to do two things: Point Mailjet’s webhooks at Customer.io. Configure Mailjet as a custom SMTP server in Customer.io. Point Mailjet’s webhooks at Customer.io Go to the Mailjet event triggers page. Add the webhook URL corresponding to your region for all events except Open and Click. US: https://track.customer.io/mailjet/events EU: https://track-eu.https://docs.customer.io/integrations/sdk/react-native/2.x/in-app-messages/in-app-actions/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/2.x/in-app-messages/in-app-actions/How it works In-app messages often have a call to action. Most basic actions are handled automatically by the SDK. For example, if you set a call-to-action button to open a web page, the SDK will open the web page when the user taps the button. But you can also listen for in-app message events and handle responses yourself. And if you set up custom actions, you’ll need to handle the action yourself and dismiss the resulting message when you’re done with it.https://docs.customer.io/integrations/sdk/react-native/3.x/in-app-messages/in-app-actions/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/3.x/in-app-messages/in-app-actions/How it works In-app messages often have a call to action. Most basic actions are handled automatically by the SDK. For example, if you set a call-to-action button to open a web page, the SDK will open the web page when the user taps the button. But you can also set up custom actions that require your app to handle the response. If you set up custom actions, you’ll need to handle the action yourself and dismiss the resulting message when you’re done with it.https://docs.customer.io/integrations/sdk/react-native/4.x/in-app-messages/in-app-actions/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/4.x/in-app-messages/in-app-actions/How it works In-app messages often have a call to action. Most basic actions are handled automatically by the SDK. For example, if you set a call-to-action button to open a web page, the SDK will open the web page when the user taps the button. But you can also set up custom actions that require your app to handle the response. If you set up custom actions, you’ll need to handle the action yourself and dismiss the resulting message when you’re done with it.https://docs.customer.io/integrations/sdk/react-native/5.x/in-app-messages/in-app-actions/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/5.x/in-app-messages/in-app-actions/How it works In-app messages often have a call to action. Most basic actions are handled automatically by the SDK. For example, if you set a call-to-action button to open a web page, the SDK will open the web page when the user taps the button. But you can also set up custom actions that require your app to handle the response. If you set up custom actions, you’ll need to handle the action yourself and dismiss the resulting message when you’re done with it.https://docs.customer.io/integrations/sdk/react-native/in-app-messages/in-app-actions/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/in-app-messages/in-app-actions/How it works In-app messages often have a call to action. Most basic actions are handled automatically by the SDK. For example, if you set a call-to-action button to open a web page, the SDK will open the web page when the user taps the button. But you can also set up custom actions that require your app to handle the response. If you set up custom actions, you’ll need to handle the action yourself and dismiss the resulting message when you’re done with it.https://docs.customer.io/integrations/data-in/connections/javascript/in-app/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/javascript/in-app/How it works In-app messages for your website work differently than push notifications would: they require JavaScript, and they don’t go through a push notification service (like APNs or FCM). In most cases, you simply need to identify your web visitors, and they’ll become eligible to receive your in-app messages. sequenceDiagram Participant a as App User Participant b as JavaScript Client Participant c as Customer.io c->>c: Trigger in-app message c-->>b: If app isn't open, holdhttps://docs.customer.io/integrations/data-in/connections/javascript/legacy-js/in-app/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/javascript/legacy-js/in-app/How it works In-app messages for your website work differently than push notifications would: they require JavaScript, and they don’t go through a push notification service (like APNs or FCM). This means that as long as you identify your web visitors, and those visitors don’t disable JavaScript, you can send in-app messages to people. sequenceDiagram Participant a as App User Participant b as SDK Participant c as Customer.io c->>c: Trigger in-app message c-->>b: If app isn't open, holdhttps://docs.customer.io/integrations/sdk/android/3.x/in-app/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/android/3.x/in-app/This page is part of a setup flow for the SDK. Before you continue, make sure you've implemented previous features—i.e. you can't receive in-app notifications before you identify people! graph LR getting-started(Install SDK) -->B(Initialize SDK) B --> identify(identify people) identify -.-> track-events(Send events) identify -.-> push(Receive push) identify -.-> rich-push(Receive Rich Push) track-events --> test-support(Write tests) push --> test-support rich-push --> test-support identify -.-> in-app(Receive in-app) in-app --> test-support click getting-started href "https://docs.customer.io/integrations/sdk/flutter/1.x/in-app-messages/in-app/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/flutter/1.x/in-app-messages/in-app/This page is part of a setup flow for the SDK. Before you continue, make sure you've implemented previous features—i.e. you can't receive in-app notifications before you identify people! graph LR getting-started(Install SDK) -->B(Initialize SDK) B --> identify(identify people) identify -.-> track-events(Send events) identify -.-> push(Receive push) identify -.-> in-app(Receive in-app) click getting-started href "/integrations/sdk/flutter/getting-started/#install" click B href "/integrations/sdk/flutter/getting-started/#initialize-the-sdk" click identify href "/integrations/sdk/flutter/identify" click track-events href "/integrations/sdk/flutter/track-events/" click register-token href "https://docs.customer.io/integrations/sdk/ios/1.x/in-app/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/1.x/in-app/This page is part of a setup flow for the SDK. Before you continue, make sure you've implemented previous features—i.e. you can't receive in-app notifications before you identify people! graph LR getting-started(Install SDK) -->B(Initialize SDK) B --> identify(identify people) identify -.-> track-events(Send events) identify -.-> register-token(Register Device Token) register-token -.-> push(Receive push) register-token -.-> rich-push(Receive Rich Push) track-events --> test-support(Write tests) push --> test-support rich-push --> test-support identify -.-> in-app(Receive in-app) in-app --> test-support click getting-started href "https://docs.customer.io/integrations/sdk/ios/2.x/in-app/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/2.x/in-app/This page is part of a setup flow for the SDK. Before you continue, make sure you've implemented previous features—i.e. you can't receive in-app notifications before you identify people! graph LR getting-started(Install SDK) -->B(Initialize SDK) B --> identify(identify people) identify -.-> track-events(Send events) identify -.-> register-token(Register Device Token) register-token -.-> push(Receive push) register-token -.-> rich-push(Receive Rich Push) track-events --> test-support(Write tests) push --> test-support rich-push --> test-support identify -.-> in-app(Receive in-app) in-app --> test-support click getting-started href "https://docs.customer.io/integrations/data-in/connections/javascript/inbox/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/javascript/inbox/How it works Unlike other messages, inbox messages don’t necessarily appear immediately to users, and they don’t disappear when the user dismisses them. Instead, you’ll display these messages through a notification inbox that your audience can access at their leisure. Customer.io also doesn’t deliver rendered inbox messages; they’re delivered as JSON payloads. The SDK helps you listen for these payloads, but you’ll determine how to display them in your own inbox client.https://docs.customer.io/integrations/sdk/android/in-app/inbox/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/android/in-app/inbox/How it works Unlike other messages, inbox messages don’t necessarily appear immediately to users, and they don’t disappear when the user dismisses them. Instead, you’ll display these messages through a notification inbox that your audience can access at their leisure. Customer.io delivers inbox messages as JSON payloads, not fully-rendered messages. The SDK helps you listen for these payloads, but you’ll determine how to display them in your own inbox client.https://docs.customer.io/integrations/sdk/expo/in-app-messages/inbox/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/expo/in-app-messages/inbox/How it works Unlike other messages, inbox messages don’t necessarily appear immediately to users, and they don’t disappear when the user dismisses them. Instead, you’ll display these messages through a notification inbox that your audience can access at their leisure. Customer.io delivers inbox messages as JSON payloads, not fully-rendered messages. The SDK helps you listen for these payloads, but you’ll determine how to display them in your own inbox client.https://docs.customer.io/integrations/sdk/flutter/in-app-messages/inbox/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/flutter/in-app-messages/inbox/How it works Unlike other messages, inbox messages don’t necessarily appear immediately to users, and they don’t disappear when the user dismisses them. Instead, you’ll display these messages through a notification inbox that your audience can access at their leisure. Customer.io delivers inbox messages as JSON payloads, not fully-rendered messages. The SDK helps you listen for these payloads, but you’ll determine how to display them in your own inbox client.https://docs.customer.io/integrations/sdk/ios/in-app/inbox/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/in-app/inbox/How it works Unlike other messages, inbox messages don’t necessarily appear immediately to users, and they don’t disappear when the user dismisses them. Instead, you’ll display these messages through a notification inbox that your audience can access at their leisure. Customer.io delivers inbox messages as JSON payloads, not fully-rendered messages. The SDK helps you listen for these payloads, but you’ll determine how to display them in your own inbox client.https://docs.customer.io/integrations/sdk/react-native/in-app-messages/inbox/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/in-app-messages/inbox/How it works Unlike other messages, inbox messages don’t necessarily appear immediately to users, and they don’t disappear when the user dismisses them. Instead, you’ll display these messages through a notification inbox that your audience can access at their leisure. Customer.io delivers inbox messages as JSON payloads, not fully-rendered messages. The SDK helps you listen for these payloads, but you’ll determine how to display them in your own inbox client.https://docs.customer.io/journeys/sms-keyword-opt-out/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/sms-keyword-opt-out/How it works While Customer.io doesn’t receive SMS replies directly, we capture opt-in and opt-out information from Twilio so that we respect your audience’s preferences and show you which numbers people have opted out of. We show a list of opt-outs in the SMS Opt-outs section of any person’s profile. This list updates in near real-time as people opt out or back into SMS messaging for a given phone number.https://docs.customer.io/journeys/schedule-campaigns/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/schedule-campaigns/How it works When you schedule a campaign, Customer.io automatically manages it based on your specified times: Start time: When the campaign starts to trigger and process journeys Stop time: When the campaign stops accepting new people Scheduled campaigns display a “Scheduled” label next to their status indicator. The “Scheduled” label shows that a start and/or stop time is set, while the status (like “Running”, “Draft”, or “Stopped”) shows the campaign’s current state.https://docs.customer.io/integrations/sdk/expo/1.x/in-app/in-app/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/expo/1.x/in-app/in-app/This page is part of a setup flow for the SDK. Before you continue, make sure you've implemented previous features—i.e. you can't receive in-app notifications before you identify people! graph LR getting-started(Install SDK) -->B(Initialize SDK) B --> identify(identify people) identify -.-> track-events(Send events) identify -.-> push(Receive push) identify -.-> in-app(Receive in-app) click getting-started href "/integrations/sdk/expo/getting-started/#install" click B href "/integrations/sdk/expo/getting-started/#initialize-the-sdk" click identify href "/integrations/sdk/expo/identify" click track-events href "/integrations/sdk/expo/track-events/" click register-token href "https://docs.customer.io/integrations/sdk/expo/in-app-messages/in-app/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/expo/in-app-messages/in-app/How it works Unlike push notifications, where you need to add settings to your Expo plugins, in-app messaging is enabled automatically. You simply need to add an inApp object with your site_id to your CioConfig to support in-app messages. An in-app message is a message that people see in your app. If you set an expiry period for your message, and that time elapses before someone opens your app, they won’t see your message.https://docs.customer.io/integrations/sdk/flutter/1.x/in-app-messages/in-app-actions/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/flutter/1.x/in-app-messages/in-app-actions/How it works In-app messages often have a call to action. Most basic actions are handled automatically by the SDK. For example, if you set a call-to-action button to open a web page, the SDK will open the web page when the user taps the button. But you can also set up custom actions that require your app to handle the response. If you set up custom actions, you’ll need to handle the action yourself and dismiss the resulting message when you’re done with it.https://docs.customer.io/integrations/sdk/flutter/2.x/in-app-messages/in-app-actions/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/flutter/2.x/in-app-messages/in-app-actions/How it works In-app messages often have a call to action. Most basic actions are handled automatically by the SDK. For example, if you set a call-to-action button to open a web page, the SDK will open the web page when the user taps the button. But you can also set up custom actions that require your app to handle the response. If you set up custom actions, you’ll need to handle the action yourself and dismiss the resulting message when you’re done with it.https://docs.customer.io/integrations/sdk/flutter/in-app-messages/in-app-actions/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/flutter/in-app-messages/in-app-actions/How it works In-app messages often have a call to action. Most basic actions are handled automatically by the SDK. For example, if you set a call-to-action button to open a web page, the SDK will open the web page when the user taps the button. But you can also set up custom actions that require your app to handle the response. If you set up custom actions, you’ll need to handle the action yourself and dismiss the resulting message when you’re done with it.https://docs.customer.io/integrations/sdk/react-native/4.x/whats-new/update-to-3.4/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/4.x/whats-new/update-to-3.4/Upgrade from 3.3 to 3.4+ As of version 3.4, the Customer.io SDK automatically registers push device tokens to identified people and handles push clicks. These features simplify your SDK integration while improving compatibility with apps that use multiple push SDKs. After you install a version of the SDK that is 3.4 or higher, follow these steps to upgrade.  Do you have a swift app? Skip ahead! If you’ve got a Swift app containing the AppDelegate.https://docs.customer.io/integrations/sdk/react-native/5.x/whats-new/update-to-3.4/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/5.x/whats-new/update-to-3.4/Upgrade from 3.3 to 3.4+ As of version 3.4, the Customer.io SDK automatically registers push device tokens to identified people and handles push clicks. These features simplify your SDK integration while improving compatibility with apps that use multiple push SDKs. After you install a version of the SDK that is 3.4 or higher, follow these steps to upgrade.  Do you have a swift app? Skip ahead! If you’ve got a Swift app containing the AppDelegate.https://docs.customer.io/integrations/sdk/react-native/whats-new/update-to-3.4/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/whats-new/update-to-3.4/Upgrade from 3.3 to 3.4+ As of version 3.4, the Customer.io SDK automatically registers push device tokens to identified people and handles push clicks. These features simplify your SDK integration while improving compatibility with apps that use multiple push SDKs. After you install a version of the SDK that is 3.4 or higher, follow these steps to upgrade.  Do you have a swift app? Skip ahead! If you’ve got a Swift app containing the AppDelegate.https://docs.customer.io/integrations/data-in/connections/salesforce/api-calls-simulator/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/salesforce/api-calls-simulator/Number of records for initial sync: Number of new/updated records per sync: Sync interval: Minutes Hours Days Weeks Use Bulk API: Bulk API REST API We require one REST call at the start of each sync, to fetch the record's fields configuration. Number of API calls for initial sync For the initial sync, we fetch all data going back to the epoch (Jan 1st 1970). We break that data down into 30-day increments, and that's how we get to such a specific (and static) number here.https://docs.customer.io/accounts-and-workspaces/canceling/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/accounts-and-workspaces/canceling/We really hate to see you go, but we understand sometimes things change. Before you part, though, we’d love it if you’d get in touch with our team and let us know if there is something we can do better. If something isn’t working right or you’re finding a feature difficult to use, we want to make it better! How to cancel How you cancel depends on your plan type.https://docs.customer.io/journeys/campaign-statuses/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/campaign-statuses/Campaigns can have one of four statuses: running - active draft - inactive; all campaigns start in a draft state. stopped - inactive archived - inactive Running is the only active status. This means customers can enter your campaign and move through your workflow, which could include messages, update actions, and more. You can edit these campaigns while they’re live, but make sure you understand how live edits impact your customers.https://docs.customer.io/journeys/bcc-trustpilot/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/bcc-trustpilot/If you want to send Trustpilot reviews through Customer.io, you can either integrate with Zapier or follow the steps below. In this guide, you BCC Trustpilot in an email and include certain metadata, no formal integration required.  Use the code editor You must create the email with our code editor to ensure the metadata is not stripped from the email. Obtain your unique BCC address from Trustpilot. In Customer.io, drag an email block onto your campaign or API-triggered broadcast.https://docs.customer.io/journeys/action-conditions/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/action-conditions/Click an action to edit conditions: Hover over the condition on the action to see the details: How they work Conditions are optional checks you can add to any message, data block, or delay in your campaign. We check the conditions before initiating the block’s action (sending a message, starting a delay timer, or sending a webhook, for instance). If people don’t meet the conditions, they skip the action and continue through the campaign.https://docs.customer.io/journeys/double-opt-in/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/double-opt-in/Introduction This document will guide you through the basics of setting up double opt-in functionality for your users. A double opt-in is a good practice to follow in order to improve your deliverability and/or comply with local laws like CASL in Canada. Ingredients A double_optin attribute to track each person’s status A data-driven segment, either for people without the double_optin attribute or for new users depending on your strategy A segment-triggered campaign where we’ll send an email with a link people can click to opt in Another data-driven segment for people who have clicked the opt-in link link Method Create a segment to trigger the campaign First and foremost, we’ll need an attribute for each person that tracks whether or not they’ve been through the double-opt in process, and what they’ve chosen.https://docs.customer.io/journeys/drag-and-drop-faq/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/drag-and-drop-faq/We’ve built and tested this editor as much as we can to pick out scenarios you may want help with, but this definitely isn’t an exhaustive list! If you have a question that isn’t addressed here, please reach out and we’ll do our best to help. Can I edit the HTML of drag-and-drop emails? This editor is built specifically to assemble emails quickly without knowledge of HTML or CSS. You can add blocks of HTML to your email, but there is no way to view all body HTML like there is with the code editor.https://docs.customer.io/journeys/conclusive-ab-results/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/conclusive-ab-results/For instance, how do you know that your most engaged users didn’t happen to end up getting the same variation by random chance? Calculating statistical significance is a way of determining how confident you can be that the results of a test are because one variation is more effective than the other. Let’s take an example: If I want to test whether one email subject line causes more opens than another, and variation A has a 60% open rate and variation B has a 40% open rate, then variation A is the more successful subject line, right?https://docs.customer.io/integrations/sdk/expo/1.x/in-app/handling-and-dismissing-actions/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/expo/1.x/in-app/handling-and-dismissing-actions/How it works In-app messages often have a call to action. Most basic actions are handled automatically by the SDK. For example, if you set a call-to-action button to open a web page, the SDK will open the web page when the user taps the button. But you can also set up custom actions that require your app to handle the response. If you set up custom actions, you’ll need to handle the action yourself and dismiss the resulting message when you’re done with it.https://docs.customer.io/integrations/sdk/expo/in-app-messages/handling-and-dismissing-actions/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/expo/in-app-messages/handling-and-dismissing-actions/How it works In-app messages often have a call to action. Most basic actions are handled automatically by the SDK. For example, if you set a call-to-action button to open a web page, the SDK will open the web page when the user taps the button. But you can also set up custom actions that require your app to handle the response. If you set up custom actions, you’ll need to handle the action yourself and dismiss the resulting message when you’re done with it.https://docs.customer.io/integrations/sdk/android/tracking/location/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/android/tracking/location/How it works The Location module captures location (with user consent) from your app and attaches it to a person’s profile in Customer.io. You can use this data for geo-aware messaging and audience segmentation with more accuracy than IP-based geolocation. When you identify a person, the SDK includes the latest location in the identify call. The SDK also sends a Location Update event to the person’s activity timeline, which you can use in journeys and segments.https://docs.customer.io/integrations/sdk/expo/tracking/location/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/expo/tracking/location/How it works The Location module captures location (with user consent) from your app and attaches it to a person’s profile in Customer.io. You can use this data for geo-aware messaging and audience segmentation with more accuracy than IP-based geolocation. When you identify a person, the SDK includes the latest location in the identify call. The SDK also sends a Location Update event to the person’s activity timeline, which you can use in journeys and segments.https://docs.customer.io/integrations/sdk/flutter/tracking/location/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/flutter/tracking/location/How it works The Location module captures location (with user consent) from your app and attaches it to a person’s profile in Customer.io. You can use this data for geo-aware messaging and audience segmentation with more accuracy than IP-based geolocation. When you identify a person, the SDK includes the latest location in the identify call. The SDK also sends a Location Update event to the person’s activity timeline, which you can use in journeys and segments.https://docs.customer.io/integrations/sdk/ios/tracking/location/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/tracking/location/How it works The Location module captures location (with user consent) from your app and attaches it to a person’s profile in Customer.io. You can use this data for geo-aware messaging and audience segmentation with more accuracy than IP-based geolocation. When you identify a person, the SDK includes the latest location in the identify call. The SDK also sends a Location Update event to the person’s activity timeline, which you can use in journeys and segments.https://docs.customer.io/integrations/sdk/react-native/tracking/location/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/tracking/location/How it works The Location module captures location (with user consent) from your app and attaches it to a person’s profile in Customer.io. You can use this data for geo-aware messaging and audience segmentation with more accuracy than IP-based geolocation. When you identify a person, the SDK includes the latest location in the identify call. The SDK also sends a Location Update event to the person’s activity timeline, which you can use in journeys and segments.https://docs.customer.io/accounts-and-workspaces/security/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/accounts-and-workspaces/security/ See our full security policy You can read more about our security practices on our website and download our compliance documents. Login sessions are managed via secure HTTP cookie We manage your session in Customer.io with a secure HTTP cookie. The cookie can only be read by the browser, protecting your session from unauthorized access and malicious cross-site scripting (XSS) attacks. If you’re an admin you can set the expiration time for sessions between 1 hour and 14 days depending on your security policy.https://docs.customer.io/accounts-and-workspaces/security-best-practices/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/accounts-and-workspaces/security-best-practices/1. Do not share login credentials Add named accounts for all of the people in your team who will be collaborating on your messaging content and strategy. Customer.io allows you to add as many team members as you need - with different levels of access. 2. Limit your team to the access level they need When you add team members, you can set their permissions at the account and workspace levels.https://docs.customer.io/journeys/push-qa-testing/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/push-qa-testing/For example, if you have an iOS app, you may have a sandbox environment set up to test your push notifications before you start your campaigns. This often has the same certification credentials as your production environment. We still recommend setting up a separate test workspace with the “Send to sandbox” option turned on: To send any type of test message, you’ll need a device token. Here’s how to find one.https://docs.customer.io/integrations/sdk/android/2.x/test-support/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/android/2.x/test-support/This page is part of a setup flow for the SDK. Before you continue, make sure you've implemented previous features—i.e. you can't receive in-app notifications before you identify people! graph LR getting-started(Install SDK) -->B(Initialize SDK) B --> identify(identify people) identify -.-> track-events(Send events) identify -.-> push(Receive push) identify -.-> rich-push(Receive Rich Push) track-events --> test-support(Write tests) push --> test-support rich-push --> test-support identify -.-> in-app(Receive in-app) in-app --> test-support click getting-started href "https://docs.customer.io/integrations/sdk/android/3.x/test-support/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/android/3.x/test-support/This page is part of a setup flow for the SDK. Before you continue, make sure you've implemented previous features—i.e. you can't receive in-app notifications before you identify people! graph LR getting-started(Install SDK) -->B(Initialize SDK) B --> identify(identify people) identify -.-> track-events(Send events) identify -.-> push(Receive push) identify -.-> rich-push(Receive Rich Push) track-events --> test-support(Write tests) push --> test-support rich-push --> test-support identify -.-> in-app(Receive in-app) in-app --> test-support click getting-started href "https://docs.customer.io/integrations/sdk/ios/1.x/test-support/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/1.x/test-support/This page is part of a setup flow for the SDK. Before you continue, make sure you've implemented previous features—i.e. you can't receive in-app notifications before you identify people! graph LR getting-started(Install SDK) -->B(Initialize SDK) B --> identify(identify people) identify -.-> track-events(Send events) identify -.-> register-token(Register Device Token) register-token -.-> push(Receive push) register-token -.-> rich-push(Receive Rich Push) track-events --> test-support(Write tests) push --> test-support rich-push --> test-support identify -.-> in-app(Receive in-app) in-app --> test-support click getting-started href "https://docs.customer.io/integrations/sdk/ios/2.x/test-support/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/2.x/test-support/This page is part of a setup flow for the SDK. Before you continue, make sure you've implemented previous features—i.e. you can't receive in-app notifications before you identify people! graph LR getting-started(Install SDK) -->B(Initialize SDK) B --> identify(identify people) identify -.-> track-events(Send events) identify -.-> register-token(Register Device Token) register-token -.-> push(Receive push) register-token -.-> rich-push(Receive Rich Push) track-events --> test-support(Write tests) push --> test-support rich-push --> test-support identify -.-> in-app(Receive in-app) in-app --> test-support click getting-started href "https://docs.customer.io/journeys/timestamp-rules/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/timestamp-rules/Introduction Timestamp rules aren’t always easy. You want to make sure you send opportune messages and campaigns to your users, using timestamp rules in your segments. But this process may require some deep thinking around when things happen, not just for one person but for a lot of people, and when you want your campaign to go out in relation. To help you get going, we’ve put together a couple of quick timestamp segment recipes and explanations here, with common use cases in mind.https://docs.customer.io/journeys/triggered-lifecycle-email-with-mandrill/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/triggered-lifecycle-email-with-mandrill/ Mandrill is designed for transactional messages only Mailchimp’s acceptable use policy prohibits the sending of bulk emails—emails directed to multiple individuals with the same content—through Mandrill. You can use your Mandrill account to send email through Customer.io with no loss in functionality. To take advantage of Mandrill, you need to do two things: Point Mandrill’s webhooks at Customer.io. Configure Mandrill as a custom SMTP server in Customer.io. Point Mandrill’s webhooks at Customer.https://docs.customer.io/journeys/triggered-lifecycle-email-with-postmark/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/triggered-lifecycle-email-with-postmark/You can use your Postmark account to send email through Customer.io with no loss in functionality. To take advantage of Postmark, you need to do two things: Point Postmark’s webhooks at Customer.io. Configure Postmark as a custom SMTP server in Customer.io. Point Postmark’s webhooks at Customer.io Log into Postmark. Select your server, the Message Stream you’ll be sending emails from, and then the Webhooks tab. Click Add webhook and enter the webhook URL that corresponds to your region in the Webhook URL field.https://docs.customer.io/integrations/data-in/connections/javascript/content-security-policy/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/javascript/content-security-policy/A Content Security Policy (CSP) is a standard that helps you control the resources that a web browser can load on your page. If you enforce a CSP on your website, you need to allow the domains that our JavaScript client communicates with.  If you’re using our legacy JavaScript snippet, where calls use the _cio prefix, see the legacy CSP page instead. Standard directives US data center US data center script-src cdp.https://docs.customer.io/journeys/push-notifications-tracking/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/push-notifications-tracking/How it works While we track the status of each individual message as it goes through Customer.io, push notifications can be trickier to track than other message channels for two main reasons: A person can have multiple devices, and you can send a message to all of a person’s devices. When you send to All Devices, we aggregate metrics across all of a person’s devices because we (and you!) monitor engagement at a personal level, not a device level.https://docs.customer.io/integrations/sdk/ios/2.x/update-210-to-211/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/2.x/update-210-to-211/Upgrade from 2.10 to 2.11+ As of version 2.11, the Customer.io SDK automatically registers push device tokens to identified people and automatically handles push clicks. These features let you simplify your SDK integration while also improving the reliability of device tokens and opened metrics. After you install version 2.11 or later: Open your AppDelegate file and review the highlighted code in the sample below. You can remove all of the highlighted code from your app.https://docs.customer.io/integrations/sdk/ios/3.x/whats-new/2.x-upgrade/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/3.x/whats-new/2.x-upgrade/Versioning We try to limit breaking or significant changes to major version increments. The three digits in our versioning scheme represent major, minor, and patch increments respectively. Major: may include breaking changes, and generally introduces significant feature updates. Minor: may include new features and fixes, but won’t include breaking changes. You may still need to do some development to use new features in your app. Patch: Increments represent minor fixes that should not require development effort.https://docs.customer.io/integrations/sdk/ios/whats-new/2.x-upgrade/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/whats-new/2.x-upgrade/Versioning We try to limit breaking or significant changes to major version increments. The three digits in our versioning scheme represent major, minor, and patch increments respectively. Major: may include breaking changes, and generally introduces significant feature updates. Minor: may include new features and fixes, but won’t include breaking changes. You may still need to do some development to use new features in your app. Patch: Increments represent minor fixes that should not require development effort.https://docs.customer.io/integrations/sdk/android/whats-new/3.x-upgrade/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/android/whats-new/3.x-upgrade/Versioning We try to limit breaking or significant changes to major version increments. The three digits in our versioning scheme represent major, minor, and patch increments respectively. Major: may include breaking changes, and generally introduces significant feature updates. Minor: may include new features and fixes, but won’t include breaking changes. You may still need to do some development to use new features in your app. Patch: Increments represent minor fixes that should not require development effort.https://docs.customer.io/integrations/sdk/react-native/4.x/whats-new/update-to-3x/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/4.x/whats-new/update-to-3x/Versioning We try to limit breaking or significant changes to major version increments. The three digits in our versioning scheme represent major, minor, and patch increments respectively. Major: may include breaking changes, and generally introduces significant feature updates. Minor: may include new features and fixes, but won’t include breaking changes. You may still need to do some development to use new features in your app. Patch: Increments represent minor fixes that should not require development effort.https://docs.customer.io/integrations/sdk/react-native/5.x/whats-new/update-to-3x/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/5.x/whats-new/update-to-3x/Versioning We try to limit breaking or significant changes to major version increments. The three digits in our versioning scheme represent major, minor, and patch increments respectively. Major: may include breaking changes, and generally introduces significant feature updates. Minor: may include new features and fixes, but won’t include breaking changes. You may still need to do some development to use new features in your app. Patch: Increments represent minor fixes that should not require development effort.https://docs.customer.io/integrations/sdk/react-native/whats-new/update-to-3x/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/whats-new/update-to-3x/Versioning We try to limit breaking or significant changes to major version increments. The three digits in our versioning scheme represent major, minor, and patch increments respectively. Major: may include breaking changes, and generally introduces significant feature updates. Minor: may include new features and fixes, but won’t include breaking changes. You may still need to do some development to use new features in your app. Patch: Increments represent minor fixes that should not require development effort.https://docs.customer.io/journeys/push-best-practices/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/push-best-practices/1. Keep the Customer.io SDK up to date Mobile operating systems regularly change and we’re constantly improving our SDKs—both to account for changes in mobile ecosystems and to better support Customer.io features. You’ll have the best mobile experience if you keep your SDK up to date. You can subscribe to SDKs to find out when we release new versions. Or check for updates here. Our SDKs use three version numbers in the format major.https://docs.customer.io/integrations/data-in/source-spec/common-fields/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/source-spec/common-fields/How it works When you send a call to Customer.io, we capture additional information from our libraries and information implicit in each call, like: context for the source of your calls the ip and locale of the person the call represents timestamps that help you understand the chronology of your data The added context these common fields provide can help you debug issues with your data or add special handling in actionsThe source event and data that triggers an API call to your destination.https://docs.customer.io/integrations/data-in/connections/javascript/legacy-js/content-security-policy/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/javascript/legacy-js/content-security-policy/Required CSP Directives for Accounts on the US Data Center script-src assets.customer.io code.gist.build customerioforms.com 'unsafe-inline' 'unsafe-eval'; connect-src track.customer.io customerioforms.com *.api.gist.build *.cloud.gist.build; frame-src renderer.gist.build code.gist.build; style-src code.gist.build 'unsafe-inline'; img-src track.customer.io; Required CSP Directives for Accounts on the EU Data Center script-src assets.customer.io code.gist.build eu.customerioforms.com 'unsafe-inline' 'unsafe-eval'; connect-src track-eu.customer.io eu.customerioforms.com *.api.gist.build *.cloud.gist.build; frame-src renderer.gist.build code.gist.build; style-src code.gist.build 'unsafe-inline'; img-src track-eu.customer.io; Glossary of Directives Directive: script-src Host Description assets.customer.io Location of the Customer.io javascript file, referenced in the installation snippet.https://docs.customer.io/journeys/push-faq/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/push-faq/How do conversions work with push notifications? Conversions are attributed to the last email or message sent, opened, or clicked before the person performs an event or enters/leaves a segment defined in your conversion criteria. If you track users performing an action or entering a segment after receiving a push, then the message will be marked as converted, regardless of the device we reached them on. What Firebase permissions does Customer.https://docs.customer.io/journeys/holdout-test/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/holdout-test/How it works A holdout is a type of A/B or random cohort test for email messages. But, rather than testing how your audience responds to variations of a message, some members of your audience will receive a message, and some won’t—they’re purposely “held out” of the test. This helps you determine whether a message is useful or not. When you setup a holdout test in your campaign, you’ll determine the percentage of your audience you want to prevent from receiving a message.https://docs.customer.io/journeys/localize-in-app-message/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/localize-in-app-message/How it works Customer.io has built-in localization features to help you deliver messages in the language your audience uses. You can send your audience translated versions of a message based on a specific attribute in Customer.io. This means that you’ll need to store language information in Customer.io. When a customer’s language attribute matches a localized version of your message, we’ll deliver that message to them. If we don’t have a localized version of your message for a customer’s language, we’ll deliver a “default” message.https://docs.customer.io/integrations/sdk/android/2.x/migrate-upgrade/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/android/2.x/migrate-upgrade/Versioning We try to limit breaking or significant changes to major version increments. The three digits in our versioning scheme represent major, minor, and patch increments respectively. Major: may include breaking changes, and generally introduces significant feature updates. Minor: may include new features and fixes, but won’t include breaking changes. You may still need to do some development to use new features in your app. Patch: Increments represent minor fixes that should not require development effort.https://docs.customer.io/integrations/sdk/android/3.x/migrate-upgrade/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/android/3.x/migrate-upgrade/Versioning We try to limit breaking or significant changes to major version increments. The three digits in our versioning scheme represent major, minor, and patch increments respectively. Major: may include breaking changes, and generally introduces significant feature updates. Minor: may include new features and fixes, but won’t include breaking changes. You may still need to do some development to use new features in your app. Patch: Increments represent minor fixes that should not require development effort.https://docs.customer.io/integrations/sdk/ios/2.x/migrate-upgrade/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/2.x/migrate-upgrade/Versioning We try to limit breaking or significant changes to major version increments. The three digits in our versioning scheme represent major, minor, and patch increments respectively. Major: may include breaking changes, and generally introduces significant feature updates. Minor: may include new features and fixes, but won’t include breaking changes. You may still need to do some development to use new features in your app. Patch: Increments represent minor fixes that should not require development effort.https://docs.customer.io/integrations/sdk/react-native/2.x/updates-and-troubleshooting/migrate-upgrade/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/2.x/updates-and-troubleshooting/migrate-upgrade/Versioning We try to limit breaking or significant changes to major version increments. The three digits in our versioning scheme represent major, minor, and patch increments respectively. Major: may include breaking changes, and generally introduces significant feature updates. Minor: may include new features and fixes, but won’t include breaking changes. You may still need to do some development to use new features in your app. Patch: Increments represent minor fixes that should not require development effort.https://docs.customer.io/integrations/sdk/react-native/3.x/updates-and-troubleshooting/migrate-upgrade/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/3.x/updates-and-troubleshooting/migrate-upgrade/Versioning We try to limit breaking or significant changes to major version increments. The three digits in our versioning scheme represent major, minor, and patch increments respectively. Major: may include breaking changes, and generally introduces significant feature updates. Minor: may include new features and fixes, but won’t include breaking changes. You may still need to do some development to use new features in your app. Patch: Increments represent minor fixes that should not require development effort.https://docs.customer.io/accounts-and-workspaces/mobile-privacy/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/accounts-and-workspaces/mobile-privacy/Take immediate action before May 1, 2024 Beginning May 1, 2024, Apple’s App store requires SDKs to include a privacy manifest describing the data they collect and use. This includes Customer.io’s SDKs! To ensure that your app meets Apple’s requirements, you must update the Customer.io SDK to a version that includes the privacy manifest. If you don’t, your app may be rejected from the App Store. Update to the following versions (or later):https://docs.customer.io/journeys/onboarding-campaign/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/onboarding-campaign/Introduction After someone signs up for your app, the task of onboarding them begins! Show how they can get value from your app and improve your user activation and retention rates. Thoughtful onboarding email campaigns are a win for everyone. This recipe will show you how to set up targeted drip series using segment triggered campaigns in Customer.io to keep people interested, learning, and making progress. Ingredients Choose a specific behavioral goal that is key to your onboarding process Optional: basic knowledge of Liquid Method While you can have several onboarding campaigns for your customers, each campaign should be focused on nudging them towards a particular goal.https://docs.customer.io/accounts-and-workspaces/privacy/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/accounts-and-workspaces/privacy/Account privacy settings You’ll find information about our privacy policy and some settings related to your privacy under Settings > Privacy, Data, & AI. Cookie settings The Performance and troubleshooting setting is enabled by default and lets us use cookies within fly.customer.io that help us track activity that we can use to troubleshoot issues in your account and workspaces. You can disable these cookies, but it may hamper our ability to troubleshoot problems you might have.https://docs.customer.io/integrations/data-in/connections/javascript/js-source-proxy/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/javascript/js-source-proxy/How it works When you load Analytics.js on your site, the script makes requests to Customer.io to load the library and to send calls. You can proxy these requests through your own domain, making all Customer.io requests look like first-party requests to your own domain. This can help you avoid problems with ad blockers or firewalls that don’t play nicely with third-party domains or requests. This page shows how to set up a custom domain that proxies to cdp.https://docs.customer.io/accounts-and-workspaces/user-privacy/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/accounts-and-workspaces/user-privacy/Cookies (when using our JavaScript libraries) Our two client-side JavaScript libraries both use cookies that make it easier to recognize your audience and use them across calls to Customer.io. Journeys JavaScript SDK The Journeys Web SDK sets cookies to determine whether someone is anonymous or identified. These cookies do not contain any personally identifiable information (PII). _cioanonid: contains an anonymous ID that the tracking snippet sets automatically on a person who has not been identified yet.https://docs.customer.io/journeys/filter-search/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/filter-search/By email If you’d like to find a person by their email address, you can do so via the input box at the top of the page: If you remember what the user’s email starts with, enter it here and then click to search. Searching for tweety, for example, would return results like: tweety@acmecorp.com tweety.bird@acmecorp.com tweety@acme.com tweetyandsylvester@gmail.com  This will not return email addresses that contain your search term somewhere in the middle.https://docs.customer.io/journeys/troubleshooting-mobile/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/troubleshooting-mobile/ This page is focused on our SDKs If you’ve written your own mobile integration with Customer.io, we may not be able to troubleshoot your app. Before you contact Customer.io Support If you’re having trouble with push notifications and in-app messages, there are a few things you can do to troubleshoot the problem before you contact Customer.io Support. These are common troubleshooting tips that are likely to fix your problem—and are the starting point for most of our SDK-related support conversations.https://docs.customer.io/journeys/troubleshooting-email-design/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/troubleshooting-email-design/Errors in email content We’ll let you know of any errors in your email content in the buttons at the top of the editor. If there are none, the buttons look like this. If there are problems, though, the button will change to “Review Errors” and animate to get your attention! Click Review Errors to see a pop-up window describing the error(s): Learn more about errors you could encounter while composing an email.https://docs.customer.io/accounts-and-workspaces/two-factor-auth/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/accounts-and-workspaces/two-factor-auth/What is two-factor authentication? Two-Factor Authentication (2FA) is an additional layer of security on your Customer.io account. By default, we require you verify your login attempt through a magic link sent to your email. You can alternatively enable 2FA through an authentication app. Why do you need it? If your regular password is ever compromised or stolen, 2FA ensures that only you can log into your account because only you have the magic link or authentication code.https://docs.customer.io/integrations/sdk/flutter/1.x/updates-and-troubleshooting/migrate-upgrade/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/flutter/1.x/updates-and-troubleshooting/migrate-upgrade/Upgrade native iOS SDK to 2.11+ As of version 2.11, the native iOS Customer.io SDK automatically handles push clicks. These features simplify your SDK integration while improving the reliability of opened metrics tracking and increasing compatibility with other push modules you may have installed in your app. Follow our native iOS update guide to update the Flutter and iOS SDK to use the latest version. Open your AppDelegate file and review all of the highlighted code below in this sample.https://docs.customer.io/integrations/sdk/react-native/3.x/updates-and-troubleshooting/update-to-3.4/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/3.x/updates-and-troubleshooting/update-to-3.4/Upgrade from 3.3 to 3.4+ As of version 3.4, the Customer.io SDK automatically registers push device tokens to identified people and handles push clicks. These features simplify your SDK integration while improving compatibility with apps that use multiple push SDKs. After you install a version of the SDK that is 3.4 or higher, follow these steps to upgrade.  Do you have a swift app? Skip ahead! If you’ve got a Swift app containing the AppDelegate.https://docs.customer.io/journeys/triggered-lifecycle-email-with-sendgrid/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/triggered-lifecycle-email-with-sendgrid/You can use your SendGrid account to send email through Customer.io with no loss in functionality. To take advantage of SendGrid, you need to do two things: Point SendGrid’s webhooks at Customer.io. Configure SendGrid as a custom SMTP server in Customer.io. Point SendGrid’s event API at Customer.io Now you’ll need to adjust some settings to make sure your SendGrid account (or subuser) sends Customer.io the right data. Go to Sendgrid. If you have a subuser for sends through Customer.https://docs.customer.io/journeys/past-x-days-help/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/past-x-days-help/Using “within the past X days” to check whether people have or haven’t done certain actions within a certain time can sometimes be tricky, due to how we store data in Customer.io. An example Check out this segment, which aims to identify people who have not made a purchase in the last seven days: What you need to know To match, people must have existed in Customer.io for at least seven days.https://docs.customer.io/journeys/a-b-test-campaigns/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/a-b-test-campaigns/You can test multiple messages in every triggered campaign, though we do recommend sticking to making just one change in your variation. This allows you to get an accurate picture of how that change measures up against the original without being confused by other data points. How do I set up an A/B test? For either email, Push, or SMS messages, this process is the same. First things first, you’ll want to head to the campaign where you want to run your test, and create the type of message you want to test—email or push notification.https://docs.customer.io/journeys/copying-workflow-items/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/copying-workflow-items/ To copy a workflow AND campaign settings, copy the campaign instead! You can duplicate a campaign from the campaigns page or an individual campaign. Copy items from another workflow When you copy items from another workflow, not all of the copied items’ settings carry over to the destination workflow. For instance, if you copy a Create or Update Person action that references trigger data from another campaign, the same logic might not work in the current campaign depending on its trigger.https://docs.customer.io/journeys/in-app-faq/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/in-app-faq/Can I stop an in-app message after it’s sent? In most cases, you can’t stop messages after they’re Sent. You’ll want to set an Expiration period for your messages to make sure that your messages expire when they’re no longer useful. However, if you’re willing to stop a campaign, you can use the Exit Immediately option to cancel in-app messages that have been sent but not opened. Note that stopping messages in this way only works for in-app messages.https://docs.customer.io/accounts-and-workspaces/datetime-displays/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/accounts-and-workspaces/datetime-displays/Overview Throughout Customer.io, we try to give you as much insight as we can into what happens and when. We know that timing of messages is critical, so we want to make sure you know exactly when your messages are sent or drafted, for example, or when a particular user was created. We use your computer’s current time zone for all times, with a few exceptions: In exports, we use Coordinated Universal Time (UTC) timestamps.https://docs.customer.io/journeys/email-code-editor/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/email-code-editor/ Check out Design Studio! Design Studio is our newest, most flexible email editor. Use components to create a block-based email from scratch, and set global styles to create a consistent brand across your messages made in Design Studio. No longer do you have to decide between a visual or code-based editor; you can use both! How it works When you create an email, you can pick the Code option to write your own HTML.https://docs.customer.io/journeys/single-user-export/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/single-user-export/Need to export all data associated with a single person? No problem!  Exports will include all attribute and event data for the selected profiles. If this includes sensitive data, you must purge that data before passing it to customers. Export data for a person Head to the individual Person page for the end-user whose data you need to export, and select the ‘Export Profile Data’ option in the dropdown: This will export all of the data that we have for a specific end-user.https://docs.customer.io/journeys/just-words/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/just-words/How it works Just Words lets you test many variations in one experiment and auto-refresh underperforming content automatically. You’ll create a campaign with an email in Customer.io and connect it to a template in Just Words. Then Just Words will automatically ingest data from Customer.io and update the template with the best performing variation(s). As a part of this process, you’ll add a random cohort branch to a campaign with two paths.https://docs.customer.io/accounts-and-workspaces/login-with-sso/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/accounts-and-workspaces/login-with-sso/ To enable/disable SSO for your account, you must be an Account Admin. How to set up SSO The process for configuring SSO will depend on your specific identity provider (IdP). Customer.io has dedicated integrations with the following providers and protocols: SSO with Google for organizations SSO with Google for consumers SSO with Okta—see SSO with SAML 2.0 for another option SSO with Microsoft Entra SSO with OpenID SSO—works with a variety of providers SSO with SAML 2.https://docs.customer.io/integrations/sdk/android/3.x/troubleshooting/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/android/3.x/troubleshooting/Basic troubleshooting steps Make sure your app meets our prerequisites: Attempting to use our SDK in an environment that doesn’t match our supported versions may result in build errors. Update to the latest version: When troubleshooting problems with our SDKs, we generally recommend that you try updating to the latest version. That helps us weed out issues that might have been seen in previous versions of the SDK. Try running our MCP server: Our MCP server includes an integration tool that can provide immediate help with your implementation, including problems with push and in-app notifications.https://docs.customer.io/integrations/sdk/android/getting-started/troubleshooting/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/android/getting-started/troubleshooting/Basic troubleshooting steps Update to the latest version: When troubleshooting problems with our SDKs, we generally recommend that you try updating to the latest version. That helps us weed out issues that might have been seen in previous versions of the SDK. Try running our MCP server: Our MCP server includes an integration tool that can provide immediate help with troubleshooting your implementation, including problems with push and in-app notifications. See Use our MCP server to troubleshoot your implementation below.https://docs.customer.io/integrations/sdk/expo/1.x/updates-and-troubleshooting/troubleshooting/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/expo/1.x/updates-and-troubleshooting/troubleshooting/Basic troubleshooting steps Make sure your app meets our prerequisites: Attempting to use our SDK in an environment that doesn’t match our supported versions may result in build errors. Update to the latest version: When troubleshooting problems with our SDKs, we generally recommend that you try updating to the latest version. That helps us weed out issues that might have been seen in previous versions of the SDK. Try running our MCP server: Our MCP server includes an integration tool that can provide immediate help with your implementation, including problems with push and in-app notifications.https://docs.customer.io/integrations/sdk/expo/getting-started/troubleshooting/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/expo/getting-started/troubleshooting/Basic troubleshooting steps Make sure your app meets our prerequisites: Attempting to use our SDK in an environment that doesn’t match our supported versions may result in build errors. Update to the latest version: When troubleshooting problems with our SDKs, we generally recommend that you try updating to the latest version. That helps us weed out issues that might have been seen in previous versions of the SDK. Try running our MCP server: Our MCP server includes an integration tool that can provide immediate help with your implementation, including problems with push and in-app notifications.https://docs.customer.io/integrations/sdk/flutter/1.x/updates-and-troubleshooting/troubleshooting/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/flutter/1.x/updates-and-troubleshooting/troubleshooting/Basic troubleshooting steps Make sure your app meets our prerequisites: Attempting to use our SDK in an environment that doesn’t match our supported versions may result in build errors. Update to the latest version: When troubleshooting problems with our SDKs, we generally recommend that you try updating to the latest version. That helps us weed out issues that might have been seen in previous versions of the SDK. Try running our MCP server: Our MCP server includes an integration tool that can provide immediate help with your implementation, including problems with push and in-app notifications.https://docs.customer.io/integrations/sdk/flutter/2.x/getting-started/troubleshooting/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/flutter/2.x/getting-started/troubleshooting/Basic troubleshooting steps Make sure your app meets our prerequisites: Attempting to use our SDK in an environment that doesn’t match our supported versions may result in build errors. Update to the latest version: When troubleshooting problems with our SDKs, we generally recommend that you try updating to the latest version. That helps us weed out issues that might have been seen in previous versions of the SDK. Try running our MCP server: Our MCP server includes an integration tool that can provide immediate help with your implementation, including problems with push and in-app notifications.https://docs.customer.io/integrations/sdk/flutter/getting-started/troubleshooting/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/flutter/getting-started/troubleshooting/Basic troubleshooting steps Make sure your app meets our prerequisites: Attempting to use our SDK in an environment that doesn’t match our supported versions may result in build errors. Update to the latest version: When troubleshooting problems with our SDKs, we generally recommend that you try updating to the latest version. That helps us weed out issues that might have been seen in previous versions of the SDK. Try running our MCP server: Our MCP server includes an integration tool that can provide immediate help with your implementation, including problems with push and in-app notifications.https://docs.customer.io/integrations/sdk/ios/2.x/troubleshooting/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/2.x/troubleshooting/Basic troubleshooting steps Make sure your app meets our prerequisites: Attempting to use our SDK in an environment that doesn’t match our supported versions may result in build errors. Update to the latest version: When troubleshooting problems with our SDKs, we generally recommend that you try updating to the latest version. That helps us weed out issues that might have been seen in previous versions of the SDK. Try running our MCP server: Our MCP server includes an integration tool that can provide immediate help with your implementation, including problems with push and in-app notifications.https://docs.customer.io/integrations/sdk/ios/3.x/getting-started/troubleshooting/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/3.x/getting-started/troubleshooting/Basic troubleshooting steps Update to the latest version: When troubleshooting problems with our SDKs, we generally recommend that you try updating to the latest version. That helps us weed out issues that might have been seen in previous versions of the SDK. Try running our MCP server: Our MCP server includes an integration tool that can provide immediate help with your implementation, including problems with push and in-app notifications. See Use our MCP server to troubleshoot your implementation below.https://docs.customer.io/integrations/sdk/ios/getting-started/troubleshooting/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/getting-started/troubleshooting/Basic troubleshooting steps Update to the latest version: When troubleshooting problems with our SDKs, we generally recommend that you try updating to the latest version. That helps us weed out issues that might have been seen in previous versions of the SDK. Try running our MCP server: Our MCP server includes an integration tool that can provide immediate help with your implementation, including problems with push and in-app notifications. See Use our MCP server to troubleshoot your implementation below.https://docs.customer.io/integrations/sdk/react-native/2.x/updates-and-troubleshooting/troubleshooting/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/2.x/updates-and-troubleshooting/troubleshooting/Basic troubleshooting steps Update to the latest version: When troubleshooting problems with our SDKs, we generally recommend that you try updating to the latest version. That helps us weed out issues that might have been seen in previous versions of the SDK. Try running our MCP server: Our MCP server includes an integration tool that can provide immediate help with your implementation, including problems with push and in-app notifications. See Use our MCP server to troubleshoot your implementation below.https://docs.customer.io/integrations/sdk/react-native/3.x/updates-and-troubleshooting/troubleshooting/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/3.x/updates-and-troubleshooting/troubleshooting/Basic troubleshooting steps Make sure your app meets our prerequisites: Attempting to use our SDK in an environment that doesn’t match our supported versions may result in build errors. Update to the latest version: When troubleshooting problems with our SDKs, we generally recommend that you try updating to the latest version. That helps us weed out issues that might have been seen in previous versions of the SDK. Try running our MCP server: Our MCP server includes an integration tool that can provide immediate help with your implementation, including problems with push and in-app notifications.https://docs.customer.io/integrations/sdk/react-native/4.x/getting-started/troubleshooting/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/4.x/getting-started/troubleshooting/Basic troubleshooting steps Make sure your app meets our prerequisites: Attempting to use our SDK in an environment that doesn’t match our supported versions may result in build errors. Update to the latest version: When troubleshooting problems with our SDKs, we generally recommend that you try updating to the latest version. That helps us weed out issues that might have been seen in previous versions of the SDK. Try running our MCP server: Our MCP server includes an integration tool that can provide immediate help with your implementation, including problems with push and in-app notifications.https://docs.customer.io/integrations/sdk/react-native/5.x/getting-started/troubleshooting/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/5.x/getting-started/troubleshooting/Basic troubleshooting steps Make sure your app meets our prerequisites: Attempting to use our SDK in an environment that doesn’t match our supported versions may result in build errors. Update to the latest version: When troubleshooting problems with our SDKs, we generally recommend that you try updating to the latest version. That helps us weed out issues that might have been seen in previous versions of the SDK. Try running our MCP server: Our MCP server includes an integration tool that can provide immediate help with your implementation, including problems with push and in-app notifications.https://docs.customer.io/integrations/sdk/react-native/getting-started/troubleshooting/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/getting-started/troubleshooting/Basic troubleshooting steps Make sure your app meets our prerequisites: Attempting to use our SDK in an environment that doesn’t match our supported versions may result in build errors. Update to the latest version: When troubleshooting problems with our SDKs, we generally recommend that you try updating to the latest version. That helps us weed out issues that might have been seen in previous versions of the SDK. Try running our MCP server: Our MCP server includes an integration tool that can provide immediate help with your implementation, including problems with push and in-app notifications.https://docs.customer.io/journeys/triggered-lifecycle-email-with-sparkpost/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/triggered-lifecycle-email-with-sparkpost/You can use your Sparkpost account to send email through Customer.io with no loss in functionality. To take advantage of Sparkpost, you need to do two things: Point Sparkpost’s webhooks at Customer.io. Configure Sparkpost as a custom SMTP server in Customer.io. Point Sparkpost’s webhooks at Customer.io Go to Sparkpost’s webhooks page. Enter the webhook URL corresponding to your Customer.io account region for every domain you want to send email from in Customer.https://docs.customer.io/journeys/validate-mobile-phone-numbers/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/validate-mobile-phone-numbers/You can solve this problem using Twilio’s lookup API, to people’s phone numbers, carriers, and line types (like mobile, landline, or VoIP) and make sure that you only send SMS and WhatsApp messages to valid recipients! This can help you prevent bounces, and filter out undeliverable messages. As a part of this recipe, you’ll: Create a segment to capture all people with a phone attribute. Send people in this segment through a campaign that calls Twilio’s lookup API.https://docs.customer.io/journeys/amp-for-email/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/amp-for-email/You can craft AMP components directly in the code editor of Design Studio or in the advanced code editor. Send test emails to ensure those with the ability to view dynamic content, and those without, will see what you expect. You also have the option to send AMP content through our App API. Requirements for sending and receiving AMP content To send an AMP message, you need to send from a domain that:https://docs.customer.io/accounts-and-workspaces/data-centers/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/accounts-and-workspaces/data-centers/We ensure that all of your customers’ data is stored in the region that you choose. So, if you select the EU region, all of the information about your customers, known as People, is stored exclusively in data centers within EU member countries. You cannot have workspaces in different regions. All customer data in your account—all of your workspaces—resides within the region you select when you set up your account.https://docs.customer.io/accounts-and-workspaces/case-sensitivity/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/accounts-and-workspaces/case-sensitivity/When is data case sensitive? AttributeA key-value pair that you associate with a person or an object—like a person’s name, the date they were created in your workspace, or a company’s billing date etc. Use attributes to target people and personalize messages. names are always case sensitive. You can save both first_name and First_Name to a profile; those fields will not merge together. This is also the case for reserved attributes like timezone and unsubscribed.https://docs.customer.io/accounts-and-workspaces/beta-experimental-features/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/accounts-and-workspaces/beta-experimental-features/How it works We aim to release features early and often. Sometimes when we release new features, we’ll mark them as beta or experimental. In both cases, we think the features are stable and ready to use (though we can’t say that they’re bug-free), but we want your feedback! Beta features are early releases of a features we’re actively working on. In general, we think beta releases are stable but they may not solve all the problems we want them to, or—in the case of our SDKs—may need scaled testing.https://docs.customer.io/journeys/exporting-users/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/exporting-users/There are a few ways for you to export people data from the People page in Customer.io. You can… Export all your users and all their data Export all your users, but only with specific attributes Export a set of users who meet certain conditions — with all of their attributes, or a specific set  Exports will include all attribute data for the selected profiles. If this includes sensitive data, you must purge that data before passing it to customers.https://docs.customer.io/journeys/grace-periods/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/grace-periods/Overview You may notice a grace period when viewing a person’s journey. A grace period is a period of time people may wait to enter a campaign. Historically, a grace period was also a period of time people might wait to exit your campaign. Grace periods were available across multiple campaign types and could impact people entering or exiting a campaign. Now, they only impact people who enter campaigns with our legacy segment trigger.https://docs.customer.io/journeys/trial-expiration-reminders/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/trial-expiration-reminders/Introduction Sending emails to remind people that their trial is ending is simply good customer service. Don’t put the burden on them to remember. The benefit is that it brings you back to front of mind as the clock starts ticking and can help nudge upgrades to happen sooner rather than later. In this recipe, you’ll learn how to use a trial expiry date to trigger a campaign with 3 emails.https://docs.customer.io/journeys/triggered-lifecycle-email-with-oracle-dyn/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/triggered-lifecycle-email-with-oracle-dyn/You can use your Oracle Dyn account to send email through Customer.io with no loss in functionality. To take advantage of Oracle Dyn, you need to do two things: Point Oracle Dyn’s webhooks at Customer.io. Configure Oracle Dyn as a custom SMTP server in Customer.io. Point Oracle Dyn’s webhooks at Customer.io Go to the Oracle Dyn Integrations page. Add the following webhook URLs for every domain you want to send mail from in Customer.https://docs.customer.io/accounts-and-workspaces/workspace-search/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/accounts-and-workspaces/workspace-search/Press ⌘K on Mac or CtrlK on Windows and Linux to open the search dialog from anywhere in your workspace.  Universal search is independent of the Customer.io AI toggle in your Privacy, Data, & AI settings. Disabling Customer.io AI doesn’t affect universal search. What you can search for The universal search feature cannot search for people or their data. It only searches workspace configuration—the names and content of things you’ve built in Customer.https://docs.customer.io/accounts-and-workspaces/security-certifications/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/accounts-and-workspaces/security-certifications/The certifications we’ve earned are the result of independent, third-party audits that verify our compliance with (and commitment to) industry standards and best practices.  See our full security policy You can read more about our security practices on our website and download our compliance documents. ISO 27001 certification Customer.io is certified for ISO 27001 compliance as of September 24, 2024. Our certification expires September 24, 2027. See our certificate. ISO 27001 is an international standard for information security management systems (ISMS).https://docs.customer.io/integrations/getting-started/demo/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/getting-started/demo/Add your API Key (found in your integration’s Settings tab). Then you can tailor and send calls to Customer.io. Requests that you make before you identify someone are anonymous. After you send an identify call with a userId, future requests are associated with the identified person. See our JavaScript and API docs for a complete payload reference.  Clear your cookies and local storage to start fresh Our JavaScript snippet stores data in cookies and falls back to local storage.https://docs.customer.io/accounts-and-workspaces/plan-features/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/accounts-and-workspaces/plan-features/How it works Customer.io offers 3 plans: Essentials, Premium, and Enterprise. You’ll find a detailed list of the differences between plans on our pricing page, but your plan determines whether or not you can use some features in the system. These are typically advanced features that take more resources to support (in terms of storage, processing, and people). General features Feature Essentials Premium Enterprise Description Extra workspaces2 Unlimited UnlimitedWorkspaces hold your people, campaigns, etc.https://docs.customer.io/journeys/assign-a-personal-support-rep/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/assign-a-personal-support-rep/Introduction Onboarding is hard to get right. You want to show off the benefits of your app at a large scale while creating a personal touchpoint. Many of our customers introduce a dedicated customer support person to their end user as soon as they sign up. The new user can then reach out directly with any concerns or questions. This way, end users know that they’re getting one-to-one attention from the start, and that someone will be there to help them as they discover the app.https://docs.customer.io/journeys/view-in-browser/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/view-in-browser/“View in browser” links let your audience view a web-hosted version of your email in their browser. If you have an image-heavy email, worry about display issues in specific email clients, or simply want to give your audience the option to view your email outside of their inbox, you can add a link that generates a web version of the email personalized for each recipient.  Email only — and publichttps://docs.customer.io/journeys/filtering-logs/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/filtering-logs/In the Activity Log, you can track which activities people and objectsAn object is a non-person entity that you can associate with one or more people—like a company, account, or online course. have performed. This can help you ensure you’re receiving certain events, troubleshoot people across a similar activity, and more.  The Activity Log shows activities processed within the last 30 days. This article is about your workspace-wide activity logs. You can also find activity logs for each of your customers within their profile page.https://docs.customer.io/journeys/message-library/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/message-library/Go to Content > Message Library to see a list of all the messages in your workspace and their current status. You can search for messages by name, subject, content, or from address. You can sort messages based on when they were last updated. Click to switch between ascending and descending sorting. Click any message in the list to go directly to the message. From here, you can edit your message or edit settings in the campaign or broadcast containing the message.https://docs.customer.io/journeys/creating-segments/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/creating-segments/Ingredients Integration with Customer.io A knowledge of the attributes you’re sending to us We’ll start with a basic segment, just to get you familiar with creating a segment in Customer.io, and then ramp up the complexity. So head on to the Segments builder and let’s get started! Basic: target users who clicked a link You can use data-driven segments to track users who clicked a specific link in your messages. First, check to see if URL parameters are enabled in your workspace.https://docs.customer.io/journeys/asset-library/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/asset-library/How it works Any images you upload are stored in your Assets page. You can upload images in bmp, jpeg, png, and gif formats. You can store PDFs that you then link to from a message. File size limits You can upload images and PDFs to your Assets library, but limits apply: Maximum image width and height: 4096 px Files must be smaller than 2 MB. For optimal loading times, we recommend that you upload images smaller than 1 MB.https://docs.customer.io/journeys/adding-sender-image/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/adding-sender-image/By default, that image people see next to your email in their inbox will be the first character of your company’s name. Occasionally we get asked how to add a logo so that it will appear next to your email messages in the end-user’s inbox instead. Unfortunately, this is not something you (or we) control exclusively as part of the email sending process but rather it is determined by the recipient’s inbox provider or email client.https://docs.customer.io/journeys/image-support/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/image-support/General image and media guidelines This page provides some guidance about the maximum file sizes and types supported by our Assets library and various platforms. However, you generally want to limit the size of your images to the smallest possible file sizes. While some messages support larger file sizes, it’s best to limit file size to reduce load time. A person viewing your message on their phone using cell service, for instance, might have trouble loading messages with large images or attachments.https://docs.customer.io/journeys/cohort-testing/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/cohort-testing/Cohort testing is great for things like: Testing timing: different delay times before sending a message Single vs multi-touch: sending a user one email vs. several emails Blackhole/holdout testing: where you want to send a message or no message at all. Check out our recipe specifically for holdout tests. Ingredients You’ll need: A basic understanding of liquid The ability to create campaigns If you decide to assign cohorts via API, you’ll also need:https://docs.customer.io/journeys/using-data-index/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/using-data-index/Why use the Data Index The Data Index is useful for things like: Troubleshooting: Are your campaigns behaving strangely? Check the Data Index to see if a particular event is being sent multiple times or if it’s being used by multiple campaigns. Data clean-up: Data gets messy sometimes. Check if your attributes or events are similarly named or near-duplicates and clean your data accordingly. Visibility and clarity: Determine if a piece of data you need for a campaign is already being sent to Customer.https://docs.customer.io/journeys/data-availability/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/data-availability/Here, you’ll find all of the attributes and events flowing into your Customer.io account via your chosen integration method. You can see: All of the events and attributes you have Where they’re being used (segments, campaigns) How they’re being used (as a trigger, filter, or Action Condition) For events, the data associated with each and when it was last seen For attributes, we list all of the attributes you have for your users, and when each was last changed or added Head over to the Data Index introduction for more details on how to navigate; otherwise, feel free to explore!https://docs.customer.io/journeys/queue-as-draft/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/queue-as-draft/In most ESPs you’re either “building” your email campaign or “sending” it. This means that once you hit “Start campaign”, your messages go live and you can only catch errors afterwards. Customer.io takes a different approach with a feature called Queue Draft, which enables you to start campaigns and generate drafts of messages without sending them. Think of this as a dry-run for your campaigns. You get to see who would have received what message when before actually going live.https://docs.customer.io/journeys/multiple-subscription-types/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/multiple-subscription-types/ Customer.io now has a subscription center! Our subscription center lets you manage multiple subscription topics and set subscription-based audiences for campaigns and broadcasts. If, however, the options in this article better serve your use case, please let us know so we can continue to improve our product. Here are three tracking subscription preferences: Use our subscription center! Custom unsubscribe links: This method lets you segment based on people who have clicked a link that represents unsubscribing.https://docs.customer.io/journeys/custom-mail-headers/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/custom-mail-headers/For example: Set the X-Mailgun-Tag header if you’re using Mailgun’s “Topic” subscription functionality Set your own List-Unsubscribe header for specific emails (if you use our unsubscribe link, we add this header automatically) Stop emails from being shown as a thread by Gmail with the X-Entity-Ref-ID header Use X-Auto-Response-Suppress:OOF to suppress auto-replies from Exchange servers Adding, editing, and removing custom headers You’ll find the custom headers option in the email composer. Add them by clicking the Add Custom link to the right of the Headers:https://docs.customer.io/journeys/people-shortcuts/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/people-shortcuts/You’ll find the Shortcuts button on the upper-right corner of any person’s page in your workspace. Go to People and select a person to add or use shortcuts. Add a shortcut  Customize links with liquid Though you add a shortcut from an individual person’s page in Customer.io, your shortcut will appear on every person’s page in your workspace. You should use liquidA syntax that supports variables, letting you personalize messages for your audience.https://docs.customer.io/journeys/role-based-messaging-campaign/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/role-based-messaging-campaign/Method Determine how you’re storing data in Customer.io. This will determine the type of campaign you should make. Are you storing role information on people as profile attributesA key-value pair that you associate with a person or an object—like a person’s name, the date they were created in your workspace, or a company’s billing date etc. Use attributes to target people and personalize messages.? Or are you storing role information on people’s relationshipsThe connection between an object and a person in your workspace.https://docs.customer.io/journeys/rss-feed-email-campaign/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/rss-feed-email-campaign/Introduction With an RSS Feed Email Campaign, you can send new posts to your audience whenever you publish content. This makes use of our API Triggered Broadcast campaigns and a Zapier workflow. Ingredients Zapier account publicly accessible RSS Feed URL Method Create an API Triggered Broadcast Campaign Learn how in our guide for API Triggered Broadcasts. Set up Zapier Workflow For those of you new to Zapier, it’s a handy tool that helps you connect your apps and automate workflows.https://docs.customer.io/journeys/custom-preheader-text/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/custom-preheader-text/Normally, this preview is pulled from the first text in your email. This is OK if your content starts right away, and is short enough for a summary. However, if that isn’t the case, you might have text like ‘Is this email not displaying correctly?’ taking up valuable inbox real estate that could be used to incentivise opens instead! In Customer.io, you can control exactly what text will appear in this preview for an email— to avoid situations like the one mentioned above.https://docs.customer.io/integrations/data-in/connections/cdps/integrating-with-mparticle/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/cdps/integrating-with-mparticle/Send Events to Customer.io Send event data to Customer.io by setting up Customer.io as an Event Output in mParticle. From the mParticle activity overview screen select Setup > Outputs > Event > Add Event Output and select or search for Customer.io from the dropdown list. Next navigate to the Customer.io workspace you’d like to send your data to. From the main dashboard select > Integrations > Customer.io API (Settings). Here you will find your Site ID and API Key.https://docs.customer.io/journeys/track-https-links/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/track-https-links/How it works We generated a unique URL for any link you track. This link proxies through our link tracking domain and then to the ultimate destination. That’s how we track clicks! But for HTTPS link tracking, we need to use a valid SSL certificate to prove that the proxy is secure—so that your audience, browsers, and any security software understands that the link is safe. In this case, we’ll generate a record you can add to your DNS provider that points to our link tracking domain and we’ll generate a valid SSL certificate for you.https://docs.customer.io/integrations/data-in/connections/classic-api/invalid-api-requests/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/data-in/connections/classic-api/invalid-api-requests/{ "meta": { "error": "name cannot be blank" } }  We strongly encourage you to implement some logging on your end to capture our responses to any invalid API requests your integration may send by mistake. This will give you something to look back on when you get notifications from our team about such errors. Common Error Messages What you see below is the list of error messages shown when API calls are rejected due to limits mentioned in our API documentation.https://docs.customer.io/journeys/fake-bcc/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/fake-bcc/“Fake Bcc” is an option available when you’re adding a Bcc address to your campaigns. It’s checked by default. If this option is checked, rather than sending a true Bcc, we’ll send you a separate copy of the email (with a slightly modified subject line containing the user’s email address). This allows you to be copied on emails and open them and click links without worrying about affecting the user’s history.https://docs.customer.io/journeys/multiple-from-addresses/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/multiple-from-addresses/Add multiple from addresses To add a new from address: Go to Settings > Workspace Settings and select Email. Find the sending domain you want to add the new address to and click Add from address. Enter the sender name and email address. After you add a new from address and the domain is verified, you can pick your new address using the drop-down next to the From label when creating an email.https://docs.customer.io/journeys/message-statuses/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/message-statuses/We also aggregate these statuses as metrics, so you know not only how well a message performed with an individual person, but how well it was received by your audience at large. This page is designed to help you understand the various states your messages progress through, and how we display those states in different areas of Customer.io. Status vs. Metric A Message Status explains the state of an individual delivery (the instance of a message intended for an individual) or journey (the instance of a campaign that a person travels through).https://docs.customer.io/journeys/legacy-in-app-editor/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/legacy-in-app-editor/ The legacy in-app editor is deprecated You will not be able to create new messages in the legacy editor after October 1, 2025. We’re sunsetting the legacy in-app editor January 31, 2026. If you haven’t made the switch yet, now’s the perfect time to start using the new in-app editor, designed to help you build better in-app experiences. How it works In-app message templates built in our older template editor include all of your message content, including the text areas you can customize when you create a message in Customer.https://docs.customer.io/journeys/localization-i18n/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/localization-i18n/ Try our new Language Settings instead! These instructions predate our new localizationA process of setting up messages with two or more languages, and using your workspace’s Language Settings to make sure that people in your audience receive messages in their preferred language. feature, which helps you send messages in multiple languages without complicated conditions or liquidA syntax that supports variables, letting you personalize messages for your audience. For example, if you want to reference a person’s first name, you might use the variable {{customer.https://docs.customer.io/journeys/deliveries-drafts-data/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/deliveries-drafts-data/To view deliveries or drafts over a specific time period: Select Deliveries & Drafts from the left hand menu. Select either the Deliveries or Drafts tab. Filter for messages across any and all channels (email, in-app, etc). For delivered messages, you can search by status (sent, failed, attempted, etc), too. Click a message to view the message body and supporting data, such as the campaign it belongs to. Export to CSV To export deliveries or drafts over time:https://docs.customer.io/journeys/geolocation/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/geolocation/How it works Customer.io determines a person’s location from two possible sources: IP-based geolocation: We infer location from IP addresses. This happens automatically when you identifyThe Customer.io operation that adds or updates a person. When you identify a person, Customer.io either adds a person if they don’t exist in your workspace, or updates them if they do. Before you identify someone (by their email address or an ID), you can track them anonymously.https://docs.customer.io/journeys/recommended-send-time/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/recommended-send-time/ Is Customer.io AI enabled? You need to enable Customer.io AI in your Data & Privacy settings to use this feature—if you haven’t already. See our AI overview to learn more about how you can use AI in Customer.io. How it works When you set up a newsletter or an email in a campaign, you can click Recommend send time to schedule the email to send at the best time for your audience.https://docs.customer.io/journeys/timezone-match/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/timezone-match/How it works You can schedule messages for your users in their time local timezones, so you engage customers at the right times, wherever they are. This feature relies on a timezone attribute you set yourself or the cio_timezone attribute, which is set by our automatic geolocation data collection. If the timezone attribute exists, we’ll use it to send the message in the customer’s time zone. If it doesn’t exist, we’ll use the cio_timezone attribute as a fallback.https://docs.customer.io/journeys/example-timezones/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/example-timezones/These are the values we support when you use the timezone attribute in your emails and attributes. Note that we support automatic geolocation data collection as well. If you use automatic geolocation data collection, we’ll set a cio_timezone attribute that you can use with our time zone-related features, so you don’t need to set the timezone attribute. Region Format - Supported in our emails and attributes as well as the Time Zone Match feature.https://docs.customer.io/journeys/message-failed/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/message-failed/If you see ‘Attempted’ or ‘Failed’ as a status on your message, there are a few reasons why that might be the case. Attempted means that your message has been created and we’ve tried to send it to the delivery provider, which then would send to your end user. If you’re sending an email, for example, that means that your email has been put together in Customer.io, and we’ve tried to send it to an ESP such as SendGrid.https://docs.customer.io/journeys/reminders-for-multiple-upcoming-trips/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/reminders-for-multiple-upcoming-trips/Introduction This recipe is useful for multiple upcoming trips but you can also adapt it for these use cases: Encourage a shopper to purchase their abandoned cart even when it’s possible for the user to have multiple carts. Let a customer know that one of their many saved coupons is expiring soon. Notify users when one job of many they’ve applied for is closed. The idea is that sometimes people can have multiples of one thing - trips, carts, coupons, and job applications - and you may want to target a specific trip, cart, etc during a campaign.https://docs.customer.io/journeys/message-limits/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/message-limits/How it works You can set a message limit at the workspace level, and then you can determine which campaigns, broadcasts, and messages count towards the limit. For example, you might have marketing campaigns that you want to count towards limits but a broadcast about changes to your terms and conditions that you need to send to everyone, whether or not they’ve reached their message limit. When a message encounters a limit, it’s marked as Undeliverable.https://docs.customer.io/integrations/sdk/android/2.x/changelog/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/android/2.x/changelog/showhttps://docs.customer.io/integrations/sdk/android/3.x/changelog/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/android/3.x/changelog/showhttps://docs.customer.io/integrations/sdk/android/whats-new/changelog/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/android/whats-new/changelog/showhttps://docs.customer.io/integrations/sdk/expo/1.x/updates-and-troubleshooting/changelog/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/expo/1.x/updates-and-troubleshooting/changelog/testhttps://docs.customer.io/integrations/sdk/expo/whats-new/changelog/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/expo/whats-new/changelog/testhttps://docs.customer.io/integrations/sdk/flutter/1.x/updates-and-troubleshooting/changelog/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/flutter/1.x/updates-and-troubleshooting/changelog/showhttps://docs.customer.io/integrations/sdk/flutter/2.x/whats-new/changelog/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/flutter/2.x/whats-new/changelog/showhttps://docs.customer.io/integrations/sdk/flutter/whats-new/changelog/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/flutter/whats-new/changelog/showhttps://docs.customer.io/integrations/sdk/ios/1.x/changelog/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/1.x/changelog/showhttps://docs.customer.io/integrations/sdk/ios/2.x/changelog/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/2.x/changelog/showhttps://docs.customer.io/integrations/sdk/ios/3.x/whats-new/changelog/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/3.x/whats-new/changelog/showhttps://docs.customer.io/integrations/sdk/ios/whats-new/changelog/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/ios/whats-new/changelog/showhttps://docs.customer.io/integrations/sdk/react-native/2.x/updates-and-troubleshooting/changelog/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/2.x/updates-and-troubleshooting/changelog/testhttps://docs.customer.io/integrations/sdk/react-native/3.x/updates-and-troubleshooting/changelog/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/3.x/updates-and-troubleshooting/changelog/testhttps://docs.customer.io/integrations/sdk/react-native/4.x/whats-new/changelog/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/4.x/whats-new/changelog/contenthttps://docs.customer.io/integrations/sdk/react-native/5.x/whats-new/changelog/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/5.x/whats-new/changelog/testhttps://docs.customer.io/integrations/sdk/react-native/whats-new/changelog/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/integrations/sdk/react-native/whats-new/changelog/testhttps://docs.customer.io/journeys/4-email-design-resources/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/4-email-design-resources/Adapt-a-template guides These guides are meant to show you the process of adapting a basic template from another service into a Customer.io Layout. Foundation - Basic Mailchimp - Two-Column Layout creation and templates Pre-built templates Mailchimp’s Blueprints Litmus community Foundation for Emails Inkbrush, an email layout builder A really simple responsive HTML email template Frameworks to build your own HTML Email Boilerplate MJML.io, a markup language that lets you code your own responsive emails emailframe.https://docs.customer.io/journeys/5-adapt-foundation-basic/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/5-adapt-foundation-basic/This template looks something like this (depending on your client): To adapt it into a Customer.io layout, remember that you have to split it into two parts: Layout - what is consistent across emails? how will it look? what is its structure? Content - what do you want to edit on a per-email basis? For this, I’ve decided that everything in the yellow box, I want to edit on a per-email basis:https://docs.customer.io/journeys/6-adapt-mc-twocol/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/journeys/6-adapt-mc-twocol/If you use MailChimp, you’ll be familiar with their pre-built templates, and this is one of the more straightforward ones! It looks something like this when you start, (depending on your client): To adapt it into a Customer.io layout, remember that you have to split it into two parts: Layout - what is consistent across emails? how will it look? what is its structure? Content - what do you want to edit on a per-email basis?https://docs.customer.io/release-notes/2026-04-08-q2-launch/Wed, 08 Apr 2026 00:00:00 +0000https://docs.customer.io/release-notes/2026-04-08-q2-launch/https://docs.customer.io/release-notes/2026-04-08-llm-actions/Wed, 08 Apr 2026 00:00:00 +0000https://docs.customer.io/release-notes/2026-04-08-llm-actions/You can use LLM actions to personalize messages, enrich data, and create conditions to help you reach the right audience. Each time an LLM action runs, it uses AI credits. Learn more in Billing.https://docs.customer.io/release-notes/2026-04-08-goals/Wed, 08 Apr 2026 00:00:00 +0000https://docs.customer.io/release-notes/2026-04-08-goals/Unlike campaign-specific conversion goals, you can now track outcomes that span multiple workflows to help you more holistically strategize around your messaging and data.https://docs.customer.io/release-notes/2026-04-08-health-dashboard/Wed, 08 Apr 2026 00:00:00 +0000https://docs.customer.io/release-notes/2026-04-08-health-dashboard/You can also use this dashboard to optimize your workspace before issues arise! Go to > Workspace performance to get started.https://docs.customer.io/release-notes/2026-04-08-universal-search/Wed, 08 Apr 2026 00:00:00 +0000https://docs.customer.io/release-notes/2026-04-08-universal-search/Note that this feature does not search for people, objects, or their data. To find people, you’ll continue to use the activity log, people page, or segments.https://docs.customer.io/release-notes/2026-04-08-agent-rebrand/Wed, 08 Apr 2026 00:00:00 +0000https://docs.customer.io/release-notes/2026-04-08-agent-rebrand/In the past, our AI Assistant was limited to specific tools. But the new agent can do just about anything you can do in Customer.io. It can create campaigns, draft emails, analyze campaign performance, and more. It can even learn from you and get better over time! You can also set up Routines to automate recurring tasks—things like checking your deliverability, auditing segments, and more. And while we’ve expanded the agent’s capabilities, we’ve also given it guardrails to make sure it works safely.https://docs.customer.io/release-notes/2026-04-08-ui-refresh/Wed, 08 Apr 2026 00:00:00 +0000https://docs.customer.io/release-notes/2026-04-08-ui-refresh/From the Home dashboard, you can see message performance at a glance and take action on your workspace. Pick up where you last left off or select a suggested action to get started.https://docs.customer.io/release-notes/2026-04-02-channel-preferences/Thu, 02 Apr 2026 00:00:00 +0000https://docs.customer.io/release-notes/2026-04-02-channel-preferences/Channel preferences add a new layer of subscription control to your subscription center. Where topic preferences let people choose what they hear about, channel preferences let them choose how they receive messages. You can set up channel-based subscription preferences for any messaging channel you have enabled in your workspace.https://docs.customer.io/release-notes/2026-03-30-daily-ramp-newsletters/Mon, 30 Mar 2026 00:00:00 +0000https://docs.customer.io/release-notes/2026-03-30-daily-ramp-newsletters/Previously, you could only set a fixed send rate for newsletters—a consistent number of messages per minute, hour, or day. If you needed to warm up a domain, you had to manually create separate newsletters for each period of your warm-up schedule. Now, domain warming is less manual and easier to set up! We’ve also increased the maximum newsletter send time to 60 days to give you more room for gradual warming and large sends.https://docs.customer.io/release-notes/2026-03-30-in-app-live-preview/Mon, 30 Mar 2026 00:00:00 +0000https://docs.customer.io/release-notes/2026-03-30-in-app-live-preview/Click Live Preview when working on your in-app message to get started. We’ll open your website in a new window where you can see and adjust your message in real time.https://docs.customer.io/release-notes/2026-03-30-in-app-tooltips/Mon, 30 Mar 2026 00:00:00 +0000https://docs.customer.io/release-notes/2026-03-30-in-app-tooltips/When you set up a tooltip, you’ll set a Target element, which is the element you want to anchor your tooltip to. You can use our new Live Preview feature or click Select Target in your message settings to open a preview window and select the target element that you want to anchor your tooltip—so you don’t have to manually enter a complicated CSS selector to find the right element.https://docs.customer.io/release-notes/2026-03-29-automatic-domain-setup/Sun, 29 Mar 2026 00:00:00 +0000https://docs.customer.io/release-notes/2026-03-29-automatic-domain-setup/Entri supports over 50 DNS providers, including GoDaddy, Namecheap, Cloudflare, and Amazon Route 53.https://docs.customer.io/release-notes/2026-03-23-multiple-short-link-domains/Mon, 23 Mar 2026 00:00:00 +0000https://docs.customer.io/release-notes/2026-03-23-multiple-short-link-domains/This is especially useful if you manage multiple brands, want to rotate domains, or want to separate domains by message type.https://docs.customer.io/release-notes/2026-03-19-limit-rate-newsletters/Thu, 19 Mar 2026 00:00:00 +0000https://docs.customer.io/release-notes/2026-03-19-limit-rate-newsletters/Rate limiting lets you control how quickly your newsletters go out, which can help reduce the load on your downstream systems and maintain deliverability, so we want to make sure you can limit sends when it makes sense for your business. On the Review step of a newsletter, you can now turn on the toggle Limit send rate when your newsletter has multiple language variants.https://docs.customer.io/release-notes/2026-03-18-ds-apis/Wed, 18 Mar 2026 00:00:00 +0000https://docs.customer.io/release-notes/2026-03-18-ds-apis/You’ll use our latest endpoints to manage content in Design Studio; you can’t update Design Studio content using other message-related endpoints. You’ll also see new Assets endpoints, which you can use to create, update, or delete images and PDFs in your Asset library for use across message channels. Keep these best practices in mind as you migrate your HTML to Design Studio!https://docs.customer.io/release-notes/2026-03-13-gemini-safety-settings/Fri, 13 Mar 2026 00:00:00 +0000https://docs.customer.io/release-notes/2026-03-13-gemini-safety-settings/Customer.io’s AI tools use Gemini models, so you’ll see Gemini Safety Settings on your Privacy page. You can filter content by four categories—Harassment, Hate Speech, Sexually Explicit, and Dangerous Content—with options ranging from Off (no filtering) to Block low and above (strictest filtering). By default, there is no filtering applied to your account. You can also include a compliance prompt to help ensure generated content aligns with other regulatory and policy guidelines.https://docs.customer.io/release-notes/2026-03-12-forced-dark-options/Thu, 12 Mar 2026 00:00:00 +0000https://docs.customer.io/release-notes/2026-03-12-forced-dark-options/Learn more about these preview settings and how to make your design more consistent in email clients that don’t support dark mode styles. These preview settings are available in our latest email editor, Design Studio, and our Code-only editor.https://docs.customer.io/release-notes/2026-03-12-mobile-sdk-location-tracking/Thu, 12 Mar 2026 00:00:00 +0000https://docs.customer.io/release-notes/2026-03-12-mobile-sdk-location-tracking/Customer.io already gives you the option to enrich locations from IP addresses, but VPNs, carrier routing, and shared Wi-Fi can reduce accuracy for mobile apps. With the new location module, our SDKs can capture device coordinates and Customer.io reverse-geocodes them into cio_city, cio_state, and cio_country profile attributes. The SDK also sends Location Update events that you can use to trigger journeys and build segments. To minimize battery usage, our SDKs limit location updates to once per day at most and only when the person has moved a meaningful distance.https://docs.customer.io/release-notes/2026-03-09-ds-seamless-editing/Mon, 09 Mar 2026 00:00:00 +0000https://docs.customer.io/release-notes/2026-03-09-ds-seamless-editing/Whether you edit the email from Design Studio or your campaign, you can now directly update your content from either place. You’ll also see a few other enhancements: Publish status so you know whether all changes are live The ability to validate links from any preview in Design Studio A confirmation modal when navigating away from a draft so you don’t accidentally lose your changeshttps://docs.customer.io/release-notes/2026-03-09-line-messaging/Mon, 09 Mar 2026 00:00:00 +0000https://docs.customer.io/release-notes/2026-03-09-line-messaging/LINE is the dominant messaging app in key Asian markets, with over 90 million monthly active users in Japan alone and market penetration of 70-95% in its core regions. In these markets, LINE isn’t just another channel—it’s how people communicate daily. Now you can send LINE messages as a part of your campaigns and broadcasts. Send text and image messages to your LINE audience, track delivery and engagement metrics, and manage your LINE contacts alongside all your other channels.https://docs.customer.io/release-notes/2026-03-03-any-rel-wait-until/Tue, 03 Mar 2026 00:00:00 +0000https://docs.customer.io/release-notes/2026-03-03-any-rel-wait-until/For instance, if you have Account and Subscription objects, you can now trigger a campaign when an account is created and wait to message someone until they’ve activated a subscription.https://docs.customer.io/release-notes/2026-03-02-set-journey-attributes-action/Mon, 02 Mar 2026 00:00:00 +0000https://docs.customer.io/release-notes/2026-03-02-set-journey-attributes-action/You might use this to set static data, like a discount code, that only applies while your customers are in the campaign. This means you can now set journey attributes based on webhook data, collection queries, and a workflow action designed specifically for journey attributes.https://docs.customer.io/release-notes/2026-03-02-ds-ai-translation/Mon, 02 Mar 2026 00:00:00 +0000https://docs.customer.io/release-notes/2026-03-02-ds-ai-translation/Multi-lingual messaging is essential for global markets, and now Design Studio can help you reach them without cumbersome branching in campaigns. Reduce time spent copying content between tools, and scale personalized messaging with less overhead.https://docs.customer.io/release-notes/2026-02-19-notification-inbox/Thu, 19 Feb 2026 00:00:00 +0000https://docs.customer.io/release-notes/2026-02-19-notification-inbox/With inbox messages, you can send important updates like announcements, order confirmations, or reminders to a notification inbox that people can check whenever they want. For now, you’ll build your notification inbox yourself and invoke inbox methods to fetch and manage messages. Your messages are delivered as JSON payloads that you can render however you want, making it easy to align with your brand and app design. But we recognize that this takes a bit of work.https://docs.customer.io/release-notes/2026-02-17-native-whatsapp/Tue, 17 Feb 2026 00:00:00 +0000https://docs.customer.io/release-notes/2026-02-17-native-whatsapp/WhatsApp messages are based on templates approved by Meta. You’ll create templates in your Facebook/WhatsApp Business Account and then use them to send messages from Customer.io.https://docs.customer.io/release-notes/2026-01-28-in-app-styles/Wed, 28 Jan 2026 00:00:00 +0000https://docs.customer.io/release-notes/2026-01-28-in-app-styles/Moving forward, new in-app messages will automatically pull from your global styles, and you can choose to sync existing messages to align them with your current branding. This release also introduces the concept of publishing to in-app messages. When you publish styles, you decide which emails and/or in-app messages to update. This pushes changes to your workflows (campaigns, broadcasts, etc) so that whether you send a test message or the campaign is actively sending to people, your messages will use the current styles.https://docs.customer.io/release-notes/2026-01-26-in-app-forms/Mon, 26 Jan 2026 00:00:00 +0000https://docs.customer.io/release-notes/2026-01-26-in-app-forms/We capture form submissions with your users’ input as a part of campaigns, broadcasts, or newsletters. You can also trigger downstream campaigns when someone submits your forms to thank them for their feedback, request a follow-up meeting, or offer a discount!https://docs.customer.io/release-notes/2026-01-23-ds-optimize-images/Fri, 23 Jan 2026 00:00:00 +0000https://docs.customer.io/release-notes/2026-01-23-ds-optimize-images/Large assets cause emails to load slowly, impacting success of your campaigns. With optimization, you can ensure graphics appear quickly (even on poor mobile connections) to prevent drop-off from blank screens and protect click-through rates.https://docs.customer.io/release-notes/2026-01-21-visual-component-saving/Wed, 21 Jan 2026 00:00:00 +0000https://docs.customer.io/release-notes/2026-01-21-visual-component-saving/Build a block using components in the visual editor, and then click to save it as a new custom component file. It’s immediately accessible in the Insert menu of the visual editor for reuse across your emails. You can also detach components from the source file if you want to make changes unique to that email.https://docs.customer.io/release-notes/2026-01-21-journey-attributes-collection-queries/Wed, 21 Jan 2026 00:00:00 +0000https://docs.customer.io/release-notes/2026-01-21-journey-attributes-collection-queries/This means you can now temporarily store data from both collections and webhooks to keep your customers’ profiles as lean as possible.https://docs.customer.io/release-notes/2026-01-16-ai-subject-lines/Fri, 16 Jan 2026 00:00:00 +0000https://docs.customer.io/release-notes/2026-01-16-ai-subject-lines/For best results, generate subject lines after your email content is complete! This feature only applies to subject lines, not preheader/preview text.https://docs.customer.io/release-notes/2026-01-14-resuable-webhooks/Wed, 14 Jan 2026 00:00:00 +0000https://docs.customer.io/release-notes/2026-01-14-resuable-webhooks/Why it matters: Less repetitive work & fewer errors. Define your webhook URL, headers, and auth details once, and reference them in any campaign. Updates at scale. When an API endpoint or auth header changes, update the configuration in one place and all referencing campaigns pick up the change automatically. Tighter security. Team members can select pre-configured webhooks without ever seeing sensitive data like API keys, auth tokens, or headers. Only Account and Workspace admins can configure reusable webhooks.https://docs.customer.io/release-notes/2026-01-14-design-studio-multi-select/Wed, 14 Jan 2026 00:00:00 +0000https://docs.customer.io/release-notes/2026-01-14-design-studio-multi-select/While message creation requires fine-tuning, it shouldn’t interrupt your creative flow. Previously, refining Design Studio emails or in-apps—like the padding on four different buttons—required you to go through a cycle of repetitive, manual adjustments. Now you can do this in a single, fluid motion: click, drag, and change your styles. To make edits across multiple components, click and drag your cursor on the canvas to select multiple components. Learn more about editing multiple components in Design Studio and in-app messages.https://docs.customer.io/release-notes/2025-12-24-wait-until-custom-objects/Wed, 24 Dec 2025 00:00:00 +0000https://docs.customer.io/release-notes/2025-12-24-wait-until-custom-objects/For example, you can: Send a message when an order’s status is equal to delivered Send reminders based on important dates and times like Appointment.starts_at Provision an account or user when they activate a subscriptionhttps://docs.customer.io/release-notes/2025-12-22-journey-attributes/Mon, 22 Dec 2025 00:00:00 +0000https://docs.customer.io/release-notes/2025-12-22-journey-attributes/This means you no longer have to store webhook data important to a person’s journey on their profile, which doesn’t expire and could clutter up your workspace.https://docs.customer.io/release-notes/2025-12-22-improved-help/Mon, 22 Dec 2025 00:00:00 +0000https://docs.customer.io/release-notes/2025-12-22-improved-help/Help & Support now available everywhere: The Need Help? option was missing on some pages. Now it’s available on every page. Simplified support form: We’ve made the Get Help form easier to find and use—now it’s a single screen rather than four separate pages. You can even generate the form’s subject line with AI! Featured videos: We’ve added videos to help you learn more about Customer.io. Better organization: Resources, education, and support options are grouped into clear categories.https://docs.customer.io/release-notes/2025-12-19-audit-logs/Fri, 19 Dec 2025 00:00:00 +0000https://docs.customer.io/release-notes/2025-12-19-audit-logs/You must be an Account Admin to access Audit Logs.https://docs.customer.io/release-notes/2025-12-16-in-app-move-settings/Tue, 16 Dec 2025 00:00:00 +0000https://docs.customer.io/release-notes/2025-12-16-in-app-move-settings/https://docs.customer.io/release-notes/2025-12-15-push-message-priority/Mon, 15 Dec 2025 00:00:00 +0000https://docs.customer.io/release-notes/2025-12-15-push-message-priority/Under normal priority, Android devices in standby mode might not wake up long enough to send delivery metrics back to Customer.io, so you might not see messages as delivered until your users open your app. Setting High priority tells the recipient’s device to wake up to properly report delivery metrics!https://docs.customer.io/release-notes/2025-12-12-last-used-login/Fri, 12 Dec 2025 00:00:00 +0000https://docs.customer.io/release-notes/2025-12-12-last-used-login/https://docs.customer.io/release-notes/2025-12-09-custom-access/Tue, 09 Dec 2025 00:00:00 +0000https://docs.customer.io/release-notes/2025-12-09-custom-access/Create roles in Account Settings to give external partners, developers, or marketers just the access they need, nothing more. You must be an Account Admin to create and assign custom roles.https://docs.customer.io/release-notes/2025-12-05-random-delay/Fri, 05 Dec 2025 00:00:00 +0000https://docs.customer.io/release-notes/2025-12-05-random-delay/This can help you greatly simplify workflows if you’ve added branches with a variety of time delays to achieve the same effect.https://docs.customer.io/release-notes/2025-11-18-sticky-notes-linking/Tue, 18 Nov 2025 00:00:00 +0000https://docs.customer.io/release-notes/2025-11-18-sticky-notes-linking/To link sticky notes to workflow items: Click the icon on the note and drag it to the workflow item you want to attach it to.https://docs.customer.io/release-notes/2025-11-13-ai-get-features/Thu, 13 Nov 2025 00:00:00 +0000https://docs.customer.io/release-notes/2025-11-13-ai-get-features/You can ask our assistant about: Segment conditions: “When do people enter my Onboarding segment?” Campaign performance: “What’s the click-to-open rate for my Onboarding campaign and how does that compare to my Welcome campaign?” Email template/content analysis: “Are there any issues with my email template that might affect performance with my audience?” You can combine these things as well. For example, you might request information about a campaign and then ask the assistant to analyze the emails in the campaign for issues that might affect performance or deliverability.https://docs.customer.io/release-notes/2025-11-06-random-cohorts-objects/Thu, 06 Nov 2025 00:00:00 +0000https://docs.customer.io/release-notes/2025-11-06-random-cohorts-objects/https://docs.customer.io/release-notes/2025-10-30-recommended-send-time/Thu, 30 Oct 2025 00:00:00 +0000https://docs.customer.io/release-notes/2025-10-30-recommended-send-time/This feature works great with our other new feature: Automatic Geolocation Data Collection. This helps you gather your audience’s time zone data, which you can use to produce better send time recommendations!https://docs.customer.io/release-notes/2025-10-24-automatic-geolocation/Fri, 24 Oct 2025 00:00:00 +0000https://docs.customer.io/release-notes/2025-10-24-automatic-geolocation/Our JavaScript client and mobile SDKs automatically capture IP addresses for you, making geolocation easy. If you use our backend libraries (like our Node.JS or Go SDKs) or our Pipelines API, you’ll need to: Go to your integration’s Settings tab and turn on the Enable Geolocation setting. Capture the IP address yourself and pass it in the context.ip field in your identify requests. This setting is on by default for workspaces in our US data center and off by default for workspaces in our EU data center.https://docs.customer.io/release-notes/2025-10-22-salesforce-filter/Wed, 22 Oct 2025 00:00:00 +0000https://docs.customer.io/release-notes/2025-10-22-salesforce-filter/While Salesforce filters typically require a SQL syntax, we’ve included a handy AI box, where you can describe the data you want to bring into Customer.io and we’ll generate a filter for you.https://docs.customer.io/release-notes/2025-10-16-collections-moved/Thu, 16 Oct 2025 00:00:00 +0000https://docs.customer.io/release-notes/2025-10-16-collections-moved/If you haven’t used collections before, now’s a great time to start! Collections let you store data that you want to use in campaigns but isn’t necessarily associated with people or objectsAn object is a non-person entity that you can associate with one or more people—like a company, account, or online course.. These could be things like available promotions/coupons or upcoming events your audience might be interested in.https://docs.customer.io/release-notes/2025-10-16-assistant-upload-image/Thu, 16 Oct 2025 00:00:00 +0000https://docs.customer.io/release-notes/2025-10-16-assistant-upload-image/Here are some examples of how you could use this feature: Upload an image for your emails and request the Assistant generate alt text. Upload charts from a third-party analytics tool and request it come up with recommendations based on the data.https://docs.customer.io/release-notes/2025-10-08-anonymous-for-mobile/Wed, 08 Oct 2025 00:00:00 +0000https://docs.customer.io/release-notes/2025-10-08-anonymous-for-mobile/You can even use inline content to populate your app for users who haven’t signed up or logged in. This helps you show default content to people who use your app but aren’t identified yet. Update to one of the following versions of our SDKs to get started. You don’t have to make any changes to your app code—just update the SDK. SDK Minimum required version for anonymous in-app messages iOS 3.https://docs.customer.io/release-notes/2025-10-07-assistant-metrics/Tue, 07 Oct 2025 00:00:00 +0000https://docs.customer.io/release-notes/2025-10-07-assistant-metrics/Ask it questions like “Which campaign had the lowest deliverability this month?” or “What’s the average click-to-open rate for my campaigns?” and it will search our docs and your workspace to give you a relevant answer. Click at the top of your workspace to get started!https://docs.customer.io/release-notes/2025-10-07-simplified-link-tracking/Tue, 07 Oct 2025 00:00:00 +0000https://docs.customer.io/release-notes/2025-10-07-simplified-link-tracking/https://docs.customer.io/release-notes/2025-10-06-in-app-lead-forms/Mon, 06 Oct 2025 00:00:00 +0000https://docs.customer.io/release-notes/2025-10-06-in-app-lead-forms/This is our first release of a component that captures form data like this, but we’re working to expand support for more complex surveys and forms in the future.https://docs.customer.io/release-notes/2025-10-03-ai-translation/Fri, 03 Oct 2025 00:00:00 +0000https://docs.customer.io/release-notes/2025-10-03-ai-translation/You can auto-translate across all message channels, but it’s not yet available for emails made in Design Studio. Not seeing this option? Check that Customer.io AI is enabled in Privacy, Data, & AI settings.https://docs.customer.io/release-notes/2025-10-02-email-content-analysis/Thu, 02 Oct 2025 00:00:00 +0000https://docs.customer.io/release-notes/2025-10-02-email-content-analysis/https://docs.customer.io/release-notes/2025-10-01-ai-business-profile/Wed, 01 Oct 2025 00:00:00 +0000https://docs.customer.io/release-notes/2025-10-01-ai-business-profile/https://docs.customer.io/release-notes/2025-09-25-assistant/Thu, 25 Sep 2025 00:00:00 +0000https://docs.customer.io/release-notes/2025-09-25-assistant/You can also create segments from the Assistant. Describe your criteria, and it will build a segment you can use to trigger campaigns or group members of your audience. At the top of your workspace, click the message bubble to get started. Make sure Customer.io AI is enabled in Privacy, Data, & AI settings to access the full experience!https://docs.customer.io/release-notes/2025-09-15-schedule-campaigns/Mon, 15 Sep 2025 00:00:00 +0000https://docs.customer.io/release-notes/2025-09-15-schedule-campaigns/Any campaign with a scheduled start or stop time will show a label “Scheduled” alongside the status (Draft, Running, or Stopped).https://docs.customer.io/release-notes/2025-09-04-inbound-sms-support/Thu, 04 Sep 2025 00:00:00 +0000https://docs.customer.io/release-notes/2025-09-04-inbound-sms-support/With this release, you can automatically handle opt-out keywords like STOP and UNSUBSCRIBE without setting up a complicated webhook-based workflow. Now we handle these for you. You can also use SMS replies from your audience as campaign triggers. Now when people respond to messages, you can add them to segments, send them follow-up messages and so on.https://docs.customer.io/release-notes/2025-09-04-send-newsletters-timezone-rate-limit/Thu, 04 Sep 2025 00:00:00 +0000https://docs.customer.io/release-notes/2025-09-04-send-newsletters-timezone-rate-limit/https://docs.customer.io/release-notes/2025-09-03-custom-short-link/Wed, 03 Sep 2025 00:00:00 +0000https://docs.customer.io/release-notes/2025-09-03-custom-short-link/Say goodbye to unbranded, spammy-looking links. Now you can send links your customers recognize and trust. Go to your > workspace settings > SMS and turn on Link shortening. Then click Add custom domain to add your own custom domain.https://docs.customer.io/release-notes/2025-09-03-ai-generated-descriptions/Wed, 03 Sep 2025 00:00:00 +0000https://docs.customer.io/release-notes/2025-09-03-ai-generated-descriptions/Go to your Data Index, select an attribute or event, and click in the description field to generate a description.https://docs.customer.io/release-notes/2025-07-23-in-app-survey-analysis/Wed, 23 Jul 2025 00:00:00 +0000https://docs.customer.io/release-notes/2025-07-23-in-app-survey-analysis/https://docs.customer.io/release-notes/2025-07-22-sunset-legacy-in-app/Tue, 22 Jul 2025 00:00:00 +0000https://docs.customer.io/release-notes/2025-07-22-sunset-legacy-in-app/We’re phasing out the legacy editor in two stages: On October 1, 2025, the legacy editor becomes edit-only. You can continue editing messages in the legacy editor, but you won’t be able to create new ones. On January 31, 2026, the legacy editor becomes read-only. You’ll still be able to see messages in the legacy editor, and they’ll continue working—but you won’t be able to edit them. We won’t delete your existing in-app messages!https://docs.customer.io/release-notes/2025-06-30-inline-in-app/Mon, 30 Jun 2025 00:00:00 +0000https://docs.customer.io/release-notes/2025-06-30-inline-in-app/When you send an inline message, you’ll specify the inline position and provide the ID of a view in your app that you want to populate with personalized content. You don’t have to push an app update or anything—just instant, relevant experiences for your users. Inline messages are great for: Contextual onboarding: Guide users step-by-step without overwhelming them Feature discovery: Highlight new features exactly where users will use them Targeted promotions: Show relevant offers based on user behavior Just-in-time help: Provide tips and guidance when users need it most Update your SDK to the latest version to get started.https://docs.customer.io/release-notes/2025-06-30-human-metrics-segments-conditions/Mon, 30 Jun 2025 00:00:00 +0000https://docs.customer.io/release-notes/2025-06-30-human-metrics-segments-conditions/https://docs.customer.io/release-notes/2025-06-19-human-metrics/Thu, 19 Jun 2025 00:00:00 +0000https://docs.customer.io/release-notes/2025-06-19-human-metrics/That’s all in the past. Our new Deliverability Analytics Dashboard—available on premium and enterprise plans—gives you detailed insights into your subscribers across inbox providers, all in one place. See your audience weight, bounce rates, and engagement metrics for Gmail, Outlook, Yahoo, and more. Just click Analysis in the left navigation area, and you’ll have the visibility you need to fix deliverability issues before they hurt your campaigns.https://docs.customer.io/release-notes/2025-06-18-transactional-sms/Wed, 18 Jun 2025 00:00:00 +0000https://docs.customer.io/release-notes/2025-06-18-transactional-sms/https://docs.customer.io/release-notes/2025-06-11-segment-builder-official/Wed, 11 Jun 2025 00:00:00 +0000https://docs.customer.io/release-notes/2025-06-11-segment-builder-official/Pro tip: add descriptions to your attributes and events to improve segment generation! Providing additional context on your data helps our segment builder better understand your data and provide more relevant results.https://docs.customer.io/release-notes/2025-06-04-in-app-page-exclusions/Wed, 04 Jun 2025 00:00:00 +0000https://docs.customer.io/release-notes/2025-06-04-in-app-page-exclusions/We also added a Test page rules feature, so you can make sure that your message will appear on the right pages before you send it.https://docs.customer.io/release-notes/2025-05-29-simple-web-in-app-setup/Thu, 29 May 2025 00:00:00 +0000https://docs.customer.io/release-notes/2025-05-29-simple-web-in-app-setup/Now, that’s all in the past. In-app messaging works automatically with our JavaScript integration. You just turn it on in your workspace settings and you’re ready to send messages to your website visitors—no extra code, no developer help needed.https://docs.customer.io/release-notes/2025-05-28-in-app-multi-step/Wed, 28 May 2025 00:00:00 +0000https://docs.customer.io/release-notes/2025-05-28-in-app-multi-step/As people click or tap buttons and links in a multi-step message, you can move them along to subsequent steps in your message. This helps you to show users the right content at the right time based on how they interact with your messages—all without complicated code or logic!https://docs.customer.io/release-notes/2025-05-27-design-studio-beta/Tue, 27 May 2025 00:00:00 +0000https://docs.customer.io/release-notes/2025-05-27-design-studio-beta/We’re rolling this out to everyone! The level of functionality you have access to depends on your workspace-level role: Workspace Admins and Authors have full access, Viewers can only view.https://docs.customer.io/release-notes/2025-05-16-sms-tracked-clicks/Fri, 16 May 2025 00:00:00 +0000https://docs.customer.io/release-notes/2025-05-16-sms-tracked-clicks/https://docs.customer.io/release-notes/2025-05-15-a-b-test-winner/Thu, 15 May 2025 00:00:00 +0000https://docs.customer.io/release-notes/2025-05-15-a-b-test-winner/https://docs.customer.io/release-notes/2025-05-14-human-metrics/Wed, 14 May 2025 00:00:00 +0000https://docs.customer.io/release-notes/2025-05-14-human-metrics/Hover over email metrics to compare human + machine metrics to human-only metrics. Human opened data is reliable as of March 20, 2025 and Human clicked data as of April 20, 2025.  We’re in the process of rolling this out Not seeing human metrics? We’re in the process of rolling this out to all customers; you’ll see them soon! Need to send these metrics to another platform or service? This data is now available through our reporting webhooks, APIs, and integrations.https://docs.customer.io/release-notes/2025-05-09-hide-sensitive-data/Fri, 09 May 2025 00:00:00 +0000https://docs.customer.io/release-notes/2025-05-09-hide-sensitive-data/Authors with sensitive data hidden have the same functionality as authors who can view all data, with one exception: they can’t edit people. If you currently use our legacy “Hide all attributes” setting, your teammates will experience no change to the data and functionality they have access to.https://docs.customer.io/release-notes/2025-04-21-attribute-or-segment-trigger/Mon, 21 Apr 2025 00:00:00 +0000https://docs.customer.io/release-notes/2025-04-21-attribute-or-segment-trigger/All campaigns that use our legacy segment trigger will continue to work as expected and you’ll be able to duplicate them. For new campaigns, you’ll use the new trigger. Note, the new trigger behaves differently than the legacy segment trigger in a few ways: filter conditions are now part of the trigger conditions, and you may need to add time-based conditions to ensure the right group of people trigger your campaigns at the correct time.https://docs.customer.io/release-notes/2025-04-16-anon-in-app-official/Wed, 16 Apr 2025 00:00:00 +0000https://docs.customer.io/release-notes/2025-04-16-anon-in-app-official/https://docs.customer.io/release-notes/2025-03-26-segment-builder-beta/Wed, 26 Mar 2025 00:00:00 +0000https://docs.customer.io/release-notes/2025-03-26-segment-builder-beta/You can opt out of this builder and revert to our standard experience through the toggle in the bottom right of segment creation.https://docs.customer.io/release-notes/2025-03-25-official-expo-release/Tue, 25 Mar 2025 00:00:00 +0000https://docs.customer.io/release-notes/2025-03-25-official-expo-release/If you’ve used a beta version of the plugin, you’ll notice that the official release includes support for Firebase Cloud Messaging (FCM) to iOS devices, and we’ve tried to slim down the workflow to make integrating even easier. Check out the changelog to see the complete list of Expo updates.https://docs.customer.io/release-notes/2025-03-20-whatsapp-content-templates/Thu, 20 Mar 2025 00:00:00 +0000https://docs.customer.io/release-notes/2025-03-20-whatsapp-content-templates/Before this release, you had to copy/paste content from Twilio into Customer.io before you could send a WhatsApp message. Now, when you add a WhatsApp message to a campaign or broadcast, you can simply select your Twilio content template. We fetch the template and expose the fields you can fill in so you don’t have to leave Customer.io.https://docs.customer.io/release-notes/2025-03-19-sms-link-shortening/Wed, 19 Mar 2025 00:00:00 +0000https://docs.customer.io/release-notes/2025-03-19-sms-link-shortening/Go to Workspace settings > SMS and turn on Shorten links. Shortened links use the format https://a.cx.io/lnk.abc123 (or https://e.cx.io/lnk.abc123 if you’re in our EU region), consuming between 28 and 38 characters so you have plenty of room to talk to your audience.https://docs.customer.io/release-notes/2025-03-10-attribute-descriptions/Mon, 10 Mar 2025 00:00:00 +0000https://docs.customer.io/release-notes/2025-03-10-attribute-descriptions/https://docs.customer.io/release-notes/2025-03-06-web-in-app-click-dismiss/Thu, 06 Mar 2025 00:00:00 +0000https://docs.customer.io/release-notes/2025-03-06-web-in-app-click-dismiss/https://docs.customer.io/release-notes/2025-02-10-object-campaigns-current-matches/Mon, 10 Feb 2025 00:00:00 +0000https://docs.customer.io/release-notes/2025-02-10-object-campaigns-current-matches/https://docs.customer.io/release-notes/2025-02-03-cioanalytics-js/Mon, 03 Feb 2025 00:00:00 +0000https://docs.customer.io/release-notes/2025-02-03-cioanalytics-js/https://docs.customer.io/release-notes/2025-01-30-inline-in-app-ios/Thu, 30 Jan 2025 00:00:00 +0000https://docs.customer.io/release-notes/2025-01-30-inline-in-app-ios/This feature is in early access and is available only to customers who are using our iOS Native SDK. Interested in joining our early release program? Fill out this form to request access. If you have questions, please let us know.https://docs.customer.io/release-notes/2025-01-23-auto-provision-access/Thu, 23 Jan 2025 00:00:00 +0000https://docs.customer.io/release-notes/2025-01-23-auto-provision-access/https://docs.customer.io/release-notes/2025-01-16-new-campaign-builder/Thu, 16 Jan 2025 00:00:00 +0000https://docs.customer.io/release-notes/2025-01-16-new-campaign-builder/https://docs.customer.io/release-notes/2024-12-24-expo-2-release/Tue, 24 Dec 2024 00:00:00 +0000https://docs.customer.io/release-notes/2024-12-24-expo-2-release/Where previous releases were mostly limited to sending message-related events (like the Push Opened event) to other platforms, this new release makes it much easier to send any data from your React Native app to the rest of your martech stack—the people you identify, the events you track, the screens people visit, and so on. And, unlike traditional CDPs (Segment, Rudderstack, and so on), you don’t have to pay for this feature.https://docs.customer.io/release-notes/2024-12-19-duplicate-campaigns/Thu, 19 Dec 2024 00:00:00 +0000https://docs.customer.io/release-notes/2024-12-19-duplicate-campaigns/https://docs.customer.io/release-notes/2024-12-13-attio-destination-integration/Fri, 13 Dec 2024 00:00:00 +0000https://docs.customer.io/release-notes/2024-12-13-attio-destination-integration/https://docs.customer.io/release-notes/2024-12-12-branching-with-objects-2/Thu, 12 Dec 2024 00:00:00 +0000https://docs.customer.io/release-notes/2024-12-12-branching-with-objects-2/https://docs.customer.io/release-notes/2024-12-10-flutter-2-release/Tue, 10 Dec 2024 00:00:00 +0000https://docs.customer.io/release-notes/2024-12-10-flutter-2-release/Where previous releases were mostly limited to sending message-related events (like the Push Opened event) to other platforms, this new release makes it much easier to send any data from your Flutter app to the rest of your martech stack—the people you identify, the events you track, the screens people visit, and so on. And, unlike traditional CDPs (Segment, Rudderstack, and so on), you don’t have to pay for this feature.https://docs.customer.io/release-notes/2024-10-17-new-data-warehouse-outputs/Thu, 17 Oct 2024 00:00:00 +0000https://docs.customer.io/release-notes/2024-10-17-new-data-warehouse-outputs/To use these new exports, simply go to your data warehouse integration and turn on the Campaign Metadata, Objects, and Object Attributes outputs.https://docs.customer.io/release-notes/2024-10-16-react-native-4-release/Wed, 16 Oct 2024 00:00:00 +0000https://docs.customer.io/release-notes/2024-10-16-react-native-4-release/Where previous releases were mostly limited to sending message-related events (like the Push Opened event) to other platforms, this new release makes it much easier to send any data from your React Native app to the rest of your martech stack—the people you identify, the events you track, the screens people visit, and so on. And, unlike traditional CDPs (Segment, Rudderstack, and so on), you don’t have to pay for this feature.https://docs.customer.io/release-notes/2024-10-15-firebase-11-support/Tue, 15 Oct 2024 00:00:00 +0000https://docs.customer.io/release-notes/2024-10-15-firebase-11-support/ iOS SDK 3.4.1 or 2.14.2 React Native SDK 3.9.1 Flutter: follow our instructions to update your iOS Native dependency version 2.14.2.https://docs.customer.io/release-notes/2024-09-17-salesforce-source/Tue, 17 Sep 2024 00:00:00 +0000https://docs.customer.io/release-notes/2024-09-17-salesforce-source/To get started, you’ll simply map your Salesforce data to its Customer.io equivalent. You determine which data you want to send into Customer.io—contacts, leads, opportunities, accounts, and whatever else you need to send messages that engage your customers and increase conversions. Once your data is in Customer.io, you can send people messages and even feed data from Salesforce back into your Salesforce environment!https://docs.customer.io/release-notes/2024-08-29-in-app-easy-audience/Thu, 29 Aug 2024 00:00:00 +0000https://docs.customer.io/release-notes/2024-08-29-in-app-easy-audience/If you already set them up with the To field, you have nothing to worry about. We’ve taken care of things for you. Your messages will go to the right person, whether you identify them by ID or email address.https://docs.customer.io/release-notes/2024-08-28-pause-newsletter/Wed, 28 Aug 2024 00:00:00 +0000https://docs.customer.io/release-notes/2024-08-28-pause-newsletter/https://docs.customer.io/release-notes/2024-07-24-android-data-pipelines/Wed, 24 Jul 2024 00:00:00 +0000https://docs.customer.io/release-notes/2024-07-24-android-data-pipelines/This latest version of the SDK supports the following new features: Anonymous tracking: You can send anonymous events, and we’ll reconcile anonymous activity with your users when you identify them. Data Pipelines Support: Sending your mobile data into our customer data platform (CDP) helps you support both Journeys and the rest of your martech stack—analytics, data warehouses, CRMs and more.* Built-in lifecycle events: the SDK now automatically captures events like “Application Installed” and “Application Updated” for you, so you better understand your users’ behaviors in your app.https://docs.customer.io/release-notes/2024-07-15-in-app-visual-editor/Mon, 15 Jul 2024 00:00:00 +0000https://docs.customer.io/release-notes/2024-07-15-in-app-visual-editor/Where our old editor’s code view had its own confusing structure, the new editor lets you switch to a full HTML-code view. If you’re a savvy developer, you’ll be able to edit HTML tags and classes directly; when you switch to the in-app code view, it’ll look and feel just like you’re editing code on your own website! New editor Old editor We’ve even included a number of new templates to help you get started.https://docs.customer.io/release-notes/2024-07-10-test-delivery-mode/Wed, 10 Jul 2024 00:00:00 +0000https://docs.customer.io/release-notes/2024-07-10-test-delivery-mode/https://docs.customer.io/release-notes/2024-06-27-data-index-export/Thu, 27 Jun 2024 00:00:00 +0000https://docs.customer.io/release-notes/2024-06-27-data-index-export/https://docs.customer.io/release-notes/2024-06-20-role-per-workspace/Thu, 20 Jun 2024 00:00:00 +0000https://docs.customer.io/release-notes/2024-06-20-role-per-workspace/https://docs.customer.io/release-notes/2024-06-20-partial-account-access/Thu, 20 Jun 2024 00:00:00 +0000https://docs.customer.io/release-notes/2024-06-20-partial-account-access/https://docs.customer.io/release-notes/2024-05-29-generic-saml/Wed, 29 May 2024 00:00:00 +0000https://docs.customer.io/release-notes/2024-05-29-generic-saml/https://docs.customer.io/release-notes/2024-05-22-salesforce-source-ea/Wed, 22 May 2024 00:00:00 +0000https://docs.customer.io/release-notes/2024-05-22-salesforce-source-ea/To get started, all you need to do is map your Salesforce data to its Customer.io equivalent. You determine which data you want to send into Customer.io—contacts, leads, opportunities, accounts, and whatever else you need to send messages that engage your customers and increase conversions. If you’re on an essentials plan, you can request access to our Salesforce integration in your Customer.io dashboard. This feature is in early access. You’re welcome to use it, but we’re still adding features (like real-time streams) and smoothing out some rough edges.https://docs.customer.io/release-notes/2024-05-02-apple-vision-pro/Thu, 02 May 2024 00:00:00 +0000https://docs.customer.io/release-notes/2024-05-02-apple-vision-pro/We’ve added a handy sample app to our iOS SDK, so you can see what Customer.io looks like in VR. But, if you’ve developed an app with our mobile SDK already, our visionOS support should come naturally to you.https://docs.customer.io/release-notes/2024-04-26-css-preprocess-workspace/Fri, 26 Apr 2024 00:00:00 +0000https://docs.customer.io/release-notes/2024-04-26-css-preprocess-workspace/https://docs.customer.io/release-notes/2024-04-10-app-store-privacy/Wed, 10 Apr 2024 00:00:00 +0000https://docs.customer.io/release-notes/2024-04-10-app-store-privacy/ iOS: ≥ 3.1.0 or ≥ 2.13.0 React Native: ≥ 3.6.0 Flutter: requires iOS ≥ 2.13.0. Follow our update instructions to update the iOS native package in Flutter. Expo: requires React Native ≥ 3.6.0. Install the latest React Native SDK and run expo prebuild --clean.https://docs.customer.io/release-notes/2024-03-28-individual-add-remove-manual-segment/Thu, 28 Mar 2024 00:00:00 +0000https://docs.customer.io/release-notes/2024-03-28-individual-add-remove-manual-segment/https://docs.customer.io/release-notes/2024-03-20-ios-data-pipelines/Wed, 20 Mar 2024 00:00:00 +0000https://docs.customer.io/release-notes/2024-03-20-ios-data-pipelines/This latest version of the SDK supports the following new features: Data Pipelines Support: Send your mobile data to Data Pipelines (our customer data platform) to route it to Journeys, and the rest of your martech stack—analytics, data warehouses, CRMs and more.* Anonymous tracking: You can send anonymous events, and we’ll reconcile anonymous activity with the user when you identify them. Built-in lifecycle events: the SDK now automatically captures events like “Application Installed” and “Application Updated” for you, so you better understand your users’ behaviors in your app.https://docs.customer.io/release-notes/2024-03-08-workspace-setting-liquid-version/Fri, 08 Mar 2024 00:00:00 +0000https://docs.customer.io/release-notes/2024-03-08-workspace-setting-liquid-version/https://docs.customer.io/release-notes/2024-02-23-download-invoice/Fri, 23 Feb 2024 00:00:00 +0000https://docs.customer.io/release-notes/2024-02-23-download-invoice/https://docs.customer.io/release-notes/2024-02-21-dmarc-policy/Wed, 21 Feb 2024 00:00:00 +0000https://docs.customer.io/release-notes/2024-02-21-dmarc-policy/https://docs.customer.io/release-notes/2024-02-20-latest-liquid/Tue, 20 Feb 2024 00:00:00 +0000https://docs.customer.io/release-notes/2024-02-20-latest-liquid/https://docs.customer.io/release-notes/2024-02-02-3mb-image-size/Tue, 13 Feb 2024 00:00:00 +0000https://docs.customer.io/release-notes/2024-02-02-3mb-image-size/We appreciate your feedback and are always looking for ways to improve our product—whether by adding new features or fixing recent changes! If you have feedback on this or any other feature, please let us know.https://docs.customer.io/release-notes/2024-02-12-ios-automatic-push-handling/Mon, 12 Feb 2024 00:00:00 +0000https://docs.customer.io/release-notes/2024-02-12-ios-automatic-push-handling/This release updates the platforms below. We’ve linked to upgrade documentation for each SDK, highlighting the code you can remove from your app when you upgrade: iOS 2.11 React Native 3.4 Flutter (affects iOS native SDK) Expo: Upgrade to 1.0.0-beta.14 and run expo prebuild --clean.https://docs.customer.io/release-notes/2024-02-09-rev-etl-updates/Fri, 09 Feb 2024 00:00:00 +0000https://docs.customer.io/release-notes/2024-02-09-rev-etl-updates/https://docs.customer.io/release-notes/2024-02-02-image-size/Fri, 02 Feb 2024 00:00:00 +0000https://docs.customer.io/release-notes/2024-02-02-image-size/https://docs.customer.io/release-notes/2024-01-29-new-campaign-ux/Mon, 29 Jan 2024 00:00:00 +0000https://docs.customer.io/release-notes/2024-01-29-new-campaign-ux/https://docs.customer.io/release-notes/2024-01-29-object-campaigns/Mon, 29 Jan 2024 00:00:00 +0000https://docs.customer.io/release-notes/2024-01-29-object-campaigns/https://docs.customer.io/release-notes/2024-01-26-import-objects/Fri, 26 Jan 2024 00:00:00 +0000https://docs.customer.io/release-notes/2024-01-26-import-objects/https://docs.customer.io/release-notes/2023-12-13-lang-variants/Wed, 13 Dec 2023 00:00:00 +0000https://docs.customer.io/release-notes/2023-12-13-lang-variants/https://docs.customer.io/release-notes/2023-11-14-object-export/Tue, 14 Nov 2023 00:00:00 +0000https://docs.customer.io/release-notes/2023-11-14-object-export/https://docs.customer.io/release-notes/2023-11-13-in-app-overlay-color/Mon, 13 Nov 2023 00:00:00 +0000https://docs.customer.io/release-notes/2023-11-13-in-app-overlay-color/https://docs.customer.io/release-notes/2023-11-13-in-app-max-width/Mon, 13 Nov 2023 00:00:00 +0000https://docs.customer.io/release-notes/2023-11-13-in-app-max-width/https://docs.customer.io/release-notes/2023-11-07-hide-data-authors/Tue, 07 Nov 2023 00:00:00 +0000https://docs.customer.io/release-notes/2023-11-07-hide-data-authors/https://docs.customer.io/release-notes/2023-11-02-multi-page-rules/Thu, 02 Nov 2023 00:00:00 +0000https://docs.customer.io/release-notes/2023-11-02-multi-page-rules/https://docs.customer.io/release-notes/2023-10-31-data-pipelines-zendesk/Tue, 31 Oct 2023 00:00:00 +0000https://docs.customer.io/release-notes/2023-10-31-data-pipelines-zendesk/https://docs.customer.io/release-notes/2023-10-25-in-app-persist-messages.md/Wed, 25 Oct 2023 00:00:00 +0000https://docs.customer.io/release-notes/2023-10-25-in-app-persist-messages.md/If you use our Web SDK, you can start sending persistent in-app messages today. If you use our Mobile SDKs, you’ll need to update to the latest version to take advantage of this feature. Persistent messages are available starting in: Android 3.7.0 iOS 2.8.4 React Native 3.2.0 Flutter 1.3.0https://docs.customer.io/release-notes/2023-10-17-third-party-delivery-metrics/Tue, 17 Oct 2023 00:00:00 +0000https://docs.customer.io/release-notes/2023-10-17-third-party-delivery-metrics/https://docs.customer.io/release-notes/2023-10-11-get-workspaces/Wed, 11 Oct 2023 00:00:00 +0000https://docs.customer.io/release-notes/2023-10-11-get-workspaces/https://docs.customer.io/release-notes/2023-10-05-hide-data-viewers/Thu, 05 Oct 2023 00:00:00 +0000https://docs.customer.io/release-notes/2023-10-05-hide-data-viewers/https://docs.customer.io/release-notes/2023-09-29-data-pipelines-gtm/Fri, 29 Sep 2023 00:00:00 +0000https://docs.customer.io/release-notes/2023-09-29-data-pipelines-gtm/https://docs.customer.io/release-notes/2023-09-11-in-app-drag-and-drop/Mon, 11 Sep 2023 00:00:00 +0000https://docs.customer.io/release-notes/2023-09-11-in-app-drag-and-drop/https://docs.customer.io/release-notes/2023-08-09-bulk-topic-assignment/Wed, 09 Aug 2023 00:00:00 +0000https://docs.customer.io/release-notes/2023-08-09-bulk-topic-assignment/https://docs.customer.io/release-notes/2023-08-09-in-app-message-outline/Wed, 09 Aug 2023 00:00:00 +0000https://docs.customer.io/release-notes/2023-08-09-in-app-message-outline/With the new message navigation panel, you can: See the structure of your message at a glance Click to a component to go directly to it in your message Hide and show components, making it easier to focus on what mattershttps://docs.customer.io/release-notes/2023-07-17-microsurveys/Mon, 17 Jul 2023 00:00:00 +0000https://docs.customer.io/release-notes/2023-07-17-microsurveys/In the past, setting up button components likely meant adding a series of parent and child components—grids, padding, etc—to your message that wasn’t always intuitive. The new Rating Scale and Survey components are preconfigured groups of components that you can add to your message, and they’re ready to use out of the box. But you can also customize these components to set button names, images, and action names that make sense to you and your audience.https://docs.customer.io/release-notes/2023-07-11-sub-center-metrics/Tue, 11 Jul 2023 00:00:00 +0000https://docs.customer.io/release-notes/2023-07-11-sub-center-metrics/https://docs.customer.io/release-notes/2023-07-05-react-native-3/Wed, 05 Jul 2023 00:00:00 +0000https://docs.customer.io/release-notes/2023-07-05-react-native-3/https://docs.customer.io/release-notes/2023-06-30-in-app-components/Fri, 30 Jun 2023 00:00:00 +0000https://docs.customer.io/release-notes/2023-06-30-in-app-components/https://docs.customer.io/release-notes/2023-06-23-override-topic/Fri, 23 Jun 2023 00:00:00 +0000https://docs.customer.io/release-notes/2023-06-23-override-topic/https://docs.customer.io/release-notes/2023-06-14-in-app-editor-improvements/Wed, 14 Jun 2023 00:00:00 +0000https://docs.customer.io/release-notes/2023-06-14-in-app-editor-improvements/Sticky preview: The preview stays in view, so you can see your message as you edit it. Expanded editing space: We increased the size of the in-app message editor and reduced the impact of other UI elements, making more room for you to work on your messages. Expand and collapse elements: The hierarchy of elements in your message are clearer, and elements aren’t hidden by default when you start a new message from a template.https://docs.customer.io/release-notes/2023-06-06-custom-sub-pref-page/Tue, 06 Jun 2023 00:00:00 +0000https://docs.customer.io/release-notes/2023-06-06-custom-sub-pref-page/https://docs.customer.io/release-notes/2023-06-05-generic-sso/Mon, 05 Jun 2023 00:00:00 +0000https://docs.customer.io/release-notes/2023-06-05-generic-sso/https://docs.customer.io/release-notes/2023-06-01-customize-sub-center-topic-order/Thu, 01 Jun 2023 00:00:00 +0000https://docs.customer.io/release-notes/2023-06-01-customize-sub-center-topic-order/https://docs.customer.io/release-notes/2023-06-01-in-app-dismiss-custom-action/Thu, 01 Jun 2023 00:00:00 +0000https://docs.customer.io/release-notes/2023-06-01-in-app-dismiss-custom-action/https://docs.customer.io/release-notes/2023-05-25-relate-objects-via-ui/Thu, 25 May 2023 00:00:00 +0000https://docs.customer.io/release-notes/2023-05-25-relate-objects-via-ui/https://docs.customer.io/release-notes/2023-05-17-translate-your-sub-center/Wed, 17 May 2023 00:00:00 +0000https://docs.customer.io/release-notes/2023-05-17-translate-your-sub-center/https://docs.customer.io/release-notes/2023-05-17-verify-webhook-actions/Wed, 17 May 2023 00:00:00 +0000https://docs.customer.io/release-notes/2023-05-17-verify-webhook-actions/https://docs.customer.io/release-notes/2023-05-12-azure-sso/Fri, 12 May 2023 00:00:00 +0000https://docs.customer.io/release-notes/2023-05-12-azure-sso/https://docs.customer.io/release-notes/2023-05-11-multiple-object-types/Thu, 11 May 2023 00:00:00 +0000https://docs.customer.io/release-notes/2023-05-11-multiple-object-types/To create object types, go to Settings > Workspace Settings > Custom Objects. After creating a new type, you can access it under People in the left hand nav. Your plan determines the number of object types you can enable at a time. All of our self-service plans (Basic, Startup) follow the count for Essentials, whereas Startup+ has the same count as Premium and Enterprise plans. On July 1, we will start charging for objects (not types) that surpass the count included in your plan.https://docs.customer.io/release-notes/2023-05-10-global-unsubscribe-branding/Wed, 10 May 2023 00:00:00 +0000https://docs.customer.io/release-notes/2023-05-10-global-unsubscribe-branding/https://docs.customer.io/release-notes/2023-05-08-transactional-api-for-push-notifications/Mon, 08 May 2023 00:00:00 +0000https://docs.customer.io/release-notes/2023-05-08-transactional-api-for-push-notifications/https://docs.customer.io/release-notes/2023-05-01-2fa-via-email/Mon, 01 May 2023 00:00:00 +0000https://docs.customer.io/release-notes/2023-05-01-2fa-via-email/https://docs.customer.io/release-notes/2023-04-29-add-dynamic-expiration-dates-to-in-app-messages/Fri, 28 Apr 2023 00:00:00 +0000https://docs.customer.io/release-notes/2023-04-29-add-dynamic-expiration-dates-to-in-app-messages/You can now use liquid syntax to set the expiration date for an in-app message. Use event properties, profile attributes, snippets, and more. For example, if you want an in-app message to expire based when an online course is scheduled to start, you can use liquid syntax to set the expiration date to {{event.class_start_date}}.https://docs.customer.io/release-notes/2023-04-18-partial-update-preferences/Tue, 18 Apr 2023 00:00:00 +0000https://docs.customer.io/release-notes/2023-04-18-partial-update-preferences/With this update, you can also import each subscription topic preference as its own attribute via CSV.https://docs.customer.io/release-notes/2023-04-03-flutter-official-release/Mon, 03 Apr 2023 00:00:00 +0000https://docs.customer.io/release-notes/2023-04-03-flutter-official-release/Our Flutter SDK supports all the same features as our other SDKs, including in-app messaging, support for images and links (rich push), and the ability to send events from your audience’s devices. As an officially-supported SDK, we’ll continue updating our Flutter library to support both OS updates and new features that we expose in Customer.io.https://docs.customer.io/release-notes/2023-03-30-push-with-default-sound/Thu, 30 Mar 2023 00:00:00 +0000https://docs.customer.io/release-notes/2023-03-30-push-with-default-sound/This only adds support for the default system sound. Our SDKs do not yet support custom sounds.https://docs.customer.io/release-notes/2023-03-29-amp-for-email/Wed, 29 Mar 2023 00:00:00 +0000https://docs.customer.io/release-notes/2023-03-29-amp-for-email/AMP lets your customers complete surveys, RSVP to events, respond to comments, and more within your emails. Visit Amp.dev to find templates and components for your use case. Toggle these experimental features on in Account Settings to get started: Advanced Code Editor and AMP for Email.https://docs.customer.io/release-notes/2023-03-07-objects-reverse-etl/Tue, 07 Mar 2023 00:00:00 +0000https://docs.customer.io/release-notes/2023-03-07-objects-reverse-etl/https://docs.customer.io/release-notes/2023-03-03-in-app-official-release/Fri, 03 Mar 2023 00:00:00 +0000https://docs.customer.io/release-notes/2023-03-03-in-app-official-release/While in beta, we’ve made some major improvements to our in-app solution: We’ve improved our UI, making it a little easier to compose in-app messages Lowered response times for in-app messages, ensuring that your audience receives messages when they’re most relevant. Removed the need for an organization_id in integrations, so it’s easier to get started with in-app messages.https://docs.customer.io/release-notes/2023-02-23-in-app-improvements/Thu, 23 Feb 2023 00:00:00 +0000https://docs.customer.io/release-notes/2023-02-23-in-app-improvements/In the improved editor, you can: See all the settings in a block without having to “reveal” or “hide” things. See how your padding and font changes affect your message in real time. See a list of available font and color settings with examples. Rename blocks and cards in your template so it’s easier to explain what each block or group of blocks does.https://docs.customer.io/release-notes/2023-02-22-rename-in-app-messages/Wed, 22 Feb 2023 00:00:00 +0000https://docs.customer.io/release-notes/2023-02-22-rename-in-app-messages/https://docs.customer.io/release-notes/2023-02-21-subscription-center-branding/Tue, 21 Feb 2023 00:00:00 +0000https://docs.customer.io/release-notes/2023-02-21-subscription-center-branding/https://docs.customer.io/release-notes/2023-02-16-segments-with-objects-in-campaigns/Thu, 16 Feb 2023 00:00:00 +0000https://docs.customer.io/release-notes/2023-02-16-segments-with-objects-in-campaigns/We’re committed to supporting one-to-many, and eventually many-to-many, relationships using objects. Stay tuned for updates as we continue working on this new feature!https://docs.customer.io/release-notes/2022-02-02-message-limit-auto-retry/Thu, 02 Feb 2023 00:00:00 +0000https://docs.customer.io/release-notes/2022-02-02-message-limit-auto-retry/https://docs.customer.io/release-notes/2022-01-23-objects-beta/Mon, 23 Jan 2023 00:00:00 +0000https://docs.customer.io/release-notes/2022-01-23-objects-beta/To create objects, you’ll define their type—like companies, accounts, and so on. Then you’ll create them—this process is a bit like identifying people. You’ll identify an object, set its attributesA key-value pair that you associate with a person or an object—like a person’s name, the date they were created in your workspace, or a company’s billing date etc. Use attributes to target people and personalize messages., and then add relationships to people.https://docs.customer.io/release-notes/2023-01-20-subscription-center-beta/Fri, 20 Jan 2023 00:00:00 +0000https://docs.customer.io/release-notes/2023-01-20-subscription-center-beta/In the past, if you wanted to manage your audience’s subscription preferences, you would have had to set up attributes representing people’s preferences and apply preferences to messages with complicated segments or campaign filters. It was a confusing, error-prone process. The new subscription center feature lets you set topics for your campaigns, broadcasts, and newsletters, and automates preference logic. When people click the Unsubscribe link in your messages, our default unsubscribe page now lets people pick their subscription preferences—providing an easy way for people to update their preferences and creating a way to retain subscribers who might not like all of your messages.https://docs.customer.io/release-notes/2023-01-17-auto-delete-devices/Tue, 17 Jan 2023 00:00:00 +0000https://docs.customer.io/release-notes/2023-01-17-auto-delete-devices/This helps you maintain a better understanding of your audience’s devices, so you know which devices are relevant and can get a real device count—without having to clean up old devices yourself.https://docs.customer.io/release-notes/2023-01-10-track-v2-api/Tue, 10 Jan 2023 00:00:00 +0000https://docs.customer.io/release-notes/2023-01-10-track-v2-api/https://docs.customer.io/release-notes/2022-12-26-flutter-alpha/Mon, 26 Dec 2022 00:00:00 +0000https://docs.customer.io/release-notes/2022-12-26-flutter-alpha/We’re committed to releasing, maintaining, and supporting Flutter. Try out our new SDK and let us know what you think. Your feedback helps us understand your needs, so that we build our SDK(s) and associated features to fit your needs.https://docs.customer.io/release-notes/2022-12-07-target-platform-with-page-rules/Wed, 07 Dec 2022 00:00:00 +0000https://docs.customer.io/release-notes/2022-12-07-target-platform-with-page-rules/https://docs.customer.io/release-notes/2022-12-05-holdout-test/Mon, 05 Dec 2022 00:00:00 +0000https://docs.customer.io/release-notes/2022-12-05-holdout-test/In the past, we had a complicated recipe to perform holdout tests, but it involved sending real messages to a black hole address, which wasn’t ideal. Now you can set up holdout tests with a simple checkbox!https://docs.customer.io/release-notes/2022-11-24-transactional-message-name/Wed, 30 Nov 2022 00:00:00 +0000https://docs.customer.io/release-notes/2022-11-24-transactional-message-name/https://docs.customer.io/release-notes/2022-11-24-database-sync-intervals/Thu, 24 Nov 2022 00:00:00 +0000https://docs.customer.io/release-notes/2022-11-24-database-sync-intervals/Now, we attempt to perform sync operations on your exact interval without regard to the time it takes to complete an import operation; if we’re still importing from your database on a sync interval, we’ll skip it (showing a skipped status in our UI), and try again at the next interval. This adds predictability to your database sync integrations, so you’ll always know when you can expect to see your data in Customer.https://docs.customer.io/release-notes/2022-11-17-amplitude-and-mixpanel-integrations/Thu, 17 Nov 2022 00:00:00 +0000https://docs.customer.io/release-notes/2022-11-17-amplitude-and-mixpanel-integrations/See our Amplitude and Mixpanel pages for more information about these integrations.https://docs.customer.io/release-notes/2022-11-17-multi-language-transactional/Thu, 17 Nov 2022 00:00:00 +0000https://docs.customer.io/release-notes/2022-11-17-multi-language-transactional/https://docs.customer.io/release-notes/2022-11-15-asset-library/Tue, 15 Nov 2022 00:00:00 +0000https://docs.customer.io/release-notes/2022-11-15-asset-library/https://docs.customer.io/release-notes/2022-11-09-wildcard-page-rules/Wed, 09 Nov 2022 00:00:00 +0000https://docs.customer.io/release-notes/2022-11-09-wildcard-page-rules/With this feature, you can use a path beginning with a set of characters (begin*), ending with a set of characters (*end), or in a path (https//example.com/*/billing).https://docs.customer.io/release-notes/2022-11-02-in-app-expiration-hours/Wed, 02 Nov 2022 00:00:00 +0000https://docs.customer.io/release-notes/2022-11-02-in-app-expiration-hours/As a part of this release, we’ve also changed the default expiration period from 365 days to 30 days.https://docs.customer.io/release-notes/2022-10-26-official-react-native/Wed, 26 Oct 2022 00:00:00 +0000https://docs.customer.io/release-notes/2022-10-26-official-react-native/https://docs.customer.io/release-notes/2022-10-24-compare-conversion-to-trigger/Mon, 24 Oct 2022 00:00:00 +0000https://docs.customer.io/release-notes/2022-10-24-compare-conversion-to-trigger/For example, imagine that you start a campaign when someone begins an educational course; maybe your event is called course_started, and it has a course_id that you use to identify different courses you offer. Your campaign’s goal is to help someone finish the exercise, so you need to look for an event called course_completed with the same course_id. That kind of comparison is now possible, and you can use it to your advantage to pinpoint highly-specific conversion criteria!https://docs.customer.io/release-notes/2022-10-21-dws-v4-content-schema/Fri, 21 Oct 2022 00:00:00 +0000https://docs.customer.io/release-notes/2022-10-21-dws-v4-content-schema/See the Delivery Content schema for information about the new table in v4. Go to the documentation link below for help updating to v4.  Upgrade to v4 to use subjects and outputs We’ve made some minor changes to subjects and outputs a part of our v4 release. If you’re using a previous schema version, we disabled your subjects and outputs on October 31st, 2022. You need to upgrade to schema version 4 or later, to continue syncing outputs and subjects data.https://docs.customer.io/release-notes/2022-10-17-copy-newsletters-broadcasts/Mon, 17 Oct 2022 00:00:00 +0000https://docs.customer.io/release-notes/2022-10-17-copy-newsletters-broadcasts/https://docs.customer.io/release-notes/2022-10-13-campaign-trigger-update/Thu, 13 Oct 2022 00:00:00 +0000https://docs.customer.io/release-notes/2022-10-13-campaign-trigger-update/https://docs.customer.io/release-notes/2022-10-05-export-duplicates-and-devices/Thu, 06 Oct 2022 00:00:00 +0000https://docs.customer.io/release-notes/2022-10-05-export-duplicates-and-devices/This feature also adds the ability to export a list of devices. You might export devices to clean up bounced or suppressed devices.https://docs.customer.io/release-notes/2022-10-05-push-composer-improvements/Wed, 05 Oct 2022 00:00:00 +0000https://docs.customer.io/release-notes/2022-10-05-push-composer-improvements/We’re rolling the new rich push editor out to accounts over the next week. Contact product@customer.io if you want to start using it today.https://docs.customer.io/release-notes/2022-09-22-wait-until-event-properties/Thu, 22 Sep 2022 00:00:00 +0000https://docs.customer.io/release-notes/2022-09-22-wait-until-event-properties/For example, if people enter your campaign when they create an appointment, you might send them a reminder before their appointment. You can use an event parameter-based wait condition to make sure that someone hasn’t cancelled their appointment before you send the reminder!https://docs.customer.io/release-notes/2022-09-20-simple-json-ui/Tue, 20 Sep 2022 00:00:00 +0000https://docs.customer.io/release-notes/2022-09-20-simple-json-ui/When you’re creating a segmentA group of people who match a series of conditions. People enter and exit the segment automatically when they match or stop matching conditions., you’ll now see two new operators: Where at least one: lets you match an item in an array (a group of items surrounded by square brackets []). You can specify a value for simple arrays or a property to traverse arrays of objects.https://docs.customer.io/release-notes/2022-09-15-react-native-open-beta/Thu, 15 Sep 2022 00:00:00 +0000https://docs.customer.io/release-notes/2022-09-15-react-native-open-beta/https://docs.customer.io/release-notes/2022-09-14-upload-csv-api/Wed, 14 Sep 2022 00:00:00 +0000https://docs.customer.io/release-notes/2022-09-14-upload-csv-api/https://docs.customer.io/release-notes/2022-09-12-message-hover-preview/Mon, 12 Sep 2022 00:00:00 +0000https://docs.customer.io/release-notes/2022-09-12-message-hover-preview/https://docs.customer.io/release-notes/2022-09-08-parcel-for-everybody/Thu, 08 Sep 2022 00:00:00 +0000https://docs.customer.io/release-notes/2022-09-08-parcel-for-everybody/https://docs.customer.io/release-notes/2022-09-08-in-app-open-beta/Thu, 08 Sep 2022 00:00:00 +0000https://docs.customer.io/release-notes/2022-09-08-in-app-open-beta/In-app messages provide a way to reach users from inside your app or on your website. You can customize your messages with branding that makes them look like a a part of your website or app, and even target messages to people who go to specific pages of your app or website. In-app messages can help you: Invite users to try new features Remind users to turn on two-factor authentication (2FA) Tell your audience when a new version of your app is available Ask people if they want to turn on push notifications after they leave your app a positive review When you Enable in-app messaging, you’ll set up the in-app messages that you want to use in campaigns.https://docs.customer.io/release-notes/2022-08-23-parcel-experimental-feature/Tue, 23 Aug 2022 00:00:00 +0000https://docs.customer.io/release-notes/2022-08-23-parcel-experimental-feature/Parcel generates responsive previews, helping you better understand how your email will look to users in both light and dark modes. It includes an autocomplete feature that makes it easier to write HTML, CSS, and liquidA syntax that supports variables, letting you personalize messages for your audience. For example, if you want to reference a person’s first name, you might use the variable {{customer.first_name}}.. And it comes with an Inspect Element mode that helps you focus on code when you click an element in your preview.https://docs.customer.io/release-notes/2022-08-22-twilio-mms-support/Mon, 22 Aug 2022 00:00:00 +0000https://docs.customer.io/release-notes/2022-08-22-twilio-mms-support/When you set up an SMS message, you can add the URL of a JPEG, PNG, and GIF image. You can send images up to 1.5MB to people with phone numbers in the United States and Canada. In general, we recommend that you limit images to 1MB or less, so that everybody in your audience can see them regardless of their connection speed.https://docs.customer.io/release-notes/2022-07-19-event-conversions-newsletters/Tue, 19 Jul 2022 00:00:00 +0000https://docs.customer.io/release-notes/2022-07-19-event-conversions-newsletters/https://docs.customer.io/release-notes/2022-07-12-json-in-segments/Tue, 12 Jul 2022 00:00:00 +0000https://docs.customer.io/release-notes/2022-07-12-json-in-segments/ You can use JSON dot notation directly in segment rules and other conditions. When you reference an array, you can set the index you want to match in a segment condition or leave the index empty to match any value in the array. Match any item in array: array[] Match first item in array: array[0] Match child property in any object in array: array[].childhttps://docs.customer.io/release-notes/2022-07-05-events-upload-csv/Tue, 05 Jul 2022 00:00:00 +0000https://docs.customer.io/release-notes/2022-07-05-events-upload-csv/https://docs.customer.io/release-notes/2022-07-01-event-conversions/Fri, 01 Jul 2022 00:00:00 +0000https://docs.customer.io/release-notes/2022-07-01-event-conversions/In the past, you could only manage conversions with segments, which was sometimes cumbersome: you may have had to create new segments specifically to record conversions. People could also match your conversion segment criteria outside a campaign which could lead to inaccurate conversion metrics. Now you can also set your campaign goal to an event. This makes it easier to set conversion criteria: you don’t have to set up a segment anymore, and you can make conversion criteria specific to your campaign’s call to action.https://docs.customer.io/release-notes/2022-06-14-export-workflow-image/Tue, 14 Jun 2022 00:00:00 +0000https://docs.customer.io/release-notes/2022-06-14-export-workflow-image/Click in the upper right of the workflow to export your workflow as an image.https://docs.customer.io/release-notes/2022-06-06-wait-until-changes/Mon, 06 Jun 2022 00:00:00 +0000https://docs.customer.io/release-notes/2022-06-06-wait-until-changes/https://docs.customer.io/release-notes/2022-06-02-localize-campaigns/Thu, 02 Jun 2022 00:00:00 +0000https://docs.customer.io/release-notes/2022-06-02-localize-campaigns/When you write messages in your campaign, you’ll set up a default message and click Add language to set up localizations of your message. When people enter your campaign, they’ll receive messages matching their language attribute. People who don’t match a language in your newsletter receive the default message. Localized items in your workflow show the icon. This makes it easier to localize messages in your campaigns, and generates unified metrics from localized messages, making it easier for you to tell how your message perform with your audience.https://docs.customer.io/release-notes/2022-06-01-android-2-release/Wed, 01 Jun 2022 00:00:00 +0000https://docs.customer.io/release-notes/2022-06-01-android-2-release/The Processing Queue automatically queues and batches requests, saving your audience’s battery life and automatically handling errors for you. The SDK now automatically captures a set of Device Attributes and grants you the ability to set your own, custom attributes for each device you register with Customer.io. You can use these properties in segmentsA segment is a group of people in your workspace. Use segments to trigger campaigns, track membership over time, or fine-tune your audience.https://docs.customer.io/release-notes/2022-06-01-ios-1.1-release/Wed, 01 Jun 2022 00:00:00 +0000https://docs.customer.io/release-notes/2022-06-01-ios-1.1-release/https://docs.customer.io/release-notes/2022-05-18-segment-source-all-channels/Wed, 18 May 2022 00:00:00 +0000https://docs.customer.io/release-notes/2022-05-18-segment-source-all-channels/https://docs.customer.io/release-notes/2022-05-13-experimental-features/Fri, 13 May 2022 00:00:00 +0000https://docs.customer.io/release-notes/2022-05-13-experimental-features/https://docs.customer.io/release-notes/2022-05-12-azure-blob-storage/Thu, 12 May 2022 00:00:00 +0000https://docs.customer.io/release-notes/2022-05-12-azure-blob-storage/https://docs.customer.io/release-notes/2022-05-02-metric-date-ranges/Mon, 02 May 2022 00:00:00 +0000https://docs.customer.io/release-notes/2022-05-02-metric-date-ranges/https://docs.customer.io/release-notes/2022-04-22-html-form-action/Fri, 22 Apr 2022 00:00:00 +0000https://docs.customer.io/release-notes/2022-04-22-html-form-action/Like other form integrations, this feature also lets you trigger campaigns when people fill out your form, so you can automatically respond to your audience with information relevant to the forms they submit.https://docs.customer.io/release-notes/2022-04-21-batch-update/Thu, 21 Apr 2022 00:00:00 +0000https://docs.customer.io/release-notes/2022-04-21-batch-update/Historically, interactions in Customer.io have been one-to-one: a person performs an event, triggering a campaign; a person gains (or loses) an attribute, triggering a campaign. Now, you can associate an individual piece of data from incoming webhook, with a group of people. When you run a batch update, you’ll update attributes for, or send events to, a group of up to 1000 people. For example, if you support multiple users in a single account, you might send a webhook to Customer.https://docs.customer.io/release-notes/2022-03-29-schedule-sync-start/Tue, 29 Mar 2022 00:00:00 +0000https://docs.customer.io/release-notes/2022-03-29-schedule-sync-start/https://docs.customer.io/release-notes/2022-03-25-snippet-search-and-delete/Fri, 25 Mar 2022 00:00:00 +0000https://docs.customer.io/release-notes/2022-03-25-snippet-search-and-delete/https://docs.customer.io/release-notes/2022-03-25-device-attributes/Fri, 25 Mar 2022 00:00:00 +0000https://docs.customer.io/release-notes/2022-03-25-device-attributes/For each device, our APIs automatically gather the platform and set a last_used timestamp based on when you last added or updating a device. If you use our SDKs, we also capture attributes containing additional device information. You can also add your own custom attributes on devices; these are additional values that you think are relevant to the devices in your mobile audience. You can use all of these attributes, both automatically-gathered and custom attributes, in segments, filters, etc.https://docs.customer.io/release-notes/2022-03-17-js-in-actions/Thu, 17 Mar 2022 00:00:00 +0000https://docs.customer.io/release-notes/2022-03-17-js-in-actions/For example, where you might have checked if a variable existed by writing a complicated Liquid if statement, you can now write simple JavaScript instead! JavaScript JavaScript return trigger.plan_name ?? 'free_trial'; Liquid Liquid {% if trigger.plan_name != blank %} {{ trigger.plan_name }} {% else %} free_trial {% endif %}https://docs.customer.io/release-notes/2022-03-07-segment-devices/Mon, 07 Mar 2022 00:00:00 +0000https://docs.customer.io/release-notes/2022-03-07-segment-devices/Our SDKs gather these attributes automatically, but you can also set them when you add and update devices using our API. The last_status attribute is set automatically based on the delivery status of the last message sent to the device—sent, bounced, suppressed, or an empty string if the device hasn’t received a push notification before.https://docs.customer.io/release-notes/2022-03-04-integration-catalog-update/Fri, 04 Mar 2022 00:00:00 +0000https://docs.customer.io/release-notes/2022-03-04-integration-catalog-update/https://docs.customer.io/release-notes/2022-02-28-beta-api-official-release/Mon, 28 Feb 2022 00:00:00 +0000https://docs.customer.io/release-notes/2022-02-28-beta-api-official-release/If you’re currently integrated with “beta-api” endpoints, you can continue to use those routes, but we encourage you to update your integration to use the new https://api.customer.io/v1/ paths. Beta API endpoints will continue to work, but we may eventually deprecate and remove them in the future (with advanced notice).https://docs.customer.io/release-notes/2022-02-23-create-update-person/Wed, 23 Feb 2022 00:00:00 +0000https://docs.customer.io/release-notes/2022-02-23-create-update-person/https://docs.customer.io/release-notes/2022-02-16-message-library-filters/Wed, 16 Feb 2022 00:00:00 +0000https://docs.customer.io/release-notes/2022-02-16-message-library-filters/https://docs.customer.io/release-notes/2022-02-10-create-event-all-campaigns/Thu, 10 Feb 2022 00:00:00 +0000https://docs.customer.io/release-notes/2022-02-10-create-event-all-campaigns/This release also makes it easier to add properties to your events, letting you click to select the values that you want your event to include so you don’t have to write liquid.https://docs.customer.io/release-notes/2022-01-31-wordpress-forms/Mon, 31 Jan 2022 00:00:00 +0000https://docs.customer.io/release-notes/2022-01-31-wordpress-forms/We developed and tested Wordpress form support with the WPForms plugin. You may be able to capture forms from other form plugins in Wordpress, but we cannot guarantee that they’ll work. Let us know if you use a different plugin and run into compatibility issues. We’ll do our best to support your use case.https://docs.customer.io/release-notes/2022-01-28-update-email-with-id/Fri, 28 Jan 2022 00:00:00 +0000https://docs.customer.io/release-notes/2022-01-28-update-email-with-id/In workspaces created before today, if you use both email and id to identify people, you needed to use cio_id to change either value—a value that you might not have available to your integration. This setting lets you change email values with id, making it easier to modify your audience without preventing you from identifying people by their email address.https://docs.customer.io/release-notes/2022-01-28-localize-newsletters/Fri, 28 Jan 2022 00:00:00 +0000https://docs.customer.io/release-notes/2022-01-28-localize-newsletters/Now, you can specify the attribute that represents your audience’s language preference in your workspace settings. This attribute can be either a language code (like es for Spanish) or a language and country code (i.e. es-ES representing Spanish formatted for people in Spain). When you write your newsletter, you’ll set up a Default message and click to add languages. When you send your newsletter, people in your audience receive the message matching their language attribute.https://docs.customer.io/release-notes/2022-01-20-amazon-redshift-sync/Thu, 20 Jan 2022 00:00:00 +0000https://docs.customer.io/release-notes/2022-01-20-amazon-redshift-sync/When you set up a sync, you provide a query determining the information that you want to reflect as attributes on people in Customer.io. You’ll also set the frequency of import operations from your Redshift instance. On each interval, you’ll import and/or update people in your workspace from your Redshift database!https://docs.customer.io/release-notes/2022-01-19-official-mobile-sdk/Wed, 19 Jan 2022 00:00:00 +0000https://docs.customer.io/release-notes/2022-01-19-official-mobile-sdk/ Check out our sample apps Our sample apps provide real-world examples that can help you implement our SDKs. Check them out for iOS and Android! We’re developing our SDKs in parallel, so that both your Android and iOS apps provide the same experiences. For now, that means that you can do the following with both of our SDKs: Identify people who use your app. When you identify someone, you’ll also register their device token and you can update their attributesA key-value pair that you associate with a person or an object—like a person’s name, the date they were created in your workspace, or a company’s billing date etc.https://docs.customer.io/release-notes/2022-01-14-microsoft-sql-in/Fri, 14 Jan 2022 00:00:00 +0000https://docs.customer.io/release-notes/2022-01-14-microsoft-sql-in/When you set up a sync, you provide a query determining exactly what information you want to reflect as attributes on people in Customer.io. You’ll also set the frequency of import operations from your Microsoft SQL instance, helping you keep your workspace up to date.https://docs.customer.io/release-notes/2021-12-22-jotform/Wed, 22 Dec 2021 00:00:00 +0000https://docs.customer.io/release-notes/2021-12-22-jotform/https://docs.customer.io/release-notes/2021-12-20-bigquery-in/Mon, 20 Dec 2021 00:00:00 +0000https://docs.customer.io/release-notes/2021-12-20-bigquery-in/When you set up a sync, you provide a query determining exactly what information you want to reflect as attributes on people in Customer.io. You’ll also set the frequency of import operations from your BigQuery instance. Your query can use a {{last_sync_time}} variable, making it easy for you to limit each import operation to changes made since the previous interval.https://docs.customer.io/release-notes/2021-12-17-create-event-action/Fri, 17 Dec 2021 00:00:00 +0000https://docs.customer.io/release-notes/2021-12-17-create-event-action/https://docs.customer.io/release-notes/segment-people-by-mobile-device-platform/Fri, 17 Dec 2021 00:00:00 +0000https://docs.customer.io/release-notes/segment-people-by-mobile-device-platform/https://docs.customer.io/release-notes/2021-12-14-snowflake-in/Tue, 14 Dec 2021 00:00:00 +0000https://docs.customer.io/release-notes/2021-12-14-snowflake-in/When you set up a sync, you provide a query determining exactly what information you want to reflect as attributes on people in Customer.io. You’ll also set the frequency of import operations from your Snowflake instance. Your query can use a {{last_sync_time}} variable, making it easy for you to limit each import operation to changes made since the previous interval.  You must map Snowflake columns to attributes Snowflake columns are all caps, but attributes in Customer.https://docs.customer.io/release-notes/2021-12-14-track-screen-views/Tue, 14 Dec 2021 00:00:00 +0000https://docs.customer.io/release-notes/2021-12-14-track-screen-views/https://docs.customer.io/release-notes/2021-12-10-transactional-send-at/Fri, 10 Dec 2021 00:00:00 +0000https://docs.customer.io/release-notes/2021-12-10-transactional-send-at/https://docs.customer.io/release-notes/2021-12-01-sql-sync-row-increase/Wed, 01 Dec 2021 00:00:00 +0000https://docs.customer.io/release-notes/2021-12-01-sql-sync-row-increase/https://docs.customer.io/release-notes/2021-11-30-campaign-segment-dates/Tue, 30 Nov 2021 00:00:00 +0000https://docs.customer.io/release-notes/2021-11-30-campaign-segment-dates/https://docs.customer.io/release-notes/2021-11-30-data-campaigns/Tue, 30 Nov 2021 00:00:00 +0000https://docs.customer.io/release-notes/2021-11-30-data-campaigns/When you set up a campaign, you can use the new Data arrives via webhook option. Provide this unique URL to an external service, like Satismeter, Stripe, or Zendesk, to send data to your workspace. Then, in your data campaign, you can reshape your incoming data using liquidA syntax that supports variables, letting you personalize messages for your audience. For example, if you want to reference a person’s first name, you might use the variable {{customer.https://docs.customer.io/release-notes/2021-11-24-typeform/Wed, 24 Nov 2021 00:00:00 +0000https://docs.customer.io/release-notes/2021-11-24-typeform/https://docs.customer.io/release-notes/2021-11-19-newsletter-dedupe/Fri, 19 Nov 2021 00:00:00 +0000https://docs.customer.io/release-notes/2021-11-19-newsletter-dedupe/https://docs.customer.io/release-notes/2021-11-04-ssl-db-integrations/Thu, 04 Nov 2021 00:00:00 +0000https://docs.customer.io/release-notes/2021-11-04-ssl-db-integrations/https://docs.customer.io/release-notes/2021-10-29-google-sheet-share/Fri, 29 Oct 2021 00:00:00 +0000https://docs.customer.io/release-notes/2021-10-29-google-sheet-share/https://docs.customer.io/release-notes/2021-10-28-query-collection-arrays/Thu, 28 Oct 2021 00:00:00 +0000https://docs.customer.io/release-notes/2021-10-28-query-collection-arrays/https://docs.customer.io/release-notes/2021-10-27-shortcuts-for-people/Wed, 27 Oct 2021 00:00:00 +0000https://docs.customer.io/release-notes/2021-10-27-shortcuts-for-people/Shortcuts let you link people in Customer.io to external services. You can even set up webhook “shortcuts” to call external APIs from a person’s page in Customer.io. Shortcuts act as simple, low- or no-code integrations. With just a little bit of liquidA syntax that supports variables, letting you personalize messages for your audience. For example, if you want to reference a person’s first name, you might use the variable {{customer.first_name}}., you can personalize links and simple API calls for services outside Customer.https://docs.customer.io/release-notes/2021-10-21-sticky-notes/Thu, 21 Oct 2021 00:00:00 +0000https://docs.customer.io/release-notes/2021-10-21-sticky-notes/https://docs.customer.io/release-notes/2021-10-12-segment-source-email/Tue, 12 Oct 2021 00:00:00 +0000https://docs.customer.io/release-notes/2021-10-12-segment-source-email/https://docs.customer.io/release-notes/2021-10-05-auto-merge/Tue, 05 Oct 2021 00:00:00 +0000https://docs.customer.io/release-notes/2021-10-05-auto-merge/You can enable the Multi-identifier profile merge setting to automatically merge duplicate profiles under Settings > Workspace Settings > Merge Settings. If you created your workspace using the email or ID option after September 24, 2021, this setting is on by default. When you turn on the Multi-identifier profile merge setting, we’ll automatically recognize and merge duplicate profilesAn instance of a person. Generally, a person is synonymous with their profile; there should be a one-to-one relationship between a real person and their profile in Customer.https://docs.customer.io/release-notes/2021-10-05-see-recent-journeys/Tue, 05 Oct 2021 00:00:00 +0000https://docs.customer.io/release-notes/2021-10-05-see-recent-journeys/https://docs.customer.io/release-notes/2021-10-05-segment-on-message/Tue, 05 Oct 2021 00:00:00 +0000https://docs.customer.io/release-notes/2021-10-05-segment-on-message/When you create a segment, select the message type under Message Data. Then you can click Any , and search for the campaigns or individual messages that you want to segment on by name.https://docs.customer.io/release-notes/2021-09-24-merge-people-api/Fri, 24 Sep 2021 00:00:00 +0000https://docs.customer.io/release-notes/2021-09-24-merge-people-api/https://docs.customer.io/release-notes/2021-09-20-message-library/Mon, 20 Sep 2021 00:00:00 +0000https://docs.customer.io/release-notes/2021-09-20-message-library/https://docs.customer.io/release-notes/2021-09-17-resolve-duplicate-people/Fri, 17 Sep 2021 00:00:00 +0000https://docs.customer.io/release-notes/2021-09-17-resolve-duplicate-people/In the past, if you inadvertently represented the same person multiple times in your workspace, you couldn’t resolve the issue without deleting duplicates and potentially losing information in the process. Now, you can merge two people together and resolve duplicates without losing information or historical data associated with two profilesAn instance of a person. Generally, a person is synonymous with their profile; there should be a one-to-one relationship between a real person and their profile in Customer.https://docs.customer.io/release-notes/2021-09-03-newsletter-webhooks/Fri, 03 Sep 2021 00:00:00 +0000https://docs.customer.io/release-notes/2021-09-03-newsletter-webhooks/https://docs.customer.io/release-notes/2021-08-26-sql-sync/Thu, 26 Aug 2021 00:00:00 +0000https://docs.customer.io/release-notes/2021-08-26-sql-sync/When you set up a sync, you can determine how often you want to import data. You also provide your own query, determining exactly what information you want to reflect as attributes on people in Customer.io. Our queries also include a {{last_sync_time}} variable, providing a quick way for you to target each sync to changes made since the previous sync interval.https://docs.customer.io/release-notes/2021-08-24-delete-rows/Tue, 24 Aug 2021 00:00:00 +0000https://docs.customer.io/release-notes/2021-08-24-delete-rows/https://docs.customer.io/release-notes/2021-08-13-disable-open-tracking/Fri, 13 Aug 2021 00:00:00 +0000https://docs.customer.io/release-notes/2021-08-13-disable-open-tracking/Open tracking relies on a “tracking pixel” in your messages. When a person opens your message, the tracking pixel loads, alerting your email delivery provider that the person opened the email. While email open tracking can provide you with an at-a-glance understanding of audience engagement, it is made increasingly unreliable by email clients that allow users to block images from loading when they open messages. Now, when you go to Settings > Workspace Settings > General Workspace Settings, you can disable open tracking all together, so you can focus on other, more reliable and meaningful metrics, like Clicks and Conversions.https://docs.customer.io/release-notes/2021-08-11-connected-forms/Tue, 10 Aug 2021 00:00:00 +0000https://docs.customer.io/release-notes/2021-08-11-connected-forms/You can integrate directly with our new /forms API, or you can add forms on the new Data & Integrations > Integrations > Forms page and use the connected forms JavaScript snippet. This new JavaScript snippet captures form fields and URL parameters from forms, and sends submissions back to Customer.io. To use our form-scanning service, you need to install the Custom forms JavaScript snippet. This snippet is different from our basic JavaScript snippet and captures form submission events from:https://docs.customer.io/release-notes/2021-08-05-campaign-overview/Wed, 04 Aug 2021 00:00:00 +0000https://docs.customer.io/release-notes/2021-08-05-campaign-overview/The Overview tab is reorganized to provide you with a better at-a-glance view of your campaign’s health and performance. The Metrics tab replaces the Journey Metrics tab. On both tabs, you’ll find a calendar and settings to customize the scope of your metrics. For charts on the metrics page, you can toggle the specific metrics that you want to see or want to hide.https://docs.customer.io/release-notes/2021-08-03-save-rows/Tue, 03 Aug 2021 00:00:00 +0000https://docs.customer.io/release-notes/2021-08-03-save-rows/https://docs.customer.io/release-notes/2021-07-15-denominator-update/Thu, 15 Jul 2021 00:00:00 +0000https://docs.customer.io/release-notes/2021-07-15-denominator-update/However, if you don’t pass delivered metrics from your delivery provider to to Customer.io, you can continue basing metrics on the number of messages sent. You can change your Metric Configuration on the Custom SMTP settings page.https://docs.customer.io/release-notes/2021-07-15-csv-upload-multi-id/Tue, 13 Jul 2021 00:00:00 +0000https://docs.customer.io/release-notes/2021-07-15-csv-upload-multi-id/https://docs.customer.io/release-notes/2021-07-12-auto-identify-js-snippet/Mon, 12 Jul 2021 00:00:00 +0000https://docs.customer.io/release-notes/2021-07-12-auto-identify-js-snippet/https://docs.customer.io/release-notes/2021-07-08-anonymous-event-merge/Thu, 08 Jul 2021 00:00:00 +0000https://docs.customer.io/release-notes/2021-07-08-anonymous-event-merge/This feature changes anonymous events to require an anonymous_id—a value representing the un-identified person. When you identify a person, if you set their anonymous_id attribute to a value represented in anonymous events, those events are associated with the appropriate person. Our JavaScript snippet automatically sets this anonymous ID, both on events and identified people, making it easy to capture anonymous events. When you send events or identify people using our API, you need to set anonymous_id yourself.https://docs.customer.io/release-notes/2021-07-08-url-params-in-pageviews/Thu, 08 Jul 2021 00:00:00 +0000https://docs.customer.io/release-notes/2021-07-08-url-params-in-pageviews/https://docs.customer.io/release-notes/2021-07-08-url-params-in-segments/Thu, 08 Jul 2021 00:00:00 +0000https://docs.customer.io/release-notes/2021-07-08-url-params-in-segments/https://docs.customer.io/release-notes/2021-06-24-untracked-unsubscribes/Thu, 24 Jun 2021 00:00:00 +0000https://docs.customer.io/release-notes/2021-06-24-untracked-unsubscribes/https://docs.customer.io/release-notes/2021-05-28-multi-id-workspace/Wed, 16 Jun 2021 00:00:00 +0000https://docs.customer.io/release-notes/2021-05-28-multi-id-workspace/You’ll find new workspace settings, letting you enable multiple identifiers, when you go to Settings > Workspace Settings and click General Workspace Settings. When you change your workspace configuration, we first validate people in your workspace, to ensure that you don’t lose any information when enabling new identifiers. If people in your workspace have duplicate or invalid email or id values (depending on the new identifier in your workspace), we’ll export a list of problem-profiles for you.https://docs.customer.io/release-notes/2021-05-28-multi-id-workspace/Fri, 28 May 2021 00:00:00 +0000https://docs.customer.io/release-notes/2021-05-28-multi-id-workspace/Previously, workspaces supported a single identifier for people—one of either ID or email. This made it difficult to track users who entered your system as a lead (by email) and graduated to a customer (with an ID). You couldn’t easily keep a complete history of a lead who graduated to a customer because this person was represented across two workspaces. With this new workspace type, you can add people to your workspace by either email address or ID, and you can update those identifiers later.https://docs.customer.io/release-notes/2021-05-27-searchable-attributes/Thu, 27 May 2021 00:00:00 +0000https://docs.customer.io/release-notes/2021-05-27-searchable-attributes/https://docs.customer.io/release-notes/2021-05-13-webhook-conversions/Thu, 13 May 2021 00:00:00 +0000https://docs.customer.io/release-notes/2021-05-13-webhook-conversions/https://docs.customer.io/release-notes/2021-04-23-sms-keyword-handling/Fri, 23 Apr 2021 00:00:00 +0000https://docs.customer.io/release-notes/2021-04-23-sms-keyword-handling/https://docs.customer.io/release-notes/2021-03-22-data-warehouse-sync-ui/Mon, 22 Mar 2021 00:00:00 +0000https://docs.customer.io/release-notes/2021-03-22-data-warehouse-sync-ui/Data warehouse integrations let you export your data in bulk, so you can take advantage of your complete Customer.io data set in Google BigQuery, Snowflake, and other business intelligence or CRM platforms. To set up a data warehouse integration, go to Integrations > Databases and select the platform you want to export data to.https://docs.customer.io/release-notes/2021-03-20-untrack-unsubscribe-links-ui/Sat, 20 Mar 2021 00:00:00 +0000https://docs.customer.io/release-notes/2021-03-20-untrack-unsubscribe-links-ui/https://docs.customer.io/release-notes/2021-03-14-workspace-user-search/Sun, 14 Mar 2021 00:00:00 +0000https://docs.customer.io/release-notes/2021-03-14-workspace-user-search/https://docs.customer.io/release-notes/2021-03-04-twilio-whatsapp-support/Thu, 04 Mar 2021 00:00:00 +0000https://docs.customer.io/release-notes/2021-03-04-twilio-whatsapp-support/To support Twilio WhatsApp messages, you must set up access to the WhatsApp Business API. When you do, contact win@customer.io, and we’ll enable WhatsApp support for your account.https://docs.customer.io/release-notes/2021-02-20-liquid-format-numbers/Sat, 20 Feb 2021 00:00:00 +0000https://docs.customer.io/release-notes/2021-02-20-liquid-format-numbers/We added three new liquid filters: The currency and format_number take regional parameters, so you can format numbers to suit your audience’s local conventions. For example: {{ 123456.78 | currency: "fr" }} outputs 123 456,78€. The where_not condition lets match negative conditions—people who do not match an attribute value or an event where a value isn’t present.https://docs.customer.io/release-notes/2021-02-10-facebook-lead-ads/Wed, 10 Feb 2021 00:00:00 +0000https://docs.customer.io/release-notes/2021-02-10-facebook-lead-ads/https://docs.customer.io/release-notes/2021-02-02-copy-whole-workflow/Tue, 02 Feb 2021 00:00:00 +0000https://docs.customer.io/release-notes/2021-02-02-copy-whole-workflow/https://docs.customer.io/release-notes/2021-02-02-multi-copy-vwb/Tue, 02 Feb 2021 00:00:00 +0000https://docs.customer.io/release-notes/2021-02-02-multi-copy-vwb/https://docs.customer.io/release-notes/2021-02-01-newsletter-variant-segments/Mon, 01 Feb 2021 00:00:00 +0000https://docs.customer.io/release-notes/2021-02-01-newsletter-variant-segments/https://docs.customer.io/release-notes/2021-01-26-email-based-workspaces/Tue, 26 Jan 2021 00:00:00 +0000https://docs.customer.io/release-notes/2021-01-26-email-based-workspaces/When you use email as your workspace’s unique key, each email address represents a unique person, helping you manage your audience directly by email address. To use email addresses as your unique key, create a new workspace and choose to identify people by “Email address”. If you want to explore the possibility of converting an existing workspace to identify people by email address, contact win@customer.io.https://docs.customer.io/academy/catalog/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/catalog/https://docs.customer.io/academy/data/goals/act-on-your-data/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/data/goals/act-on-your-data/Scenario: “So what are we doing about it?” Your goal is fully set up with criteria, impact, sources, and attribution settings. The data has been flowing for a few weeks. You sit down with your manager and walk through the goal report. She can see total upgrades, revenue, and a breakdown by source. Some campaigns are driving more upgrades. Some are driving more revenue. And a chunk of upgrades are unattributed.https://docs.customer.io/academy/quick-guides/choose-message/message-activity/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/quick-guides/choose-message/message-activity/https://docs.customer.io/academy/data/course-3/document-data/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/data/course-3/document-data/Scenario: What does this even mean? A new teammate just joined your team at Sketcher.io. They’re excited to build their first campaign to target free users who might be ready for an upgrade. But… they open Customer.io and immediately have questions: What attribute tells me someone is on the free plan? Is it plan_type, plan, or subscription_tier? What does exp_lvl mean? Experience level or expertise? What are the possible values?https://docs.customer.io/academy/quick-start/course-4/campaign-delays/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/quick-start/course-4/campaign-delays/Scenario: Don’t message too soon At Sketcher.io, someone just upgraded to premium. 🎊 But now isn’t the time to overwhelm them with follow-ups. You want to give them a moment to explore, and then check in if they haven’t made progress. In other words, you want your campaign to feel thoughtful and not rushed. That’s where timing logic comes in. Why pacing matters Timing can make or break your message.https://docs.customer.io/academy/quick-start/course-1/add-people/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/quick-start/course-1/add-people/Scenario: Get your people into your workspace You know who you want to message and how to identify them. Now you need to get those people into Customer.io so you can actually reach them. How data gets into Customer.io Before you can message anyone, Customer.io needs to know they exist. That means getting your customer data (like signups, product activity, or subscription status) into your workspace. You can do that a few ways:https://docs.customer.io/academy/design-and-content/send-first-email/ds-global-styles/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/design-and-content/send-first-email/ds-global-styles/What’s my button color again? So you’re building an email and you know the button background should be dark blue. But you notice there are several blues used across your company’s emails, and not all buttons look the same. Slightly different hex values. Slightly different appearance. Seems like some folks weren’t sure what to do, so they guessed the right colors. Not just that, but if your customers use dark mode, what should the button change to?https://docs.customer.io/academy/quick-start/course-4/create-campaign-message/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/quick-start/course-4/create-campaign-message/Scenario: Time to say hello Your new premium user has logged in, and you’ve given them a little breathing room with a short delay. Now it’s time to welcome them properly, and guide them toward Brand Kits. This is your first real message in the flow and it sets the tone for what follows. Click to view imageOpen image in new window What kind of message should you send? Campaigns in Customer.https://docs.customer.io/academy/design-and-content/send-first-email/ds-columns/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/design-and-content/send-first-email/ds-columns/Now to hone in on the core of your template—the features you want to draw your customers’ eyes to. So you made a two-column block for each feature you want to announce and increase adoption for. You want to make sure it’s immediately clear the amazing things your colleagues have been building and why they’re useful—and that it looks great on mobile! Tips When working with columns, here’s a few things to keep in mind.https://docs.customer.io/academy/quick-start/course-5/analysis-reports/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/quick-start/course-5/analysis-reports/Scenario: Which campaigns are actually working? Your manager stops by your desk: “I see our overall numbers look decent, but how does that Brand Kits campaign compare to our other onboarding flows? And are our newsletters outperforming our automated campaigns?” You’ve got a general sense of how things are going, but a general sense won’t answer that question. You need to investigate. Where to start Customer.io gives you several ways to examine your messaging performance.https://docs.customer.io/academy/quick-start/course-5/analyze-with-agent/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/quick-start/course-5/analyze-with-agent/Scenario: The follow-up questions never stop You’ve reviewed your onboarding campaign workflow and spotted a potential bottleneck. Your welcome email is getting solid opens, but fewer people than expected are clicking through to the next step. You have a hunch, but you want data to back it up before you start making changes. And that’s just the first thing you want to look into. You also want to know how this compares to last month, whether other onboarding campaigns have the same drop-off, and what the click-to-open rate looks like on that welcome email.https://docs.customer.io/academy/quick-start/course-5/workflow-metrics/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/quick-start/course-5/workflow-metrics/Scenario: The detective work begins Your Brand Kits campaign overview shows decent engagement and people are taking action. But “decent” isn’t good enough. You want to know exactly where you can make improvements. The overall numbers tell you what happened, but they don’t tell you where it happened. That’s where workflow metrics come in. Click to view imageOpen image in new window Why workflow metrics matter Think of your campaign like a funnel.https://docs.customer.io/academy/data/course-3/audit-data/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/data/course-3/audit-data/Scenario: Is it actually working? Your developer messages you: “The integration’s deployed! You should start seeing data flow in.” Before you start building messages and campaigns, you want to verify that everything’s coming through correctly. Is design_started actually firing? Does exp_lvl exist as an attribute? Now is the time to check and see. Your data command center: The data index The Data Index shows you the data in your workspace, including every attribute and event that’s ever been sent to Customer.https://docs.customer.io/academy/data/goals/before-you-start/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/data/goals/before-you-start/Set up your training workspace To follow along with the hands-on activities in this course, create a new Customer.io workspace just for training if you haven’t already done so.  Collaborating with team members? Planning to share your training workspace with others? You can invite team members to join your training workspace under the Settings > Workspace settings > General workspace settings section. This workspace will simulate Sketcher.io’s real customer data so you can build campaigns, test messages, and practice without affecting your live workspace.https://docs.customer.io/academy/quick-start/course-3/newsletter-best-practices/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/quick-start/course-3/newsletter-best-practices/Scenario: Back at Sketcher.io You’ve put together your Brand Kits newsletter and you’re excited to send it out into the world. You’ve chosen your segment, dialed in your sending settings, and written the message. You’re about to hit send, but you pause for a moment before you do. You decide to run through a quick checklist. You know a few smart choices now can make the difference between a message that performs well and one that hurts your deliverability.https://docs.customer.io/academy/data/objects/welcome-objects/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/data/objects/welcome-objects/👋 Welcome to the course If you enrolled in this course, you likely know how to work with person-level data in Customer.io. Person attributes describe people, events track what they do, and event attributes describe the events themselves. But there’s one more data structure that unlocks more powerful messaging: Objects. In this course, you’ll learn what objects are, when to use them, and how to set them up for your business needs.https://docs.customer.io/academy/quick-start/course-2/build-segment/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/quick-start/course-2/build-segment/Scenario: Target engaged users Brand Kits is live, and you want to send an upgrade message to free users who are already getting value from the product. But which free users? Well, the ones who are highly engaged is probably your best bet. So that means people who are inviting their teammates and creating projects regularly. You don’t want to pitch an upgrade to someone who signed up yesterday and hasn’t done anything yet.https://docs.customer.io/academy/quick-start/course-2/ai-segment/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/quick-start/course-2/ai-segment/✨ Generate segments with AI The segmentA segment is a group of people in your workspace. Use segments to trigger campaigns, track membership over time, or fine-tune your audience. There are two types of segments: data-driven and manual. Data-driven segments automatically update when people start or stop matching criteria. Manual segments are static. builder leverages publicly available data about your company and data from your workspace to suggest conditions for targeting specific audiences.https://docs.customer.io/academy/design-and-content/send-first-email/build-template-with-components/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/design-and-content/send-first-email/build-template-with-components/Back at Sketcher.io, you’re sending product announcements every month and tired of rebuilding the same email structure from scratch—or worse, copying last month’s email and hoping you caught all the changes. Now that you’ve added your branding, you won’t have to worry about using the wrong styles! Next step is to create a template so all you have to do is add the right content before sending every month. Showcase your features To showcase your product announcements, make a block that includes a brief preview of the feature.https://docs.customer.io/academy/quick-start/course-4/campaign-branching/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/quick-start/course-4/campaign-branching/Scenario: Guide the journey with flow control Your user just created a Brand Kit—great! 🎉 Now what? You want to help them get even more value out of it. At Sketcher.io, that means encouraging them to invite a teammate to collaborate. But not everyone needs that prompt. Some folks already invited a teammate. Others haven’t yet—and might benefit from a little nudge. So how do you guide each person down the right path that’s personalized based on their actions?https://docs.customer.io/academy/quick-start/course-3/newsletter-content/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/quick-start/course-3/newsletter-content/Scenario: Design your Brand Kits message You’ve chosen your audience and set a clear goal. Now it’s time to create the message itself. Your job is to craft a clear, engaging email that introduces Brand Kits to your most interested free plan users. To do that, you’ll use Design Studio, Customer.io’s email editor. ✨ Why use Design Studio? Design Studio gives you full control over the look and layout of your messages.https://docs.customer.io/academy/data/goals/campaigns-dont-add-up/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/data/goals/campaigns-dont-add-up/Scenario: The math isn’t mathing It’s the end of the month, and your manager wants an answer: which of our campaigns are driving trial-to-paid upgrades? You have some suspicions and pull up the first three items that come to mind. The welcome series shows 47 upgrades. Feature adoption shows 31. The newsletter shows 22. You add them all up and get 100. But your actual paid upgrades for the month? 68.https://docs.customer.io/academy/quick-guides/choose-message/message-types/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/quick-guides/choose-message/message-types/Scenario: Three different messaging needs You’re the growth marketer at Sketcher.io, and this week you need to: Announce that Brand Kits just launched to everyone on the waitlist Onboard new premium users who upgrade and help them create their first Brand Kit Confirm password reset requests instantly when users request them So which message type fits each of these needs? It’s time to find out. Pick your message type Customer.io offers three core message types, each designed for specific use cases.https://docs.customer.io/academy/data/goals/choose-right-outcome/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/data/goals/choose-right-outcome/Scenario: The goal that didn’t answer the question Your team has been tracking email clicks as the primary success metric for your campaigns. The click rates look good: the welcome series has a 28% click rate, feature adoption is at 19%, and your newsletter pulls 12%. Your manager sees those numbers and says, “Great, so our campaigns are working.” But then comes the real question: “How many of those clicks turned into paid upgrades?https://docs.customer.io/academy/quick-start/course-3/choose-newsletter-audience/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/quick-start/course-3/choose-newsletter-audience/Scenario: Announce your new feature You want to reach people who already showed interest in Brand Kits by joining your waitlist. These are users who are new and likely to engage, but haven’t converted just yet. You built a segment for this group in an earlier course. Now it’s time to put it to work. Send to the right people You’re ready to create your first newsletter. The first question is, who should receive it?https://docs.customer.io/academy/design-and-content/send-first-email/ds-connect-and-publish/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/design-and-content/send-first-email/ds-connect-and-publish/You previewed your message, made a couple tweaks, and now your template is complete! Time to create your first product announcement and send it off. You want to email your customers about your product’s latest features and send follow-up messages based on whether they engage with the new features. Since you want to make a multi-step workflow, you’ll want to create a Campaign. In this interaction, you’ll create your first product announcement from a Design Studio template and learn when to publish changes to make your latest edits live.https://docs.customer.io/academy/data/goals/connect-your-sources/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/data/goals/connect-your-sources/Scenario: The missing link Your goal is live. You can see that people are upgrading, and those upgrades are generating revenue. 🎊 BUT when your manager asks the obvious follow-up, “which messaging drove those upgrades?”, you can’t answer. Right now, you know what happened, but you can’t say with certainty which messages helped make it happen. Click to view imageOpen image in new window For that, you need to connect your messages to your goal.https://docs.customer.io/academy/data/objects/control-timing/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/data/objects/control-timing/Scenario: Help teams get the most from their upgrade You’re in the middle of building out your object-triggered campaign that celebrates when accounts upgrade to Pro. You’ve set it up so everyone at the account gets the good news immediately. But you want to take it further. After upgrading you want to track if teams are actually using the premium features. If they do, you’ll send them advanced tips based on their team size.https://docs.customer.io/academy/design-and-content/send-first-email/ds-footer/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/design-and-content/send-first-email/ds-footer/One footer for all Some elements just need to be the same everywhere—across all your emails and templates, like a footer. You can build a footer anywhere, save it as a custom component, and reuse it throughout your Design Studio files! In this interaction, you’ll build a footer from standard components in your template then save it as a custom component for future use. In the interactive video, you added liquid to the footer to render the current year.https://docs.customer.io/academy/design-and-content/send-first-email/ds-create-file/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/design-and-content/send-first-email/ds-create-file/Scenario: Build a template for product announcements Like other courses in our Academy, imagine you work at Sketcher.io, a SaaS platform where your customers can design mockups and collaborate on the vision of their product. You send out monthly communications that announce product updates and new features. In this course, you’ll design a template that you can reuse every month to email your customers. Click to view imageOpen image in new window What can I create with Design Studio?https://docs.customer.io/academy/quick-guides/custom-roles/create-custom-roles/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/quick-guides/custom-roles/create-custom-roles/See it in action Watch this video to see how to create those Designer and Data Architect roles from the scenarios you just saw. The key to building roles that work Before you start clicking checkboxes, get crystal clear on the actual person and their actual job. Don’t just think “I need a Designer role.” Think “Several people on my team need to build emails and upload images, but if they accidentally launch a broadcast to 50,000 customers, we’re all in trouble.https://docs.customer.io/academy/quick-start/course-4/campaign-triggers/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/quick-start/course-4/campaign-triggers/Scenario: Launch onboarding at the right moment Back at Sketcher.io, people are upgrading to premium accounts after getting your newsletter about Brand Kits. 🎉 Now that they’ve signed up, you want to reach them while they’re still excited, before the momentum fades into the abyss. Click to view imageOpen image in new window To do that, you need a way to automatically start their onboarding journey the moment they become premium users.https://docs.customer.io/academy/data/goals/define-your-goal/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/data/goals/define-your-goal/Scenario: Time to build Your manager is on board with your initial goal of tracking trial-to-paid upgrades, but she has one more thing to add. (Of course she does.) Click to view imageOpen image in new window So you need to answer two questions before you start: what event represents the exact moment someone converts, and can you capture the dollar value behind it? Set your criteria When you create a goal in Customer.https://docs.customer.io/academy/data/objects/decision-framework/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/data/objects/decision-framework/Scenario: A conversation in the Customer.io community You’re in the Customer.io community, reading through questions and posts and come across the following: “Should I use objects for my fitness app? I want to track each user’s workout streak, personal goals, and achievement badges.” You think through what you just learned about objects and if they’re a fit for this use case. Let’s build a framework to help you decide. The decision framework Do multiple people connect to the same instance of a thing?https://docs.customer.io/academy/data/course-1/document-data/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/data/course-1/document-data/Scenario: From scattered thoughts to clear requirements You’ve spent the last hour mapping out what data Sketcher.io needs for the activation campaign. Your notes are… everywhere. Sticky notes on your monitor. A Google Doc with half-formed thoughts. Some whiteboard scribbles you’ll definitely remember later. Then your developer Slacks you: “Can you send the requirements?” You could frantically copy-paste from five different places. Or you could pull up one organized document that has everything they need.https://docs.customer.io/academy/design-and-content/send-first-email/ds-style-messages/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/design-and-content/send-first-email/ds-style-messages/Your template is really shaping up! You’ve created your intro and a reusable feature block. But you take a closer look at your button and wish the text were a littler larger. When to update global styles vs one-off properties? You increase the text size of the button in your template and like that a lot more. But you realize this should be the default for all buttons, not just the one in this template.https://docs.customer.io/academy/quick-start/course-3/sending-options/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/quick-start/course-3/sending-options/Scenario: Earn your open Brand Kits is a big moment for Sketcher.io. The people on the waitlist already raised their hand, so you’re not cold-emailing strangers. The risk now isn’t “can we send it?” It’s whether this feels like the message they signed up for, and whether you’re asking for attention when you’ve already taken a lot lately. This step is where you align the send with what people agreed to hear about and how often they should hear from you.https://docs.customer.io/academy/data/course-2/format-data/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/data/course-2/format-data/Scenario: Format affects what you can do You’re building a segment to target users who’ve created more than 5 designs. You set it up, but the segment’s empty. You check a customer profile and see they’ve definitely created designs. But the data isn’t working the way you expected. Your developer takes a look. “Oh, I’m sending designs_created as text, not a number. That’s probably the issue.” Format matters. The way data comes in determines what you can do with it in Customer.https://docs.customer.io/academy/data/course-2/start-implementation/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/data/course-2/start-implementation/ Getting started This course continues the Set up your data learning path or works perfectly if you’ve already identified your data needs and just need implementation guidance. You’ll use the Data Tracking Plan template for activities throughout this course. If you completed the first course in this learning path, you should have already saved a copy. If you haven’t, download it now! Set the scene Quick context: Throughout this course, imagine you’re a growth marketer at Sketcher.https://docs.customer.io/academy/quick-start/course-5/get-started-metrics/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/quick-start/course-5/get-started-metrics/🎯 Welcome to the course  The final piece This course completes the Quick start learning path or stands alone if you want to understand how your messages are performing. You’ve built campaigns, sent newsletters, and automated customer journeys. Now comes the best part: seeing how they performed and making them even better. In this course, you’ll learn to answer questions like “are my messages reaching people?”, “which campaigns are getting the best engagement?https://docs.customer.io/academy/quick-start/course-4/get-started-campaign/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/quick-start/course-4/get-started-campaign/🎯 Welcome to the course  Scaling up This course is part of the Quick start learning path—or works independently if you’re ready to automate customer messaging. You’ve already learned how to structure your data and build data-driven segments, and you’ve sent your first newsletter too! Now it’s time to put automation to work. In this course, you’ll create a campaign that automatically sends a targeted onboarding experience to new premium users.https://docs.customer.io/academy/quick-start/course-3/get-started-newsletter/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/quick-start/course-3/get-started-newsletter/🎯 Welcome to the course  Ready to send This course is part of the Quick start learning path or perfect on its own if you want to learn all about one-time messaging. You’ve got your data and your audience in Customer.io. Now it’s time to put that audience to use by sending your first message! In this course, you’ll learn how to create and send a one-time newsletter, ideal for product announcements, updates, or promotional messages.https://docs.customer.io/academy/quick-start/course-2/get-started-segments/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/quick-start/course-2/get-started-segments/🎯 Welcome to the course  Building on the basics This is the second course in the Quick start learning path. It also works great as a standalone if you’re ready to dive into audience targeting. You’ve got your people and your data in Customer.io. Now it’s time to make sure your messages reach the people they’re meant for, using segments. In this course, you’ll learn how to group people based on what you know about them—like when they signed up or what plan they’re on—so your messages feel more relevant, better timed, and personalized.https://docs.customer.io/academy/quick-guides/customerio-101/whats-cio/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/quick-guides/customerio-101/whats-cio/New to Customer.io? This quick guide will get you oriented fast. See Customer.io in action Get the full picture by watching this video, which walks you through what Customer.io does, how it works, and what you can build with it. What to expect before you start Customer.io requires some setup and ongoing work. To use it effectively, you’ll need to: Send data about your customers, either from your website, app, CRM, or other tools Spend time building segments and the messaging you want to send Test and iterate on your messaging strategy  Who’s this for?https://docs.customer.io/academy/quick-start/course-1/attributes/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/quick-start/course-1/attributes/You’ve added your people—now what? Now that your people are in Customer.io, it’s time to start exploring what you know about them. Every person in your workspace has a profile, and each profile has attributes, which are facts about that person. Person attributes are how you go from messaging “everyone” to messaging the right people with the right content. Click to view imageOpen image in new window What are attributes in Customer.https://docs.customer.io/academy/data/course-2/integration-methods/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/data/course-2/integration-methods/Scenario: Understand the options You’re looking at your Data Tracking Plan, ready to discuss implementation with your developer. You know what data you need and why.  Slack conversation Your developer: How do you want to send this data? JavaScript SDK, server-side API, or should we use Segment? You: Uh… which one should we use? Your developer: Depends on where the data is and what you need it to do. Let’s break down your options so you can have that conversation confidently.https://docs.customer.io/academy/data/objects/relationships/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/data/objects/relationships/Scenario: Connecting people to Acme Corp At Sketcher.io, you’ve created the Account object type and the actual Acme Corp object. Great! But now you need to answer: Which people are connected to this account? You know Sarah, Aniyah, and Garrick all work at Acme Corp. They all use Sketcher.io through the company’s account. But how do you tell Customer.io that these three people belong to Acme Corp’s account? That’s what relationships do.https://docs.customer.io/academy/quick-start/course-1/identifiers/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/quick-start/course-1/identifiers/Scenario: Who’s who? You’re about to bring your Brand Kits waitlist into Customer.io so you can start messaging them. To do that, each person needs a unique identifier, something like an email address or user ID. This is how Customer.io keeps track of people across your workspace and connects their data to the right messages. Click to view imageOpen image in new window What’s an identifier? You identify, add, and update people using their identifiers, which are unique values like an email address or a database ID.https://docs.customer.io/academy/data/course-1/identify-campaign-data/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/data/course-1/identify-campaign-data/Scenario: The activation problem You’ve documented Sketcher.io’s goals. Now it’s time to act on one of them. Looking at the Goals tab of your Data Tracking Plan, your team decides to tackle activation first: “Reactivate free customers who signed up but never created their first design.” The numbers make this urgent: only 30% of new signups complete their first design. And since completing a design strongly indicates someone will upgrade to a paid plan, that’s a lot of potential revenue slipping away.https://docs.customer.io/academy/data/course-2/data-priorities/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/data/course-2/data-priorities/Scenario: Your developer needs context You’ve got your Sketcher.io Data Tracking Plan ready, including all the events and attributes for the activation campaign. Now you need to meet with your developer to figure out how to get this data into Customer.io. Your developer will fill in the Source column of your tracking plan, documenting which integration method to use for each piece of data. But to make those decisions, they need to understand your priorities first.https://docs.customer.io/academy/data/course-3/clean-data/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/data/course-3/clean-data/Scenario: The cleanup conversation You’ve done your audit. You’ve added descriptions. But you also spotted some issues: there’s firstName AND first_name sitting right there in the list, and an event called test_click_DELETE that definitely shouldn’t be in production. Click to view imageOpen image in new window Later, when you start building a segment for website signups, you discover signup_source has messy values: some profiles show website, others Website, WEBSITE, or web.https://docs.customer.io/academy/quick-start/course-1/data-index/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/quick-start/course-1/data-index/Scenario: Time to double-check your foundation You’re getting ready to build your first message, maybe a launch announcement for Brand Kits, or a follow-up onboarding campaign. But imagine hitting send and realizing the attribute you’re personalizing with doesn’t exist, or an event you’re triggering on was never tracked. The Data Index helps you avoid that. Before you build anything, you can check: Did the attributes from your CSV upload come through?https://docs.customer.io/academy/quick-start/course-4/launch-campaign/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/quick-start/course-4/launch-campaign/Scenario: You’re ready to welcome new premium users At Sketcher.io, the team’s excited about the launch of the new Brand Kits feature. And your onboarding campaign is a key part of turning curiosity into action. You’ve done the work: mapped the journey, added messages, tracked behaviors, and measured success. Now all that’s left? Making sure your messages are ready to send and hitting Start. Set your messages to send automatically Before launching your campaign, there’s one crucial step: ensuring all your messages are set to send automatically rather than staying in draft mode.https://docs.customer.io/academy/quick-start/course-1/lay-foundation/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/quick-start/course-1/lay-foundation/Set the scene  Getting started This course begins the Quick start learning path or works perfectly if you just need to learn Customer.io data fundamentals. You’re sitting in a meeting room at Sketcher.io, and your product manager just said the words every marketer both loves and fears: “Brand Kits launches in two weeks.” This is a really big opportunity for both you and the team. Brand Kits is your company’s first premium feature: it’s a tool that lets design teams save and reuse logos, fonts, and color palettes.https://docs.customer.io/academy/data/objects/personalize-messages-objects/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/data/objects/personalize-messages-objects/Scenario: Make every message feel like it was written for them You’re sending the large team collaboration guide to every account that upgraded to Pro, used a premium feature, and has more than 25 seats allocated to their account. Acme Corp is one of them—they have 50 seats, they’re a tech company, and they’ve already tried out a Pro feature. But “Your team is using Pro!” feels generic when you actually know things about the account.https://docs.customer.io/academy/quick-start/course-2/manual-segment/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/quick-start/course-2/manual-segment/This course has focused mostly on data-driven segments—because they’re dynamic, flexible, and built for long-term growth. They update automatically based on user behavior and attributes, which makes them a great fit for onboarding, lifecycle messaging, and anything tied to real-time data. But that’s not the only way to build a segment. Sometimes, you just need a simple list and that’s where manual segments come in. What manual segments are good for Manual segments are flexible and quick to set up.https://docs.customer.io/academy/data/goals/measure-your-impact/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/data/goals/measure-your-impact/👋 Welcome to the course Your manager asks you a simple question: “Which campaigns are driving our paid upgrades?” You check your various campaign results and look at all the numbers. You add them up, but the total doesn’t match your actual paid upgrades. The math doesn’t work, and you can’t explain why. Goals changes that. Scenario: Meet the team You’re the growth marketer at Sketcher.io, a B2B SaaS product. Your team runs a welcome series, a feature adoption campaign, and a monthly release newsletter, all aimed at converting trial users to paid plans.https://docs.customer.io/academy/quick-start/course-4/intro-workflow-builder/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/quick-start/course-4/intro-workflow-builder/Scenario: Your onboarding strategy, in action You’ve got a plan: welcome new premium users, help them succeed with Brand Kits, and follow up if they don’t take action. You know what you want to say and who you want to reach. But how do you make it all run, automatically, for every user—without you having to lift a finger? Click to view imageOpen image in new window That’s where the workflow builder comes in.https://docs.customer.io/academy/quick-start/course-1/meet-your-people/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/quick-start/course-1/meet-your-people/Scenario: Who are you messaging? You’re getting ready to send a launch email about Brand Kits. Your waitlist has a number of people who all raised their hand for early access. They’re people who are tired of re-uploading the same logo to every project. You want that message to land in their inboxes with a personal touch, like “Hey Jason, your wait is over!” Click to view imageOpen image in new window For any of this to work, every person you want to message needs a profile in Customer.https://docs.customer.io/academy/data/course-1/naming-conventions/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/data/course-1/naming-conventions/Scenario: Make it readable You’re about to list out all the events and attributes Sketcher.io needs for the activation campaign. Before you start, you realize something: if you name these poorly now, you’ll create confusion later. Your developer will need to implement these. Your future self will need to reference them. New teammates will need to understand them. Good naming isn’t just about following rules, it’s about making your data readable for everyone who’ll work with it.https://docs.customer.io/academy/quick-start/course-1/navigate-the-course/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/quick-start/course-1/navigate-the-course/🧑‍🎨 Meet Sketcher.io Throughout this course, you’ll work alongside a fictional company called Sketcher.io, a design platform with tools for graphic and product designers. Like many product-led companies, they offer a freemium plan and they rely on great messaging to get users to see value and upgrade. Sketcher.io is launching a new premium feature called Brand Kits, a tool that lets teams save and reuse logos, fonts, and color palettes across projects.https://docs.customer.io/academy/design-and-content/send-first-email/ds-organize-files/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/design-and-content/send-first-email/ds-organize-files/Have you ever been a new hire, expected to hit the ground running by week 2? But your new employer’s documentation and marketing files are in more places than you can find? This is why organization matters! Make it easier on your next hires, as well as your future self, by creating a strategy upfront for your files. Then your teammates won’t get lost as the volume of files increases and creators change over time.https://docs.customer.io/academy/design-and-content/send-first-email/ds-liquid/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/design-and-content/send-first-email/ds-liquid/Now, you’ve already added a greeting that includes your recipient’s name as well as some standard links to your template. We did this by adding liquid to the message! {{ customer.first_name | default: "there" }}—The customer object lets you pull in data stored on your recipients’ profiles. This assumes you save an attribute called first_name to people’s profiles, so make sure you’re using an attribute name available in your workspace! The default filter sets a fallback if the attribute doesn’t exist for a recipient.https://docs.customer.io/academy/quick-guides/customerio-101/put-to-work/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/quick-guides/customerio-101/put-to-work/What you can actually do with Customer.io Take a look at how real teams use Customer.io once they’re up and running. Turn signups into active users Someone just created an account but hasn’t done anything yet? Send them a welcome email with a clear next step. Still crickets after 3 days? Follow up with a “stuck?” message that links to your most helpful resource. Already active? Skip the nudge and show them how to get even more value, like inviting their team, taking a tour, or trying your premium features.https://docs.customer.io/academy/quick-guides/custom-roles/put-role-to-work/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/quick-guides/custom-roles/put-role-to-work/Assign your roles You’ve built the role, now get it into the hands of the people who need it. For new team members, assign the custom role when you send their invite. For existing teammates, update their role when responsibilities shift. Maybe your junior marketer just got promoted and needs campaign launch access, or your contractor’s project wrapped up and they no longer need integration access. Update roles as jobs change, not weeks later when someone realizes they can’t do their work.https://docs.customer.io/academy/quick-guides/choose-message/decision-framework/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/quick-guides/choose-message/decision-framework/How to choose You know what each message type does. Now let’s figure out which one fits your need. flowchart LR Start([What are you sending?]) --> Q1{Is this a direct response toone person's action?Like: password reset,purchase receipt, verification code} Q1 -->|Yes| Trans[🔔 Transactional message—• One-to-one response• Sent via API• User expects it] Q1 -->|No| Q2{One message to a groupor multiple messagesover time?} Q2 -->|One messageto a group| News[📣 Newsletter—• Announcement or update• You schedule when• Everyone gets it at once] Q2 -->|Multiple messagesover time| Camp[⚙️ Campaign—• Automated journey• Adapts to behavior• People move at own pace] Quick decision guide Your situation Use this Why Someone clicked Forgot password and needs a reset link 🔔 Transactional One-to-one response to their action Someone just purchased and needs a receipt 🔔 Transactional One-to-one confirmation they expect Announce Brand Kits feature launch to waitlist 📣 Newsletter One-time message to a group you define Send monthly product updates to customers 📣 Newsletter Scheduled send to a segment Welcome new users and guide them through first week ⚙️ Campaign Multiple messages adapting to behavior Re-engage users who haven’t logged in for 30 days ⚙️ Campaign Ongoing automation triggered by inactivity Common confusion: Campaigns vs transactional messages Both can be triggered by user actions, so what’s the difference?https://docs.customer.io/academy/data/course-2/quick-wins/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/data/course-2/quick-wins/Scenario: You don’t always need a developer After learning about all those integration methods, you might be thinking: “Great, now I just have to wait for my developer to build everything.” Not necessarily! While your developer handles the technical integrations, there are a few self-service options that might be useful depending on your situation. Click to view imageOpen image in new window Three quick wins Self-service options are useful in a few common scenarios: when you need data before your technical integration is complete, when you have a one-time dataset to import (like historical customer lists or unsubscribed contacts), or when you want to test campaigns before committing to a full integration.https://docs.customer.io/academy/quick-start/course-5/campaign-analysis/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/quick-start/course-5/campaign-analysis/Scenario: The numbers are in You’ve got your Analysis report open. Brand Kits is sitting at 12% conversion, 45% open rate, and 3% click rate. But what do those numbers actually mean? And what should you do about them? Finding metrics is the easy part. The harder part is reading the story they’re telling you. Click to view imageOpen image in new window The difference between data and insights Anyone can pull up a conversion or open rate.https://docs.customer.io/academy/design-and-content/send-first-email/ds-intro-recap/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/design-and-content/send-first-email/ds-intro-recap/Next time someone asks you to send an email, you won’t be starting from zero. You’ve built the scaffolding that makes product announcements faster to build, more consistent, and a little less stressful. And a template that keeps you on-brand, reusable components that update everywhere at once, and a workflow connection that takes you from idea to inbox. That’s not a small thing. A lot of teams are still copy-pasting footers and rebuilding layouts from scratch every single time.https://docs.customer.io/academy/quick-start/course-3/newsletter-send/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/quick-start/course-3/newsletter-send/Scenario: One last review before you send You’ve set your audience, built your email, and connected it to your newsletter. The Review step is your final checkpoint before your message goes out. Here you’ll confirm everything looks right, decide when to send, and make a few last decisions about how your message gets delivered. One final check Before pressing send, take a moment and go through everything you’ve already set up.https://docs.customer.io/academy/quick-start/course-1/all-works-together/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/quick-start/course-1/all-works-together/Power your messages with data Now that you’ve seen people, attributes, and events in action, here’s how they all work together to support smarter, more personalized messaging. Remember Jason? Jason signed up from your launch email and just created his first project in Sketcher.io. Here’s what Customer.io knows about him: Identifier: jason.mendoza@example.com Attributes (who he is): Jason’s plan is “free”, he signed up on April 1, and he came from your product waitlist.https://docs.customer.io/academy/quick-start/course-2/timestamps-segment/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/quick-start/course-2/timestamps-segment/Scenario: Target recent sign-ups The Brand Kits feature just launched and you’re thinking of following up with users who signed up for Sketcher.io within the last 30 days. These users are still new and likely to engage if they get the right message at the right time. You could manually pull this audience every week… but there’s a better way. Click to view imageOpen image in new window Segment by time using timestamps Timestamps help you build dynamic segments that update based on when something happened—like when someone signed up, last logged in, or hit a key milestone.https://docs.customer.io/academy/design-and-content/send-first-email/ds-send-test/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/design-and-content/send-first-email/ds-send-test/Alright, so you’ve added your content, branded your components, adjusted your columns, and created a footer! You’re happy with the design and think this is a solid foundation for your product announcements. So what’s left? Send a test! Click to view imageOpen image in new window Previewing your design in your workspace is essential. It helps you catch issues with liquid, styling, content placement, and more. But sending a test lets you see what this will look like in an actual inbox.https://docs.customer.io/academy/quick-start/course-4/campaign-goals-exit/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/quick-start/course-4/campaign-goals-exit/Scenario: Define success and finish the journey Back at Sketcher.io, your onboarding campaign is nearly complete. 🎉 You’ve guided new premium users toward creating their first Brand Kit, followed up based on their behavior, and adapted the journey to their needs. Now it’s time to tie it all together: What counts as a win? When should someone leave the journey? How do you make sure your messages behave exactly the way you want?https://docs.customer.io/academy/quick-start/course-3/newsletter-goals/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/quick-start/course-3/newsletter-goals/Back at Sketcher.io… You’re not sending this newsletter just to tick a box. This send is part of a bigger plan: to drive upgrades and turn interest into action. But how do you know if it worked? You need a way to track results and prove your message made an impact. Bonus points if it gives you insights to make the next one ✨ even better ✨. What are conversion criteria?https://docs.customer.io/academy/quick-start/course-4/data-actions/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/quick-start/course-4/data-actions/Scenario: Mark a user as disengaged At Sketcher.io, you’ve nudged new premium users to try Brand Kits. If they still haven’t logged in, you want to capture that moment—not just for reporting, but so you can follow up later with a re-engagement flow. Your plan: If they didn’t log in, update their attribute to onboarding_status = disengaged. Guide the experience beyond messaging Your campaign doesn’t have to stop at messages. With data actions, you can update a person’s profile, trigger other campaigns, or sync with external tools—directly from the workflow.https://docs.customer.io/academy/data/course-2/data-deliverability/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/data/course-2/data-deliverability/Scenario: One more thing before you send Your Data Tracking Plan is complete and implementation is underway. You’re excited to start building campaigns. If you’re migrating from another email platform, there’s one critical step before you send: managing your email reputation data properly. If you skip this, you risk damaging your sender reputation before you even get started.  Starting fresh? If Customer.io is your first email platform, you can skip the migration steps.https://docs.customer.io/academy/data/course-3/data-success/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/data/course-3/data-success/ Getting started This course completes the Set up your data learning path or works perfectly if you already have data flowing into Customer.io and want to organize it properly. Set the scene You did it. After weeks of planning and collaboration with your developer, Sketcher.io’s data integration is live. Your events are flowing, your attributes are populating, and you can finally start building the campaigns you’ve only dreamed of until now.https://docs.customer.io/academy/data/course-2/special-formatting/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/data/course-2/special-formatting/Scenario: The phone number problem Your SMS campaign is ready to launch. You’ve built your segment, set up the messages, tested it all out, and worked up the courage to press Send. And… nothing sent. Just a wall of red Failed statuses. Click to view imageOpen image in new window You check a profile. The phone number is right there: (415) 555-1234. It looks fine to you. Your developer explains: “SMS needs phone numbers in E.https://docs.customer.io/academy/data/course-1/data-goals/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/data/course-1/data-goals/Scenario: Before you ask for data, know why you need it You’re ready to start planning Sketcher.io’s activation campaign, or so you think… Your instinct might be to jump straight to “what data do we need?” But that’s backwards. Before you can identify data requirements, you need to answer a more fundamental question: What are you trying to accomplish? That’s where resources like a data tracking plan can help out…https://docs.customer.io/academy/quick-start/course-2/target-right-people/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/quick-start/course-2/target-right-people/Scenario: Plan your audiences As you get ready for the upcoming Brand Kits launch at Sketcher.io, you’re mapping out your marketing strategy. You don’t want to send generic messages to everyone. Instead, you need to reach specific groups, like: Users currently on the free plan who might be ready to upgrade. Waitlist signups who haven’t converted into active users yet. Users who joined recently but haven’t created their first project. That’s where segments come in.https://docs.customer.io/academy/build-journeys/course-1/test-folder/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/build-journeys/course-1/test-folder/Test content Here’s some content. Tooltip Check out a tooltip about identifying people: identifyThe Customer.io operation that adds or updates a person. When you identify a person, Customer.io either adds a person if they don’t exist in your workspace, or updates them if they do. Before you identify someone (by their email address or an ID), you can track them anonymously. Here’s an h3 And here’s an h4 Include The next paragraph is an include.https://docs.customer.io/academy/build-journeys/course-2/test-folder/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/build-journeys/course-2/test-folder/Test content Here’s some content. Tooltip Check out a tooltip about identifying people: identifyThe Customer.io operation that adds or updates a person. When you identify a person, Customer.io either adds a person if they don’t exist in your workspace, or updates them if they do. Before you identify someone (by their email address or an ID), you can track them anonymously. Here’s an h3 And here’s an h4 Include The next paragraph is an include.https://docs.customer.io/academy/build-journeys/course-3/test-folder/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/build-journeys/course-3/test-folder/Test content Here’s some content. Tooltip Check out a tooltip about identifying people: identifyThe Customer.io operation that adds or updates a person. When you identify a person, Customer.io either adds a person if they don’t exist in your workspace, or updates them if they do. Before you identify someone (by their email address or an ID), you can track them anonymously. Here’s an h3 And here’s an h4 Include The next paragraph is an include.https://docs.customer.io/academy/build-journeys/course-4/test-folder/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/build-journeys/course-4/test-folder/Test content Here’s some content. Tooltip Check out a tooltip about identifying people: identifyThe Customer.io operation that adds or updates a person. When you identify a person, Customer.io either adds a person if they don’t exist in your workspace, or updates them if they do. Before you identify someone (by their email address or an ID), you can track them anonymously. Here’s an h3 And here’s an h4 Include The next paragraph is an include.https://docs.customer.io/academy/deliverability/course-1/test-folder/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/deliverability/course-1/test-folder/Test content Here’s some content. Tooltip Check out a tooltip about identifying people: identifyThe Customer.io operation that adds or updates a person. When you identify a person, Customer.io either adds a person if they don’t exist in your workspace, or updates them if they do. Before you identify someone (by their email address or an ID), you can track them anonymously. Here’s an h3 And here’s an h4 Include The next paragraph is an include.https://docs.customer.io/academy/deliverability/course-3/test-folder/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/deliverability/course-3/test-folder/Test content Here’s some content. Tooltip Check out a tooltip about identifying people: identifyThe Customer.io operation that adds or updates a person. When you identify a person, Customer.io either adds a person if they don’t exist in your workspace, or updates them if they do. Before you identify someone (by their email address or an ID), you can track them anonymously. Here’s an h3 And here’s an h4 Include The next paragraph is an include.https://docs.customer.io/academy/deliverability/course-4/test-folder/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/deliverability/course-4/test-folder/Test content Here’s some content. Tooltip Check out a tooltip about identifying people: identifyThe Customer.io operation that adds or updates a person. When you identify a person, Customer.io either adds a person if they don’t exist in your workspace, or updates them if they do. Before you identify someone (by their email address or an ID), you can track them anonymously. Here’s an h3 And here’s an h4 Include The next paragraph is an include.https://docs.customer.io/academy/deliverability/course-5/test-folder/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/deliverability/course-5/test-folder/Test content Here’s some content. Tooltip Check out a tooltip about identifying people: identifyThe Customer.io operation that adds or updates a person. When you identify a person, Customer.io either adds a person if they don’t exist in your workspace, or updates them if they do. Before you identify someone (by their email address or an ID), you can track them anonymously. Here’s an h3 And here’s an h4 Include The next paragraph is an include.https://docs.customer.io/academy/test/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/test/Test content Here’s some content. Tooltip Check out a tooltip about identifying people: identifyThe Customer.io operation that adds or updates a person. When you identify a person, Customer.io either adds a person if they don’t exist in your workspace, or updates them if they do. Before you identify someone (by their email address or an ID), you can track them anonymously. Here’s an h3 And here’s an h4 Include The next paragraph is an include.https://docs.customer.io/academy/quick-start/test-folder/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/quick-start/test-folder/Test content Here’s some content. Tooltip Check out a tooltip about identifying people: identifyThe Customer.io operation that adds or updates a person. When you identify a person, Customer.io either adds a person if they don’t exist in your workspace, or updates them if they do. Before you identify someone (by their email address or an ID), you can track them anonymously. Here’s an h3 And here’s an h4 Include The next paragraph is an include.https://docs.customer.io/academy/quick-start/course-5/test-improvements/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/quick-start/course-5/test-improvements/NOT IN COURSE Scenario: Test your welcome email improvement You’ve identified that your Brand Kits welcome email needs a stronger call-to-action to improve Brand Kit creation rates. You want to change from “Get started with Brand Kits” to “Create Your First Brand Kit Now” with a prominent button. But instead of just making the change and hoping it works, let’s test it properly. The simple A/B test approach The easiest way to test improvements in Customer.https://docs.customer.io/academy/design-and-content/send-first-email/ds-track-changes/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/design-and-content/send-first-email/ds-track-changes/Sometimes you make some change to an email and realize that was a good old-fashioned mistake. In comes version control to save the day! Each time you publish an email, Design Studio saves your current version. If you ever need to revert back, head to your Version History to preview previous edits. Click to view imageOpen image in new window Design Studio automatically saves your work as you go, but it only creates versions when you publish.https://docs.customer.io/academy/quick-start/course-1/events/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/quick-start/course-1/events/Scenario: Follow up after someone takes action Imagine you’ve just sent Sketcher.io’s new feature launch email announcing Brand Kits and users are starting to engage. Some have signed up and begun exploring templates. Others haven’t done much… yet. Wouldn’t it be helpful to follow up based on what someone has (or hasn’t) done? Luckily, you can use events! Events let you track user actions and use that behavior to send more timely, relevant messages.https://docs.customer.io/academy/data/objects/trigger-object-campaigns/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/data/objects/trigger-object-campaigns/Scenario: Notify teams when they upgrade You’re in the middle of planning your Team Workspaces messaging. You’ve noticed that when Sketcher.io customers upgrade from Starter to Pro plans, team members don’t seem to realize that they have access to new features and capabilities. But don’t fear, objects are here, and you can now let all people in an account know when this upgrade happens. Your goal: When an account upgrades, you want to celebrate with the entire team.https://docs.customer.io/academy/data/objects/trigger-relationship-campaigns/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/data/objects/trigger-relationship-campaigns/Scenario: Keep admins informed across all accounts You’re at Sketcher.io planning your Team Workspaces messaging strategy. You have hundreds of customer accounts using your platform—companies like Acme Corp, Beta Industries, Gamma LLC, and more. You want to be able to notify a team’s admin when someone joins their team. Not all admins across your workspace, but just the admin of the account that changed. You decide to investigate how this works with Acme Corp as your example… A new designer just joined their workspace, and you want Sarah (Acme’s admin) to know.https://docs.customer.io/academy/data/course-1/events-attributes/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/data/course-1/events-attributes/Scenario: Get ready to document By now, you understand what data your Sketcher.io activation campaign needs. You’re almost ready to document those requirements for your development team. But your developer asks: “For each piece of data, do you want it tracked as an event or a people attribute?” Click to view imageOpen image in new window Good question. Before you can document anything, you need to understand the difference. People attributes: What you know about people People attributes are information about a person, like their name, email, account type, or preferences.https://docs.customer.io/academy/data/objects/three-layers/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/data/objects/three-layers/Scenario: Figuring out where data lives You’re planning data for Sketcher.io’s Team Workspaces. You need to store information about Acme Corp and the people who work there. You need to track: Sarah’s email address Acme Corp’s company name How many seats Acme Corp has Sarah’s role at Acme Corp But you start to wonder, where does each piece of data live in Customer.io? The three layers When you work with objects, data can live in three different places:https://docs.customer.io/academy/data/goals/how-attribution-works/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/data/goals/how-attribution-works/Scenario: The data is in Your goal has been live for a few weeks. You can see total upgrades and revenue, and now there’s a breakdown by source. Some campaigns are contributing more than others. And a chunk of upgrades are marked as unattributed. Before you dig into what you do about it, you want to understand how credit got attributed in the first place. Last-touch attribution When someone achieves your goal, Goals looks backward and asks: of the campaigns I’m tracking, which message last qualified for credit before they upgraded?https://docs.customer.io/academy/quick-start/course-5/campaign-performance/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/quick-start/course-5/campaign-performance/Scenario: Your Brand Kits campaign is a top performer—now what? Great news! Your Analysis report showed that your Brand Kits onboarding campaign is outperforming your other campaigns with solid conversion rates and engagement. Remember, the whole point of this campaign is to get people to create their first Brand Kit, and early data shows it’s working. Click to view imageOpen image in new window Your manager is impressed and wants to know: “What’s making this campaign so successful?https://docs.customer.io/academy/design-and-content/send-first-email/ds-welcome/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/design-and-content/send-first-email/ds-welcome/Scenario: Product announcements for all You’re a growth marketer at Sketcher.io, and you’re sending product announcements every month and tired of rebuilding the same email structure from scratch—or worse, copying last month’s email and hoping you caught all the changes. Design Studio solves this. Use it to set brand defaults once, build reusable templates, and stop reinventing the wheel. You can drag in pre-built blocks or jump into the code when you need to, whatever works for your workflow!https://docs.customer.io/academy/data/course-1/data-journey/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/data/course-1/data-journey/ Getting started This course begins the Set up your data learning path or works as a standalone course if you just need to identify what customer data your team should bring into Customer.io. Set the scene You’re the growth marketer at Sketcher.io, a design platform with big ambitions but an even bigger problem. Your CEO just pulled you into an urgent meeting. The dashboard in front of her shows a stark number: 30%https://docs.customer.io/academy/quick-start/course-4/why-campaigns/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/quick-start/course-4/why-campaigns/Scenario: Onboard new premium users Good news: your newsletter worked! A healthy number of free users saw the announcement about Brand Kits and upgraded to a premium account so they could get access. Now what? Well, Sketcher.io’s product team noticed something important 👀: many new premium users drop off if they don’t use Brand Kits in the first week. So they’ve asked for your help to fix that. The solution? A simple onboarding campaign that:https://docs.customer.io/academy/data/objects/objects-explained/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/data/objects/objects-explained/Scenario: The challenge you’re facing Remember your VP’s question about messaging admins when someone joins a team? To answer if that’s possible, you first need to figure out where team account data should live in Customer.io. Let’s work through this with Acme Corp, one of Sketcher.io’s customers who have 50 employees using Team Workspaces. You need to store their account information: things like the company name, subscription tier, renewal date, and total seat number.https://docs.customer.io/academy/quick-start/course-2/segments-whats-next/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/quick-start/course-2/segments-whats-next/🎉 You made it! You’ve just learned how to build segments that help you reach the right people—at the right time—with the right message. Whether you’re onboarding new users, re-engaging inactive ones, or preparing for a campaign, segmentation gives you the foundation to do it with focus and flexibility. Now that you know how to build your audience, it’s time to put it to work. Up next: Sending your first newsletter In the next course in this learning path, you’ll learn how to create and send a one-time newsletter—perfect for product announcements, updates, and promotional messages.https://docs.customer.io/academy/data/course-1/whats-next/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/data/course-1/whats-next/🎉 You’ve built the foundation Look at all you’ve accomplished in this course: Started with clear campaign goals instead of vague “track everything” requests Applied the three-question framework to help identify data needs Learned how to structure data as events and attributes Named your data using clear, consistent conventions Documented your requirements in a developer-ready format You’ve transformed scattered campaign ideas into organized, actionable requirements. That’s the hard part! What comes next?https://docs.customer.io/academy/data/course-2/whats-next/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/data/course-2/whats-next/Congratulations! 🎉 You now have an understanding of integration methods, you know how to communicate priorities with your development team, and you can spot data formatting issues before they cause problems. That’s real progress on a topic that’s not always easy. What happens next Your developer builds the integration based on your tracking plan and data starts flowing into Customer.io. Then what? Start by taking the next course in this learning path, Organize your data for long-term success, which shows you how to keep everything clean and documented as your workspace grows.https://docs.customer.io/academy/data/course-3/whats-next/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/data/course-3/whats-next/You did it! 🎉 Think about what you can do now: audit your workspace to spot problems before they cause issues, document your data so teammates and AI can actually use it, and have productive conversations with your developer about what needs fixing so you can keep your data clean. Those are real, practical skills that’ll save you headaches down the road. What you can do now With clean, documented data in your workspace, you’re set up to:https://docs.customer.io/academy/data/goals/whats-next/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/data/goals/whats-next/You’ve made the shift You started this course with campaigns running and outcomes that mattered, but no clear line connecting the two. Now you can define a goal around a real business outcome, connect your campaigns to it, understand how attribution assigns credit, and use that data to decide what to scale, what to fix, and where the opportunities are. Click to view imageOpen image in new window That’s a shift from measuring campaigns in isolation to measuring what your messaging actually drives.https://docs.customer.io/academy/data/objects/whats-next/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/data/objects/whats-next/You’ve unlocked a new level of messaging You started this course wondering when (and if) you needed objects. Or maybe even just what objects were. Now you can: Recognize when objects solve a messaging challenge that person data can’t Design object structures with object attributes and relationship attributes Trigger campaigns when objects change and route messages based on relationships Use object data to personalize content and control campaign timing Document object requirements for your dev team Click to view imageOpen image in new window You’ve moved beyond person-level messaging into messaging that responds to what happens at the object level.https://docs.customer.io/academy/quick-start/course-1/whats-next/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/quick-start/course-1/whats-next/🎉 You made it! You’ve set up your data, explored real profiles, and seen how Customer.io turns attributes and events into personalized, meaningful messages. Nice work! Plan ahead for messaging strategy Before you add people to your own workspace, think about how you want to group them. You’ll use attributes and event data to group people into segments. And that determines who enters your campaigns, which messages they receive, and when they receive them.https://docs.customer.io/academy/quick-start/course-3/newsletters-whats-next/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/quick-start/course-3/newsletters-whats-next/🎉 You’ve sent your first message! Congratulations! You’ve mastered the art of the one-time newsletter. Throughout this course, you’ve learned how to: 💡 Decide when to use a newsletter vs. a campaign or other automation 🎯 Choose the right audience using a data-driven segment 📅 Fine-tune sending options like message limits and pacing 📊 Set a conversion goal to measure the real impact of your message 📝 Create and personalize newsletter content using Design Studio ✅ Apply best practices for sending smarter, not broader, by focusing on engaged audiences You’re now equipped to quickly announce new features, share product updates, or promote limited-time offers to a targeted group, all while optimizing for deliverability and engagement.https://docs.customer.io/academy/quick-start/course-4/campaigns-whats-next/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/quick-start/course-4/campaigns-whats-next/🎉 You built your first automated campaign! Congratulations! You’ve just created something powerful: an automated onboarding campaign that welcomes new premium users, guides them toward value, and adapts based on their behavior. What you accomplished Let’s take a moment to appreciate what you’ve accomplished: ✅ Built a complete customer journey that runs automatically ✅ Used smart timing to send messages at the right moments ✅ Created personalized paths based on user behavior ✅ Set up data actions to track engagement and outcomes ✅ Defined success metrics to measure real business impact Think like a growth professional As you build more campaigns, remember:https://docs.customer.io/academy/quick-start/course-5/metrics-whats-next/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/quick-start/course-5/metrics-whats-next/🎉 You finished the Quick Start learning path! Throughout this course, you learned how to: Identify what’s working and where people are dropping off using Analysis reports and workflow metrics Read campaign data and understand the story behind the numbers Go from spotting a problem to fixing it in the same conversation with the agent Click to view imageOpen image in new window You can now look at your messaging data and know what it’s telling you and what to do about it.https://docs.customer.io/academy/quick-guides/custom-roles/why-custom-roles/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/quick-guides/custom-roles/why-custom-roles/Scenario: When standard roles aren’t enough Standard roles in Customer.io—Workspace Admin, Author, and Viewer—work great for many teams. But sometimes, your team’s actual needs don’t fit neatly into these categories. Here are three situations where standard roles fall short: Click to view imageOpen image in new window In each case, standard roles are either too broad (they can see and do way too much) or too narrow (they can’t do their actual job).https://docs.customer.io/academy/quick-start/course-3/why-newsletters/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/quick-start/course-3/why-newsletters/Scenario: Announce your new feature Brand Kits just launched and the team wants to turn waitlist interest into paid upgrades. You’ve got a group of free plan users who signed up to hear about this premium feature. Now you need to get them excited enough to act. The message needs to be timely and targeted. You don’t need ongoing automations for now, you just need a clear announcement to the right people.https://docs.customer.io/academy/data/objects/dev-collaboration-objects/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/data/objects/dev-collaboration-objects/From concept to implementation Throughout this course, you’ve been learning through Sketcher.io’s example. Their objects were already set up and Acme Corp’s and other account data was flowing in, campaigns were triggering when seat limits changed, and everything just worked. But Sketcher.io didn’t start that way. At some point, someone at Sketcher.io (likely) had to work with their dev team to get objects implemented. And if you want to use objects in your workspace, you’ll probably need to do the same thing.https://docs.customer.io/academy/data/course-2/work-with-dev/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/data/course-2/work-with-dev/Scenario: The awkward Slack message You have your Data Tracking Plan ready including all the events and attributes you need for your activation campaign, neatly documented with descriptions and campaign goals. Now you need to talk to your developer about actually implementing it. You’ve drafted a Slack message three times and deleted it each time. Should you just send them the spreadsheet and let them figure it out? Should you explain every single detail?https://docs.customer.io/academy/quick-guides/customerio-101/what-you-do/Mon, 01 Jan 0001 00:00:00 +0000https://docs.customer.io/academy/quick-guides/customerio-101/what-you-do/The data that powers your messaging Before you can send behavior-based messages, Customer.io needs context about your customers. Getting that context means sending certain types of data to Customer.io: Data type What it is Examples People Your customers and users jason@example.com, sarah@company.com Person attributes Facts about them plan_type = premium, signup_date = 2025-01-10, location = San Francisco Events Actions they take signed_up, upgraded_plan, invited_teammate This combination is what makes behavior-based messaging work.