diff --git a/src/_data/products.yml b/src/_data/products.yml index 4a9e8cfe02..2975ee59c5 100644 --- a/src/_data/products.yml +++ b/src/_data/products.yml @@ -37,6 +37,15 @@ items: # engage-foundations: false # engage-plus: false +- product_display_name: Unify Plus + slug: unify-plus + plan-note: "Unify Plus requires a business tier account and is included with Engage" + addon: true + plans: + free: false + team: false + business: true + - product_display_name: Protocols slug: protocols plan-note: "Protocols is available as an add-on for Business plans only." diff --git a/src/_data/sidenav/main.yml b/src/_data/sidenav/main.yml index b090aa5ded..3f22b06efd 100644 --- a/src/_data/sidenav/main.yml +++ b/src/_data/sidenav/main.yml @@ -322,16 +322,32 @@ sections: title: Sample Queries - path: /unify/profiles-sync/tables title: Tables & Materialized Views + - section_title: Traits + slug: unify/traits + section: + - section_title: Predictive Traits + slug: unify/traits/predictive-traits + section: + - path: '/unify/traits/predictive-traits/' + title: Predictive Traits + - path: '/unify/traits/predictive-traits/using-predictive-traits' + title: Using Predictive Traits + - path: '/unify/traits/predictive-traits/suggested-predictive-audiences' + title: Suggested Predictive Audiences + - path: '/unify/traits/computed-traits' + title: Computed Traits + - path: '/unify/traits/sql-traits' + title: SQL Traits - path: /unify/profile-api title: Profile API - - path: /unify/profile-api-limits - title: Profile API Limits - path: /unify/debugger title: Profile Debugger - path: /unify/unify-gdpr title: Unify and GDPR - path: /unify/faqs title: Unify FAQs + - path: /unify/product-limits + title: Unify Limits - section_title: Engage section: @@ -370,19 +386,6 @@ sections: title: Account-level Audiences - path: '/engage/audiences/organization' title: Organize Audiences - - path: '/engage/audiences/computed-traits' - title: Computed Traits - - path: '/engage/audiences/sql-traits' - title: SQL Traits - - section_title: Predictive Traits - slug: engage/audiences/predictive-traits - section: - - path: '/engage/audiences/predictive-traits/' - title: Predictive Traits - - path: '/engage/audiences/predictive-traits/using-predictive-traits' - title: Using Predictive Traits - - path: '/engage/audiences/predictive-traits/suggested-predictive-audiences' - title: Suggested Predictive Audiences - section_title: Journeys description: "Learn how to create multi-step Journeys to tailor messages to your users." diff --git a/src/engage/index.md b/src/engage/index.md index c170797928..127745e96d 100644 --- a/src/engage/index.md +++ b/src/engage/index.md @@ -21,7 +21,7 @@ Add detail to user profiles with new traits and use them to power personalized m - [**Computed Traits:**](/docs/engage/audiences/computed-traits/) Use the Engage drag-and-drop interface to build per-user (B2C) or per-account (B2B) metrics on user profiles (for example, “lifetime value” or “lead score”). - [**SQL Traits:**](/docs/engage/audiences/sql-traits/) Run custom queries on your data warehouse using the Engage SQL editor, and import the results into Segment. With SQL Traits, you can pull rich, uncaptured user data back into Segment. -- [**Predictive Traits (Beta)**:](/docs/engage/audiences/predictive-traits/) Predict the likelihood that users will perform custom events tracked in Segment, like LTV, churn, and purchase. +- [**Predictive Traits (Beta)**:](/docs/unify/traits/predictive-traits/) Predict the likelihood that users will perform custom events tracked in Segment, like LTV, churn, and purchase. #### Build Audiences Create lists of users or accounts that match specific criteria. For example, after creating an `inactive accounts` audience that lists paid accounts with no logins in 60 days, you can push the audience to your analytics tools or send an SMS, email, or WhatsApp campaign with Engage Channels. Learn more about [Engage audiences](/docs/engage/audiences/). diff --git a/src/engage/product-limits.md b/src/engage/product-limits.md index a0be628b6d..bab9a3575d 100644 --- a/src/engage/product-limits.md +++ b/src/engage/product-limits.md @@ -10,8 +10,10 @@ To provide consistent performance and reliability at scale, Segment enforces def To learn more about custom limits and upgrades, contact your dedicated Customer Success Manager or [friends@segment.com](mailto:friends@segment.com). +> info "" +> Beginning August 18, 2023, Segment has [updated product limits](/docs/unify/product-limits/) that apply to new Engage and Unify users. -## Default Limits +## Default limits | Name | limit | Details | | ------------------------------------------- | ----------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | @@ -46,6 +48,10 @@ To learn more about custom limits and upgrades, contact your dedicated Customer ## Journeys +> info "" +> These limits only apply to existing users who started with Engage prior to August 18, 2023. Visit Segment's updated Unify and Engage [limits](/docs/unify/product-limits/) to learn more. + + | Item | Limit description | Details | | --------------- | -------------------------------- | ---------------------------------------------------------------------------- | | Steps | 500 | The maximum number of steps per Journey. | @@ -55,6 +61,7 @@ To learn more about custom limits and upgrades, contact your dedicated Customer | Compute credits | Half a credit for each step (up to 250 compute credits) | Each step in a published Journey consumes half of one compute credit. | + ## Channels | Item | Limit description | Details | diff --git a/src/engage/audiences/computed-traits.md b/src/unify/Traits/computed-traits.md similarity index 92% rename from src/engage/audiences/computed-traits.md rename to src/unify/Traits/computed-traits.md index 8ca6e9aca0..88c55346bc 100644 --- a/src/engage/audiences/computed-traits.md +++ b/src/unify/Traits/computed-traits.md @@ -1,17 +1,20 @@ --- title: Computed Traits -plan: engage-foundations +plan: unify-plus redirect_from: - "/personas/computed-traits" + - "/engage/audiences/computed-traits" --- +> info "" +> Beginning August 18, 2023, new Unify Plus users can access Computed Traits in Unify. Computed Traits allow you to quickly create user or account-level calculations that Segment keeps up-to-date over time. These can be computations like the `total_num_orders` a customer has completed, the `lifetime_revenue` of a customer, the `most_frequent_user` to determine which user is most active in an account, or the `unique_visitors_count` to assess how many visitors from a single domain. These computations are based on your events and event properties that you are sending through Segment on the [page](/docs/connections/spec/page/) and [track](/docs/connections/spec/track) calls. ## Types of Computed Traits -Engage currently supports the following types of computed traits: +Segment currently supports the following types of computed traits: - [Types of Computed Traits](#types-of-computed-traits) - [Event Counter](#event-counter) - [Aggregation](#aggregation) @@ -153,7 +156,7 @@ The following operators are available. ## Connecting your Computed Trait to a Destination -Engage sends user-level computed Traits to destinations using the [Identify call](/docs/connections/spec/identify/) for user traits, or using the [Track call](/docs/connections/spec/track/) for event properties. Segment includes the trait value and property in the identify and track calls. +Segment sends user-level computed Traits to destinations using the [Identify call](/docs/connections/spec/identify/) for user traits, or using the [Track call](/docs/connections/spec/track/) for event properties. Segment includes the trait value and property in the identify and track calls. For example, the name of a computed trait is added to the user profile as a trait, and the trait's value is set to the value of the computed trait. Segment sends an identify or track call when the trait is computed, depending on the destination configuration. If a computed trait counts the number of times a user visits your pricing page, and the user visits your pricing page five times, Segment sends an identify call with the property `pricing_page_visits: 5`. @@ -166,20 +169,20 @@ For account-level computed traits, you have the option to send either a [group]( After you create a computed trait, use the Overview page to view a compute progress bar, current [status](/docs/engage/audiences#compute-statuses), number of users with the trait, connected destinations, and more. For real-time traits, click **Refresh Trait** to update the current number of users with the trait. > info "Viewing compute progress" -> When you create a real-time computed trait, you'll see a progress bar, computed percentage, and status updates. For existing traits that you edit, Engage displays the compute status but not the progress bar or percentage. +> When you create a real-time computed trait, you'll see a progress bar, computed percentage, and status updates. For existing traits that you edit, Segment displays the compute status but not the progress bar or percentage. ## Editing Realtime Traits -Engage supports the editing of real-time Traits, which allows you to make nuanced changes to existing Traits in situations where cloning or building from scratch may not suit your use case. +Segment supports the editing of real-time Traits, which allows you to make nuanced changes to existing Traits in situations where cloning or building from scratch may not suit your use case. To edit a real-time Trait, follow these steps: -1. In your Engage Space, select the **Computed Traits** tab. +1. In your Unify or Engage space, select the **Computed Traits** tab. 2. Select the realtime Trait you want to edit. 3. Select the **Builder** tab and make your edits. 4. Preview the results, then select **Save Computed Trait** to confirm your edits. -Engage then processes your Trait edits. While the edit task runs, the trait remains locked and you can't make further changes. Once Engage incorporates your changes, you'll be able to access your updated Trait. +Segment then processes your Trait edits. While the edit task runs, the trait remains locked and you can't make further changes. Once Segment incorporates your changes, you'll be able to access your updated Trait. > warning "" diff --git a/src/engage/audiences/predictive-traits/index.md b/src/unify/Traits/predictive-traits/index.md similarity index 94% rename from src/engage/audiences/predictive-traits/index.md rename to src/unify/Traits/predictive-traits/index.md index d8e270556f..e813208279 100644 --- a/src/engage/audiences/predictive-traits/index.md +++ b/src/unify/Traits/predictive-traits/index.md @@ -1,6 +1,8 @@ --- title: Predictive Traits -plan: engage-foundations +plan: unify-plus +redirect_from: + - "/engage/audiences/predictive-traits" --- Predictive Traits, Segment's artificial intelligence and machine learning feature, lets you predict the likelihood that users will perform any event tracked in Segment. @@ -21,7 +23,7 @@ To create a Predictive Trait, you'll first request access, then build a Predicti Follow these steps to access Predictive Trait: -1. Navigate to **Engage > Audiences > Computed Traits**. Select **Create computed trait**. +1. Navigate to **Engage > Audiences > Computed traits** or **Unify > Traits**. Select **Create computed trait**. 2. Select **Request Access** to access Predictive Traits. ### Build a Predictive Trait @@ -90,4 +92,4 @@ Predicted LTV has strict data requirements. Segment can only make predictions fo ## Use cases -For use cases and information on how Segment builds Predictive Traits, read [Using Predictive Traits](/docs/engage/audiences/predictive-traits/using-predictive-traits/). +For use cases and information on how Segment builds Predictive Traits, read [Using Predictive Traits](/docs/unify/traits/predictive-traits/using-predictive-traits/). diff --git a/src/engage/audiences/predictive-traits/suggested-predictive-audiences.md b/src/unify/Traits/predictive-traits/suggested-predictive-audiences.md similarity index 83% rename from src/engage/audiences/predictive-traits/suggested-predictive-audiences.md rename to src/unify/Traits/predictive-traits/suggested-predictive-audiences.md index d27376c300..41206182b2 100644 --- a/src/engage/audiences/predictive-traits/suggested-predictive-audiences.md +++ b/src/unify/Traits/predictive-traits/suggested-predictive-audiences.md @@ -1,6 +1,8 @@ --- title: Suggested Predictive Audiences -plan: engage-foundations +plan: unify-plus +redirect_from: + - "/engage/audiences/predictive-traits/suggested-predictive-audiences" --- Suggested Predictive Audiences can help you improve customer engagement, drive higher conversion rates, and reduce ad spend. @@ -11,7 +13,7 @@ This page explains what a Suggested Predictive Audience is, how to build a Sugge A Suggested Predictive Audience is an out-of-the-box Audience template driven by machine learning. -Segment offers [five templates](/docs/engage/audiences/predictive-traits/suggested-predictive-audiences/#suggested-predictive-audience-types) that are prebuilt with [Predictive Traits](/docs/engage/audiences/predictive-traits) like likelihood to purchase and lifetime predicted value. Selecting a template generates a Predictive Audience whose members you can engage in a number of ways: +Segment offers [five templates](/docs/unify/traits/predictive-traits/suggested-predictive-audiences/#suggested-predictive-audience-types) that are prebuilt with [Predictive Traits](/docs/unify/traits/predictive-traits) like likelihood to purchase and lifetime predicted value. Selecting a template generates a Predictive Audience whose members you can engage in a number of ways: - [Send an email or SMS campaign](/docs/engage/campaigns/) with a discount code - Promote a new product line with a drip campaign @@ -53,7 +55,7 @@ Engage offers five Suggested Predictive Audiences. The following table summarize Choose a **Ready to buy** Predictive Audience to target customers who show a high propensity to make a purchase. -Segment builds this Audience with the [Likelihood to Purchase Predictive Trait](/docs/engage/audiences/predictive-traits//#likelihood-to-purchase). Audience members show encouraging engagement and have a likelihood to buy in the top 20th percentile. +Segment builds this Audience with the [Likelihood to Purchase Predictive Trait](/docs/unify/traits/predictive-traits//#likelihood-to-purchase). Audience members show encouraging engagement and have a likelihood to buy in the top 20th percentile. #### Long shots @@ -65,7 +67,7 @@ Segment builds this Audience with the `Order Completed` event and `Likelihood to Choose a **High lifetime value** Predictive Audience to target customers that show a high predicted lifetime value. -Segment builds this Audience with the [Predicted LTV Predictive Trait](/docs/engage/audiences/predictive-traits//#predicted-lifetime-value). Audience members are in the top 10th percentile of predicted lifetime value and Segment expects that they'll spend the most over the next 90 days. +Segment builds this Audience with the [Predicted LTV Predictive Trait](/docs/unify/traits/predictive-traits//#predicted-lifetime-value). Audience members are in the top 10th percentile of predicted lifetime value and Segment expects that they'll spend the most over the next 90 days. #### Potential VIPs diff --git a/src/engage/audiences/predictive-traits/using-predictive-traits.md b/src/unify/Traits/predictive-traits/using-predictive-traits.md similarity index 97% rename from src/engage/audiences/predictive-traits/using-predictive-traits.md rename to src/unify/Traits/predictive-traits/using-predictive-traits.md index 8672880585..3cd55dedea 100644 --- a/src/engage/audiences/predictive-traits/using-predictive-traits.md +++ b/src/unify/Traits/predictive-traits/using-predictive-traits.md @@ -1,6 +1,8 @@ --- title: Using Predictive Traits -plan: engage-foundations +plan: unify-plus +redirect_from: + - "/engage/audiences/predictive-traits/using-predictive-traits" --- ## Working with Predictive Traits in Segment @@ -9,7 +11,7 @@ Segment creates Predictive Traits as Computed Traits, with scores saved to user Once you've selected a cohort, you can use Predictive Traits in concert with other Segment features: -- [Audiences](/docs/engage/audiences/), which you can create with Predictive Traits as a base. As part of Engage, Segment also offers prebuilt [Suggested Predictive Audiences](/docs/engage/audiences/predictive-traits/suggested-predictive-audiences/). +- [Audiences](/docs/engage/audiences/), which you can create with Predictive Traits as a base. As part of Engage, Segment also offers prebuilt [Suggested Predictive Audiences](/docs/unify/traits/predictive-traits/suggested-predictive-audiences/). - [Journeys](/docs/engage/journeys/); use Predictive Traits in Journeys to trigger [Engage marketing campaigns](/docs/engage/campaigns/) when users enter a high-percentage cohort, or send promotional material if a customer shows interest and has a high propensity to buy. - [Destinations](/docs/connections/destinations/); send your Predictive Traits downstream to [Warehouses](/docs/connections/storage/warehouses/), support systems, and ad platforms. @@ -22,7 +24,7 @@ Once Segment has generated your Prediction, you can access it in your Trait's ** The **Explore your prediction** section of the Prediction tab visualizes Prediction data and lets you create Audiences to target. An interactive chart displays a percentile cohort score that indicates the likelihood of users in each group to convert on your chosen goal. You can choose the top 20%, bottom 80%, or create custom ranges for specific use cases. You can then create an Audience from the group you've selected, letting you send efficient, targeted marketing campaigns within Journeys. You can also send your Prediction data to downstream Destinations. - + #### Model statistics The Predictions tab's **Understand your prediction** section provides insights into the performance of the underlying predictive model. This information helps you understand the data points that contribute to the prediction results. diff --git a/src/engage/audiences/sql-traits.md b/src/unify/Traits/sql-traits.md similarity index 97% rename from src/engage/audiences/sql-traits.md rename to src/unify/Traits/sql-traits.md index 16cdf61e08..0dbdd06aa0 100644 --- a/src/engage/audiences/sql-traits.md +++ b/src/unify/Traits/sql-traits.md @@ -1,11 +1,16 @@ --- title: SQL Traits -plan: engage-foundations +plan: unify-plus redirect_from: - '/personas/sql-traits' + - '/engage/audiences/sql-traits' --- -Use SQL Traits to import user or account traits from your data warehouse back into Engage to build audiences or to enhance Segment data that you send to other Destinations. +> info "" +> Beginning August 18, 2023, new Unify Plus users can access SQL Traits in Unify. + + +Use SQL Traits to import user or account traits from your data warehouse back into Unify or Engage to build audiences or to enhance data that you send to other Destinations. SQL Traits are only limited by the data in your warehouse. Because anything you can write a query for can become a SQL Trait, you can add detail to your user and account profiles, resulting in more nuanced personalization. @@ -60,8 +65,8 @@ This query computes whether a user has an open ticket: To use SQL Traits, you need the following: - a warehouse connected to Segment -- an Engage Segment workspace -- a user account with access to Engage in that workspace +- a Segment workspace +- a user account with access to Unify in that workspace ### Step 1. Set up a warehouse source diff --git a/src/engage/images/explore_prediction.png b/src/unify/images/explore_prediction.png similarity index 100% rename from src/engage/images/explore_prediction.png rename to src/unify/images/explore_prediction.png diff --git a/src/engage/images/trait_builder.png b/src/unify/images/trait_builder.png similarity index 100% rename from src/engage/images/trait_builder.png rename to src/unify/images/trait_builder.png diff --git a/src/engage/images/understand_prediction.png b/src/unify/images/understand_prediction.png similarity index 100% rename from src/engage/images/understand_prediction.png rename to src/unify/images/understand_prediction.png diff --git a/src/unify/index.md b/src/unify/index.md index 392f0e9fb4..3a2727173f 100644 --- a/src/unify/index.md +++ b/src/unify/index.md @@ -44,6 +44,13 @@ With the Profile explorer, you have a complete view of your customers. > info "" > If you're using Engage, use the Profile explorer to view audiences, traits, journey membership, and [subscription states](/docs/engage/user-subscriptions/) for email and phone numbers. +## Enrich profiles with traits +Add detail to user profiles with new traits and use them to power personalized marketing campaigns. You can add new traits to your user or account profiles in Unify using: + +- [**Computed Traits:**](/docs/unify/traits/computed-traits/) Use the Unify drag-and-drop interface to build per-user (B2C) or per-account (B2B) metrics on user profiles (for example, “lifetime value” or “lead score”). +- [**SQL Traits:**](/docs/unify/traits/sql-traits/) Run custom queries on your data warehouse using the Unify SQL editor, and import the results into Segment. With SQL Traits, you can pull rich, uncaptured user data back into Segment. +- [**Predictive Traits (Beta)**:](/docs/unify/traits/predictive-traits/) Predict the likelihood that users will perform custom events tracked in Segment, like LTV, churn, and purchase. + ## Profile API Use Segment's Profile API to programmatically access all traits stored for a user. This includes the `external_ids`, `traits`, and `events` that make up a customer's journey with your product. diff --git a/src/unify/product-limits.md b/src/unify/product-limits.md new file mode 100644 index 0000000000..b507f22907 --- /dev/null +++ b/src/unify/product-limits.md @@ -0,0 +1,83 @@ +--- +title: Unify Limits +plan: unify-plus +redirect_from: + - '/profiles/product-limits' + - '/unify/profile-api-limits' +--- + +> info "" +> Beginning August 18, 2023, new Unify Plus and Engage users can refer to this page for Segment's product limits. Existing users prior to this date can continue to refer to the Engage product limits [here](/docs/engage/product-limits/). + + +To provide consistent performance and reliability at scale, Segment enforces default use and rate limits within Unify. Most customers do not exceed these limits. + +To learn more about custom limits and upgrades, contact your dedicated Customer Success Manager or [friends@segment.com](mailto:friends@segment.com){:target="_blank"}. + +## Unify Plus limits + +Beginning August 18, 2023, new Unify Plus users will receive 50 Computed or SQL Traits and five AI Traits. In addition, new users will receive the following depending on your Engage plan: +- **Engage Foundations**: 100 Audiences and 75 Journey Steps +- **Engage Premier**: 125 Audiences and 100 Journey Steps + +Visit Segment's [pricing page](https://segment.com/pricing/){:target="_blank"} to learn more. + + +## Default limits + +| Name | limit | Details | +| ------------------------------------------- | ----------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Inbound Data Throughput | 1000 events per second | Total event stream from sources connected to Engage, including historical data replays. Segment may slow request processing once this limit is reached. | +| Outbound Downstream Destination Rate Limits | Reduced retries when failures exceed 1000 events per second | Outbound Destination requests may fail for reasons outside of Segment's control. For example, most Destinations enforce their own rate limits. As a result, Segment may deliver data faster than the Destination can accept.

When Destination requests fail, Segment tries to deliver the data again. However, if more than 1000 requests per second fail or if the failure rate exceeds 50% for over 72 hours, Segment may reduce additional delivery attempts until the failure condition resolves. | + + +## Audiences and Computed Traits + +| name | limit | Details | +| --------------------------------------------- | ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| Compute Concurrency | 5 concurrent audiences or computed traits | Segment computes five new audiences or computed traits at a time. Once the limit is reached, Segment queues additional computations until one of the five finishes computing. | +| Edit Concurrency | 2 concurrent audiences or computed traits | You can edit two concurrent audiences or computed traits at a time. Once the limit is reached, Segment queues and locks additional computations until one of the two finishes computing. | +| Compute Throughput | 10000 computations per second | Computations include any Track or Identify call that triggers an audience or computed trait re-computation. Once the limit is reached, Segment may slow audience processing. | +| Events Lookback History | 3 years | The period of time for which Segment stores audience and computed traits computation events. | +| Real-time to batch destination sync frequency | 2-3 hours | The frequency with which Segment syncs real-time audiences to batch destinations. | +| Event History | `1970-01-01` | Events with a timestamp less than `1970-01-01` aren't always ingested, which could impact audience backfills with event timestamps prior to this date. | +| Engage Data Ingest | 1x the data ingested into Connections | The amount of data transferred into the Compute Engine. | +| Audience Frequency Update | 1 per 8 hours | Audiences that require time windows, [funnels](/docs/engage/audiences/#funnel-audiences), [dynamic properties](/docs/engage/audiences/#dynamic-property-references), or [account-level membership](/docs/engage/audiences/#account-level-audiences) are processed on chronological schedules. Unless otherwise agreed upon, the audiences will compute at the limit set forth. | +| Event Properties (Computed Traits) | 10,000 | For Computed Traits that exceed this limit, Segment will not persist any new Event Properties and will drop new trait keys and corresponding values. | + + +## SQL Traits + + +| name | limit | Details | +| --------------------------- | -------------------------- | ------------------------------------------------------------------------------------------------------------ | +| SQL Traits | 25 | The number of SQL traits you can sync to your Space. | +| SQL Traits - Sync Frequency | customizable, up to hourly | The frequency with which Segment runs your SQL traits. Contact your account team to customize your schedule. | +| SQL Traits - Rows | 25 million | The number of rows each SQL trait can return. | +| SQL Traits - Columns | 25 | The number of columns each SQL trait can return. | + + +## Profile API + +| Name | limit | Details | +| ----------------------- | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Profile API Throughput | 100 requests per second | If requests exceed 100 per second, the Profile API returns HTTP Error `429 Too Many Requests`. | +| Events Lookback History | 14 days | The Profile API retrieves up to 14 days of a profile's historical events within a collection. This applies to Track events, not traits sent through Identify calls. | + + +## Identity + +| name | Limit | Details | +| ----------------- | ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Identity Merges | 100 merges | Engage supports up to 100 merges per profile in its identity graph. Merges occur when a common `external_id` joins two existing profiles. For example, if a user initiates a mobile session but then signs in through a web application, a common identifier like `user_id` will join the two user profiles. No additional merges will be added once the profile reaches this limit. Event resolution for the profile, however, will continue. | +| Identity Mappings | 1000 mappings | Engage supports up to 1000 mappings per profile in its identity graph. Mappings are external identifier values like a `user_id`, email, mobile advertising `id`, or any custom identifier. No additional mappings will be added once the profile reaches this limit. Event resolution for the profile, however, will continue. | +| Identify calls | 300 traits | Engage rejects Identify events with 300 or more traits. If your use case requires more than 300 traits, you can split the traits into multiple Identify calls. | + +### Unify ingestion limitations + +Unify will silently drop events if: +- The `groupId` has more than 500 characters. +- Events have more than 300 properties/traits. +- `messageId` is longer than 100 characters. +- The `groupId` is empty in a Group call or `context.groupId` is empty in a Track call. +