diff --git a/src/_data/catalog/destination_categories.yml b/src/_data/catalog/destination_categories.yml index 643b9105e5..f8a919c06e 100644 --- a/src/_data/catalog/destination_categories.yml +++ b/src/_data/catalog/destination_categories.yml @@ -1,5 +1,5 @@ # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT -# destination categories last updated 2025-04-16 +# destination categories last updated 2025-04-24 items: - display_name: A/B Testing slug: a-b-testing diff --git a/src/_data/catalog/destinations.yml b/src/_data/catalog/destinations.yml index 27ea7a85e2..96babbfd9a 100644 --- a/src/_data/catalog/destinations.yml +++ b/src/_data/catalog/destinations.yml @@ -1,5 +1,5 @@ # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT -# destination data last updated 2025-04-16 +# destination data last updated 2025-04-24 items: - id: 637e8d185e2dec264895ea89 display_name: 1Flow @@ -42463,115 +42463,6 @@ items: hidden: false presets: [] partnerOwned: false -- id: 58ae54dc70a3e552b95415f6 - display_name: Facebook Offline Conversions - name: Facebook Offline Conversions - slug: facebook-offline-conversions - hidden: false - endpoints: - - US - regions: - - us-west-2 - - eu-west-1 - url: connections/destinations/catalog/facebook-offline-conversions - previous_names: - - Facebook Offline Conversions - website: https://www.facebook.com/business/help/1782327938668950 - status: PUBLIC - categories: - - Advertising - logo: - url: https://cdn.filepicker.io/api/file/MjCkA4RSTm7BQMFAcy8N - mark: - url: https://cdn.filepicker.io/api/file/TP1ONlaTGaF8fjL5XWhI - methods: - track: true - identify: false - group: false - alias: false - screen: false - page: false - platforms: - browser: false - mobile: false - server: true - warehouse: false - cloudAppObject: false - linkedAudiences: false - components: - - code: >- - https://github.com/segmentio/integrations/tree/master/integrations/facebook-offline-conversions - type: SERVER - browserUnbundlingSupported: false - browserUnbundlingPublic: true - replay: false - connection_modes: - device: - web: false - mobile: false - server: false - cloud: - web: false - mobile: true - server: true - settings: - - name: completeRegistrations - type: text-map - defaultValue: {} - description: >- - Enter your Segment `.track()` event names on the left that you want to - send as `CompleteRegistration` conversions. On the right hand side, put - the ID of the Facebook Offline Event Set where you want to send these - conversions. - required: false - label: Map Track Events as CompleteRegistration Conversions to Event Set IDs - - name: events - type: text-map - defaultValue: {} - description: >- - Enter your Segment `.track()` event names on the left that you want to - send as conversions. On the right hand side, put the ID of the Facebook - Offline Event Set where you want to send these conversions. - required: false - label: Map Track Events to Event Set IDs - - name: leads - type: text-map - defaultValue: {} - description: >- - Enter your Segment `.track()` event names on the left that you want to - send as `Lead` conversions. On the right hand side, put the ID of the - Facebook Offline Event Set where you want to send these conversions. - required: false - label: Map Track Events as Lead Conversions to Event Set IDs - - name: limitedDataUse - type: boolean - defaultValue: false - description: >- - The Limited Data Use (LDU) setting controls whether or not Data Processing - Options are sent to Facebook. When enabling LDU, you **must** set the user - geography values in the `Facebook Offline Conversions` integration options - under the `dataProcessingOptions` key. If you do not pass specific - geography values, Segment will default to empty Data Processing Options. - required: false - label: Limited Data Use - - name: oauth - type: oauth - defaultValue: {} - description: 'Authorize Segment to oauth `` ' - required: false - label: oauth - - name: valueIdentifier - type: select - defaultValue: value - description: >- - For pre-purchase events such as `Product Viewed`, `Product Added`, and - `Product List Viewed`, choose which Segment property you would like to map - to Facebook's `value` property. - required: false - label: Value Field Identifier - actions: [] - presets: [] - partnerOwned: false - id: 5661eb58e954a874ca44cc07 display_name: Facebook Pixel name: Facebook Pixel @@ -90228,7 +90119,7 @@ items: hidden: false defaultTrigger: type = "identify" fields: - - id: gaoUZPQZpURjeHcjj7mALm + - id: sWtUU45JDUQZ5FCL92HJ8C sortOrder: 0 fieldKey: user_identifiers label: User identifiers @@ -90256,12 +90147,16 @@ items: '@path': $.properties.optimizely_vuid else: '@path': $.traits.optimizely_vuid + fs_user_id: + '@path': $.userId + web_user_id: + '@path': $.userId required: true multiple: false choices: null dynamic: false allowNull: false - - id: xw1ikonZfaWKAjdatV2xv + - id: kgdLx9q7Jq1t8VM4LPDiWJ sortOrder: 1 fieldKey: company label: Company Name @@ -90275,7 +90170,7 @@ items: choices: null dynamic: false allowNull: false - - id: fMjdXqJDHsT4rfrRt8tESH + - id: 4bYsSx3pXPHvsMxRPv51f1 sortOrder: 2 fieldKey: title label: Title @@ -90289,7 +90184,7 @@ items: choices: null dynamic: false allowNull: false - - id: iybbwS7cUeZfWeBWf285xV + - id: eqjC7oBPuB6xaXCUfRGju1 sortOrder: 3 fieldKey: name label: Name @@ -90303,7 +90198,7 @@ items: choices: null dynamic: false allowNull: false - - id: jQQuEDs5didv1HvgJ4uLU6 + - id: 9wBFCgQFsSJUZzHSxc2qF9 sortOrder: 4 fieldKey: firstname label: First Name @@ -90317,7 +90212,7 @@ items: choices: null dynamic: false allowNull: false - - id: 212jp4XFL3FnzzTZoufV7E + - id: x6k4L2itAPMrFsbUfxgHuB sortOrder: 5 fieldKey: lastname label: Last Name @@ -90331,7 +90226,7 @@ items: choices: null dynamic: false allowNull: false - - id: aJG9xokgqjjg1EeC9nwocS + - id: e3uzYhjnjfpqprzUpQyc1a sortOrder: 6 fieldKey: gender label: Gender @@ -90345,7 +90240,7 @@ items: choices: null dynamic: false allowNull: false - - id: piPkDaZDvsNvxmXNn2ebcc + - id: 23w7GDVXndkJ2Qi5ovCF2s sortOrder: 7 fieldKey: DOB label: Birthday @@ -90359,7 +90254,7 @@ items: choices: null dynamic: false allowNull: false - - id: sqYqZHz4KbKwfqDRyjZALQ + - id: tjju6UnfFpRaEsW5LduNE2 sortOrder: 8 fieldKey: phone label: Phone @@ -90373,7 +90268,7 @@ items: choices: null dynamic: false allowNull: false - - id: msHxKMpN3tcXpwduiBDnPp + - id: rXpqNfQt3UucQnc57HA7jP sortOrder: 9 fieldKey: age label: Age @@ -90387,7 +90282,7 @@ items: choices: null dynamic: false allowNull: false - - id: 5qM5kK9b9d8ZnUV26RPXZC + - id: 9pGCjbJ2CjzBdkzWaihLiv sortOrder: 10 fieldKey: address label: Address @@ -90410,7 +90305,7 @@ items: choices: null dynamic: false allowNull: false - - id: jhJfvsfEGTGZzEC6dpdRZK + - id: 5tDd9irhQKJGCWVb1WZF1z sortOrder: 11 fieldKey: avatar label: avatar @@ -90424,7 +90319,7 @@ items: choices: null dynamic: false allowNull: false - - id: uc5tzWoN6FeAq2hgAovLFo + - id: 5vfbfoGi34VxHjy9WVEK7L sortOrder: 12 fieldKey: additional_traits label: Addition User Traits @@ -90444,7 +90339,7 @@ items: hidden: false defaultTrigger: null fields: - - id: iff8iAHVoS5CExhSuge4ZQ + - id: ty3D3VLGGD3X5UYLTZ764e sortOrder: 0 fieldKey: user_identifiers label: User identifiers @@ -90472,12 +90367,16 @@ items: '@path': $.properties.optimizely_vuid else: '@path': $.context.traits.optimizely_vuid + fs_user_id: + '@path': $.userId + web_user_id: + '@path': $.userId required: true multiple: false choices: null dynamic: false allowNull: false - - id: 8f4YNXHK5CtFnCUnvGV6Q9 + - id: tHij7D1fg8H3KUuC6hqFf sortOrder: 1 fieldKey: event_action label: Optimizely Event Action @@ -90489,7 +90388,7 @@ items: choices: null dynamic: false allowNull: false - - id: xg2H1RYJ2FiHTfPYkzStjL + - id: aWDvskPwGeqZPdD7HCkNDg sortOrder: 2 fieldKey: campaign label: Campaign Name @@ -90503,7 +90402,7 @@ items: choices: null dynamic: false allowNull: false - - id: sJaWbY1CPvCm3eYW86zSQL + - id: rFyE5wvxoYHdxSYoCde5bp sortOrder: 3 fieldKey: campaign_id label: Campaign ID @@ -90517,7 +90416,7 @@ items: choices: null dynamic: false allowNull: false - - id: if66b7vsHktLPQSYbhR5ca + - id: qJb5GuwUGmc7RYQErzSBjy sortOrder: 4 fieldKey: link_url label: Link URL @@ -90531,7 +90430,7 @@ items: choices: null dynamic: false allowNull: false - - id: 4tBBsWt6KutdAoKM4rr2jk + - id: 8SsyoKcvYqJBH1AuGps1AP sortOrder: 5 fieldKey: timestamp label: Timestamp @@ -90553,7 +90452,7 @@ items: hidden: false defaultTrigger: null fields: - - id: 7oERk4PHbNESX5V4irBxUW + - id: 5ByVEAaN4d1UdTGSyBN81f sortOrder: 0 fieldKey: user_identifiers label: User identifiers @@ -90581,12 +90480,16 @@ items: '@path': $.properties.optimizely_vuid else: '@path': $.traits.optimizely_vuid + fs_user_id: + '@path': $.userId + web_user_id: + '@path': $.userId required: true multiple: false choices: null dynamic: false allowNull: false - - id: bEjPGknXCxxyQbcYQFYA93 + - id: ADTWeEnk85sTSCZuZXwD4 sortOrder: 1 fieldKey: event_type label: Optimizely Event Type @@ -90600,7 +90503,7 @@ items: choices: null dynamic: false allowNull: false - - id: u3z41Dt5qHkuJEoA9mS4r8 + - id: qbTEuuwM5CBve8L5gvi2Fq sortOrder: 2 fieldKey: event_action label: Optimizely Event Action @@ -90612,7 +90515,7 @@ items: choices: null dynamic: false allowNull: false - - id: bb6d3kFwvzX225Sqhjwkjy + - id: seCKLjbxhZqiqPkQxrVKNy sortOrder: 3 fieldKey: products label: Product details @@ -90633,7 +90536,7 @@ items: choices: null dynamic: false allowNull: false - - id: wpTXtX1NZbkZTtDpd4CdNm + - id: e1iyvMzZCRFy5ohAAWuct5 sortOrder: 4 fieldKey: order_id label: Order ID @@ -90647,7 +90550,7 @@ items: choices: null dynamic: false allowNull: false - - id: deZWVgeJdUbxALrawUmG5j + - id: mgYJ1HGrftbYTHbFrZmt3R sortOrder: 5 fieldKey: total label: Order Total @@ -90661,7 +90564,7 @@ items: choices: null dynamic: false allowNull: false - - id: 5kxuyG37oHoBxFCpvgDVpG + - id: rFy9rXhHvhMYWs31Hy2mYa sortOrder: 6 fieldKey: timestamp label: Timestamp @@ -90683,7 +90586,7 @@ items: hidden: false defaultTrigger: null fields: - - id: 9SvrqpiESGuWqLFVfNzHob + - id: heW1fP9ZggtrUhZeNEuYmk sortOrder: 0 fieldKey: user_identifiers label: User identifiers @@ -90711,12 +90614,16 @@ items: '@path': $.properties.optimizely_vuid else: '@path': $.traits.optimizely_vuid + fs_user_id: + '@path': $.userId + web_user_id: + '@path': $.userId required: true multiple: false choices: null dynamic: false allowNull: false - - id: wmufL5LBhvXk8pZoEeQP7z + - id: jeRXqeaks1TxHfM57n1jPg sortOrder: 1 fieldKey: event_type label: Optimizely Event Type @@ -90730,7 +90637,7 @@ items: choices: null dynamic: false allowNull: false - - id: 44BrCsz1Jiq6Tp8GF74euQ + - id: izuwbaiu8g9Vfu39ka9xU6 sortOrder: 2 fieldKey: event_action label: Optimizely Event Action @@ -90742,7 +90649,7 @@ items: choices: null dynamic: false allowNull: false - - id: 9egos4J7DtbQTaLTwdgPoU + - id: k2QWpArvTsnuDwkJGrkod4 sortOrder: 3 fieldKey: data label: Event Properties @@ -90756,7 +90663,7 @@ items: choices: null dynamic: false allowNull: false - - id: obpagJcURrkD7AdJgNhboT + - id: 9Z927KoQweF4eR81mURyPG sortOrder: 4 fieldKey: timestamp label: Timestamp @@ -90772,7 +90679,7 @@ items: allowNull: false presets: - actionId: hcqEnue2U8oG3e3iVHW5KV - name: Unsubscribed + name: Email Link Clicked fields: user_identifiers: anonymousId: @@ -90795,6 +90702,10 @@ items: '@path': $.properties.optimizely_vuid else: '@path': $.context.traits.optimizely_vuid + fs_user_id: + '@path': $.userId + web_user_id: + '@path': $.userId campaign: '@path': $.properties.campaign_name campaign_id: @@ -90805,52 +90716,10 @@ items: '@path': $.timestamp enable_batching: true batch_size: 100 - event_action: unsubscribe - trigger: type = "track" and event = "Unsubscribed" - - actionId: meD4xgcJ8b3f29gWudiuFQ - name: Order Completed - fields: - user_identifiers: - anonymousId: - '@path': $.anonymousId - userId: - '@path': $.userId - email: - '@if': - exists: - '@path': $.properties.email - then: - '@path': $.properties.email - else: - '@path': $.traits.email - optimizely_vuid: - '@if': - exists: - '@path': $.properties.optimizely_vuid - then: - '@path': $.properties.optimizely_vuid - else: - '@path': $.traits.optimizely_vuid - event_type: order - products: - '@arrayPath': - - $.properties.products - - product_id: - '@path': $.product_id - qty: - '@path': $.quantity - order_id: - '@path': $.properties.order_id - total: - '@path': $.properties.total - timestamp: - '@path': $.timestamp - enable_batching: true - batch_size: 100 - event_action: purchase - trigger: type = "track" and event = "Order Completed" + event_action: click + trigger: type = "track" and event = "Email Link Clicked" - actionId: hcqEnue2U8oG3e3iVHW5KV - name: Email Sent + name: Email Opened fields: user_identifiers: anonymousId: @@ -90873,6 +90742,10 @@ items: '@path': $.properties.optimizely_vuid else: '@path': $.context.traits.optimizely_vuid + fs_user_id: + '@path': $.userId + web_user_id: + '@path': $.userId campaign: '@path': $.properties.campaign_name campaign_id: @@ -90883,8 +90756,8 @@ items: '@path': $.timestamp enable_batching: true batch_size: 100 - event_action: sent - trigger: type = "track" and event = "Email Sent" + event_action: open + trigger: type = "track" and event = "Email Opened" - actionId: meD4xgcJ8b3f29gWudiuFQ name: Product Added fields: @@ -90909,6 +90782,10 @@ items: '@path': $.properties.optimizely_vuid else: '@path': $.traits.optimizely_vuid + fs_user_id: + '@path': $.userId + web_user_id: + '@path': $.userId event_type: product products: '@arrayPath': @@ -90928,7 +90805,7 @@ items: event_action: add_to_cart trigger: type = "track" and event = "Product Added" - actionId: meD4xgcJ8b3f29gWudiuFQ - name: Product Viewed + name: Order Completed fields: user_identifiers: anonymousId: @@ -90951,10 +90828,14 @@ items: '@path': $.properties.optimizely_vuid else: '@path': $.traits.optimizely_vuid - event_type: product + fs_user_id: + '@path': $.userId + web_user_id: + '@path': $.userId + event_type: order products: '@arrayPath': - - $.properties + - $.properties.products - product_id: '@path': $.product_id qty: @@ -90967,10 +90848,10 @@ items: '@path': $.timestamp enable_batching: true batch_size: 100 - event_action: detail - trigger: type = "track" and event = "Product Viewed" + event_action: purchase + trigger: type = "track" and event = "Order Completed" - actionId: hcqEnue2U8oG3e3iVHW5KV - name: Email Marked as Spam + name: Email Sent fields: user_identifiers: anonymousId: @@ -90993,6 +90874,10 @@ items: '@path': $.properties.optimizely_vuid else: '@path': $.context.traits.optimizely_vuid + fs_user_id: + '@path': $.userId + web_user_id: + '@path': $.userId campaign: '@path': $.properties.campaign_name campaign_id: @@ -91003,8 +90888,8 @@ items: '@path': $.timestamp enable_batching: true batch_size: 100 - event_action: spam_report - trigger: type = "track" and event = "Email Marked as Spam" + event_action: sent + trigger: type = "track" and event = "Email Sent" - actionId: meD4xgcJ8b3f29gWudiuFQ name: Product Removed fields: @@ -91029,6 +90914,10 @@ items: '@path': $.properties.optimizely_vuid else: '@path': $.traits.optimizely_vuid + fs_user_id: + '@path': $.userId + web_user_id: + '@path': $.userId event_type: product products: '@arrayPath': @@ -91048,7 +90937,7 @@ items: event_action: remove_from_cart trigger: type = "track" and event = "Product Removed" - actionId: hcqEnue2U8oG3e3iVHW5KV - name: Email Link Clicked + name: Email Marked as Spam fields: user_identifiers: anonymousId: @@ -91071,6 +90960,10 @@ items: '@path': $.properties.optimizely_vuid else: '@path': $.context.traits.optimizely_vuid + fs_user_id: + '@path': $.userId + web_user_id: + '@path': $.userId campaign: '@path': $.properties.campaign_name campaign_id: @@ -91081,10 +90974,56 @@ items: '@path': $.timestamp enable_batching: true batch_size: 100 - event_action: click - trigger: type = "track" and event = "Email Link Clicked" + event_action: spam_report + trigger: type = "track" and event = "Email Marked as Spam" + - actionId: meD4xgcJ8b3f29gWudiuFQ + name: Product Viewed + fields: + user_identifiers: + anonymousId: + '@path': $.anonymousId + userId: + '@path': $.userId + email: + '@if': + exists: + '@path': $.properties.email + then: + '@path': $.properties.email + else: + '@path': $.traits.email + optimizely_vuid: + '@if': + exists: + '@path': $.properties.optimizely_vuid + then: + '@path': $.properties.optimizely_vuid + else: + '@path': $.traits.optimizely_vuid + fs_user_id: + '@path': $.userId + web_user_id: + '@path': $.userId + event_type: product + products: + '@arrayPath': + - $.properties + - product_id: + '@path': $.product_id + qty: + '@path': $.quantity + order_id: + '@path': $.properties.order_id + total: + '@path': $.properties.total + timestamp: + '@path': $.timestamp + enable_batching: true + batch_size: 100 + event_action: detail + trigger: type = "track" and event = "Product Viewed" - actionId: hcqEnue2U8oG3e3iVHW5KV - name: Email Opened + name: Unsubscribed fields: user_identifiers: anonymousId: @@ -91107,6 +91046,10 @@ items: '@path': $.properties.optimizely_vuid else: '@path': $.context.traits.optimizely_vuid + fs_user_id: + '@path': $.userId + web_user_id: + '@path': $.userId campaign: '@path': $.properties.campaign_name campaign_id: @@ -91117,8 +91060,8 @@ items: '@path': $.timestamp enable_batching: true batch_size: 100 - event_action: open - trigger: type = "track" and event = "Email Opened" + event_action: unsubscribe + trigger: type = "track" and event = "Unsubscribed" partnerOwned: true - id: 641d5acea88fa531b9068608 display_name: Optimizely Feature Experimentation (Actions) @@ -111327,7 +111270,7 @@ items: regions: - us-west-2 - eu-west-1 - url: connections/destinations/catalog/sendgrid + url: connections/destinations/catalog/actions-sendgrid previous_names: - Sendgrid Marketing Campaigns - SendGrid Marketing Campaigns diff --git a/src/_data/catalog/destinations_private.yml b/src/_data/catalog/destinations_private.yml index 321738d13b..98f8b93312 100644 --- a/src/_data/catalog/destinations_private.yml +++ b/src/_data/catalog/destinations_private.yml @@ -1,5 +1,5 @@ # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT -# destination data last updated 2025-04-16 +# destination data last updated 2025-04-24 items: - id: 54521fd925e721e32a72eee1 display_name: Pardot diff --git a/src/_data/catalog/source_categories.yml b/src/_data/catalog/source_categories.yml index 9f2655d02f..19058f5719 100644 --- a/src/_data/catalog/source_categories.yml +++ b/src/_data/catalog/source_categories.yml @@ -1,5 +1,5 @@ # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT -# source categories last updated 2025-04-16 +# source categories last updated 2025-04-24 items: - display_name: A/B Testing slug: a-b-testing diff --git a/src/_data/catalog/sources.yml b/src/_data/catalog/sources.yml index d99cc6d0ff..cbb8203ced 100644 --- a/src/_data/catalog/sources.yml +++ b/src/_data/catalog/sources.yml @@ -1,5 +1,5 @@ # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT -# sources last updated 2025-04-16 +# sources last updated 2025-04-24 items: - id: 8HWbgPTt3k display_name: .NET diff --git a/src/connections/auto-instrumentation/configuration.md b/src/connections/auto-instrumentation/configuration.md index cb1e143e5c..d0a9c7b6db 100644 --- a/src/connections/auto-instrumentation/configuration.md +++ b/src/connections/auto-instrumentation/configuration.md @@ -26,6 +26,9 @@ After you set up the Signals SDK to capture the signals you want to target, you 1. In your Segment workspace, go to to **Connections > Auto-Instrumentation** and click on a source. 2. Click **Create Rules**. +> info "Where's the Event Builder tab?" +> The Event Builder tab only appears after you've installed the Auto-Instrumentation snippet in your site or app. If you don’t see the tab, double check your implementation or reach out to your Segment CSM. + ### Using the Rules Editor The Rules Editor is where you define rules that transform raw signal data into analytics events. In the editor, you write functions that convert signals into events and then call them in the `processSignal()` function. diff --git a/src/connections/auto-instrumentation/event-builder.md b/src/connections/auto-instrumentation/event-builder.md new file mode 100644 index 0000000000..c52f14a8de --- /dev/null +++ b/src/connections/auto-instrumentation/event-builder.md @@ -0,0 +1,89 @@ +--- +title: Auto-Instrumentation Event Builder +hidden: true +--- + +The Event Builder provides a no-code way to define analytics events based on signals collected by Auto-Instrumentation. + +You can use it to create Track, Identify, Page, and other event types directly from your Segment workspace. + +> info "Auto-Instrumentation Private Beta" +> Auto-Instrumentation is currently in Private Beta and is governed by Segment's [First Access and Beta Preview Terms](https://www.twilio.com/en-us/legal/tos){:target="_blank"}. Segment is actively iterating on and improving the Auto-Instrumentation user experience. + +## Access the Event Builder + +The Event Builder appears as a tab within each source, next to the Debugger. If you don't see the Event Builder tab, first confirm that you've installed the required Auto-Instrumentation SDK. + +If you've installed the SDK but still don't see the Event Builder tab, reach out to your Segment account manager to verify your workspace is included in the Auto-Instrumentation Private Beta. + +![The Event Builder tab shown in the navigation bar between Debugger and Schema in a Segment source](images/event_builder_tab.png) + +> info "Event Builder during Private Beta" +> During Private Beta, both the Event Builder and the legacy Auto-Instrumentation tab appear in the navigation. Segment will remove the legacy tab once all customers have migrated to the Event Builder experience. + +## Generate activity + +To populate the Event Builder with signals, you first need to open your website or app with a special query parameter that enables signal detection. + +1. Visit your site or app in a browser, and add `?segment_signals_debug=true` to the end of the URL. + For example: `https://www.your-website.com?segment_signals_debug=true`. +2. Interact with your app as a user would: click buttons, navigate between pages or screens, submit forms, and so on. +3. Return to the Event Builder tab in Segment to view the signals being collected in real time. + + +![Prompt in the Event Builder showing how to start detecting activity by visiting the website with a debug query parameter and interacting with the app](images/detecting_activity.png) + +> info "Enable signal detection" +> Segment only detects signals when you access your site using the `?segment_signals_debug=true` query parameter. If you visit your site without it, signals won't show up in the Event Builder. + +Segment collects and displays activity as signals. These signals are grouped into types, like: + +- Interaction: clicks, taps, and UI interactions. +- Navigation: screen changes and page transitions +- Network: requests and responses +- `LocalData`, Instrumentation, and `UserDefined`: additional signal types from the SDK. + +### How signals relate to events + +Segment separates signal collection from event creation. Signals represent raw user interactions, like a button click or screen view. Events, on the other hand, are analytics calls you define based on those signals. This two-step process lets you observe user behavior first, and then decide how and when to turn that behavior into structured analytics events, without needing to modify your code. + +Signal detection is active for 24 hours after you generate activity. Detected signals are available in the Event Builder for 72 hours. + +## Create an event + +You can create events by selecting individual signals or combining multiple signals in sequence. + +Follow these steps to create an event: + +1. Find the signal you want to use and click **Configure event**. +2. Add one or more conditions. The order matters; Segment evaluates them in the order you add them. + - For example, to track a successful login, first select a **button click** signal, then the **network response** signal. +3. Select properties from the signal(s) to include in your event. +4. Map those properties to your targeted Segment event fields. +5. Name your event. This name will appear in the Debugger and downstream tools. +6. Click **Publish event rules** to activate the event in your workspace. + - You must publish each rule before Segment starts collecting data for the event. + +For example, suppose a user taps an "Add to Cart" button. You can define an `Add to Cart` event by combining the button click signal with a network response signal that includes product details. You can then map properties like product name, ID, and price directly from the network response to your event. + +Once published, your event rules appear in the **Event Rules** tab of the Event Builder. From this tab, you can view all of your published rules and delete rules you no longer need. + +![The Event Rules tab shown in the Event Builder, showing six custom rules, categorized by event type](images/event_rules.png) + +## Choose an event type + +When you define an event in the Event Builder, you assign it a type that determines how Segment and your connected destinations process it. These event types (Track, Identify, Page, and Screen) follow the same structure and behavior defined in the [Segment Spec](/docs/connections/spec/). + +| Event type | Description | +| ---------- | ----------------------------------------------------------------------------------------------------------- | +| Track | Custom event tracking. Use this for user actions like `Product Viewed`, `Add to Cart`, or `Signup Started`. | +| Identify | User identification. Use this to associate traits (like `email`, `userId`, or `plan`) with a known user. | +| Page | Web page view tracking. Use this to record visits to pages on your website. | +| Screen | Mobile screen view tracking. Use this to record views of screens in your mobile app. | + +For example, to track a login flow, you might define an Identify event that maps traits like `userId` and `email` from a network response signal. To track cart activity, you could define a Track event like `Checkout Started` with properties like cart value, item count, and currency. + +Segment uses the event name and any mapped properties to format each event according to the Segment Spec. Events you create in the Event Builder behave the same way as events sent through Segment SDKs or APIs. + +> info "Event type behavior in destinations" +> While Segment handles these event types consistently, downstream tools may treat them differently. For example, Identify events often update user profiles, while Page or Screen events may be handled as pageviews instead of custom events. \ No newline at end of file diff --git a/src/connections/auto-instrumentation/images/detecting_activity.png b/src/connections/auto-instrumentation/images/detecting_activity.png new file mode 100644 index 0000000000..daa6774561 Binary files /dev/null and b/src/connections/auto-instrumentation/images/detecting_activity.png differ diff --git a/src/connections/auto-instrumentation/images/event_builder_tab.png b/src/connections/auto-instrumentation/images/event_builder_tab.png new file mode 100644 index 0000000000..8de6f6e78f Binary files /dev/null and b/src/connections/auto-instrumentation/images/event_builder_tab.png differ diff --git a/src/connections/auto-instrumentation/images/event_rules.png b/src/connections/auto-instrumentation/images/event_rules.png new file mode 100644 index 0000000000..98000b46f2 Binary files /dev/null and b/src/connections/auto-instrumentation/images/event_rules.png differ diff --git a/src/connections/auto-instrumentation/index.md b/src/connections/auto-instrumentation/index.md index 5045ffa336..28e0b014aa 100644 --- a/src/connections/auto-instrumentation/index.md +++ b/src/connections/auto-instrumentation/index.md @@ -24,35 +24,36 @@ redirect_from: - '/docs/connections/auto-instrumentation/setup/' --- -Auto-Instrumentation simplifies tracking in your websites and apps by eliminating the need for a traditional Segment instrumentation. +Auto-Instrumentation simplifies tracking in your websites and apps by removing the need for a traditional Segment instrumentation. -> info "Auto-Instrumentation Pilot" -> Auto-Instrumentation is currently in pilot and is governed by Segment's [First Access and Beta Preview Terms](https://www.twilio.com/en-us/legal/tos){:target="_blank"}. Segment is actively iterating on and improving the Auto-Instrumentation user experience. +> info "Auto-Instrumentation Private Beta" +> Auto-Instrumentation is currently in private beta and is governed by Segment's [First Access and Beta Preview Terms](https://www.twilio.com/en-us/legal/tos){:target="_blank"}. Segment is actively iterating on and improving the Auto-Instrumentation user experience. > success "Enable Auto-Instrumentation in your workspace" > To enable Auto-Instrumentation in your Segment workspace, reach out to your dedicated account manager. ## Background -Gathering actionable and timely data is crucial to the success of your business. However, collecting this data in real time has historically proven to be challenging. - -As your business needs change, keeping instrumentation up-to-date across all of your digital properties can be time-consuming, often taking weeks or months. This delay can lead to lost insights, frustration for your marketers and developers, and open-ended support of your Segment instrumentation. +Collecting high-quality analytics data is essential, but traditional tracking setups often fall behind as business needs change. Instrumentation updates can take weeks or months, and these delays reduce visibility and increase the burden on engineering teams. ## Auto-Instrumentation as a solution With just a few lines of code, Auto-Instrumentation handles device tracking for you, helping you focus on collecting the data that's essential to your business and letting your marketers and data analysts gather and update data without relying on engineering teams. -Some Auto-Instrumentation advantages include: +Key Auto-Instrumentation benefits include: + +- **No-code event creation**: Use the Event Builder tab to define events based on user activity; no JavaScript required. +- **Fast iteration**: Update your tracking configuration at any time, without deploying new app versions. +- **Fewer dependencies**: Reduce the need for engineering support while still maintaining reliable event tracking. -- **JavaScript-based instrumentation logic**: Configure and refine your instrumentation logic entirely within JavaScript, simplifying the development process and reducing dependencies on other environments. -- **Rapid iteration**: Update your instrumentation logic without the need to constantly release new versions of your mobile app, enabling faster iterations and improvements. -- **Bypass update delays**: Avoid the typical delays associated with app update cycles and app store approvals. Auto-Instrumentation lets you update your tracking setups or fix errors immediately, ensuring your data collection remains accurate and timely. +> info "Event Builder during Private Beta" +> During the Auto-Instrumentation Private Beta, both the Event Builder and the legacy Auto-Instrumentation tab appear in the Segment UI. Segment will remove the legacy tab once all customers have migrated to the Event Builder experience. ## How it works -Once you integrate the Analytics SDK and Signals SDK into your website or application, Segment begins to passively monitor user activity like button clicks, page navigation, and network data. Segment captures these events as "signals" and sends them to your Auto-Instrumentation source in real time. +After you install the required SDKs and enable Auto-Instrumentation, Segment detects activity like button clicks, navigation, and network calls. Segment captures these events as signals, which appear in the Event Builder. -In Segment, the Auto-Instrumentation source lets you view raw signals. You can then [use this data to create detailed analytics events](/docs/connections/auto-instrumentation/configuration/) based on those signals, enriching your insights into user behavior and application performance. +You can group signals into complete analytics events, assign names, and map custom properties. You can then [use this data to create detailed analytics events](/docs/connections/auto-instrumentation/configuration/) based on those signals, enriching your insights into user behavior and application performance. ## Setup Guides diff --git a/src/connections/auto-instrumentation/kotlin-setup.md b/src/connections/auto-instrumentation/kotlin-setup.md index b2c44a6f86..acb8f587e9 100644 --- a/src/connections/auto-instrumentation/kotlin-setup.md +++ b/src/connections/auto-instrumentation/kotlin-setup.md @@ -79,18 +79,15 @@ Next, you'll need to add the Signals SDKs to your Kotlin application. ## Step 3: Verify and deploy events -Next, you'll need to verify signal emission and [create rules](/docs/connections/auto-instrumentation/configuration/#example-rule-implementations) to convert those signals into events: - -1. In your Segment workspace, return to **Connections > Auto-Instrumentation** and click on the new source you created. -2. Verify that signals appear as expected on the dashboard. - - ![Signals successfully appearing in the Segment UI](images/autoinstrumentation_signals.png "Signals successfully appearing in the Segment UI") - -3. Click **Create Rules**. -4. In the Rules Editor, add a rule that converts signal data into an event. -5. Click **Preview**, then click **Save & Deploy**. - -Segment displays `Rule updated successfully` to verify that it saved your rule. +After integrating the SDK and running your app, verify that Segment is collecting signals: + +1. In your Segment workspace, go to **Connections > Sources** and select the source you created for Auto-Instrumentation. +2. In the source overview, look for the **Event Builder** tab. If the tab doesn’t appear: + - Make sure you've installed the SDK correctly. + - Reach out to your Segment CSM to confirm that your workspace has the necessary feature flags enabled. +3. Launch your app [in debug mode](https://github.com/segmentio/analytics-next/tree/master/packages/signals/signals#sending-and-viewing-signals-on-segmentcom-debug-mode){:target="_blank"}, for example, by running the app from Android Studio on a simulator or test device. This enables signal collection so you can see activity in the Event Builder. +4. Use the app as a user would: navigate between screens, tap buttons, trigger network requests. Signals appear in real time as you interact with the app. +5. In the Event Builder, find a signal and click **Configure event** to define a new event. After configuring the event, click **Publish event rules**. ## Configuration Options diff --git a/src/connections/auto-instrumentation/swift-setup.md b/src/connections/auto-instrumentation/swift-setup.md index 62fc46572a..78bbbc2327 100644 --- a/src/connections/auto-instrumentation/swift-setup.md +++ b/src/connections/auto-instrumentation/swift-setup.md @@ -77,18 +77,15 @@ typealias SecureField = SignalSecureField ``` ## Step 3: Verify and deploy events -Next, you'll need to verify signal emission and [create rules](/docs/connections/auto-instrumentation/configuration/#example-rule-implementations) to convert those signals into events: - -1. In your Segment workspace, return to **Connections > Auto-Instrumentation** and click on the new source you created. -2. Verify that signals appear as expected on the dashboard. - - ![Signals successfully appearing in the Segment UI](images/autoinstrumentation_signals.png "Signals successfully appearing in the Segment UI") - -3. Click **Create Rules**. -4. In the Rules Editor, add a rule that converts signal data into an event. -5. Click **Preview**, then click **Save & Deploy**. - -Segment displays `Rule updated successfully` to verify that it saved your rule. +After integrating the SDK and running your app, verify that Segment is collecting signals: + +1. In your Segment workspace, go to **Connections > Sources** and select the source you created for Auto-Instrumentation. +2. In the source overview, look for the **Event Builder** tab. If the tab doesn’t appear: + - Make sure you've installed the SDK correctly. + - Reach out to your Segment CSM to confirm that your workspace has the necessary feature flags enabled. +3. Launch your app [in debug mode](https://github.com/segmentio/analytics-next/tree/master/packages/signals/signals#sending-and-viewing-signals-on-segmentcom-debug-mode){:target="_blank"}. This enables signal collection so you can see activity in the Event Builder. +4. Use the app as a user would: navigate between screens, tap buttons, trigger network requests. Signals appear in real time as you interact with the app. +5. In the Event Builder, find a signal and click **Configure event** to define a new event. After configuring the event, click **Publish event rules**. ## Configuration Options diff --git a/src/connections/auto-instrumentation/web-setup.md b/src/connections/auto-instrumentation/web-setup.md index acb2da05c7..97f759ca56 100644 --- a/src/connections/auto-instrumentation/web-setup.md +++ b/src/connections/auto-instrumentation/web-setup.md @@ -65,18 +65,18 @@ Verify that you replaced `` with the actual write key you copied in S ## Step 3: Verify and deploy events -Next, you'll need to verify signal emission and [create rules](/docs/connections/auto-instrumentation/configuration/#example-rule-implementations) to convert those signals into events: +After integrating the SDK and running your app, verify that Segment is collecting signals: + +1. In your Segment workspace, return to **Connections > Sources**, then select the source you created for Auto-Instrumentation. +2. In the source overview, look for the **Event Builder** tab. If the tab doesn’t appear: + - Make sure you've installed the SDK correctly. + - Reach out to your Segment CSM to confirm that your workspace has the necessary feature flags enabled. + ![The Event Builder tab shown in the navigation bar between Debugger and Schema in a Segment Source](images/event_builder_tab.png) +3. Open the **Event Builder** and follow the on-screen instructions to start signal detection. + - To collect signals in the UI, visit your site in a browser using the query string:`?segment_signals_debug=true` +4. Interact with your app to trigger signals: click buttons, navigate pages, submit forms, and so on. Segment collects and displays these as signals in real time. +5. From the signals list, click **Configure event** to define a new event based on one or more signals. After configuring the event, click **Publish event rules**. -1. In your Segment workspace, return to **Connections > Auto-Instrumentation** and click on the new source you created. -2. Verify that signals appear as expected on the dashboard. - - ![Signals successfully appearing in the Segment UI](images/autoinstrumentation_signals.png "Signals successfully appearing in the Segment UI") - -3. Click **Create Rules**. -4. In the Rules Editor, add a rule that converts signal data into an event. -5. Click **Preview**, then click **Save & Deploy**. - -Segment displays `Rule updated successfully` to verify that it saved your rule. ### Debugging #### Enable debug mode diff --git a/src/connections/destinations/catalog/actions-hubspot-cloud/index.md b/src/connections/destinations/catalog/actions-hubspot-cloud/index.md index 4d8c70ccf8..8f1a219b6d 100644 --- a/src/connections/destinations/catalog/actions-hubspot-cloud/index.md +++ b/src/connections/destinations/catalog/actions-hubspot-cloud/index.md @@ -16,13 +16,18 @@ HubSpot is an all-in-one marketing tool that helps attract new leads and convert When you use the HubSpot Cloud Mode (Actions) destination, Segment sends your data to [HubSpot's REST API](https://developers.hubspot.com/docs/api/overview){:target="_blank"}. -> warning "" -> The **Upsert Company** action is not compatible with the Mapping Tester on the mappings page if Associate Contact is set to **Yes**. As a result, Segment recommends using the Event Tester or other tools to test and troubleshoot creating and updating companies in HubSpot. -> -> Note that for the company to contact association to work, you are required to trigger an Upsert Contact action before triggering an Upsert Company action. Contacts created with batch endpoint can not be associated to a Company from the Upsert Company Action. +Keep in mind that: +* The **Upsert Company** action is not compatible with the Mapping Tester on the mappings page if Associate Contact is set to **Yes**. As a result, Segment recommends using the Event Tester or other tools to test and troubleshoot creating and updating companies in HubSpot. For the company to contact association to work, you are required to trigger an Upsert Contact action before triggering an Upsert Company action. Contacts created with batch endpoint can not be associated to a Company from the Upsert Company Action. +* **Behavioral Events (Legacy)** are only supported with [Hubspot Classic Destination](/docs/connections/destinations/catalog/hubspot/). > warning "" -> **Behavioral Events (Legacy)** are only supported with [Hubspot Classic Destination](/docs/connections/destinations/catalog/hubspot/). +> As of April 29, 2025, HubSpot no longer supports referencing custom object types by their base names. Instead, you must reference all custom objects by using their short-hand custom object type name, `fullyQualifiedName`, or `objectTypeId`. To avoid issues, update the following fields: +> +>- **Object Type** and **ObjectType to associate** in the **Upsert Custom Object Record** action +>- **Object Type** in the **Custom Event V2** action +>- **Object Type** and **To Object Type** in the **Custom Object V2** action +> +> For further details, refer to the [HubSpot documentation](https://developers.hubspot.com/changelog/breaking-change-removed-support-for-referencing-custom-object-types-by-base-name){:target="_blank"}. ## Benefits of HubSpot Cloud Mode (Actions) vs HubSpot Classic diff --git a/src/engage/audiences/index.md b/src/engage/audiences/index.md index cb92ee1830..a52c924ba3 100644 --- a/src/engage/audiences/index.md +++ b/src/engage/audiences/index.md @@ -374,5 +374,8 @@ The audience builder accepts CSV and TSV lists. This error occurs when creating audiences that reference each other, meaning audience X refers to audience Y in its trigger condition, and later you attempt to modify audience Y's trigger condition to refer back to audience X. To avoid this error, ensure that the audiences do not reference each other in their conditions. +### Can I build an audience based on `context.traits` in a Track event? +No. Traits located in the `context.traits` object of a Track event aren’t available in the Event Properties section of the Audience Builder. You can only use top-level event properties to define event-based audience conditions. + ### How does the historical data flag work? -The **Include Historical Event Data** option lets you take past event data into account and control how much of it is considered when creating real-time audiences. You can set a lookback window (for example, the “last 90 days”) to limit the processed event data, or disable it entirely to use only data arriving after creation. For batch audiences, Segment includes historical data by default. +The **Include Historical Event Data** option lets you take past event data into account and control how much of it is considered when creating real-time audiences. You can set a lookback window (for example, the “last 90 days”) to limit the processed event data, or disable it entirely to use only data arriving after creation. For batch audiences, Segment includes historical data by default. \ No newline at end of file diff --git a/src/engage/product-limits.md b/src/engage/product-limits.md index c7d74d06ce..059f3736c2 100644 --- a/src/engage/product-limits.md +++ b/src/engage/product-limits.md @@ -26,7 +26,7 @@ To learn more about custom limits and upgrades, contact your dedicated Customer | name | limit | Details | | --------------------------------------------- | --------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Compute Concurrency | 5 new 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. | +| Edit Concurrency | 5 concurrent audiences or computed traits | You can edit five concurrent audiences or computed traits at a time. Once the limit is reached, Segment queues and locks additional computations until one of the five finishes computing. | | Batch Compute Concurrency Limit | 10 (default) per space | The number of batch computations that can run concurrently per space. When this limit is reached, Segment delays subsequent computations until current computations finish. | | 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. | | Real-time to batch destination sync frequency | 12-15 hours | The frequency with which Segment syncs real-time audiences to batch destinations. | diff --git a/src/privacy/data-retention-policy.md b/src/privacy/data-retention-policy.md index 3721bc4558..f4cf16e58e 100644 --- a/src/privacy/data-retention-policy.md +++ b/src/privacy/data-retention-policy.md @@ -61,19 +61,23 @@ Select the default retention period for the workspace in this setting. This valu With this data retention policy, all data beyond the retention period is unrecoverably deleted from all of Segment and impacts the following: * [Data Replays](/docs/guides/what-is-replay/) will only be available for data within the retention period. Unify, Engage and Linked customers that replay data to recreate Unify Spaces or Profiles may encounter variations in the number of profiles, as well as in the identifiers, traits and properties associated with the profiles, depending on the data available. -* Backfill Data is only available for data within the retention period when sources are connected to your warehouse. +* Backfill Data is only available for data within the retention period, when sources are connected to your warehouse. * [Data residency](/docs/guides/regional-segment/) migrations across regions (US and EU) is only available for data within the retention period. * Additional impacts to Object data: - * [Object API](/docs/connections/sources/catalog/libraries/server/object-api/#set), [Bulk API](/docs/connections/sources/catalog/libraries/server/object-bulk-api/), or [SendGrid](/docs/connections/sources/catalog/cloud-apps/sendgrid/#streaming) and [Mandrill](/docs/connections/sources/catalog/cloud-apps/mandrill/#streaming) streaming sources: Any data older than 180 days is treated as a new record and may not contain any historic properties. To prevent loss of data properties, Segment recommends that you always send full objects with all properties. + * [Object API](/docs/connections/sources/catalog/libraries/server/object-api/#set) or [Bulk API](/docs/connections/sources/catalog/libraries/server/object-bulk-api/): Object data not updated within the retention period will be deleted. Any new data will treated as a new record and may not contain any historic properties. To prevent loss of data properties, Segment recommends that you always send full objects with all properties. * Users and Accounts: Segment aggregates data from Identify and Group events into [Users and Account objects and tables for warehouse destinations](/docs/connections/storage/warehouses/schema/#warehouse-tables) object store records. Any object store records not updated in the last 180 days will be deleted from Segment's object stores. Any new data after object store records are deleted for inactivity is treated as a new object store record. If the source is connected to a Warehouse destination, object store entities are synced into [`.users` and `.accounts` tables](/docs/connections/storage/warehouses/schema/#warehouse-tables), and the existing record in the warehouse will be replaced with the new object store record, resulting in possible loss of attribute data. To prevent loss of attributes, Segment advises customers to migrate to using [Profiles Sync](/docs/unify/profiles-sync/overview/), always send complete Identify and Group calls, or back up your `.users` and `.accounts` tables. * [Computed traits](/docs/unify/Traits/computed-traits/) is built using the available data within the retention period. Recreating these traits may result in different values based on the available data. -* [Profiles](/docs/unify/), [Engage](/docs/engage/) [Audiences](/docs/engage/audiences/) and [Journeys](/docs/engage/journeys/) that are built using Events will use available data within the retention period. Recreating these may result in different Profiles based on the available data. Depending on how the conditions are defined, Profiles may or may not exit Computed traits, Engage Audiences, and Journeys due to the data retention policy, and this may result in mismatches in counts when comparing against a preview. +* [Profiles](/docs/unify/), [Engage](/docs/engage/) [Audiences](/docs/engage/audiences/) and [Journeys](/docs/engage/journeys/) that are built using Events will use available data within the retention period. Recreating these may result in different Profiles based on the available data. + * [Real Time Computation](/docs/engage/audiences/#refresh-real-time-audiences-and-traits) (Audiences, Computed Traits, Journeys): When backfilling with historical data, backfill will use available data within the retention period. Once a computation is live, events that are removed due to data retention will not cause Profiles to enter/exit audiences and will not cause computed trait value changes. However, if you edit the definition or disable then re-enable them, this will cause the computation to re-backfill, which will cause Profiles to enter/exit audiences and computed trait value to change. + * [Batch Computation](/docs/engage/audiences/#real-time-compute-compared-to-batch) (Audiences, Computed Traits): Batch computation always computes based on available data, events removed due to data retention will cause Profile to enter/exit an Audience or computed trait values to change. + ### What data is not impacted? With this policy the following data is not impacted, but may be subject to other policies: -* **[Object Cloud Sources](/docs/connections/sources/#object-cloud-sources)**: This involves Segment fetching object data from third party Cloud Sources. Since Segment always fetches the full objects, the retention policy will have no impact. +* **[Object Cloud Sources](/docs/connections/sources/#object-cloud-sources)**: Segment fetches complete object data from third party Object Cloud Sources. Objects older than the retention period will be deleted. However, since Segment always fetches the complete object, Objects deleted will be fetched and made available again. + * [SendGrid](/docs/connections/sources/catalog/cloud-apps/sendgrid/) is both an Event Source and Object Source, therefore Events from SendGrid have retention period applicable to Archive and Profile stores while Objects from SendGrid have retention period applicable to the Object store retention period. * **Profiles**: Unify Profiles, Identifiers, and Traits created are not subject to this data retention policy. * **Third Party Destinations**: Data in your third party destinations shared by Segment in the course of your implementation remains unaffected. Data stored in a third party system may be subject to the data retention policy of that system. * Anything a user creates in the Segment App, like Audiences, Journeys, Data Graphs, Connections, and more, **are not subject to this data retention policy**. @@ -130,4 +134,4 @@ Segment unrecoverably deletes the workspace after 30 days of inactivity, unless ### Data deletion delays -When data reaches the end of its retention period, deletion is scheduled in accordance with Segment’s data retention policy. While Segment aims to complete the deletion process promptly, there may be occasional delays due to processing times or technical constraints. Segment is committed to initiating data deletions as soon as possible and strives to complete deletions within 7 days of the scheduled date. +When data reaches the end of its retention period, deletion is scheduled in accordance with Segment’s data retention policy. While Segment aims to complete the deletion process promptly, there may be occasional delays due to processing times or technical constraints. Segment is committed to initiating data deletions as soon as possible and strives to complete deletions within 7 days of the scheduled date. \ No newline at end of file diff --git a/src/unify/product-limits.md b/src/unify/product-limits.md index 9f7c9c1df5..44979fe2ac 100644 --- a/src/unify/product-limits.md +++ b/src/unify/product-limits.md @@ -42,7 +42,7 @@ Visit Segment's [pricing page](https://segment.com/pricing/){:target="_blank"} t | name | limit | Details | | --------------------------------------------- | --------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Compute Concurrency | 5 new 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. | +| Edit Concurrency | 5 concurrent audiences or computed traits | You can edit five concurrent audiences or computed traits at a time. Once the limit is reached, Segment queues and locks additional computations until one of the five finishes computing. | | Batch Compute Concurrency Limit | 10 (default) per space | The number of batch computations that can run concurrently per space. When this limit is reached, Segment delays subsequent computations until current computations finish. | | 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. | | Real-time to batch destination sync frequency | 2-3 hours | The frequency with which Segment syncs real-time audiences to batch destinations. |