2024 Release Notes

Read about all the great new updates and features we've released in 2024!

If you have questions about any of these features, talk to your Iterable customer success manager.

# September 2024

# Log in faster with biometrics for MFA

September 11, 2024

Iterable is commited to making your account more secure and easier to access. Today, we're releasing biometric authentication for Multi-Factor Authentication (MFA). Members who log in to Iterable using MFA can now enroll in biometric authentication to use methods like fingerprint or facial recognition to log in to their accounts. This step bypasses the need to enter a password when logging in to Iterable.

Eligible users can enroll in biometric authentication by following the prompts when you log in to Iterable and are asked to remember your device.

To learn more about biometric authentication and how to enroll, see MFA with Biometric Authentication.

# EDC support for Embedded Messaging

Sept 6, 2024

Iterable's European Data Center (EDC) now supports Embedded Messaging.

To learn how to configure Iterable's iOS, Android, and Web SDKs to use Iterable's EDC, see:

• Iterable's iOS SDK
• Iterable's Android SDK
• Iterable's Web SDK SDK

# August 2024

# More subscribe events can add users to journeys

August 20, 2024

Now you can add users to journeys when they subscribe to a message channel or type! Over the next couple of weeks, we'll be adding two new options under the Event Occurs entry source in the Start tile: Subscribe to Channel and Subscribe to Message Type.

To learn more about this update and start using these events in your journeys, see Journey Setup: The Start Tile.

# Saved rows in the Drag and Drop editor

August 15, 2024

We updated the Drag and Drop template editor to make it easier for your team to build delightful messages in Iterable. With saved rows, your team can create reusable stylistic and structural template elements that you can insert into templates again and again. Saved rows make it faster and easier to build message templates, maintain a consistent look and feel across your brand's messages, and reduce the likelihood of design errors creeping in.

To learn more and get started with this feature, see Creating Reusable Template Content. Happy building!

# Iterable SMS expands to new countries

August 1, 2024

Iterable SMS is expanding service to new countries to help you reach even more of your audience worldwide! Here's what's new:

• Alphanumeric support is now available in Greece and Israel.
• Short code support is now available in New Zealand.

To learn more about Iterable SMS and where services are available, see Iterable SMS Services.

To get started with Iterable SMS in these new countries, talk to your customer success manager.

# July 2024

# Now available: Journey Assist

July 29, 2024

After a highly-anticipated and successful beta, Journey Assist is being made available to all Iterable customers. 🎉

This feature is part of a rolling release and will become available to groups of customers over the next few weeks. If you don't see it yet, check back soon!

In the meantime, if you'd like to learn more about this feature and how to use it, see:

• Journey Assist
• Generating a Journey with AI

# Now available: Journey conversion goals + feature enhancements

July 23, 2024

We just released a batch of updates that make tracking journey engagement and conversions easier than ever. Here's what's new:

• Journey conversion events (New feature!)

  Some journeys are designed to encourage users to take a specific action (for example, set up an account with your brand, make a purchase, or review a product). With journey conversion goals, you can specify a conversion event for a journey and its associated campaigns — then track how well you're meeting that conversion goal.

• New Exit Rules functionality

  Now when users match your exit rules criteria, you can remove them from the current journey and send them to another journey. Plus, you can use journey conversions as exit criteria!

• Updated default attribution method

  To help more Iterable customers benefit from tracking conversion events, we've updated the default attribution method for both journey and campaign conversion events to time-based attribution. This method provides automatic conversion tracking and is generally the best option for most Iterable customers, as it requires the least work from your engineering team.

  NOTE

  This change does not affect your conversion tracking settings for existing campaigns and journeys. When you set up a conversion event for a new campaign or journey, time-based attribution is selected by default — however, you can change it to attribution by campaignId if you prefer. See Campaign Attribution to learn how to send the right data to Iterable for this attribution method.

To learn more about this update and get started with journey conversion goals, see Monitoring Journey Engagement.

# New comparators for segmentation queries

July 8, 2024

To make it easier to identify groups of similar users, we've added two new comparators to Iterable's Segmentation tool: Is One Of and Is Not One Of. With these new comparators, you can specify up to 100 possible values that a field must match or must not match. These comparators work with fields that have the following data types: string, long, and double (their values must be words or numbers).

To start adding values, click into the text entry box. From here, there are three ways to add your desired values:

• Select one or more existing values from the dropdown menu that appears.
• Type individual values into the text entry box, and press Enter on your keyboard to submit each value.
• Paste multiple values into the text entry box (separated by commas, pipes, or line breaks), and press Enter on your keyboard.

Keep in mind that searches are case- and formatting-sensitive (a search for a value of multicity will yield different results than a search for multiCity or multi-city). For the most accurate segmentation results, be sure to check your search values for correct formatting, capitalization, spelling, and typos.

To learn more about this update, see Segmentation Overview.

# Journey Assist beta

July 1, 2024

Have you ever wished that there was an easier way to create and set up journeys? Well, today’s your lucky day! With today's release of Journey Assist, a brand-new Iterable AI feature, you can describe the kind of journey or tiles you want to create, and with a single click, Journey Assist will build them for you. Review and edit the generated tiles as you would for any journey, and you’re all set!

To learn more and get started, see Iterable AI Overview and Journey Assist.

# June 2024

# Journeys: Embedded Message tile

June 13, 2024

Now you can send embedded messages from journeys! The new Embedded Message tile displays an embedded message in your app or website to users who pass through the tile.

To learn more about this update and get started with this feature, see Journey Setup: Message Tiles.

# Embedded Messaging support in Iterable's Web SDK

June 12, 2024

Version 1.1.0 of Iterable's Web SDK brings GA support for Embedded Messaging, including support for out-of-the-box views (cards, notifications, and banners).

For more information, read:

• Embedded Messages with Iterable's Web SDK
• Web SDK release notes on GitHub (which include information about breaking changes between the beta and GA releases of this feature).

Documentation about out-of-the-box views in the Web SDK is coming soon.

# May 2024

# Next Best Action campaign recommendations

May 30, 2024

If you've ever wanted help deciding when to send retargeting campaigns, and who to send them to, today's your lucky day. With today's release of Next Best Action, you'll get:

• Details about campaigns that have completed with lower engagement than expected, but are considered good candidates for retargeting.

• A list of users who didn't engage with a campaign, but were expected to do so based on historical user engagement data.

• Ready-to-send campaigns, with creative copy suggestions and an audience to retarget.

To learn more, read Next Best Action Overview. To add Next Best Action to your Iterable account, talk to your customer success manager.

# Disabling new email-based projects and improving userId validation

May 29, 2024

Starting on Friday July 5, 2024, Iterable is making changes to project types and unique identifiers as part of our continuing effort to improve your data environment. At that time, the following changes will take effect:

• Deprecating email-based projects: Iterable will no longer allow the creation of new email-based projects. Existing email-based projects will continue to function as they do today and are not affected by this change.

  Hybrid projects will be the default choice. Hybrid projects flexibly allow you to use email or userId to identify users, and enforce uniqueness for both fields.

  NOTE

  Organizations that have created a new email-based project within the 12 months preceding this announcement are exempt from this change and can continue to create email-based projects for the forseeable future. If you have questions, please contact your customer success manager.

• Improved validation for userId field: Iterable will begin enforcing improved validation rules for theuserId field. This change was announced earlier this year, and we have updated the enforcement date to July 5, 2024.

To learn more about these changes, read Project Types and Unique Identifiers.

# Journeys: Yes/No Split tile testing

May 28, 2024

Want to make sure your Yes/No Split tiles are set up right before you send users through a journey? We added a new Preview results button in the Yes/No Split tile that lets you see which branch users would go down in the journey once it's published and turned on — so you can find out in advance if the tile isn't working as you expect and adjust your criteria before any users actually go through the journey.

To learn more about this update and get started with this new feature, see Journey Setup: Filter Tiles.

# Manage your Iterable data schema with Data Schema Management

May 28, 2024

Today, we're excited to announce a new feature that helps you manage your data schema in Iterable: Data Schema Management. This feature puts controls in place that enable you to intentionally and accurately manage a project’s data schema. This update to Iterable includes these new capabilities:

• Create new fields for custom events, purchase events, and user profiles directly from the app.
• Lock your data fields and add new ones only when you want to.
• Iterable enforces your data schema, avoiding excessive and flawed data.

Overall, these updates improve your ability to maintain good data hygiene so you can stay focused on value-added marketing activities.

Things that are changing in Iterable include:

• Data Schema Management – a new page where you can view, create, and manage your custom events, user profile fields, and purchase event fields. This replaces Settings > Custom Event Usage.

• New settings that enforce a project’s existing data schema and prevent accidental addition of new fields and custom events.

• Name validation for custom events and fields: When creating new fields in Data Schema Management, Iterable stops users from creating field and event names that don’t meet new requirements that fit best practices. (No change to field names when using our API.)

• Changes to some data types: Data Schema Management introduces new rules for creating arrays and nested fields.

API updates include:

• A new, optional parameter, createNewFields, which overrides field lock settings, allowing your developers to create fields when they need to (and, to prevent accidents).

• Updated response bodies that provide visibility when your API requests change your data schema (such as adding a new field), and when data isn’t accepted by Iterable.

To learn more, read Data Schema Management Overview.

# Now available: Image uploader

May 22, 2024

Now you can upload images directly to the templates you create with the WYSIWYG and Side by Side editors! With a simple, visual interface and the ability to access and re-use recently uploaded images in your project, this new feature makes it faster and easier to add images to the campaigns you build in Iterable.

To learn more about this update and get started with this feature, see Uploading Images to Iterable.

# Now available: Dynamic Content Builder

May 22, 2024

There's an easier way to add dynamic content to your Iterable templates! Dynamic Content Builder, our new Handlebars code generator feature, is now available to all Iterable customers. You can use it in the WYSIWYG and Side by Side template editors, as well as the snippet editor.

To learn more about this update and get started with this feature, see Dynamic Content Builder.

# Multi-Factor Authentication (MFA) improvements

May 21, 2024

Today we're updating Iterable's Multi-Factor Authentication (MFA). We've made several enhancements to improve account security, with additional changes on the way that you should be aware of.

Here's what's new in today's release:

• Reset MFA for other members

  Members with the Manage Members org permission can reset Multi-Factor Authentication (MFA) enrollment for other members of the account. This feature is especially useful when members need to register a new device.

  Once MFA is reset, members can follow these instructions to enroll a new device in MFA.

  To learn more, read Managing and Resetting Multi-Factor Authentication (MFA) for Iterable Members.

• Security key support

  Members can now enroll in MFA using a security key or an authenticator app. Security keys are physical devices that generate one-time codes to log in to an account.

• Recovery codes

  For you to self-service account recovery, Iterable now provides a recovery code that you can use to regain access to your account if you lose access. Save this code when you enroll in MFA, and keep it in a safe place.

• MFA is required for new orgs

  Starting today, all new Iterable organizations require MFA for all members signing in with email and password.

Changes coming in the future include:

• MFA required for all orgs

  Beginning Tuesday, July 23, all members who sign in with email and password will be required to enroll in Multi-Factor Authentication (MFA) in a phased rollout.

  Once your org has been automatically enrolled in MFA, you can no longer disable MFA for individual users.

  Next steps for enrollment:

  • Self-managed enrollment (now - July 22)

    Members can enroll in MFA any time before the rollout starts on July 23rd by following these instructions: Enrolling in Multi-Factor Authentication (MFA).

  • Automated enrollment (July 23 - August 9)

    From July 23rd to August 9th, all members who log into Iterable with their email and password will be enrolled in MFA on a rolling basis. Once prompted, members must complete the MFA enrollment process to log into the Iterable platform.

We strongly recommend that admins audit Iterable members to validate that all should continue to have access before the July 23rd MFA rollout period begins.

Additional communications have been sent to org admins to notify them about these changes. If you have any questions, contact your customer success manager.

# Performance enhancement: Select lists to be excluded from a journey

20 May, 2024

Now when you set up a journey with the Schedule entry source, you can choose lists of users to exclude from the journey. This not only lets you be sure the right users (and only the right users) are added to each journey, but also improves the performance of your journeys by reducing the number of users who enter the journey and then have to be filtered out.

If you have journeys that use the Schedule entry source, consider updating your list selections in the Start tile to take advantage of this performance improvement — then remove any filter tiles that are no longer necessary.

To learn more about this update, see Journey Setup: The Start Tile.

# SMS Double Opt-In

May 14, 2024

SMS Double Opt-In is an automated subscription flow that asks users to confirm their subscription before receiving SMS messages from your brand.

With SMS Double Opt-In, users who express interest in receiving SMS messages from your brand receive a confirmation message sent to their phone. To complete the subscription, users simply need to reply to the message.

By implementing SMS Double Opt-In, you unlock these benefits:

• No complicated journey setup.
• Time saved with pre-built confirmation and legal disclaimer messages.
• A digital record of opt-in consent, supporting compliance and building trust.
• Improved data quality with real phone numbers confirmed by engaged users.

Don't miss out on the opportunity to fast-forward your SMS marketing strategy. Discover the power of SMS Double Opt-In today. To learn more about how it works, read SMS Double Opt-In Overview.

# Smart Ingest now available

May 1, 2024

Starting today, Iterable's Smart Ingest is now available to all customers. Co-developed with Hightouch, Smart Ingest enables you to quickly set up and manage your data source imports directly within your Iterable project.

Things that are coming to Iterable include:

• A new page: Integrations > Smart Ingest
• Import data from supported data sources into Iterable
• Flexible data import options, including field mapping and custom field transformations
• No-code setup (advanced configurations are optional)
• A dashboard to view your project's syncs, their health status, and their run history
• Sync scheduling and monitoring
• Support for multiple sync types, including users, events, and more

If you joined the Smart Ingest beta, you'll see some additional features in today's release, including:

• Enhanced sync monitoring – We've added more detailed sync monitoring capabilities, including a new Runs tab that shows the status of each sync run and the types of operations completed.
• Lightning sync is now available as a self-service action, allowing you to upgrade to Lightning sync directly from the Smart Ingest dashboard.

It's never been easier to import data into Iterable!

Currently, Smart Ingest supports these data sources:

• Amazon Redshift
• Databricks
• Google BigQuery
• SFTP (supports CSV files only)
• Snowflake

Additional sources are available as an open beta. Talk to your Iterable customer success manager if you're interested in connecting to one of these data sources:

• Amazon Athena
• Amazon S3
• Azure Blob Storage
• Azure Synapse
• Google Cloud Storage
• Microsoft SQL Server
• MySQL
• Oracle
• PostgreSQL

To learn more about Smart Ingest and get started today, read Smart Ingest Overview.

# April 2024

# Migrating from legacy Firebase to Firebase HTTP v1

April 30, 2024

Google has deprecated the legacy Firebase Cloud Messaging (FCM) API, and replaced it with the FCM HTTP v1 API.

If any of your Iterable projects use Firebase Cloud Messaging (FCM) to send mobile or web push notifications, migrate them to the FCM HTTP v1 API before July 22, 2024 (Google has changed the deadline from June 20 to July 22). On July 22, 2024, Google will start shutting down the legacy FCM API, and Iterable projects that still use it will no longer be able to send mobile or web push notifications.

To learn more, read:

• Mobile Push Notifications: Migrating to the FCM HTTP v1 API
• Web Push Notifications: Migrating to the FCM HTTP v1 API

If you have any questions, contact Iterable support.

# Segmentation updates

April 29, 2024

We've made some updates to Iterable's Segmentation tool to give you a more seamless experience identifying and saving user cohorts.

Now, when you create a new segmentation query, the most popular search option (All) is selected by default. You can still change it to Any or None if you prefer, and your existing queries won't be affected by this change.

To learn more about this update, see Segmentation Overview.

# Now available: Campaign Performance Alerts

April 25, 2024

Now you can monitor how your campaigns are performing — even when you're not signed in to Iterable! With alerts, you can set up performance thresholds that notify you via webhook when a campaign isn't performing as expected. If a campaign exceeds one of your alert thresholds, you'll receive a notification outside of Iterable prompting you to sign in and troubleshoot the issue.

To learn more about this update and get started with alerts, see Campaign Performance Alerts.

# Identifying deleted user profile data in Iterable's Snowflake Data Share

April 22, 2024

With this update, we're making it easier to find fields that are related to deleted user profiles. We've added a new User Identities Deletions table, which you can use in hybrid and userID-based projects to map ITBL_USER_ID to either email or userId for deleted user profiles.

For those who are currently using the User Identities table, we've added the DELETED_AT field to isolate this information for your current use. However, the User Identities table will be deprecated in the coming months, so we recommend that you transition to the other User-related tables at your earliest convenience. If you have questions about this change, please contact your customer success manager.

# Display update for SMS sending platforms: Iterable SMS, Twilio Direct, and Telnyx Direct

April 3, 2024

To make it easier to understand the SMS services you're using and how you're billed for them, you’ll see these updates to your SMS sending platforms in Iterable. We're rolling out these changes to accounts over the next few weeks, so if you don’t see them yet, they’ll be there soon.

Iterable SMS, Twilio, and Telnyx accounts connected to Iterable now display as Iterable SMS, Twilio Direct, and Telnyx Direct respectively on the Sending Platforms and Usage and Billing screens.

If your update happens during the current billing cycle, you may see a mix of the old and new display names for SMS services on the Usage and Billing screen. This will be resolved on your next billing cycle. The total volume of SMS and MMS sent and received is not changing.

No changes have been made to your existing and future SMS campaigns, SMS provider credentials, settings, or SMS sender configurations in Iterable.

If you have questions about your billing after these changes, contact your customer success manager.

Example updated Usage and Billing screen:

To learn more about viewing your SMS usage details, read Usage and Billing.

Example updated Sending Platforms screen:

To learn more about adding your SMS sending platform to Iterable, read Setting up SMS.

# March 2024

# Smart Ingest beta expands to more data warehouses

March 19, 2024

Today we've expanded the data warehouses that Smart Ingest can import from. Now, you can use Smart Ingest to import from any of these data warehouse providers:

• Snowflake
• Amazon Redshift
• Databricks
• Google BigQuery

To learn more, read Smart Ingest Overview.

# Import data from Snowflake using Smart Ingest (beta)

March 12, 2024

Iterable's Smart Ingest, co-developed with Hightouch, enables you to quickly set up and import data from your data warehouse directly in your Iterable project.

Smart Ingest is now available during a beta period for customers who use Snowflake and want to import data from Snowflake to Iterable.

Additional data warehouse sources coming soon: Amazon Redshift, Databricks, and Google BigQuery.

To learn more, read Smart Ingest Overview.

# Improved validation for userId field

March 6, 2024

We're making some changes to validation requirements for the userId field. Currently, when you create or update a user, Iterable enforces a maximum character length of 128 characters.

As part of our continuing effort to improve your data environment, Iterable will start enforcing additional requirements for the userId field beginning July 5, 2024.

Updates to user ID field validation may change your experience in two ways:

• List uploads of CSV files skip rows with invalid userId values
• API requests reject invalid or null userId values

New validation specifications for all project types include:

• Must be non-empty. Blank, null, or empty values are not accepted in requests to identify users.

  API requests with a userId lookup field that is blank, null, or empty are rejected. Instead, if a user doesn't have a userId value, such as in a Hybrid project, use the email field to identify the user and don't include a blank userId field in the API request.

  API requests for email-based and hybrid projects that include userId with a null value in dataFields with intention to clear the data from a user profile are still accepted.

• Maximum length of 128 characters.

  NOTE

  Initially this accouncement included a character length of 52 for email-based projects. This is no longer the case. All project types have the same limit of 128 characters for the userId field.

• Must not contain non-printable ASCII characters, such as non-breaking spaces and soft hyphens.

  Non-printable characters are typically created programmatically and aren't visible printed characters. Not to be confused with spaces, tabs, or other whitespace characters, or with [hard hyphens](https://www.ascii-code.com/ character/-) (or minus sign).

• Must not end with a space.

Existing user profiles with invalid userId values are not affected by these changes and these users will remain in Iterable as functional records. However, if you update an existing user profile with an invalid userId value, Iterable rejects the value. Users with invalid userId values will remain as records in Iterable.

You can update existing user profiles with invalid userId values to use an accepted value, but cannot create new users with invalid userId values.

To prepare for these upcoming changes, make sure to update your userId field data values so that they meet our new validation requirements as well as technical best practices.

To learn more about userId field, Iterable's validation rules, and recommended best practices for userId field values, read Project Types and Unique Identifiers.

To learn how to change the user ID value for a user's profile, read Updating a User's Email Address or User ID.

# Updates to Snowflake Data Share

March 5, 2024

If you're using Iterable's Snowflake Secure Data Sharing and have wished you could access user profile data, we've got great news for you! With this release, Snowflake Secure Data Sharing now includes a new User table. Now, you'll have access to valuable data like city, region, country, and timezone fields, as well as AI insights like Brand Affinity and Predictive Goals scores (depending on your use of these features).

For more information, read Snowflake + Iterable Integration.

# Create triggered campaigns via API

March 1, 2024

Now you can use the POST /api/campaigns/create API endpoint to create triggered campaigns. This endpoint previously only supported blast campaigns, but the updated version allows you to specify which campaign type you want to create each time you call it.

# February 2024

# Predictive Goals templates

February 20, 2024

With this release, creating Predictive Goals is easier than ever with the addition of templates. If you’ve already added Predictive Goals to your Iterable account, but have been waiting to get started, there’s no better time. Pick one of our predefined Predictive Goals templates to unlock the insights they provide for some of marketers’ most common business cases.

For information about adding Predictive Goals to your Iterable account, talk to your customer success manager. See the Predictive Goals support docs for more information.

# Embedded Messaging

February 1, 2024

Embedded Messaging is a new message channel that allows you to deliver inline, native messaging experiences in your mobile and web apps — all powered by Iterable campaigns.

Embedded messages are designed to help you deliver relevant, engaging messages to your users.

• Inline, native message interfaces — Your apps and websites can display embedded messages however you like — with customizable, out-of-the-box views included in the latest updates to Iterable's SDKs (banners, cards, and notifications), or with fully custom interfaces of your own design and implementation (carousels, for example). However your apps display embedded messages, they'll appear right in context — no overlays or popups necessary!

• Real-time eligibility – As users interact with your mobile and web apps, they're only shown the embedded messages for which they're eligible at that exact moment, based on their current user profile data. As user profile data changes in Iterable, so does campaign eligibility, and Iterable silently prompts your apps to refresh the user's embedded messages whenever their eligibility changes.

• Placements – Your apps and websites can contain many embedded message placements — places where embedded messages are displayed. Every placement can appear in one or more of your apps and websites, and every embedded message campaign is associated with a single placement. With placements, your apps and websites will always display your embedded messages right where they're most useful.

• Prioritized – When a user is eligible for multiple embedded message campaigns that all target the same placement in your app, you can use message priority to ensure that you display the highest priority message or messages.

• Personalized – Just like other message channels, you can personalize embedded messages with user data, through Handlebars, Catalog, data feeds, and snippets.

• Measurable – As users interact with your embedded messages, you can monitor various campaign metrics in Campaign Analytics and Messaging Insights.

• SDKs and APIs – To retrieve and display embedded messages in your apps and websites, and to track engagement events, you can use Iterable's mobile SDKs, or you can make direct calls to Iterable's Embedded Messaging API endpoints.

Ready to get started? Read Embedded Messaging Overview.

# January 2024

# Predictive Goals Enhancements

# Media URLs in the pushSend system webhook payload

January 18, 2024

We've updated the payload of the pushSend (push notification send) system webhook to include two more fields:

• attachmentUrlAndroid – The Android media URL specified in the campaign.
• attachmentUrlIos – The iOS media URL specified in the campaign.

These fields correspond to the campaign's media URLs:

If your campaign doesn't specify values for these fields, they'll be present in the pushSend system webhook payload and set to null.

For more information about system webhooks, read System Webhooks.

# New experiment experience

January 17, 2024

We’ve got great news! With this release, Iterable experiments are easier to use than ever. We've made some significant updates to the experiments UI that streamline experiment creation to a single page, with the look and feel you’ve come to know throughout the Iterable product. Other changes include:

• The addition of the Iterable template editor to make editing and creating variant body text more straightforward.

• Access to Iterable's Copy Assist to provide fresh ideas for message variant subject lines based on your original control copy.

  

We’re releasing these updates to Iterable customers over the coming weeks, so if you don’t see them yet, check back soon! In the meantime, check out the Experiments support docs for more details.

# Predictive Goals enhancements

January 8, 2024

We're excited to announce the following new enhancements to Iterable's Predictive Goals:

• To simplify goal setup and to optimize goal performance, all predictions are now based on a 30-day time period. Existing goals with a different duration will be updated to the 30-day duration.

• You can now preview the number of users associated with the goal criteria you're selecting while you're building a goal.

  

  In addition, when you create a goal, your criteria is now automatically checked to ensure that the minimum audience threshold is met for goal creation. If too few users satisfy the goal criteria, you'll receive a message that alerts you to revisit your criteria before the goal can be processed.

  Both of these changes are designed to help you gauge whether the criteria you're using aligns well with the type of insights you hope to gain so you can make changes before submitting the goal for creation. Remember that goal criteria that applies to most, or very few, of your users won't produce insightful predictions.

See the Predictive Goals support docs for more information.