diff --git a/src/_data/catalog/destination_categories.yml b/src/_data/catalog/destination_categories.yml index b4bed5a424..313cc8de2e 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 2024-12-16 +# destination categories last updated 2024-12-19 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 839b172a31..123a51d90e 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 2024-12-16 +# destination data last updated 2024-12-19 items: - id: 637e8d185e2dec264895ea89 display_name: 1Flow @@ -73357,7 +73357,7 @@ items: previous_names: - Klaviyo (Actions) website: http://www.segment.com - status: PUBLIC_BETA + status: PUBLIC categories: [] logo: url: https://cdn-devcenter.segment.com/1e93dfd5-878e-4a28-8ffe-bcb562b27861.svg diff --git a/src/_data/catalog/destinations_private.yml b/src/_data/catalog/destinations_private.yml index adaddb2da3..06a0c4819e 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 2024-12-16 +# destination data last updated 2024-12-19 items: - id: 54521fd925e721e32a72eee1 display_name: Pardot diff --git a/src/_data/catalog/source_categories.yml b/src/_data/catalog/source_categories.yml index 4bb9592d8c..27434ac33c 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 2024-12-16 +# source categories last updated 2024-12-19 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 cb465a0818..74b2a13c38 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 2024-12-16 +# sources last updated 2024-12-19 items: - id: 8HWbgPTt3k display_name: .NET diff --git a/src/_data/changelogs/analytics-android.yml b/src/_data/changelogs/analytics-android.yml index bbf55d2454..4c27a09432 100644 --- a/src/_data/changelogs/analytics-android.yml +++ b/src/_data/changelogs/analytics-android.yml @@ -1,5 +1,5 @@ # AUTOGENERATED FROM GITHUB API. DO NOT EDIT -# Releases last updated 2024-01-30 +# Releases last updated 2024-12-19 releases: - version: 4.11.3 url: https://github.com/segmentio/analytics-android/releases/tag/4.11.3 diff --git a/src/_data/changelogs/analytics-go.yml b/src/_data/changelogs/analytics-go.yml index 4f1bab3b81..e24c0d7594 100644 --- a/src/_data/changelogs/analytics-go.yml +++ b/src/_data/changelogs/analytics-go.yml @@ -1,5 +1,5 @@ # AUTOGENERATED FROM GITHUB API. DO NOT EDIT -# Releases last updated 2024-01-30 +# Releases last updated 2024-12-19 releases: - version: v3.3.0 url: https://github.com/segmentio/analytics-go/releases/tag/v3.3.0 diff --git a/src/_data/changelogs/analytics-ios.yml b/src/_data/changelogs/analytics-ios.yml index 4f3d743303..8a96782e5d 100644 --- a/src/_data/changelogs/analytics-ios.yml +++ b/src/_data/changelogs/analytics-ios.yml @@ -1,5 +1,5 @@ # AUTOGENERATED FROM GITHUB API. DO NOT EDIT -# Releases last updated 2024-01-30 +# Releases last updated 2024-12-19 releases: - version: 4.1.8 url: https://github.com/segmentio/analytics-ios/releases/tag/4.1.8 diff --git a/src/_data/changelogs/analytics-java.yml b/src/_data/changelogs/analytics-java.yml index 92a9c7423b..f8a187c8e0 100644 --- a/src/_data/changelogs/analytics-java.yml +++ b/src/_data/changelogs/analytics-java.yml @@ -1,3 +1,3 @@ # AUTOGENERATED FROM GITHUB API. DO NOT EDIT -# Releases last updated 2024-01-30 +# Releases last updated 2024-12-19 releases: [] diff --git a/src/_data/changelogs/analytics-node.yml b/src/_data/changelogs/analytics-node.yml index 5471ab37e7..1fac05eb28 100644 --- a/src/_data/changelogs/analytics-node.yml +++ b/src/_data/changelogs/analytics-node.yml @@ -1,5 +1,5 @@ # AUTOGENERATED FROM GITHUB API. DO NOT EDIT -# Releases last updated 2024-01-30 +# Releases last updated 2024-12-19 releases: - version: '' url: https://github.com/segmentio/analytics-node/releases/tag/v6.2.0 diff --git a/src/_data/changelogs/analytics-php.yml b/src/_data/changelogs/analytics-php.yml index a56bc6e5c3..75578a34c5 100644 --- a/src/_data/changelogs/analytics-php.yml +++ b/src/_data/changelogs/analytics-php.yml @@ -1,6 +1,10 @@ # AUTOGENERATED FROM GITHUB API. DO NOT EDIT -# Releases last updated 2024-01-30 +# Releases last updated 2024-12-19 releases: +- version: 3.8.0 + url: https://github.com/segmentio/analytics-php/releases/tag/3.8.0 + date: '2024-02-15T16:09:44Z' + notes: "## What's Changed\r\n* Update to PHP 8.3 by @nd4p90x in https://github.com/segmentio/analytics-php/pull/231\r\n\r\n**Full Changelog**: https://github.com/segmentio/analytics-php/compare/3.7.0...3.8.0" - version: 3.7.0 url: https://github.com/segmentio/analytics-php/releases/tag/3.7.0 date: '2023-09-11T13:53:19Z' diff --git a/src/_data/changelogs/analytics-python.yml b/src/_data/changelogs/analytics-python.yml index 92a9c7423b..f8a187c8e0 100644 --- a/src/_data/changelogs/analytics-python.yml +++ b/src/_data/changelogs/analytics-python.yml @@ -1,3 +1,3 @@ # AUTOGENERATED FROM GITHUB API. DO NOT EDIT -# Releases last updated 2024-01-30 +# Releases last updated 2024-12-19 releases: [] diff --git a/src/_data/changelogs/analytics-react-native.yml b/src/_data/changelogs/analytics-react-native.yml index 11ea6df108..b245dbd731 100644 --- a/src/_data/changelogs/analytics-react-native.yml +++ b/src/_data/changelogs/analytics-react-native.yml @@ -1,692 +1,221 @@ # AUTOGENERATED FROM GITHUB API. DO NOT EDIT -# Releases last updated 2024-01-30 +# Releases last updated 2024-12-19 releases: -- version: '@segment/sovran-react-native-v1.1.0-beta.1' - url: >- - https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/sovran-react-native-v1.1.0-beta.1 - date: '2023-12-15T20:21:53Z' - notes: >+ - ## @segment/sovran-react-native - [1.1.0-beta.1](https://github.com/segmentio/analytics-react-native/compare/@segment/sovran-react-native-v1.0.4...@segment/sovran-react-native-v1.1.0-beta.1) - (2023-12-15) - - - - ### Features - - - * RN 0.72 Upgrade - ([03f13a1](https://github.com/segmentio/analytics-react-native/commit/03f13a19c79d8aaad726639de5f0327c748fed1f)) - -- version: '@segment/analytics-react-native-v2.18.0-beta.1' - url: >- - https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-v2.18.0-beta.1 - date: '2023-12-15T20:23:24Z' - notes: >- - ## @segment/analytics-react-native - [2.18.0-beta.1](https://github.com/segmentio/analytics-react-native/compare/@segment/analytics-react-native-v2.17.0...@segment/analytics-react-native-v2.18.0-beta.1) - (2023-12-15) - - - - ### Features - - - * add support for hasUnmappedDestinations - ([#905](https://github.com/segmentio/analytics-react-native/issues/905)) - ([545d596](https://github.com/segmentio/analytics-react-native/commit/545d596e2b1fd5f83b229e7d3526ebf59ab62295)) - - * consent plugin updates and test cases - ([#894](https://github.com/segmentio/analytics-react-native/issues/894)) - ([ff1d332](https://github.com/segmentio/analytics-react-native/commit/ff1d33213108199d9486592d8a0372191f17dc2e)) - - * RN 0.72 Upgrade - ([03f13a1](https://github.com/segmentio/analytics-react-native/commit/03f13a19c79d8aaad726639de5f0327c748fed1f)) - - - - +- version: '@segment/analytics-react-native-plugin-advertising-id-v1.3.3' + url: >- + https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-plugin-advertising-id-v1.3.3 + date: '2024-11-14T20:19:14Z' + notes: '' +- version: '@segment/analytics-react-native-v2.20.3' + url: >- + https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-v2.20.3 + date: '2024-11-13T15:47:18Z' + notes: '' +- version: '@segment/analytics-react-native-v2.20.2' + url: >- + https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-v2.20.2 + date: '2024-10-23T09:15:00Z' + notes: '' +- version: '@segment/analytics-react-native-plugin-advertising-id-v1.3.2' + url: >- + https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-plugin-advertising-id-v1.3.2 + date: '2024-10-23T09:15:29Z' + notes: |- ### Dependencies - - * **@segment/sovran-react-native:** upgraded to 1.1.0-beta.1 -- version: '@segment/analytics-react-native-plugin-mixpanel-v0.4.0-beta.1' - url: >- - https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-plugin-mixpanel-v0.4.0-beta.1 - date: '2023-12-15T20:40:30Z' - notes: >- - ## @segment/analytics-react-native-plugin-mixpanel - [0.4.0-beta.1](https://github.com/segmentio/analytics-react-native/compare/@segment/analytics-react-native-plugin-mixpanel-v0.3.4...@segment/analytics-react-native-plugin-mixpanel-v0.4.0-beta.1) - (2023-12-15) - - - - ### Features - - - * RN 0.72 Upgrade - ([03f13a1](https://github.com/segmentio/analytics-react-native/commit/03f13a19c79d8aaad726639de5f0327c748fed1f)) - - - - + * **@segment/analytics-react-native:** upgraded to 2.20.2 +- version: '@segment/analytics-react-native-v2.20.1' + url: >- + https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-v2.20.1 + date: '2024-10-11T19:53:05Z' + notes: '' +- version: '@segment/analytics-react-native-v2.20.0' + url: >- + https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-v2.20.0 + date: '2024-10-08T20:16:21Z' + notes: '' +- version: '' + url: >- + https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-v2.19.5 + date: '2024-09-16T13:45:20Z' + notes: "- fix: add conditional to queue restoration error reporting #999 \r\n- chore: update async-storage dependency to 2.0.0 #1000 " +- version: '@segment/analytics-react-native-v2.19.4' + url: >- + https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-v2.19.4 + date: '2024-08-15T13:43:33Z' + notes: '' +- version: '@segment/analytics-react-native-plugin-firebase-v0.4.2' + url: >- + https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-plugin-firebase-v0.4.2 + date: '2024-08-01T15:34:51Z' + notes: '' +- version: '@segment/analytics-react-native-plugin-onetrust-v1.2.1' + url: >- + https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-plugin-onetrust-v1.2.1 + date: '2024-07-31T15:27:06Z' + notes: '' +- version: '@segment/analytics-react-native-v2.19.1' + url: >- + https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-v2.19.1 + date: '2024-02-28T00:40:43Z' + notes: '' +- version: '@segment/analytics-react-native-plugin-idfa-v0.7.2' + url: >- + https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-plugin-idfa-v0.7.2 + date: '2024-02-28T00:41:22Z' + notes: |- ### Dependencies - - * **@segment/analytics-react-native:** upgraded to 2.18.0-beta.1 - - * **@segment/sovran-react-native:** upgraded to 1.1.0-beta.1 -- version: '@segment/analytics-react-native-plugin-idfa-v0.7.0-beta.1' + * **@segment/analytics-react-native:** upgraded to 2.19.1 +- version: '@segment/sovran-react-native-v1.1.1' url: >- - https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-plugin-idfa-v0.7.0-beta.1 - date: '2023-12-15T20:38:11Z' - notes: >- - ## @segment/analytics-react-native-plugin-idfa - [0.7.0-beta.1](https://github.com/segmentio/analytics-react-native/compare/@segment/analytics-react-native-plugin-idfa-v0.6.2...@segment/analytics-react-native-plugin-idfa-v0.7.0-beta.1) - (2023-12-15) - - - - ### Features - - - * RN 0.72 Upgrade - ([03f13a1](https://github.com/segmentio/analytics-react-native/commit/03f13a19c79d8aaad726639de5f0327c748fed1f)) - - - - - ### Dependencies - - - * **@segment/analytics-react-native:** upgraded to 2.18.0-beta.1 - - * **@segment/sovran-react-native:** upgraded to 1.1.0-beta.1 -- version: '@segment/analytics-react-native-plugin-firebase-v0.4.0-beta.1' + https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/sovran-react-native-v1.1.1 + date: '2024-02-26T23:22:10Z' + notes: '' +- version: '@segment/analytics-react-native-v2.19.0' url: >- - https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-plugin-firebase-v0.4.0-beta.1 - date: '2023-12-15T20:37:44Z' - notes: >- - ## @segment/analytics-react-native-plugin-firebase - [0.4.0-beta.1](https://github.com/segmentio/analytics-react-native/compare/@segment/analytics-react-native-plugin-firebase-v0.3.11...@segment/analytics-react-native-plugin-firebase-v0.4.0-beta.1) - (2023-12-15) - - - - ### Features - - - * RN 0.72 Upgrade - ([03f13a1](https://github.com/segmentio/analytics-react-native/commit/03f13a19c79d8aaad726639de5f0327c748fed1f)) - - - - + https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-v2.19.0 + date: '2024-02-26T23:22:58Z' + notes: |- ### Dependencies - - * **@segment/analytics-react-native:** upgraded to 2.18.0-beta.1 - - * **@segment/sovran-react-native:** upgraded to 1.1.0-beta.1 -- version: '@segment/analytics-react-native-plugin-facebook-app-events-v0.6.0-beta.1' + * **@segment/sovran-react-native:** upgraded to 1.1.1 +- version: '@segment/analytics-react-native-plugin-onetrust-v1.2.0' url: >- - https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-plugin-facebook-app-events-v0.6.0-beta.1 - date: '2023-12-15T20:36:58Z' - notes: >- - ## @segment/analytics-react-native-plugin-facebook-app-events - [0.6.0-beta.1](https://github.com/segmentio/analytics-react-native/compare/@segment/analytics-react-native-plugin-facebook-app-events-v0.5.4...@segment/analytics-react-native-plugin-facebook-app-events-v0.6.0-beta.1) - (2023-12-15) - - - - ### Features - - - * RN 0.72 Upgrade - ([03f13a1](https://github.com/segmentio/analytics-react-native/commit/03f13a19c79d8aaad726639de5f0327c748fed1f)) - - - - + https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-plugin-onetrust-v1.2.0 + date: '2024-02-26T23:28:18Z' + notes: |- ### Dependencies - - * **@segment/analytics-react-native:** upgraded to 2.18.0-beta.1 - - * **@segment/sovran-react-native:** upgraded to 1.1.0-beta.1 -- version: '@segment/analytics-react-native-plugin-device-token-v1.1.0-beta.1' + * **@segment/analytics-react-native:** upgraded to 2.19.0 + * **@segment/sovran-react-native:** upgraded to 1.1.1 +- version: '@segment/analytics-react-native-plugin-idfa-v0.7.1' url: >- - https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-plugin-device-token-v1.1.0-beta.1 - date: '2023-12-15T20:35:27Z' - notes: >- - ## @segment/analytics-react-native-plugin-device-token - [1.1.0-beta.1](https://github.com/segmentio/analytics-react-native/compare/@segment/analytics-react-native-plugin-device-token-v1.0.2...@segment/analytics-react-native-plugin-device-token-v1.1.0-beta.1) - (2023-12-15) - - - - ### Features - - - * RN 0.72 Upgrade - ([03f13a1](https://github.com/segmentio/analytics-react-native/commit/03f13a19c79d8aaad726639de5f0327c748fed1f)) - - - - + https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-plugin-idfa-v0.7.1 + date: '2024-02-26T23:27:34Z' + notes: |- ### Dependencies - - * **@segment/analytics-react-native:** upgraded to 2.18.0-beta.1 - - * **@segment/sovran-react-native:** upgraded to 1.1.0-beta.1 -- version: '@segment/analytics-react-native-plugin-destination-filters-v1.1.0-beta.1' + * **@segment/analytics-react-native:** upgraded to 2.19.0 + * **@segment/sovran-react-native:** upgraded to 1.1.1 +- version: '@segment/analytics-react-native-plugin-firebase-v0.4.1' url: >- - https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-plugin-destination-filters-v1.1.0-beta.1 - date: '2023-12-15T20:34:33Z' - notes: >- - ## @segment/analytics-react-native-plugin-destination-filters - [1.1.0-beta.1](https://github.com/segmentio/analytics-react-native/compare/@segment/analytics-react-native-plugin-destination-filters-v1.0.4...@segment/analytics-react-native-plugin-destination-filters-v1.1.0-beta.1) - (2023-12-15) - - - - ### Features - - - * RN 0.72 Upgrade - ([03f13a1](https://github.com/segmentio/analytics-react-native/commit/03f13a19c79d8aaad726639de5f0327c748fed1f)) - - - - + https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-plugin-firebase-v0.4.1 + date: '2024-02-26T23:26:52Z' + notes: |- ### Dependencies - - * **@segment/analytics-react-native:** upgraded to 2.18.0-beta.1 - - * **@segment/sovran-react-native:** upgraded to 1.1.0-beta.1 -- version: '@segment/analytics-react-native-plugin-clevertap-v1.1.0-beta.1' + * **@segment/analytics-react-native:** upgraded to 2.19.0 + * **@segment/sovran-react-native:** upgraded to 1.1.1 +- version: '@segment/analytics-react-native-plugin-device-token-v1.1.1' url: >- - https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-plugin-clevertap-v1.1.0-beta.1 - date: '2023-12-15T20:33:38Z' - notes: >- - ## @segment/analytics-react-native-plugin-clevertap - [1.1.0-beta.1](https://github.com/segmentio/analytics-react-native/compare/@segment/analytics-react-native-plugin-clevertap-v1.0.3...@segment/analytics-react-native-plugin-clevertap-v1.1.0-beta.1) - (2023-12-15) - - - - ### Features - - - * RN 0.72 Upgrade - ([03f13a1](https://github.com/segmentio/analytics-react-native/commit/03f13a19c79d8aaad726639de5f0327c748fed1f)) - - - - + https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-plugin-device-token-v1.1.1 + date: '2024-02-26T23:26:07Z' + notes: |- ### Dependencies - - * **@segment/analytics-react-native:** upgraded to 2.18.0-beta.1 - - * **@segment/sovran-react-native:** upgraded to 1.1.0-beta.1 -- version: '@segment/analytics-react-native-plugin-braze-v0.6.0-beta.1' + * **@segment/analytics-react-native:** upgraded to 2.19.0 + * **@segment/sovran-react-native:** upgraded to 1.1.1 +- version: '@segment/analytics-react-native-plugin-braze-v0.6.1' url: >- - https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-plugin-braze-v0.6.0-beta.1 - date: '2023-12-15T20:29:43Z' - notes: >- - ## @segment/analytics-react-native-plugin-braze - [0.6.0-beta.1](https://github.com/segmentio/analytics-react-native/compare/@segment/analytics-react-native-plugin-braze-v0.5.4...@segment/analytics-react-native-plugin-braze-v0.6.0-beta.1) - (2023-12-15) - - - - ### Features - - - * RN 0.72 Upgrade - ([03f13a1](https://github.com/segmentio/analytics-react-native/commit/03f13a19c79d8aaad726639de5f0327c748fed1f)) - - - - + https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-plugin-braze-v0.6.1 + date: '2024-02-26T23:25:15Z' + notes: |- ### Dependencies - - * **@segment/analytics-react-native:** upgraded to 2.18.0-beta.1 - - * **@segment/sovran-react-native:** upgraded to 1.1.0-beta.1 -- version: '@segment/analytics-react-native-plugin-braze-middleware-v1.1.0-beta.1' + * **@segment/analytics-react-native:** upgraded to 2.19.0 + * **@segment/sovran-react-native:** upgraded to 1.1.1 +- version: '@segment/analytics-react-native-plugin-branch-v1.1.1' url: >- - https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-plugin-braze-middleware-v1.1.0-beta.1 - date: '2023-12-15T20:31:18Z' - notes: >- - ## @segment/analytics-react-native-plugin-braze-middleware - [1.1.0-beta.1](https://github.com/segmentio/analytics-react-native/compare/@segment/analytics-react-native-plugin-braze-middleware-v1.0.1...@segment/analytics-react-native-plugin-braze-middleware-v1.1.0-beta.1) - (2023-12-15) - - - - ### Features - - - * RN 0.72 Upgrade - ([03f13a1](https://github.com/segmentio/analytics-react-native/commit/03f13a19c79d8aaad726639de5f0327c748fed1f)) - - - - + https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-plugin-branch-v1.1.1 + date: '2024-02-26T23:24:32Z' + notes: |- ### Dependencies - - * **@segment/analytics-react-native:** upgraded to 2.18.0-beta.1 - - * **@segment/sovran-react-native:** upgraded to 1.1.0-beta.1 -- version: '@segment/analytics-react-native-plugin-branch-v1.1.0-beta.1' + * **@segment/analytics-react-native:** upgraded to 2.19.0 + * **@segment/sovran-react-native:** upgraded to 1.1.1 +- version: '@segment/analytics-react-native-plugin-advertising-id-v1.3.1' url: >- - https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-plugin-branch-v1.1.0-beta.1 - date: '2023-12-15T20:28:46Z' - notes: >- - ## @segment/analytics-react-native-plugin-branch - [1.1.0-beta.1](https://github.com/segmentio/analytics-react-native/compare/@segment/analytics-react-native-plugin-branch-v1.0.3...@segment/analytics-react-native-plugin-branch-v1.1.0-beta.1) - (2023-12-15) - - - - ### Features - - - * RN 0.72 Upgrade - ([03f13a1](https://github.com/segmentio/analytics-react-native/commit/03f13a19c79d8aaad726639de5f0327c748fed1f)) - - - - + https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-plugin-advertising-id-v1.3.1 + date: '2024-02-26T23:23:43Z' + notes: |- ### Dependencies - - * **@segment/analytics-react-native:** upgraded to 2.18.0-beta.1 - - * **@segment/sovran-react-native:** upgraded to 1.1.0-beta.1 -- version: '@segment/analytics-react-native-plugin-appsflyer-v0.6.0-beta.1' + * **@segment/analytics-react-native:** upgraded to 2.19.0 + * **@segment/sovran-react-native:** upgraded to 1.1.1 +- version: '@segment/sovran-react-native-v1.1.0' url: >- - https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-plugin-appsflyer-v0.6.0-beta.1 - date: '2023-12-15T20:27:52Z' - notes: >- - ## @segment/analytics-react-native-plugin-appsflyer - [0.6.0-beta.1](https://github.com/segmentio/analytics-react-native/compare/@segment/analytics-react-native-plugin-appsflyer-v0.5.3...@segment/analytics-react-native-plugin-appsflyer-v0.6.0-beta.1) - (2023-12-15) - - - - ### Features - - - * RN 0.72 Upgrade - ([03f13a1](https://github.com/segmentio/analytics-react-native/commit/03f13a19c79d8aaad726639de5f0327c748fed1f)) - - - - - ### Dependencies - - - * **@segment/analytics-react-native:** upgraded to 2.18.0-beta.1 - - * **@segment/sovran-react-native:** upgraded to 1.1.0-beta.1 -- version: '@segment/analytics-react-native-plugin-amplitude-session-v0.4.0-beta.1' + https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/sovran-react-native-v1.1.0 + date: '2024-02-05T22:29:56Z' + notes: '' +- version: '@segment/analytics-react-native-v2.18.0' url: >- - https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-plugin-amplitude-session-v0.4.0-beta.1 - date: '2023-12-15T20:25:34Z' - notes: >- - ## @segment/analytics-react-native-plugin-amplitude-session - [0.4.0-beta.1](https://github.com/segmentio/analytics-react-native/compare/@segment/analytics-react-native-plugin-amplitude-session-v0.3.3...@segment/analytics-react-native-plugin-amplitude-session-v0.4.0-beta.1) - (2023-12-15) - - - - ### Features - - - * RN 0.72 Upgrade - ([03f13a1](https://github.com/segmentio/analytics-react-native/commit/03f13a19c79d8aaad726639de5f0327c748fed1f)) - - - - + https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-v2.18.0 + date: '2024-02-05T22:31:36Z' + notes: |- ### Dependencies - - * **@segment/analytics-react-native:** upgraded to 2.18.0-beta.1 - - * **@segment/sovran-react-native:** upgraded to 1.1.0-beta.1 -- version: '@segment/analytics-react-native-plugin-advertising-id-v1.3.0-beta.1' + * **@segment/sovran-react-native:** upgraded to 1.1.0 +- version: '@segment/analytics-react-native-plugin-onetrust-v1.1.0' url: >- - https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-plugin-advertising-id-v1.3.0-beta.1 - date: '2023-12-15T20:24:41Z' - notes: >- - ## @segment/analytics-react-native-plugin-advertising-id - [1.3.0-beta.1](https://github.com/segmentio/analytics-react-native/compare/@segment/analytics-react-native-plugin-advertising-id-v1.2.4...@segment/analytics-react-native-plugin-advertising-id-v1.3.0-beta.1) - (2023-12-15) - - - - ### Features - - - * RN 0.72 Upgrade - ([03f13a1](https://github.com/segmentio/analytics-react-native/commit/03f13a19c79d8aaad726639de5f0327c748fed1f)) - - - - + https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-plugin-onetrust-v1.1.0 + date: '2024-02-05T22:51:01Z' + notes: |- ### Dependencies - - * **@segment/analytics-react-native:** upgraded to 2.18.0-beta.1 - - * **@segment/sovran-react-native:** upgraded to 1.1.0-beta.1 -- version: '@segment/analytics-react-native-plugin-adjust-v0.7.0-beta.1' + * **@segment/analytics-react-native:** upgraded to 2.18.0 + * **@segment/sovran-react-native:** upgraded to 1.1.0 +- version: '@segment/analytics-react-native-plugin-mixpanel-v0.4.0' url: >- - https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-plugin-adjust-v0.7.0-beta.1 - date: '2023-12-15T20:23:46Z' - notes: >- - ## @segment/analytics-react-native-plugin-adjust - [0.7.0-beta.1](https://github.com/segmentio/analytics-react-native/compare/@segment/analytics-react-native-plugin-adjust-v0.6.3...@segment/analytics-react-native-plugin-adjust-v0.7.0-beta.1) - (2023-12-15) - - - - ### Features - - - * RN 0.72 Upgrade - ([03f13a1](https://github.com/segmentio/analytics-react-native/commit/03f13a19c79d8aaad726639de5f0327c748fed1f)) - - - - + https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-plugin-mixpanel-v0.4.0 + date: '2024-02-05T22:50:09Z' + notes: |- ### Dependencies - - * **@segment/analytics-react-native:** upgraded to 2.18.0-beta.1 - - * **@segment/sovran-react-native:** upgraded to 1.1.0-beta.1 -- version: '@segment/analytics-react-native-v2.17.0' - url: >- - https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-v2.17.0 - date: '2023-10-20T22:05:30Z' - notes: >+ - ## - [@segment/analytics-react-native-v2.17.0](https://github.com/segmentio/analytics-react-native/compare/@segment/analytics-react-native-v2.16.1...@segment/analytics-react-native-v2.17.0) - (2023-10-20) - - - - ### Features - - - * add consent management and support for onetrust cmp - ([#882](https://github.com/segmentio/analytics-react-native/issues/882)) - ([375684f](https://github.com/segmentio/analytics-react-native/commit/375684f99ac4324d30c009924ad004098d9feb38)) - - - - ### Bug Fixes - - - * add unknown option to current state - ([#887](https://github.com/segmentio/analytics-react-native/issues/887)) - ([a0a3b0d](https://github.com/segmentio/analytics-react-native/commit/a0a3b0df3269542fcbd836ae1d2d5d7a77157313)) - - * change content type to json - ([#885](https://github.com/segmentio/analytics-react-native/issues/885)) - ([e8ddeb4](https://github.com/segmentio/analytics-react-native/commit/e8ddeb49a97e62ccd6150e88bfb16014ede1332e)) - -- version: '@segment/analytics-react-native-plugin-onetrust-v1.0.0' - url: >- - https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-plugin-onetrust-v1.0.0 - date: '2023-10-20T22:07:14Z' - notes: >+ - ## @segment/analytics-react-native-plugin-onetrust-v1.0.0 (2023-10-20) - - - - ### Features - - - * add consent management and support for onetrust cmp - ([#882](https://github.com/segmentio/analytics-react-native/issues/882)) - ([375684f](https://github.com/segmentio/analytics-react-native/commit/375684f99ac4324d30c009924ad004098d9feb38)) - -- version: '@segment/analytics-react-native-plugin-firebase-v0.3.11' - url: >- - https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-plugin-firebase-v0.3.11 - date: '2023-10-20T22:06:39Z' - notes: >+ - ## - [@segment/analytics-react-native-plugin-firebase-v0.3.11](https://github.com/segmentio/analytics-react-native/compare/@segment/analytics-react-native-plugin-firebase-v0.3.10...@segment/analytics-react-native-plugin-firebase-v0.3.11) - (2023-10-20) - - - - ### Bug Fixes - - - * update peer dependency to version 18 of Firebase - ([#883](https://github.com/segmentio/analytics-react-native/issues/883)) - ([8796020](https://github.com/segmentio/analytics-react-native/commit/87960204260bf3aa14ad5f7d777b2f7bbb42c018)) - -- version: '@segment/analytics-react-native-v2.16.1' - url: >- - https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-v2.16.1 - date: '2023-09-14T15:21:01Z' - notes: >+ - ## - [@segment/analytics-react-native-v2.16.1](https://github.com/segmentio/analytics-react-native/compare/@segment/analytics-react-native-v2.16.0...@segment/analytics-react-native-v2.16.1) - (2023-09-14) - - - - ### Bug Fixes - - - * split userInfo/context stamping from raw event data - ([#876](https://github.com/segmentio/analytics-react-native/issues/876)) - ([c220376](https://github.com/segmentio/analytics-react-native/commit/c220376a393b2d89a3ebb91b572edeb21cdcd5a4)) - -- version: '@segment/analytics-react-native-plugin-mixpanel-v0.3.4' + * **@segment/analytics-react-native:** upgraded to 2.18.0 + * **@segment/sovran-react-native:** upgraded to 1.1.0 +- version: '@segment/analytics-react-native-plugin-idfa-v0.7.0' url: >- - https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-plugin-mixpanel-v0.3.4 - date: '2023-09-14T15:23:26Z' - notes: >+ - ## - [@segment/analytics-react-native-plugin-mixpanel-v0.3.4](https://github.com/segmentio/analytics-react-native/compare/@segment/analytics-react-native-plugin-mixpanel-v0.3.3...@segment/analytics-react-native-plugin-mixpanel-v0.3.4) - (2023-09-14) - - - - ### Bug Fixes - - - * package dependency fixes - ([#869](https://github.com/segmentio/analytics-react-native/issues/869)) - ([08d415e](https://github.com/segmentio/analytics-react-native/commit/08d415e3b1cfd8499f5f6984f2859a30a851da12)) - -- version: '@segment/analytics-react-native-plugin-firebase-v0.3.10' - url: >- - https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-plugin-firebase-v0.3.10 - date: '2023-09-14T15:22:53Z' - notes: >+ - ## - [@segment/analytics-react-native-plugin-firebase-v0.3.10](https://github.com/segmentio/analytics-react-native/compare/@segment/analytics-react-native-plugin-firebase-v0.3.9...@segment/analytics-react-native-plugin-firebase-v0.3.10) - (2023-09-14) - - - - ### Bug Fixes - - - * add firebase view cart mapping - ([#871](https://github.com/segmentio/analytics-react-native/issues/871)) - ([ef0e02f](https://github.com/segmentio/analytics-react-native/commit/ef0e02fcc247e722c0119e3420812d855a2fe5c1)) - -- version: '@segment/analytics-react-native-plugin-facebook-app-events-v0.5.4' - url: >- - https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-plugin-facebook-app-events-v0.5.4 - date: '2023-09-14T15:22:24Z' - notes: >+ - ## - [@segment/analytics-react-native-plugin-facebook-app-events-v0.5.4](https://github.com/segmentio/analytics-react-native/compare/@segment/analytics-react-native-plugin-facebook-app-events-v0.5.3...@segment/analytics-react-native-plugin-facebook-app-events-v0.5.4) - (2023-09-14) - - - - ### Bug Fixes - - - * switch FBSDK logTime to number - ([#878](https://github.com/segmentio/analytics-react-native/issues/878)) - ([2ed6d34](https://github.com/segmentio/analytics-react-native/commit/2ed6d34c46063330c6573774906cae5afc9d5e06)) - -- version: '@segment/analytics-react-native-v2.16.0' - url: >- - https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-v2.16.0 - date: '2023-08-21T16:56:42Z' - notes: >+ - ## - [@segment/analytics-react-native-v2.16.0](https://github.com/segmentio/analytics-react-native/compare/@segment/analytics-react-native-v2.15.0...@segment/analytics-react-native-v2.16.0) - (2023-08-21) - - - - ### Features - - - * add saveDelay option for persistor - ([#811](https://github.com/segmentio/analytics-react-native/issues/811)) - ([11d5e87](https://github.com/segmentio/analytics-react-native/commit/11d5e87648938220732ea2e2c35d499789413b72)) - - - - ### Bug Fixes - - - * package dependency fixes - ([#869](https://github.com/segmentio/analytics-react-native/issues/869)) - ([08d415e](https://github.com/segmentio/analytics-react-native/commit/08d415e3b1cfd8499f5f6984f2859a30a851da12)) - - * resolve potential build issues with RN 0.72 - ([#841](https://github.com/segmentio/analytics-react-native/issues/841)) - ([d287304](https://github.com/segmentio/analytics-react-native/commit/d287304383b22b7d0344d0f2c68fccce8aec76cb)) - -- version: '@segment/analytics-react-native-plugin-facebook-app-events-v0.5.3' - url: >- - https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-plugin-facebook-app-events-v0.5.3 - date: '2023-08-21T17:00:29Z' - notes: >+ - ## - [@segment/analytics-react-native-plugin-facebook-app-events-v0.5.3](https://github.com/segmentio/analytics-react-native/compare/@segment/analytics-react-native-plugin-facebook-app-events-v0.5.2...@segment/analytics-react-native-plugin-facebook-app-events-v0.5.3) - (2023-08-21) - - - - ### Bug Fixes - - - * package dependency fixes - ([#869](https://github.com/segmentio/analytics-react-native/issues/869)) - ([08d415e](https://github.com/segmentio/analytics-react-native/commit/08d415e3b1cfd8499f5f6984f2859a30a851da12)) - -- version: '@segment/analytics-react-native-plugin-destination-filters-v1.0.4' - url: >- - https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-plugin-destination-filters-v1.0.4 - date: '2023-08-21T16:59:57Z' - notes: >+ - ## - [@segment/analytics-react-native-plugin-destination-filters-v1.0.4](https://github.com/segmentio/analytics-react-native/compare/@segment/analytics-react-native-plugin-destination-filters-v1.0.3...@segment/analytics-react-native-plugin-destination-filters-v1.0.4) - (2023-08-21) - - - - ### Bug Fixes - - - * package dependency fixes - ([#869](https://github.com/segmentio/analytics-react-native/issues/869)) - ([08d415e](https://github.com/segmentio/analytics-react-native/commit/08d415e3b1cfd8499f5f6984f2859a30a851da12)) + https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-plugin-idfa-v0.7.0 + date: '2024-02-05T22:47:41Z' + notes: |- + ### Dependencies -- version: '@segment/analytics-react-native-plugin-clevertap-v1.0.3' + * **@segment/analytics-react-native:** upgraded to 2.18.0 + * **@segment/sovran-react-native:** upgraded to 1.1.0 +- version: '@segment/analytics-react-native-plugin-firebase-v0.4.0' url: >- - https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-plugin-clevertap-v1.0.3 - date: '2023-08-21T16:59:31Z' - notes: >+ - ## - [@segment/analytics-react-native-plugin-clevertap-v1.0.3](https://github.com/segmentio/analytics-react-native/compare/@segment/analytics-react-native-plugin-clevertap-v1.0.2...@segment/analytics-react-native-plugin-clevertap-v1.0.3) - (2023-08-21) - - - - ### Bug Fixes - - - * package dependency fixes - ([#869](https://github.com/segmentio/analytics-react-native/issues/869)) - ([08d415e](https://github.com/segmentio/analytics-react-native/commit/08d415e3b1cfd8499f5f6984f2859a30a851da12)) + https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-plugin-firebase-v0.4.0 + date: '2024-02-05T22:47:08Z' + notes: |- + ### Dependencies -- version: '@segment/analytics-react-native-plugin-branch-v1.0.3' + * **@segment/analytics-react-native:** upgraded to 2.18.0 + * **@segment/sovran-react-native:** upgraded to 1.1.0 +- version: '@segment/analytics-react-native-plugin-facebook-app-events-v0.6.0' url: >- - https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-plugin-branch-v1.0.3 - date: '2023-08-21T16:58:54Z' - notes: >+ - ## - [@segment/analytics-react-native-plugin-branch-v1.0.3](https://github.com/segmentio/analytics-react-native/compare/@segment/analytics-react-native-plugin-branch-v1.0.2...@segment/analytics-react-native-plugin-branch-v1.0.3) - (2023-08-21) - - - - ### Bug Fixes - - - * package dependency fixes - ([#869](https://github.com/segmentio/analytics-react-native/issues/869)) - ([08d415e](https://github.com/segmentio/analytics-react-native/commit/08d415e3b1cfd8499f5f6984f2859a30a851da12)) + https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-plugin-facebook-app-events-v0.6.0 + date: '2024-02-05T22:46:10Z' + notes: |- + ### Dependencies -- version: '@segment/analytics-react-native-plugin-appsflyer-v0.5.3' + * **@segment/analytics-react-native:** upgraded to 2.18.0 + * **@segment/sovran-react-native:** upgraded to 1.1.0 +- version: '@segment/analytics-react-native-plugin-device-token-v1.1.0' url: >- - https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-plugin-appsflyer-v0.5.3 - date: '2023-08-21T16:58:27Z' - notes: >+ - ## - [@segment/analytics-react-native-plugin-appsflyer-v0.5.3](https://github.com/segmentio/analytics-react-native/compare/@segment/analytics-react-native-plugin-appsflyer-v0.5.2...@segment/analytics-react-native-plugin-appsflyer-v0.5.3) - (2023-08-21) - - - - ### Bug Fixes - - - * package dependency fixes - ([#869](https://github.com/segmentio/analytics-react-native/issues/869)) - ([08d415e](https://github.com/segmentio/analytics-react-native/commit/08d415e3b1cfd8499f5f6984f2859a30a851da12)) + https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-plugin-device-token-v1.1.0 + date: '2024-02-05T22:44:32Z' + notes: |- + ### Dependencies -- version: '@segment/analytics-react-native-plugin-advertising-id-v1.2.4' + * **@segment/analytics-react-native:** upgraded to 2.18.0 + * **@segment/sovran-react-native:** upgraded to 1.1.0 +- version: '@segment/analytics-react-native-plugin-destination-filters-v1.1.0' url: >- - https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-plugin-advertising-id-v1.2.4 - date: '2023-08-21T16:57:54Z' - notes: >+ - ## - [@segment/analytics-react-native-plugin-advertising-id-v1.2.4](https://github.com/segmentio/analytics-react-native/compare/@segment/analytics-react-native-plugin-advertising-id-v1.2.3...@segment/analytics-react-native-plugin-advertising-id-v1.2.4) - (2023-08-21) - - - - ### Bug Fixes - - - * resolve potential build issues with RN 0.72 - ([#841](https://github.com/segmentio/analytics-react-native/issues/841)) - ([d287304](https://github.com/segmentio/analytics-react-native/commit/d287304383b22b7d0344d0f2c68fccce8aec76cb)) + https://github.com/segmentio/analytics-react-native/releases/tag/%40segment/analytics-react-native-plugin-destination-filters-v1.1.0 + date: '2024-02-05T22:43:30Z' + notes: |- + ### Dependencies + * **@segment/analytics-react-native:** upgraded to 2.18.0 + * **@segment/sovran-react-native:** upgraded to 1.1.0 diff --git a/src/_data/changelogs/analytics.NET.yml b/src/_data/changelogs/analytics.NET.yml index 337e4f0234..35bd8b5a18 100644 --- a/src/_data/changelogs/analytics.NET.yml +++ b/src/_data/changelogs/analytics.NET.yml @@ -1,5 +1,5 @@ # AUTOGENERATED FROM GITHUB API. DO NOT EDIT -# Releases last updated 2024-01-30 +# Releases last updated 2024-12-19 releases: - version: '' url: https://github.com/segmentio/Analytics.NET/releases/tag/3.8.1 diff --git a/src/_data/sidenav/main.yml b/src/_data/sidenav/main.yml index c1b1f0ac97..fa6d41dfc7 100644 --- a/src/_data/sidenav/main.yml +++ b/src/_data/sidenav/main.yml @@ -482,6 +482,13 @@ sections: title: Send Data to Destinations - path: '/engage/journeys/journeys-analytics' title: Journeys Analytics + - section_title: Event-Triggered Journeys + slug: '/engage/journeys/event-triggered-journeys' + section: + - path: /engage/journeys/event-triggered-journeys + title: Event-Triggered Journeys Overview + - path: /engage/journeys/journey-context + title: Journey Context - path: '/engage/journeys/faq-best-practices' title: Journeys Best Practices and FAQ - path: '/engage/journeys/use-cases' diff --git a/src/connections/destinations/actions.md b/src/connections/destinations/actions.md index 7f76703047..040d47fd55 100644 --- a/src/connections/destinations/actions.md +++ b/src/connections/destinations/actions.md @@ -305,3 +305,7 @@ Threfore, if you see a 401 error in a sample response, it is likely that you’l ### Is it possible to map a field from one event to another? Segment integrations process events through mappings individially. This means that no context is held that would allow you to map a value from one event to the field of a subsequent event. Each event itself must contain all of the data you'd like to send downstream in regards to it. For example, you cannot send `email` in on an Identify call and then access that same `email` field on a Track call that comes in later if that Track call doesn't also have `email` set on it. + +### I'm getting a 'Couldn't load page' error when viewing or editing a mapping + +This issue can occur due to a browser cache conflict or if an event property name includes a `/`. To resolve it, try clearing your browser cache or accessing the mapping page in an incognito window. Additionally, check if the mapped property name contains a `/`. If it does, rename the property to remove the `/` and update the mapping. diff --git a/src/connections/destinations/catalog/actions-amplitude/index.md b/src/connections/destinations/catalog/actions-amplitude/index.md index 90ba8fb904..3427980bac 100644 --- a/src/connections/destinations/catalog/actions-amplitude/index.md +++ b/src/connections/destinations/catalog/actions-amplitude/index.md @@ -241,13 +241,36 @@ In the following example, the Amplitude User property `friendCount` equals 4. "traits" : {"$add": {"friendCount": 3} } "traits" : {"$add": {"friendCount": 1} } ``` -## FAQ and troubleshooting +## FAQs and troubleshooting -### Why doesn't Segment automatically add the `session_id` to my web events? -For Segment to automatically add the `session_id` to events, your browser must allow the following request URL to load: +### Does Segment load the Amplitude SDK on the webpage to collect data? +Segment doesn't load the Amplitude SDK directly on the webpage. Instead, Segment collects data using the Analytics.js library. Once events reach Segment’s servers, they are forwarded to Amplitude’s servers using Amplitude’s HTTP API. +### How does Segment handle the Amplitude session ID? +The Analytics.js library includes a plugin that sets the Amplitude session ID on the device. This session ID is used to track sessions and is automatically attached to events sent to Amplitude. By default, the session ID is set to timeout after 30 minutes of inactivity. You can review the code implementation for setting the [session ID](https://github.com/segmentio/action-destinations/blob/12255568e4a6d35cf05ee79a118ee6c1a6823f31/packages/browser-destinations/destinations/amplitude-plugins/src/sessionId/index.ts#L33){:target="_blank”}. + +### How can I retrieve the Amplitude session ID set by Segment? +Since Segment doesn't load the Amplitude SDK, the Amplitude native method `amplitude.getInstance()._sessionId` won't work. You can retrieve the session ID using the this method: + +``` js +localStorage.getItem('analytics_session_id'); ``` + +This call accesses the session ID stored in the browser's local storage. You can review the [retrieval code](https://github.com/segmentio/action-destinations/blob/12255568e4a6d35cf05ee79a118ee6c1a6823f31/packages/browser-destinations/destinations/amplitude-plugins/src/sessionId/index.ts#L64){:target="_blank”}. + +### Why doesn't Segment automatically add the session_id to my Web Events? + +For Segment to automatically add the session_id to your web events, your website must allow the following URL: + +``` js https://cdn.segment.com/next-integrations/actions/amplitude-plugins/.. ``` -To check if you are loading this request, [inspect the network requests](https://developer.chrome.com/docs/devtools/network){:target="_blank”} on your website and look for 'Amplitude.' If the request is not loading, confirm it is allowed on your side. +To check if your website allows the URL: + +1. Open your browser’s developer tools and [inspect the network requests](https://developer.chrome.com/docs/devtools/network){:target="_blank”} on your website. +2. Look for a request related to Amplitude. + +If the request is missing: + * Ensure your browser settings or network configuration allow the URL to load. + * Check for any third-party script blockers or restrictions that might prevent it. diff --git a/src/connections/destinations/catalog/actions-google-enhanced-conversions/index.md b/src/connections/destinations/catalog/actions-google-enhanced-conversions/index.md index 93f1ccfb97..1c5b8ddf28 100644 --- a/src/connections/destinations/catalog/actions-google-enhanced-conversions/index.md +++ b/src/connections/destinations/catalog/actions-google-enhanced-conversions/index.md @@ -204,3 +204,5 @@ You may encounter this error if you use more than one identifier to update a con Events going to Google for this integration require a `GCLID` field, an `email`, or a `phone_number`. If one of those identifiers isn't being sent properly, then you may see the `The required field was not present., at conversions[0].gclid` error. To fix this, double check that at least one of those fields is being passed to Google on each payload. +### What are the differences between the Upload Click Conversions and Click Conversion V2 Actions? +The only difference between the Upload Click Conversions and Click Conversion V2 Actions is that the Click Conversion V2 Action has [sync modes](/docs/connections/destinations/#sync-modes). diff --git a/src/connections/destinations/catalog/actions-google-sheets/index.md b/src/connections/destinations/catalog/actions-google-sheets/index.md index fe6b9ad858..764e89c89f 100644 --- a/src/connections/destinations/catalog/actions-google-sheets/index.md +++ b/src/connections/destinations/catalog/actions-google-sheets/index.md @@ -58,3 +58,7 @@ When syncing data to Google Sheets, the columns will be arranged alphabetically, ### Can I add or remove columns after data has been synced? Once data has been synced to Google Sheets, any subsequent addition or removal of columns in the RETL Model and/or Mapping may lead to misalignment of existing data, as Segment does not retroactively adjust previously synced data. For updates involving column modifications, Segment recommends starting with a new Sheet to ensure data integrity. + +### Can I send objects to Google Sheets? + +You can't send JavaScript objects as they're not a supported data type in Google Sheets. You need to stringify the property first. Failure to do so results in a `400` error. Segment's Actions mapping framework supports encoding objects as strings through the `json(properties, encode)` method. Alternatively, you can use an Insert Function to modify the property. diff --git a/src/connections/destinations/catalog/actions-s3/index.md b/src/connections/destinations/catalog/actions-s3/index.md index 906f2cf0c6..61acf60c98 100644 --- a/src/connections/destinations/catalog/actions-s3/index.md +++ b/src/connections/destinations/catalog/actions-s3/index.md @@ -25,6 +25,12 @@ The AWS S3 (Actions) destination enhances this capability by introducing configu * **Enhanced Delivery Controls**. The destination provides advanced options for batch size controls and file naming conventions. These controls can help optimize efficiency and simplify data retrieval workflows. +## Supported Integrations +The AWS S3 (Actions) Destination supports the following Segment features as supported native Destination integration points: +* [Reverse ETL](/docs/connections/reverse-etl/) +* [Classic and Linked Audiences](/docs/engage/audiences/) +* [Connections](/docs/connections/) + ## Getting started Setting up the AWS S3 (Actions) destination is a straightforward process designed to help you configure and deploy standardized event data to your Amazon S3 bucket. Follow these steps to get started: @@ -69,7 +75,7 @@ To set up the IAM role to properly authorize Segment with the AWS S3 (Actions) d "Effect": "Allow", "Principal": { "AWS": - "arn:aws:iam::595280932656:role/customer-s3-prod-action-destination-access" + "arn:aws:iam::595280932656:role/customer-s3-prod-action-destination-access" }, "Action": "sts:AssumeRole", "Condition": { @@ -81,8 +87,9 @@ To set up the IAM role to properly authorize Segment with the AWS S3 (Actions) d ] } ``` -## Step 2: Add the AWS S3 (Actions) Destination in Segment -To finish the configuration, enable the AWS S3 (Actions) Destination in your workspace. + +### Step 2: Add the AWS S3 (Actions) Destination in Segment +To finish the setup, enable the AWS S3 (Actions) Destination in your workspace: 1. Add the **AWS S3 (Actions)** destination from the Destinations tab of the catalog. 2. Select the data source you want to connect to the destination. @@ -93,8 +100,15 @@ To finish the configuration, enable the AWS S3 (Actions) Destination in your wor * Enter the ARN of the IAM role you created above. The ARN should follow the format `arn:aws:iam::ACCOUNT_ID:role/ROLE_NAME.` * Enter the IAM External ID, which is a value set in the Trust Relationship under your AWS IAM Role. 5. Enable the destination. -6. Verify the Segment data is stored in the S3 bucket by navigating to the `/` in the AWS console. {% include components/actions-fields.html settings="true"%} +### Step 3: Configure the AWS S3 (Actions) Destination mappings +To finish the configuration, add mappings to your new AWS S3 (Actions) Destination: +1. Add a new **Sync to S3** Action into the destination. +2. Define the Event Trigger. If multiple types are accepted in the Event Trigger, the generated files will automatically be split by type in S3 (for example, you might have a Track events file and an Identify events file). +3. Configure the Column Mappings. If you don't need any of the default columns, leave the value blank. You can also choose to add new mapping fields to set up customized columns as needed. +4. Configure any additional settings as required. +5. Enable the Mapping. +6. Verify that Segment is sending data to your S3 bucket by navigating to `/` in the AWS console. \ No newline at end of file diff --git a/src/connections/destinations/catalog/actions-sendgrid/index.md b/src/connections/destinations/catalog/actions-sendgrid/index.md index 666c4a5db0..102a99527b 100644 --- a/src/connections/destinations/catalog/actions-sendgrid/index.md +++ b/src/connections/destinations/catalog/actions-sendgrid/index.md @@ -5,9 +5,6 @@ hide-dossier: true redirect_from: - "/connections/destinations/catalog/sendgrid-marketing-campaigns/" id: 631a6f32946dd8197e9cab66 -hide_action: - - id: 2NyqxNN5TGJa1CP5xEYeLu - name: "Send email with Dynamic Template" --- diff --git a/src/connections/destinations/catalog/antavo/index.md b/src/connections/destinations/catalog/antavo/index.md new file mode 100644 index 0000000000..1ecd5eeb07 --- /dev/null +++ b/src/connections/destinations/catalog/antavo/index.md @@ -0,0 +1,21 @@ +--- +title: Antavo (Actions) Destination +hidden: true +--- + +The Antavo (Actions) Destination allows you to sync profile updates in Segment and trigger loyalty events. +This destination is maintained by Antavo. For any issues with the destination, [contact the Antavo support team](mailto:support@antavo.com). + +## Getting started + +1. From your workspace's [Destination catalog page](https://app.segment.com/goto-my-workspace/destinations/catalog){:target="_blank"} search for **Antavo (Actions)**. +2. Click **Add Destination**. +3. Select an existing Source to connect to Antavo (Actions). +4. Log in to Antavo and go to the **Settings > API Settings** and copy your Antavo **API key**. +5. Paste the **API Key** in the destination settings in Segment. +6. Configure your mappings to set events you want to sync to Antavo. You can choose from 2 actions: Send Loyalty Event and Send Profile Update. + - If the multi-account extension is enabled in Antavo, make sure to include the account ID. + - If customer attributes are included in the Data section - make sure attribute names match your Antavo settings. +7. If you haven’t configured the Segment integration in Antavo, go to the **Modules** menu and enable the Twilio Segment Extension in Antavo. + +{% include components/actions-fields.html %} diff --git a/src/connections/destinations/catalog/bucket/index.md b/src/connections/destinations/catalog/bucket/index.md index 158b8d0134..fd6d353eb7 100644 --- a/src/connections/destinations/catalog/bucket/index.md +++ b/src/connections/destinations/catalog/bucket/index.md @@ -4,7 +4,13 @@ rewrite: true id: 5fabc0b00f88248bbce4db48 --- -[Bucket](https://bucket.co/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="blank"} is feature-focused analytics. Bucket empowers software teams with a repeatable approach to shipping features that customers crave. +[Bucket](https://bucket.co/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="blank"} is feature flagging that’s purpose-built for B2B. + + +With Bucket, you can: +- Release features gradually with simple flags. +- Gate features based on customer subscriptions. +- Iterate fast with adoption metrics and feedback. This destination is maintained by Bucket. For any issues with the destination, [contact the Bucket Support team](mailto:support@bucket.co). @@ -15,7 +21,7 @@ This destination is maintained by Bucket. For any issues with the destination, [ 1. From the Destinations catalog page in the Segment App, click **Add Destination**. 2. Search for "Bucket" in the Destinations Catalog, and select the Bucket destination. 3. Choose which Source should send data to the Bucket destination. -4. Go to [Bucket's Settings](https://app.bucket.co){:target="blank"} and find and copy the "Publishable Key" under Settings. +4. Go to [Bucket's Environment Settings](https://app.bucket.co/envs/current/settings/app-environments){:target="blank"} and find and copy the "Publishable Key" for the Production environment. 5. Enter the "Publishable Key" as "Publishable Key" in the "Bucket" destination settings in Segment. ## Identify diff --git a/src/connections/destinations/catalog/facebook-pixel/index.md b/src/connections/destinations/catalog/facebook-pixel/index.md index 6071fec508..4f8dbd7080 100644 --- a/src/connections/destinations/catalog/facebook-pixel/index.md +++ b/src/connections/destinations/catalog/facebook-pixel/index.md @@ -245,5 +245,9 @@ Facebook Pixel events typically don't display in real-time within the Facebook A Segment does not handle nested properties that need to be blocklisted, including the standard PII properties. If you have properties you would like to blocklist, you can use [destination filters](/docs/connections/destinations/destination-filters/) to drop those properties before they are sent downstream. +### Mapping `revenue` to `value` + +Segment pre-maps `revenue` or `total` to `value`. If you have a custom `value` property, it's overwritten with the value from `revenue` or `total`, or it appears as '0.00' if those two properties aren't present. If you have a `value` property, you can use a [destination middleware](/docs/connections/sources/catalog/libraries/website/javascript/middleware/#using-destination-middlewares) or [destination plugin](/docs/connections/sources/catalog/libraries/website/javascript/#advanced-plugin-api){:target="_blank"} to transform the name before it is sent downstream to avoid any data loss. + {% include content/client-side-script-unverified.md %} diff --git a/src/connections/destinations/catalog/marketo-v2/index.md b/src/connections/destinations/catalog/marketo-v2/index.md index c3e01de9a0..635c934faa 100644 --- a/src/connections/destinations/catalog/marketo-v2/index.md +++ b/src/connections/destinations/catalog/marketo-v2/index.md @@ -162,6 +162,9 @@ Analytics.track( - **Primary Field**. When creating a Custom Activity in Marketo, you have to set a Primary Field. If you are unsure which field was set as the primary field, when you are looking at the list of fields for your Custom Activity in Marketo, there will be a red star next to your Primary Field. ![A screenshot of the Fields tab inside of the Marketo Custom Activities page.](images/cZuvsHeaepX+.png) +> info "" +> You can't map fields nested in objects as Marketo Custom Activity property names. You must flatten any objects you may need to access data from either before you send it to Segment, or while using an [Insert Function](/docs/connections/functions/insert-functions/). + ## Page When you call [`Page`](/docs/connections/spec/page/), Segment uses [Marketo's Munchkin.js `visitWebPage` method](http://developers.marketo.com/javascript-api/lead-tracking/api-reference/#munchkin_visitwebpage){:target="_blank"}. The URL is built from your `.page()` event and properties object into the form Marketo expects, so no need to worry about doing that yourself. diff --git a/src/connections/functions/destination-functions.md b/src/connections/functions/destination-functions.md index 915f9f6d7d..0efa9fc2fa 100644 --- a/src/connections/functions/destination-functions.md +++ b/src/connections/functions/destination-functions.md @@ -83,6 +83,8 @@ To change which event type the handler listens to, you can rename it to the name {% include content/functions/errors-and-error-handling.md %} +You can incorporate a a `try-catch` block to ensure smooth operation of functions even when fetch calls fail. This allows for the interception of any errors during the API call, enabling the application of specific error handling procedures, such as error logging for future debugging, or the assignment of fallback values when the API call is unsuccessful. By positioning the continuation logic either outside the `try-catch` block or within a `finally` block, the function is guaranteed to proceed with its execution, maintaining its workflow irrespective of the outcome of the API call. + You can read more about [error handling](#destination-functions-logs-and-errors) below. ### Runtime and dependencies diff --git a/src/connections/functions/insert-functions.md b/src/connections/functions/insert-functions.md index c43b130209..07211091be 100644 --- a/src/connections/functions/insert-functions.md +++ b/src/connections/functions/insert-functions.md @@ -506,7 +506,11 @@ Insert Functions are only supported by Cloud Mode (server-side) destinations and ##### Can I connect an insert function to multiple destinations? -Yes, an insert function can be connected to multiple destinations. +Yes, you can connect an insert function to multiple destinations. + +##### Can I connect multiple insert functions to one destination? + +No, you can only connect one insert function to a destination. ##### Can I have destination filters and a destination insert function in the same connection? diff --git a/src/connections/reverse-etl/setup.md b/src/connections/reverse-etl/setup.md index ba795eb770..c1a7a201ac 100644 --- a/src/connections/reverse-etl/setup.md +++ b/src/connections/reverse-etl/setup.md @@ -50,6 +50,10 @@ Models define sets of data you want to sync to your Reverse ETL destinations. A ### dbt model Use Segment's dbt extension to centralize model management and versioning. Users who set up a BigQuery, Databricks, Postgres, Redshift, or Snowflake source can use Segment's [dbt extension](/docs/segment-app/extensions/dbt/) to centralize model management and versioning, reduce redundancies, and run CI checks to prevent breaking changes. +> success " " +> If you use dbt Cloud with Reverse ETL, you can [create up to 5 mappings](#step-4-create-mappings) that use the sync strategy **dbt Cloud**, which extracts data from your warehouse and syncs it with your destination after a job in dbt Cloud is complete. + + ## Step 3: Add a destination In Reverse ETL, destinations are the business tools or apps you use that Segment syncs the data from your warehouse to. A model can have multiple destinations. diff --git a/src/connections/sources/catalog/libraries/server/csharp/index.md b/src/connections/sources/catalog/libraries/server/csharp/index.md index 9281e8cab4..493245910a 100644 --- a/src/connections/sources/catalog/libraries/server/csharp/index.md +++ b/src/connections/sources/catalog/libraries/server/csharp/index.md @@ -56,6 +56,9 @@ To get started with the Analytics-CSharp library: var analytics = new Analytics(configuration); ``` +> info "" +> Segment's SDK is designed to be disposable, meaning Segment disposes of objects when the analytics instance is disposed. Segment avoids using singletons for configurations or HTTP clients to prevent memory management issues. If you want to use singletons, create your own HTTP client provider with a singleton HTTP client for better control and management. + | Option Name | Description | |-----------------------------|---------------| | `writeKey` *required* | This is your Segment write key. | diff --git a/src/connections/sources/catalog/libraries/server/go/index.md b/src/connections/sources/catalog/libraries/server/go/index.md index bd8c279e48..e6fe6f457a 100644 --- a/src/connections/sources/catalog/libraries/server/go/index.md +++ b/src/connections/sources/catalog/libraries/server/go/index.md @@ -41,11 +41,17 @@ That will create a `client` that you can use to send data to Segment for your so The default initialization settings are production-ready and queue 20 messages before sending a batch request, and a 5 second interval. ### Regional configuration -For Business plans with access to Regional Segment, you can use the host configuration parameter to send data to the desired region: +For Business plans with access to Regional Segment, you can use the endpoint configuration parameter to send data to the desired region: -Oregon (Default) — api.segment.io/ -Dublin — events.eu1.segmentapis.com +- Oregon (Default) — https://api.segment.io +- Dublin — https://events.eu1.segmentapis.com +Example configuration for EU region: +```go +client, err := analytics.NewWithConfig(writeKey, analytics.Config{ + Endpoint: "https://events.eu1.segmentapis.com", +}) +``` ## Identify > note "" diff --git a/src/connections/sources/catalog/libraries/website/javascript/cookie-validity-update.md b/src/connections/sources/catalog/libraries/website/javascript/cookie-validity-update.md index 39ab1647f2..4a647e6eda 100644 --- a/src/connections/sources/catalog/libraries/website/javascript/cookie-validity-update.md +++ b/src/connections/sources/catalog/libraries/website/javascript/cookie-validity-update.md @@ -43,6 +43,22 @@ analytics.load('writeKey', { } }) ``` + +To set cookie values using the [NPM package](https://github.com/segmentio/analytics-next/tree/master/packages/browser){:target="_blank"}, use the following code snippet: + +```js + analytics = AnalyticsBrowser.load({ + writeKey: 'writeKey' + }, { + cookie: { + domain: 'sub.site.example', + maxage: 7, // 7 days + path: '/', + sameSite: 'Lax', + secure: true + } + }) +``` > info "" > Chrome has a maximum limit of 400 days for cookies. If a value is set beyond that, then Chrome sets the upper limit to 400 days instead of rejecting it. Visit Chrome's [docs](https://developer.chrome.com/blog/cookie-max-age-expires/){:target="blank"} to learn more. diff --git a/src/connections/sources/catalog/libraries/website/javascript/index.md b/src/connections/sources/catalog/libraries/website/javascript/index.md index a247af0176..44e3a40650 100644 --- a/src/connections/sources/catalog/libraries/website/javascript/index.md +++ b/src/connections/sources/catalog/libraries/website/javascript/index.md @@ -838,6 +838,28 @@ So, for example, if somebody follows the link with above query string to your si Whenever the UTM parameters are no longer a part of the URL, Segment no longer includes them. For example, if the user goes to a new page within your website which does not contain these parameters, they will not be included in subsequent events. UTM parameters are non-persistent by default as they could potentially cause data accuracy problems. Here's an example of why: Say a user clicks on an ad and lands on your site. He navigates around and bookmarks an internal page - or maybe shares a link with a friend, who shares it with another friend. All those links would then point back to the same test utm_source as the initial referrer for any purchase. +Segment doesn't validate UTM parameter names. This design supports the flexibility to track both standard parameters (for example, utm_source, utm_medium) and custom parameters defined by users. As a result, all parameters present in the URL collected as is, and are added to the context field without checks for naming conventions or validity. + +If you want to ensure that only standard UTM parameters (such as, utm_source, utm_medium, utm_campaign, utm_content, utm_term) are included in the context.campaign object, you can implement [Source middleware](/docs/connections/sources/catalog/libraries/website/javascript/middleware/) in your Analytics.js setup. + +For example: + +```js +window.analytics.addSourceMiddleware(({ payload, next }) => { + if (payload.obj.context?.campaign) { + const allowedFields = ["source", "medium", "term", "campaign", "content"]; + const campaign = payload.obj.context.campaign; + Object.keys(campaign).forEach(key => { + if (!allowedFields.includes(key)) { + delete campaign[key]; + } + }); + } + next(payload); +}); +``` +This middleware filters out any non-standard parameters from the `context.campaign` object before they're sent to Segment or forwarded to your enabled destinations. + ## Analytics.js performance The Analytics.js library and all Destination libraries are loaded with the [HTML script `async` tag](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/script#attr-async){:target="_blank"}. This also means that Segment fires methods asynchronously, so you should adjust your code accordingly if you require that events be sent from the browser in a specific order. diff --git a/src/connections/storage/warehouses/schema.md b/src/connections/storage/warehouses/schema.md index e8eaeaafc7..4c35f49b72 100644 --- a/src/connections/storage/warehouses/schema.md +++ b/src/connections/storage/warehouses/schema.md @@ -132,7 +132,7 @@ The table below describes the schema in Segment Warehouses: | `.pages` | A table with your `page` method calls. This table includes the `properties` you record for pages as top-level columns, for example `.pages.title`. | | `.screens` | A table with your `screen` method calls. This table includes `properties` you record for screens as top-level columns, for example `.screens.title`. | | `.tracks` | A table with your `track` method calls. This table includes standardized properties that are all common to all events: `anonymous_id`, `context_*`, `event`, `event_text`, `received_at`, `sent_at`, and `user_id`. This is because every event that you send to Segment has different properties. For querying by the custom properties, use the `.` tables instead. | -| `.` | For `track` calls, each event like `Signed Up` or `Order Completed` also has it's own table (for example. `initech.clocked_in`) with columns for each of the event's distinct `properties` (for example. `initech.clocked_in.time`). | +| `.` | For `track` calls, each event like `Signed Up` or `Order Completed` also has its own table (for example. `initech.clocked_in`) with columns for each of the event's distinct `properties` (for example. `initech.clocked_in.time`). | ## Identifies table diff --git a/src/engage/audiences/linked-audiences-limits.md b/src/engage/audiences/linked-audiences-limits.md index fa8e777feb..97adbb5587 100644 --- a/src/engage/audiences/linked-audiences-limits.md +++ b/src/engage/audiences/linked-audiences-limits.md @@ -31,11 +31,12 @@ Name | Limit | Details ---- | ----- | -------- RETL row limit | 150 million | The audience compute fails if the total output exceeds the limit. RETL column limit | 500 columns | The audience compute fails if the number of columns exceeds the limit. -Global concurrent audience runs | 5 total within any given space | New audience runs are queued once the limit is reached and will start execution once prior audience runs complete. +Global concurrent audience runs | 5 total within any given space | New audience runs are queued once the limit is reached and will start execution once prior audience runs complete. If you need a higher global concurrent audience runs limit, contact [friends@segment.com](mailto:friends@segment.com){:target="_blank"}. Event Size | 32 KB | Segment doesn’t emit messages for profiles whose total related entities and enrichments exceed the limit. Data Graph depth | 6 | You can't save a Data Graph if you exceed the limit. Preview size | 3K rows | The maximum number of rows you can have to generate a preview. The preview fails if you bring back too many entities. Entity value type ahead cache | Up to 100 unique values | The maximum number of entity values Segment stores in cache. Entity columns | Up to 1000 unique values | The maximum number of entity property columns Segment surfaces in the condition builder. -Run frequency | 15 minutes (this is the fastest time) | You can’t configure more frequency syncs. You can select **Run Now** to trigger runs, but you’re limited by Profiles Sync for when new data syncs back to the data warehouse. +Run frequency | 15 minutes (this is the fastest time) | You can’t configure more frequency syncs. You can select **Run Now** to trigger runs, but you’re limited by Profiles Sync for when new data syncs back to the data warehouse. +Destination Mappings | Up to 100 mappings | You can set up to 100 action destination mappings per destination instance. diff --git a/src/engage/journeys/event-triggered-journeys.md b/src/engage/journeys/event-triggered-journeys.md index 9b4010a2b8..0816956535 100644 --- a/src/engage/journeys/event-triggered-journeys.md +++ b/src/engage/journeys/event-triggered-journeys.md @@ -1,7 +1,6 @@ --- title: Event-Triggered Journeys plan: engage-foundations -hidden: true --- With Event-Triggered Journeys, you can build real-time, event-based marketing workflows to automate and personalize customer journeys. @@ -37,15 +36,48 @@ To set up an event-triggered journey: 3. Give your new journey a name and, optionally, a description. 4. Select entry event: - Choose the event that will trigger user entry into the journey. - - (*Optional*) Use an audience filter to restrict entry to users who are already part of a specific audience. + - (*Optional*) Use an audience filter to restrict entry to users who are already part of a specific audience when they perform the triggering event. - (*Optional*) Apply filters based on event property values to refine entry conditions. For example, enter only if `{property} = value A, value B, or value C`. 5. Configure entry rules: - **Re-enter every time event occurs** (*default*): Users enter the journey each time they trigger the specified event. - **Enter one time**: Users enter the journey once only, regardless of repeated event triggers. -6. **If you chose Re-enter every time event occurs in Step 5**, select a [unique identifier](#unique-identifiers). -7. Configure event delivery to destinations by selecting a destination or setting up a custom destination function. -8. Preview the contextual payload that Segment will send to your destination(s). -9. After you've finished setting up your journey, click **Publish**, then click **Publish** again in the popup. +6. **If you chose Re-enter every time event occurs in Step 5**, select a [unique identifier](#unique-identifiers). +7. Build your journey using logical operators. +8. Configure event delivery to destinations by selecting a destination or setting up a custom destination function. +9. Preview the contextual payload that Segment will send to your destination(s). +10. After you've finished setting up your journey, click **Publish**, then click **Publish** again in the popup. + +### Send data to downstream destinations + +When a journey instance reaches a **Send to Destination** step, you can configure how data is sent to your desired destination. This step allows you to define where the data goes, what actions are performed, and how information is mapped, giving you control over the integration. Event-Triggered Journeys currently supports all [Actions Destinations](docs/connections/destinations/actions/). + +For other destinations or more complex logic, you can use [Destination Functions](/docs/connections/functions/destination-functions/). + +#### Configure the Destination Send Step + +1. **Select a Destination** + Choose the destination where you want to send data. Currently, only [Actions Destinations](docs/connections/destinations/actions/) and [Destination Functions](/docs/connections/functions/destination-functions/) are supported. + +2. **Choose an Action** + Specify the action to take within the selected destination. For example, you might update a user profile, trigger an email, or log an event. + +3. **Define the Event Name** + Add a descriptive event name to send to your destination. + +4. **Define the Payload Attributes** + - The **journey context** provides a set of attributes from the entry event or events used in the Hold Until operator that can be included in the payload. + - You may also add a user's profile traits to the destination payload. + - Review the available attributes and decide which ones to include in your data send. + +5. **Map Attributes to Destination Keys** + - Use the mapping interface to link payload attributes to the appropriate keys required by the destination. + - For example, map `user_email` from the journey context to the `email` field expected by the destination. + +6. **Test the Integration** + - Send a **test event** to validate the configuration. + - Ensure that the data is received correctly by the destination and mapped as expected. + +When a journey reaches this step, the Segment prepares and sends the payload based on your configuration. The integration ensures compatibility with the selected destination’s API, allowing seamless data transfer and execution of the specified action. ### Journey setup configuration options @@ -62,11 +94,10 @@ When you select **Re-enter every time event occurs** when you create an event-tr For example, in an abandonment journey, suppose a user starts two applications (like `application_started`), each with a different `application_id`. By setting `application_id` as the unique identifier, Segment can match follow-up events (like `application_completed`) to the correct application journey. As a result, each journey instance only receives the completion event for its specific application. -#### Send data to downstream destinations - -Event-Triggered Journeys lets you send journey data to supported destinations, facilitating real-time, personalized messaging. Event-Triggered Journeys supports the [Braze (Actions)](/docs/connections/destinations/catalog/actions-braze-cloud/), [Customer.io (Actions)](/docs/connections/destinations/catalog/actions-customerio/), and [Iterable (Actions)](/docs/connections/destinations/catalog/actions-iterable/) destinations. +### Notes and limitations -For other destinations, you can use [Destination Functions](/docs/connections/functions/destination-functions/) to run additional logic, like enriching with [Profile API traits](/docs/unify/profile-api/) or filtering the payload. +- **Supported destinations:** Only Actions Destinations in the Segment catalog are supported. +- **Data mapping:** Ensure all required keys for the destination are properly mapped to avoid errors. ## Best practices @@ -87,7 +118,7 @@ Segment built Event-Triggered Journeys to respond instantly to events, offering - **Entry event requirements**: The entry event you use must already exist in your Segment workspace for it to appear as a selection in journey setup. Make sure that you've already created the event before setting up your journey. - **Event property filters**: You can filter event properties using the `equals` or `equals any of` operators. When you apply multiple conditions, filters operate with `AND` logic, meaning all conditions must be true for the event to trigger entry into the journey. - **Audience filtering**: You can only use active, pre-existing audience records as filters. For more complex filtering, like specific profile traits or multiple audiences, first [create the audience](/docs/engage/audiences/#building-an-audience) in **Engage > Audiences**, then apply it as a filter once it’s live. -- **Destination options**: While Event-Triggered Journeys support several [actions-based destinations](/docs/connections/destinations/actions/) (like Braze, Customer.io, and Iterable) you can only add one destination for each journey instance. For other destinations, use a Destination Function to apply custom logic to the payload. +- **Destination options**: While Event-Triggered Journeys support all [actions-based destinations](/docs/connections/destinations/actions/) and Destination Functions, you can only add one destination per Send to Destination step. If you need to send to multiple destinations, you can use multiple Send to Destination steps. - **Event payload structure**: Each payload sent to a destination includes a unique key to identify the specific send step within the journey, rather than the journey instance itself. You can also set a custom event name to make it easier to identify the specific event instance you want to track in your destination. - **Editing and versioning**: After you publish an event-triggered journey, you won't be able to edit it. To modify a journey, create a new journey. - **Real-time delivery**: Event-Triggered Journeys aim for an expected delivery time of under 5 minutes from the moment an event is performed to when the payload reaches the destination, assuming there is no delay step in the journey. However, external factors outside of Segment's control may occasionally introduce latency. diff --git a/src/engage/journeys/journey-context.md b/src/engage/journeys/journey-context.md index 4466399871..a6d8410e5a 100644 --- a/src/engage/journeys/journey-context.md +++ b/src/engage/journeys/journey-context.md @@ -1,7 +1,6 @@ --- title: Journey Context plan: engage-foundations -hidden: true --- [Event-Triggered Journeys](/docs/engage/journeys/event-triggered-journeys/) redefine how you orchestrate and personalize customer experiences. diff --git a/src/guides/usage-and-billing/startup-program.md b/src/guides/usage-and-billing/startup-program.md index 1a0eff242d..34550e8c16 100644 --- a/src/guides/usage-and-billing/startup-program.md +++ b/src/guides/usage-and-billing/startup-program.md @@ -2,7 +2,7 @@ title: Segment Startup Program --- -Segment offers a **Startup Program** to enable early startups to track data correctly and easily test the marketing and analytics tools necessary to grow their business. The program is open to any early-stage startup that meets the following eligibility requirements: +Segment offers a **Startup Program** to enable early startups to track data and test the marketing and analytics tools necessary to grow their business. The program is open to any early-stage startup that meets the following eligibility requirements: - Incorporated less than two years ago @@ -18,6 +18,9 @@ The Segment Startup Program includes three components: Interested companies can apply on the [Startup Program](http://segment.com/industry/startups){:target="_blank”} site. +> info "Application deadline" +> Effective January 6, 2025, Segment will no longer accept applications for the Segment Startup Program. Applications submitted before 11:59 PM PT on December 5, 2024 will be reviewed and honored. Any applications received after this deadline won't be accepted. There will be no exceptions. + *Can vary based on affiliated accelerator and VC partners. diff --git a/src/protocols/faq.md b/src/protocols/faq.md index d91b5cdb6e..42c0c54683 100644 --- a/src/protocols/faq.md +++ b/src/protocols/faq.md @@ -148,6 +148,12 @@ That being said, there are plenty of scenarios where the reactive Schema functio Blocked events are blocked from sending to all Segment Destinations, including warehouses and streaming Destinations. When an Event is blocked using a Tracking Plan, it does not count towards your MTU limit. They will, however, count toward your MTU limit if you enable [blocked event forwarding](/docs/protocols/enforce/forward-blocked-events/) in your Source settings. +### If I omit unplanned properties or properties that generate JSON schema violations, what happens to them? + +Segment doesn't store unplanned properties and properties omitted due to JSON Schema Violations in Segment logs. Segment drops omitted properties from the events. You can find the omitted properties in the `context.violations` object of an event payload. If you forward Violations to a new source, then you can also see the omitted properties in the Violation Generated event under `violationField` in the `properties` object. + +Segment only stores fully blocked events for 30 days. + ### Why am I seeing unplanned properties/traits in the payload when violations are triggered, despite using schema controls to omit them? If you're seeing unplanned properties/traits in your payload despite using Schema Controls, you might want to select a new degree of blocking controls. diff --git a/src/unify/faqs.md b/src/unify/faqs.md index 251af20490..189654b8de 100644 --- a/src/unify/faqs.md +++ b/src/unify/faqs.md @@ -9,22 +9,22 @@ Yes, Identity Graph supports multiple external IDs. Identity Graph automatically collects a rich set of external IDs without any additional code: -1. Device level IDs (ex: `anonymous_id`, `ios.idfa` and `android.id`) -2. Device token IDs (ex: `ios.push_token` and `android_push_token`) -3. User level IDs (ex: `user_id`) +1. Device level IDs (example: `anonymous_id`, `ios.idfa` and `android.id`) +2. Device token IDs (example: `ios.push_token` and `android_push_token`) +3. User level IDs (example: `user_id`) 4. Common external IDs (`email`) -5. Cross domain analytics IDs (`cross_domain_id`) +5. Cross-domain analytics IDs (`cross_domain_id`) -If you want Identity Graph to operate on a different custom ID, you can pass it in using `context.externalIds` on an `identify()` or `track()`. If you're interested in this feature, contact your CSM to discuss the best way to implement this feature. +If you want Identity Graph to operate on a different custom ID, you can pass it in using `context.externalIds` on an [Identify](/docs/connections/spec/identify/) or [Track call](/docs/connections/spec/identify/). If you're interested in this feature, contact your CSM to discuss the best way to implement this feature. ## How does Unify handle identity merging? -Each incoming event is analyzed and external IDs are extracted (`user_id`, `anonymous_id`, `email`). The simplified algorithm works as follows: +Segment analyzes each incoming event and extracts external IDs (like `user_id`, `anonymous_id`, `email`). The simplified algorithm works as follows: 1. Segment first searches the Identity Graph for incoming external IDs. 2. If Segment finds no matching profile(s), it creates one. -3. If Segment finds one profile, it merges the incoming event with that profile. (This means that Segment adds the external IDs on the incoming message and resolves the event to the profile.) +3. If Segment finds one profile, it merges the incoming event with that profile. This means that Segment adds the external IDs on the incoming message and resolves the event to the profile. 4. If Segment finds multiple matching profiles, Segment applies the identity resolution settings for merge protection. Specifically, Segment uses identifier limits and priorities to add the correct identifiers to the profile. -5. Segment then applies [limits](/docs/unify/profile-api-limits/) to ensure profiles remain under these limits. Segment doesn't add any further merges or mappings if the profile is at either limit, but event resolution for the profile will continue. +5. Segment then [applies limits](/docs/unify/profile-api-limits/) to ensure profiles remain under these limits. Segment doesn't add any further merges or mappings if the profile is at either limit, but event resolution for the profile will continue. {% comment %} @@ -48,8 +48,8 @@ If two merged user profiles contain conflicting profile attributes, Segment sele Any of the external IDs can be used to query a profile. When a profile is requested, Segment traverses the merge graph and resolves all merged profiles. The result is a single profile, with the latest state of all traits, events, and identifiers. -### Can ExternalID's be changed or removed from the profiles? -No. As the Identity Graph uses ExternalIDs, they remain for the lifetime of the user profile. +### Can external IDs be changed or removed from the profiles? +No. As the Identity Graph uses external IDs, they remain for the lifetime of the user profile. ### Can I delete specific events from a user profile in Unify? No. Alternatively, you may delete the entire user profile from Segment using a [GDPR deletion request](/docs/privacy/user-deletion-and-suppression/). @@ -59,3 +59,26 @@ Segment determines the Monthly Tracked Users (MTUs) count by the number of uniqu ### What is the event lookback period on the Profile Explorer? The [Profile Explorer](/docs/unify/#profile-explorer) retains event details for a period of up to 2 weeks. If you need event information beyond this timeframe, Segment recommends using [Profiles Sync](/docs/unify/profiles-sync/overview/) for comprehensive event analysis and retention. + +### Can I remove a trait from a user profile? + +Yes, you can remove a trait from a user profile by sending an Identify event with the trait value set to `null` in the traits object from one of your connected sources. For example: + +```json +{ + "traits": { + "trait1": null + } +} +``` +Setting the trait value to an empty string won't remove the trait, like in this example: + +```json +{ + "traits": { + "trait2": "" + } +} +``` + +Instead, this updates the trait to an empty string within the user profile.