Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Add section for supported Alias call to CleverTap #3904

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 6, 2022
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions src/connections/destinations/catalog/clevertap/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,6 +27,13 @@ When you identify a user, Segment passes that user's information to CleverTap wi

All other traits will be sent to CleverTap as custom attributes. The default logic will lower case and snake_case any user traits - custom or special - passed to CleverTap.

## Alias

> warning ""
> Alias is supported by Device-mode Web connections

When you send an Alias call to CleverTap, CleverTap updates the user's profile with the contents of the Alias call.

## Track

When you `track` an event, Segment sends that event to CleverTap as a custom event. Note that CleverTap does not support arrays or nested objects for custom track event properties.
Expand Down