You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/actions-fullsession/index.md
-71Lines changed: 0 additions & 71 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,75 +18,4 @@ This destination is maintained by FullSession. For any issues with the destinati
18
18
6. Before enabling the destination, open the **Mappings** tab and configure the mappings to ensure the correct data is captured.
19
19
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.
20
20
21
-
22
-
## Identify User
23
-
24
-
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.
25
-
26
-
An example call which does not include a `userId` will send FullSession the value of the `anonymousId` and would look like:
27
-
28
-
```javascript
29
-
analytics.identify();
30
-
```
31
-
32
-
If an `identify` call does contain a `userId`, that will be the ID sent along to FullSession.
33
-
34
-
```javascript
35
-
analytics.identify("userId");
36
-
```
37
-
38
-
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`.
39
-
40
-
```javascript
41
-
analytics.identify("userId123", {
42
-
plan:"premium",
43
-
logins:5
44
-
});
45
-
```
46
-
47
-
### Specifying user name and email
48
-
49
-
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.
50
-
51
-
```javascript
52
-
analytics.identify("userId123", {
53
-
email:"john.doe@example.com",
54
-
name:"John Doe"
55
-
});
56
-
```
57
-
58
-
## Record Event
59
-
60
-
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.
61
-
62
-
An example call would look like:
63
-
64
-
```javascript
65
-
analytics.track('Product Purchased', {
66
-
order_ID:'2969302398',
67
-
category:'boots',
68
-
product_name:'yellow_cowboy_boots',
69
-
price:99.95,
70
-
currency:'EUR'
71
-
});
72
-
```
73
-
74
-
This allows you to correlate specific user actions with session recordings, making it easier to analyze user behavior patterns and identify conversion bottlenecks.
75
-
76
-
## Visit Page
77
-
78
-
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.
79
-
80
-
An example call would look like:
81
-
82
-
```javascript
83
-
analytics.page('Product Page', {
84
-
category:'Electronics',
85
-
name:'iPhone 15',
86
-
price:999
87
-
});
88
-
```
89
-
90
-
This helps you understand how users navigate through your site and which pages are most important in their journey.
0 commit comments