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-fullstory/index.md
+5
Original file line number
Diff line number
Diff line change
@@ -14,6 +14,11 @@ hide-dossier: true
14
14
> success ""
15
15
> **Good to know**: This page is about the [Actions-framework](/docs/connections/destinations/actions/) FullStory Segment destination. There's also a page about the [non-Actions FullStory destination](/docs/connections/destinations/catalog/fullstory/). Both of these destinations receives data from Segment.
16
16
17
+
## Benefits of FullStory (Actions) vs FullStory Classic
18
+
19
+
- Greater control over the page properties you send.
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/adobe-analytics/heartbeat.md
+37-16
Original file line number
Diff line number
Diff line change
@@ -97,7 +97,7 @@ options:@{
97
97
98
98
## Supported Video Events
99
99
100
-
Adobe Analytics supports many - but not all - of the [Segment video spec events](/docs/connections/spec/video/), however **some events required for Adobe Analytics are not included as part of Segment's standard video tracking**, so read the documentation closely. The list below shows supported events and the corresponding Adobe method(s) they trigger. The next section explains the function of each event in more detail, and lists any required properties.
100
+
Adobe Analytics supports many - but not all - of the [Segment Video Spec events](/docs/connections/spec/video/), however **some events required for Adobe Analytics are not included as part of Segment's standard video tracking**, so read the documentation closely. The list below shows supported events and the corresponding Adobe method(s) they trigger. The next section explains the function of each event in more detail, and lists any required properties.
101
101
102
102
<table>
103
103
<tr>
@@ -174,9 +174,11 @@ Adobe Analytics supports many - but not all - of the [Segment video spec events]
174
174
</tr>
175
175
</table>
176
176
177
+
On web, multiple video sessions can be open at once so video events must have a `session_id` property unique to the session the content belongs to. If a `session_id` is not included, Segment will send `default` as the [s:event:sid](https://experienceleague.adobe.com/docs/media-analytics/using/sdk-implement/validation/heartbeat-params.html?lang=en) and Adobe will create a new session. For more information on `session_id`, please visit [Segment's Video Spec](/docs/connections/spec/video/#playback).
178
+
177
179
### Video Playback Started
178
180
179
-
"Video Playback Started" is required to begin a new video session. This event **must** include the appropriate properties and options to configure the `MediaHeartbeat` instance for this video session. Although all the properties and options listed below are also **required**, you can also send additional standard and custom video properties with this event. See the [Custom Video Metadata section below.](#custom-video-metadata)
181
+
"Video Playback Started" is required to begin a new video session. This event **must** include the appropriate properties and options to configure the `MediaHeartbeat` instance for this video session. Although all the properties and options listed below are also **required**, you can also send additional standard and custom video properties with this event. See the [Custom Video Metadata section below](#custom-video-metadata).
180
182
181
183
<table>
182
184
<tr>
@@ -193,19 +195,23 @@ Adobe Analytics supports many - but not all - of the [Segment video spec events]
193
195
</tr>
194
196
<tr>
195
197
<td>`properties.title`</td>
196
-
<td>The title of the video session.</td>
198
+
<td>The title of the video.</td>
197
199
</tr>
198
200
<tr>
199
201
<td>`properties.contentAssetId`</td>
200
-
<td>The unique id for the video session.</td>
202
+
<td>The unique id for the video.</td>
201
203
</tr>
202
204
<tr>
203
205
<td>`properties.totalLength`</td>
204
-
<td>The total length in seconds of the video session.</td>
206
+
<td>The total length in seconds of the video.</td>
205
207
</tr>
206
208
<tr>
207
209
<td>`properties.livestream`</td>
208
-
<td>Whether the session is a livestream (boolean).</td>
210
+
<td>Whether the video is a livestream (boolean).</td>
211
+
</tr>
212
+
<tr>
213
+
<td>`properties.session_id`</td>
214
+
<td>The unique id for the session. Required for web.</td>
209
215
</tr>
210
216
<tr>
211
217
<td>`options.ovp`</td>
@@ -215,7 +221,7 @@ Adobe Analytics supports many - but not all - of the [Segment video spec events]
215
221
216
222
### Video Playback Completed
217
223
218
-
This Segment event triggers an Adobe `trackSessionEnd()` event. You do not need to pass any properties along with this event. Properties passed to this event are not forwarded to Adobe (but are sent to other downstream destinations that support video events).
224
+
This Segment event triggers an Adobe `trackSessionEnd()` event. On web, you must include a `session_id` property to tie this event to the correct video session. Any other properties passed to this event are not forwarded to Adobe (but are sent to other downstream destinations that support video events).
219
225
220
226
### Video Content Started
221
227
@@ -242,35 +248,39 @@ This Segment event triggers an Adobe `trackSessionEnd()` event. You do not need
242
248
<td>`properties.startTime`</td>
243
249
<td>The position of the video playhead in seconds when the chapter starts playing.</td>
244
250
</tr>
251
+
<tr>
252
+
<td>`properties.session_id`</td>
253
+
<td>The unique id for the session. Required for web.</td>
254
+
</tr>
245
255
</table>
246
256
247
257
### Video Content Completed
248
258
249
-
This Segment event triggers an Adobe `trackEvent(chapterComplete)` event and a `trackComplete()` event. You do not need to pass any properties along with this event. Properties passed to this event are not forwarded to Adobe (but are sent to other downstream destinations that support video events).
259
+
This Segment event triggers an Adobe `trackEvent(chapterComplete)` event and a `trackComplete()` event. On web, you must include a `session_id` property to tie this event to the correct video session. Any other properties passed to this event are not forwarded to Adobe (but are sent to other downstream destinations that support video events).
250
260
251
261
### Video Playback Paused
252
262
253
-
This Segment event triggers an Adobe `trackPause()` event. You do not need to pass any properties along with this event. Properties passed to this event are not forwarded to Adobe (but are sent to other downstream destinations that support video events).
263
+
This Segment event triggers an Adobe `trackPause()` event. On web, you must include a `session_id` property to tie this event to the correct video session. Any other properties passed to this event are not forwarded to Adobe (but are sent to other downstream destinations that support video events).
254
264
255
265
### Video Playback Resumed
256
266
257
-
This Segment event triggers an Adobe `trackPlay()` event. You do not need to pass any properties along with this event. Properties passed to this event are not forwarded to Adobe (but are sent to other downstream destinations that support video events).
267
+
This Segment event triggers an Adobe `trackPlay()` event. On web, you must include a `session_id` property to tie this event to the correct video session. Any other properties passed to this event are not forwarded to Adobe (but are sent to other downstream destinations that support video events).
258
268
259
269
### Video Playback Buffer Started
260
270
261
-
This Segment event triggers an Adobe `trackEvent(bufferStart)` event. You do not need to pass any properties along with this event. Properties passed to this event are not forwarded to Adobe (but are sent to other downstream destinations that support video events).
271
+
This Segment event triggers an Adobe `trackEvent(bufferStart)` event. On web, you must include a `session_id` property to tie this event to the correct video session. Any other properties passed to this event are not forwarded to Adobe (but are sent to other downstream destinations that support video events).
262
272
263
273
### Video Playback Buffer Completed
264
274
265
-
This Segment event triggers an Adobe `trackEvent(bufferComplete)` event. You do not need to pass any properties along with this event. Properties passed to this event are not forwarded to Adobe (but are sent to other downstream destinations that support video events).
275
+
This Segment event triggers an Adobe `trackEvent(bufferComplete)` event. On web, you must include a `session_id` property to tie this event to the correct video session. Any other properties passed to this event are not forwarded to Adobe (but are sent to other downstream destinations that support video events).
266
276
267
277
### Video Playback Seek Started
268
278
269
-
This Segment event triggers an Adobe `trackEvent(seekStart)` event. You do not need to pass any properties along with this event. Properties passed to this event are not forwarded to Adobe (but are sent to other downstream destinations that support video events).
279
+
This Segment event triggers an Adobe `trackEvent(seekStart)` event. On web, you must include a `session_id` property to tie this event to the correct video session. Any other properties passed to this event are not forwarded to Adobe (but are sent to other downstream destinations that support video events).
270
280
271
281
### Video Playback Seek Completed
272
282
273
-
This Segment event triggers an Adobe `trackEvent(seekComplete)` event. To reconcile the new playhead position, you **must** pass this value as `seekPosition`.
283
+
This Segment event triggers an Adobe `trackEvent(seekComplete)` event. On web, you must include a `session_id` property to tie this event to the correct video session. To reconcile the new playhead position, you **must** also pass the position as `seekPosition`.
274
284
275
285
<table>
276
286
<tr>
@@ -304,11 +314,15 @@ This Segment event triggers an Adobe `trackEvent(adBreakStart)` event. This even
304
314
<td>`properties.startTime`</td>
305
315
<td>The position of the video playhead in seconds when the chapter starts playing.</td>
306
316
</tr>
317
+
<tr>
318
+
<td>`properties.session_id`</td>
319
+
<td>The unique id for the session. Required for web.</td>
320
+
</tr>
307
321
</table>
308
322
309
323
### Video Ad Break Completed
310
324
311
-
This Segment event triggers an Adobe `trackEvent(adBreakComplete)` event. You do not need to pass any properties along with this event. Properties passed to this event are not forwarded to Adobe (but are sent to other downstream destinations that support video events).
325
+
This Segment event triggers an Adobe `trackEvent(adBreakComplete)` event. On web, you must include a `session_id` property to tie this event to the correct video session. Any other properties passed to this event are not forwarded to Adobe (but are sent to other downstream destinations that support video events).
312
326
313
327
### Video Ad Started
314
328
@@ -335,11 +349,15 @@ This Segment event triggers an Adobe `trackEvent(adStart)` event. This event **m
335
349
<td>`properties.totalLength`</td>
336
350
<td>The total length of the ad in seconds.</td>
337
351
</tr>
352
+
<tr>
353
+
<td>`properties.session_id`</td>
354
+
<td>The unique id for the session. Required for web.</td>
355
+
</tr>
338
356
</table>
339
357
340
358
#### Video Ad Completed
341
359
342
-
This Segment event triggers an Adobe `trackEvent(adComplete)` event. You do not need to pass any properties along with this event. Properties passed to this event are not forwarded to Adobe (but are sent to other downstream destinations that support video events).
360
+
This Segment event triggers an Adobe `trackEvent(adComplete)` event. On web, you must include a `session_id` property to tie this event to the correct video session. Any other properties passed to this event are not forwarded to Adobe (but are sent to other downstream destinations that support video events).
343
361
344
362
### Video Quality Updated
345
363
@@ -358,6 +376,9 @@ This event is required to set quality of service information in the `MediaHeartb
358
376
<tr>
359
377
<td>`properties.droppedFrames`</td>
360
378
</tr>
379
+
<tr>
380
+
<td>`properties.session_id` _Required for web. Defaults to `default` if missing._</td>
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/hotjar/index.md
+2
Original file line number
Diff line number
Diff line change
@@ -33,6 +33,8 @@ Hotjar automatically starts tracking visitors based on the tools you have enable
33
33
34
34
The Hotjar destination will automatically ingest a User ID, as well as values sent over your Identify spec as [traits](/docs/connections/spec/identify/#traits), as long as [User Attributes are enabled in Hotjar](https://help.hotjar.com/hc/en-us/articles/360038394053-How-to-Setup-User-Attributes-in-4-Steps#step-2-review-your-privacy-requirements-and-enable-user-attributes).
35
35
36
+
Identify calls that do not have a User ID value will not be sent to Hotjar.
37
+
36
38
### Nested values or lists
37
39
38
40
The Hotjar Identify API is unable to ingest values passed as nested objects or lists over your `identify` Spec:
0 commit comments