From 9cd095c2b7b8f0c1a49e43e21fc4976e58a3582b Mon Sep 17 00:00:00 2001 From: Mohammad nasser Date: Thu, 2 Oct 2025 19:42:01 +0300 Subject: [PATCH 1/8] add docs --- .../catalog/actions-fullsession/index.md | 91 +++++++++++++++++++ 1 file changed, 91 insertions(+) create mode 100644 src/connections/destinations/catalog/actions-fullsession/index.md diff --git a/src/connections/destinations/catalog/actions-fullsession/index.md b/src/connections/destinations/catalog/actions-fullsession/index.md new file mode 100644 index 0000000000..120193ff78 --- /dev/null +++ b/src/connections/destinations/catalog/actions-fullsession/index.md @@ -0,0 +1,91 @@ +--- +title: FullSession (Actions) Destination +--- + +{% include content/plan-grid.md name="actions" %} + +[FullSession](https://fullsession.io/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank"} provides user behavior analytics software that helps you visualize all user interactions, analyze trends and patterns with laser precision, and optimize your website for peak performance. The Segment integration for FullSession helps accurately identify your customers and track their behavior within the FullSession dashboard. + +This destination is maintained by FullSession. For any issues with the destination, [contact their Support team](mailto:support@fullsession.com). + +## Getting started + +1. From your workspace's [Destination catalog page](https://app.segment.com/goto-my-workspace/destinations/catalog){:target="_blank"} search for "FullSession". +2. Select FullSession and click **Add Destination**. +3. Select an existing Source to connect to FullSession (Actions). +4. Go to the [FullSession setup page](https://app.fullsession.io/settings/setup){:target="_blank"} and copy your **Customer ID** (starts with `cus_`). +5. Enter the **Customer ID** in the FullSession destination settings in Segment. + +and then Analytics.js starts asynchronously loading FullSession's recording snippet on your page and sending data. + +## Identify User + +If you're not familiar with the Segment Specs, take a look to understand what the [identify method](/docs/connections/spec/identify/) does. Identify calls sent to Segment will be transformed and sent to FullSession's identify method to help you track and segment users in your session recordings. + +An example call which does not include a `userId` will send FullSession the value of the `anonymousId` and would look like: + +```javascript +analytics.identify(); +``` + +If an `identify` call does contain a `userId`, that will be the ID sent along to FullSession. + +```javascript +analytics.identify("userId"); +``` + +In addition, Segment will send over along any traits included in the `identify` call. The example call below would send over both `plan` and `logins`. + +```javascript +analytics.identify("userId123", { + plan: "premium", + logins: 5 +}); +``` + +### Specifying user name and email + +Both `email` and `name` are special traits that will be passed to FullSession to be used in their interface for better user identification. These traits are optional. + +```javascript +analytics.identify("userId123", { + email: "john.doe@example.com", + name: "John Doe" +}); +``` + +## Record Event + +If you're not familiar with the Segment Specs, take a look to understand what the [track method](/docs/connections/spec/track/) does. Track calls sent to Segment will be automatically passed directly to FullSession using their event tracking method, including all the properties passed in the event. + +An example call would look like: + +```javascript +analytics.track('Product Purchased', { + order_ID: '2969302398', + category: 'boots', + product_name: 'yellow_cowboy_boots', + price: 99.95, + currency: 'EUR' +}); +``` + +This allows you to correlate specific user actions with session recordings, making it easier to analyze user behavior patterns and identify conversion bottlenecks. + +## Visit Page + +If you're not familiar with the Segment Specs, take a look to understand what the [page method](/docs/connections/spec/page/) does. Page calls sent to Segment will be automatically passed to FullSession to set page-specific attributes and properties. + +An example call would look like: + +```javascript +analytics.page('Product Page', { + category: 'Electronics', + name: 'iPhone 15', + price: 999 +}); +``` + +This helps you understand how users navigate through your site and which pages are most important in their journey. + +{% include components/actions-fields.html %} \ No newline at end of file From dfef9f3277849066d65b627ca44789fccbec2341 Mon Sep 17 00:00:00 2001 From: Mohammad nasser <76165108+mohamadhase@users.noreply.github.com> Date: Mon, 13 Oct 2025 23:19:32 +0300 Subject: [PATCH 2/8] Update src/connections/destinations/catalog/actions-fullsession/index.md Co-authored-by: Joe Ayoub <45374896+joe-ayoub-segment@users.noreply.github.com> --- .../catalog/actions-fullsession/index.md | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/src/connections/destinations/catalog/actions-fullsession/index.md b/src/connections/destinations/catalog/actions-fullsession/index.md index 120193ff78..4119f30694 100644 --- a/src/connections/destinations/catalog/actions-fullsession/index.md +++ b/src/connections/destinations/catalog/actions-fullsession/index.md @@ -10,13 +10,14 @@ This destination is maintained by FullSession. For any issues with the destinati ## Getting started -1. From your workspace's [Destination catalog page](https://app.segment.com/goto-my-workspace/destinations/catalog){:target="_blank"} search for "FullSession". -2. Select FullSession and click **Add Destination**. -3. Select an existing Source to connect to FullSession (Actions). -4. Go to the [FullSession setup page](https://app.fullsession.io/settings/setup){:target="_blank"} and copy your **Customer ID** (starts with `cus_`). -5. Enter the **Customer ID** in the FullSession destination settings in Segment. +1. From your workspace’s [Destination Catalog](https://app.segment.com/goto-my-workspace/destinations/catalog){:target="_blank"}, search for **“FullSession.”** +2. Select **FullSession**, then click **Add Destination**. +3. Choose an existing **JavaScript Source** to connect with FullSession (Actions). +4. Navigate to the [FullSession Setup](https://app.fullsession.io/settings/setup){:target="_blank"} page and copy your **Customer ID** (it begins with `cus_`). +5. Paste the **Customer ID** into the **FullSession Destination settings** in Segment. +6. Before enabling the destination, open the **Mappings** tab and configure the mappings to ensure the correct data is captured. +7. Once your mappings are configured and enabled, go to the **Settings** tab and enable the Destination. Segment will then automatically load the **FullSession recording snippet** in the user’s browser. -and then Analytics.js starts asynchronously loading FullSession's recording snippet on your page and sending data. ## Identify User From 569aa1999f0181a0079d34c4bedeb813da5807e6 Mon Sep 17 00:00:00 2001 From: Mohammad nasser <76165108+mohamadhase@users.noreply.github.com> Date: Mon, 13 Oct 2025 23:23:59 +0300 Subject: [PATCH 3/8] resolve comments --- .../catalog/actions-fullsession/index.md | 71 ------------------- 1 file changed, 71 deletions(-) diff --git a/src/connections/destinations/catalog/actions-fullsession/index.md b/src/connections/destinations/catalog/actions-fullsession/index.md index 4119f30694..13a6476c1f 100644 --- a/src/connections/destinations/catalog/actions-fullsession/index.md +++ b/src/connections/destinations/catalog/actions-fullsession/index.md @@ -18,75 +18,4 @@ This destination is maintained by FullSession. For any issues with the destinati 6. Before enabling the destination, open the **Mappings** tab and configure the mappings to ensure the correct data is captured. 7. Once your mappings are configured and enabled, go to the **Settings** tab and enable the Destination. Segment will then automatically load the **FullSession recording snippet** in the user’s browser. - -## Identify User - -If you're not familiar with the Segment Specs, take a look to understand what the [identify method](/docs/connections/spec/identify/) does. Identify calls sent to Segment will be transformed and sent to FullSession's identify method to help you track and segment users in your session recordings. - -An example call which does not include a `userId` will send FullSession the value of the `anonymousId` and would look like: - -```javascript -analytics.identify(); -``` - -If an `identify` call does contain a `userId`, that will be the ID sent along to FullSession. - -```javascript -analytics.identify("userId"); -``` - -In addition, Segment will send over along any traits included in the `identify` call. The example call below would send over both `plan` and `logins`. - -```javascript -analytics.identify("userId123", { - plan: "premium", - logins: 5 -}); -``` - -### Specifying user name and email - -Both `email` and `name` are special traits that will be passed to FullSession to be used in their interface for better user identification. These traits are optional. - -```javascript -analytics.identify("userId123", { - email: "john.doe@example.com", - name: "John Doe" -}); -``` - -## Record Event - -If you're not familiar with the Segment Specs, take a look to understand what the [track method](/docs/connections/spec/track/) does. Track calls sent to Segment will be automatically passed directly to FullSession using their event tracking method, including all the properties passed in the event. - -An example call would look like: - -```javascript -analytics.track('Product Purchased', { - order_ID: '2969302398', - category: 'boots', - product_name: 'yellow_cowboy_boots', - price: 99.95, - currency: 'EUR' -}); -``` - -This allows you to correlate specific user actions with session recordings, making it easier to analyze user behavior patterns and identify conversion bottlenecks. - -## Visit Page - -If you're not familiar with the Segment Specs, take a look to understand what the [page method](/docs/connections/spec/page/) does. Page calls sent to Segment will be automatically passed to FullSession to set page-specific attributes and properties. - -An example call would look like: - -```javascript -analytics.page('Product Page', { - category: 'Electronics', - name: 'iPhone 15', - price: 999 -}); -``` - -This helps you understand how users navigate through your site and which pages are most important in their journey. - {% include components/actions-fields.html %} \ No newline at end of file From 5b5b4649f2acc050c00a817d95f8aa9b5e8359ca Mon Sep 17 00:00:00 2001 From: sade-wusi Date: Tue, 14 Oct 2025 15:24:25 +0100 Subject: [PATCH 4/8] Adding docs for Fullsession destination --- .../destinations/catalog/actions-fullsession/index.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/src/connections/destinations/catalog/actions-fullsession/index.md b/src/connections/destinations/catalog/actions-fullsession/index.md index 13a6476c1f..69b7d8109e 100644 --- a/src/connections/destinations/catalog/actions-fullsession/index.md +++ b/src/connections/destinations/catalog/actions-fullsession/index.md @@ -1,21 +1,22 @@ --- title: FullSession (Actions) Destination +id: 68c14f4eefb643527597844c --- {% include content/plan-grid.md name="actions" %} [FullSession](https://fullsession.io/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank"} provides user behavior analytics software that helps you visualize all user interactions, analyze trends and patterns with laser precision, and optimize your website for peak performance. The Segment integration for FullSession helps accurately identify your customers and track their behavior within the FullSession dashboard. -This destination is maintained by FullSession. For any issues with the destination, [contact their Support team](mailto:support@fullsession.com). +This destination is maintained by FullSession. For any issues with the destination, [contact the Fullsession support team](mailto:support@fullsession.com){:target="_blank"}. ## Getting started -1. From your workspace’s [Destination Catalog](https://app.segment.com/goto-my-workspace/destinations/catalog){:target="_blank"}, search for **“FullSession.”** +1. From your workspace’s [Destination Catalog](https://app.segment.com/goto-my-workspace/destinations/catalog){:target="_blank"}, search for **“FullSession”**. 2. Select **FullSession**, then click **Add Destination**. 3. Choose an existing **JavaScript Source** to connect with FullSession (Actions). -4. Navigate to the [FullSession Setup](https://app.fullsession.io/settings/setup){:target="_blank"} page and copy your **Customer ID** (it begins with `cus_`). +4. Navigate to the [FullSession Setup](https://app.fullsession.io/settings/setup){:target="_blank"} page and copy your **Customer ID**, beginning with `cus_`. 5. Paste the **Customer ID** into the **FullSession Destination settings** in Segment. -6. Before enabling the destination, open the **Mappings** tab and configure the mappings to ensure the correct data is captured. -7. Once your mappings are configured and enabled, go to the **Settings** tab and enable the Destination. Segment will then automatically load the **FullSession recording snippet** in the user’s browser. +6. Before enabling the destination, go to the **Mappings** tab and configure the mappings to ensure the correct data is captured. +7. Once your mappings are configured and enabled, go to the **Settings** tab and enable the destination. Segment then automatically loads the **FullSession recording snippet** in the user’s browser. {% include components/actions-fields.html %} \ No newline at end of file From 83a71b447cca13edd7d6d50bb4a11fabdf422a77 Mon Sep 17 00:00:00 2001 From: Sharon Adewusi Date: Tue, 14 Oct 2025 15:29:00 +0100 Subject: [PATCH 5/8] casing --- .../destinations/catalog/actions-fullsession/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/connections/destinations/catalog/actions-fullsession/index.md b/src/connections/destinations/catalog/actions-fullsession/index.md index 69b7d8109e..a918fc9231 100644 --- a/src/connections/destinations/catalog/actions-fullsession/index.md +++ b/src/connections/destinations/catalog/actions-fullsession/index.md @@ -7,7 +7,7 @@ id: 68c14f4eefb643527597844c [FullSession](https://fullsession.io/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank"} provides user behavior analytics software that helps you visualize all user interactions, analyze trends and patterns with laser precision, and optimize your website for peak performance. The Segment integration for FullSession helps accurately identify your customers and track their behavior within the FullSession dashboard. -This destination is maintained by FullSession. For any issues with the destination, [contact the Fullsession support team](mailto:support@fullsession.com){:target="_blank"}. +This destination is maintained by FullSession. For any issues with the destination, [contact the FullSession support team](mailto:support@fullsession.com){:target="_blank"}. ## Getting started @@ -19,4 +19,4 @@ This destination is maintained by FullSession. For any issues with the destinati 6. Before enabling the destination, go to the **Mappings** tab and configure the mappings to ensure the correct data is captured. 7. Once your mappings are configured and enabled, go to the **Settings** tab and enable the destination. Segment then automatically loads the **FullSession recording snippet** in the user’s browser. -{% include components/actions-fields.html %} \ No newline at end of file +{% include components/actions-fields.html %} From 5ed9cf62cbf0b6ab19dfb08a6fffe4216f6d22cd Mon Sep 17 00:00:00 2001 From: Sharon Adewusi Date: Thu, 16 Oct 2025 14:14:58 +0100 Subject: [PATCH 6/8] Update src/connections/destinations/catalog/actions-fullsession/index.md Co-authored-by: pwseg <86626706+pwseg@users.noreply.github.com> --- .../destinations/catalog/actions-fullsession/index.md | 1 + 1 file changed, 1 insertion(+) diff --git a/src/connections/destinations/catalog/actions-fullsession/index.md b/src/connections/destinations/catalog/actions-fullsession/index.md index a918fc9231..b3dd292b23 100644 --- a/src/connections/destinations/catalog/actions-fullsession/index.md +++ b/src/connections/destinations/catalog/actions-fullsession/index.md @@ -1,6 +1,7 @@ --- title: FullSession (Actions) Destination id: 68c14f4eefb643527597844c +hidden: true --- {% include content/plan-grid.md name="actions" %} From 5840176d05f3d0480779d93c4d56f9c0c62e5e5d Mon Sep 17 00:00:00 2001 From: Sharon Adewusi Date: Thu, 16 Oct 2025 14:16:00 +0100 Subject: [PATCH 7/8] Add beta flag to FullSession destination metadata --- .../destinations/catalog/actions-fullsession/index.md | 1 + 1 file changed, 1 insertion(+) diff --git a/src/connections/destinations/catalog/actions-fullsession/index.md b/src/connections/destinations/catalog/actions-fullsession/index.md index b3dd292b23..c9fe5a59d0 100644 --- a/src/connections/destinations/catalog/actions-fullsession/index.md +++ b/src/connections/destinations/catalog/actions-fullsession/index.md @@ -2,6 +2,7 @@ title: FullSession (Actions) Destination id: 68c14f4eefb643527597844c hidden: true +beta: true --- {% include content/plan-grid.md name="actions" %} From 596ebf93d38e4832f5a1c5800fac13761f2980bf Mon Sep 17 00:00:00 2001 From: pwseg <86626706+pwseg@users.noreply.github.com> Date: Thu, 16 Oct 2025 09:58:15 -0500 Subject: [PATCH 8/8] never mind, apparently it's public beta --- .../destinations/catalog/actions-fullsession/index.md | 1 - 1 file changed, 1 deletion(-) diff --git a/src/connections/destinations/catalog/actions-fullsession/index.md b/src/connections/destinations/catalog/actions-fullsession/index.md index c9fe5a59d0..084b38fd50 100644 --- a/src/connections/destinations/catalog/actions-fullsession/index.md +++ b/src/connections/destinations/catalog/actions-fullsession/index.md @@ -1,7 +1,6 @@ --- title: FullSession (Actions) Destination id: 68c14f4eefb643527597844c -hidden: true beta: true ---