Skip to content

Commit fe4e30c

Browse files
authored
Edits
1 parent ed2eabf commit fe4e30c

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

+1-1
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ CleverTap supports the Identify, Track, Page (server-side only), and Screen (iOS
1111

1212
You can integrate CleverTap using a server-side or mobile destination (iOS or Android). If you are interested in using CleverTap's push notifications or in-app notifications products, you should use the mobile destinations.
1313

14-
All server-side destination requests require both the Segment `anonymousId` and `userId` in the payload. This is a requirement from CleverTap.
14+
For server-side destination requests, CleverTap requires both the Segment `anonymousId` and `userId` in the payload.
1515

1616
CleverTap maintains the server-side and mobile integrations:
1717
- [Android](https://github.com/CleverTap/clevertap-segment-android)

0 commit comments

Comments
 (0)