Skip to content

Commit 7b04e94

Browse files
authored
Update index.md
Calling out specifically that the user ID must be set (not null) for the identify call to work properly, since our integration checks for a value. https://github.com/segmentio/analytics.js-integrations/blob/3644ec30dd0f235e64d113911ae9e69f76d66168/integrations/hotjar/lib/index.js#L71
1 parent 39d17a5 commit 7b04e94

File tree

1 file changed

+2
-0
lines changed
  • src/connections/destinations/catalog/hotjar

1 file changed

+2
-0
lines changed

src/connections/destinations/catalog/hotjar/index.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -33,6 +33,8 @@ Hotjar automatically starts tracking visitors based on the tools you have enable
3333

3434
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).
3535

36+
Identify calls that do not have a User ID value will not be sent to Hotjar.
37+
3638
### Nested values or lists
3739

3840
The Hotjar Identify API is unable to ingest values passed as nested objects or lists over your `identify` Spec:

0 commit comments

Comments
 (0)