Clickstream Event API Authentication

The Clickstream Event APIs support two types of integration methods to suit different deployment needs: Client-to-Business (C2B) and Business-to-Business (B2B).

C2B Integration (Client-to-Business)

This is the standard method for integrating clickstream data. Here, data is collected directly from the client’s device via the JS SDK (for web) or Android/iOS SDKs (for mobile). These SDKs automatically create the necessary JSON payloads to integrate clickstream events with the Real-time CDP (rCDP) platform. As the requests originate from the client-side, no additional authentication is required.

B2B Integration (Business-to-Business)

Also known as server-side integration, this method requires resource-based API authentication. All B2B Clickstream Event Data APIs are protected by OAuth authentication, ensuring secure access for tenants with enabled authentication. OAuth serves as a robust, token-based framework that controls and authorizes access to protected resources.

• The eventType (e.g., eventAddToCart, eventTransactionComplete) acts as the resource.

• If authentication is enabled, all Clickstream Event Data APIs require the mandatory access_token in the request header, which contains the OAuth token generated via the Creating Access Token API.

For detailed information on OAuth-related APIs, refer to the API Authentication section, which includes endpoint details, authentication methods, token management, and more.