Skip to content

Commit d28f2c2

Browse files
tobiordobimarkzegarelli
andauthored
Update CleverTap wording
Co-authored-by: markzegarelli <[email protected]>
1 parent 30a45d7 commit d28f2c2

File tree

1 file changed

+1
-1
lines changed
  • src/connections/destinations/catalog/clevertap

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ All other traits will be sent to CleverTap as custom attributes. Please also not
3131
When you `track` an event, we will send that event to CleverTap as a custom event. Note that CleverTap does not support arrays or nested objects for custom track event properties.
3232

3333
> note ""
34-
> **NOTE:** For your `track` events to appear on CleverTap, an accompanying trait such as `userId` or `email` from `identify` is required in order for CleverTap to record and associate the `track` event.
34+
> CleverTap requires `identify` traits such as `userId` or `email` to record and associate the Track event. Without these traits, the Track event does not appear in CleverTap.
3535
3636
Please also note that the default logic for our cloud mode connection to CleverTap will lower case and snake_case any event properties passed from Segment's servers to CleverTap. Our device mode connection will not lower case or snake_case any event properties passed directly to CleverTap from the client.
3737

0 commit comments

Comments
 (0)