Ellipse Gradient for Header

CleverTap Integration Guide

Connect CleverTap with enterprise systems through regional REST APIs, batch uploads, selected webhook notifications, and Martini workflows.

CleverTap integration options at a glance

CleverTap provides regional REST APIs for user profile updates, event ingestion, selected platform operations, and batch uploads. Upload APIs support multiple profile or event records per request for initial loads, scheduled synchronization, and event replay. CleverTap also supports webhook-style outbound delivery for selected engagement and campaign use cases, although this is not a universal change-notification stream. Server-side authentication uses an account ID and passcode in request headers, with credentials and the regional API host stored securely in Martini environment configuration. Martini can consume these APIs, receive supported callbacks, map and validate payloads, schedule synchronization, and route failures for retry or review.

Integration pointSupported by CleverTap?Common use casesHow Martini supports it
REST APIsYesCleverTap REST APIs support profile updates, event ingestion, selected campaign, segment, reporting, and other platform operations. Regional API hosts must be selected for the account.Martini can consume the APIs through workflow HTTP/API steps, map source data into CleverTap payloads, and expose a controlled API façade for internal consumers.
Webhooks / outbound callbacksLimitedCleverTap supports webhook-style delivery for selected engagement or campaign-related use cases. It is not confirmed as a universal notification stream for all profile, event, or configuration changes.Martini can expose an inbound API or webhook workflow, validate the notification, apply idempotency controls, route the event, and record processing outcomes.
Bulk / batch APIsYesUpload APIs support batched profile and event ingestion for initial loads, scheduled synchronization, buffered-event replay, and high-volume requests.Martini can split source data into acceptable request sizes, preserve checkpoints, throttle submissions, and distinguish successful records from rejected records.
AuthenticationYesServer-side API requests commonly use X-CleverTap-Account-Id and X-CleverTap-Passcode headers together with the regional API host. OAuth was not confirmed as the standard mechanism.Martini can store the account ID, passcode, and regional base URL in secure environment configuration or secrets and apply them to outbound requests.
Analytics and reporting APIsLimitedSelected CleverTap reporting or export capabilities can provide data for warehouse synchronization and operational analysis. Exact availability depends on the account and subscription.Martini can schedule retrieval, normalize responses, persist cursors or time windows, and write data to approved analytical destinations.
File and attachment APIsNot confirmedNo general-purpose file or attachment API was confirmed. Specific CleverTap import or export products should be evaluated separately.Martini can process files when a documented CleverTap export or import mechanism provides them, but should not treat CleverTap as a generic attachment store.
Database accessNoDirect database access to CleverTap was not confirmed. Analytics and reporting should be accessed through documented APIs or export capabilities.Martini should consume approved CleverTap APIs or exports rather than connect directly to a CleverTap database.

How CleverTap exposes data and business events

CleverTap REST APIs

CleverTap's primary integration mechanism is its regional REST API surface. The APIs support user profile updates, event ingestion, selected platform operations, reporting functions, and upload-style batch requests, with exact availability varying by product and account configuration.

Martini implementation pattern

Martini uses a workflow to authenticate with the CleverTap account ID and passcode, call the account's regional API host, validate responses, and transform source application data into CleverTap User Profiles, Events, or other supported payloads. A Martini API can also provide a governed internal façade over these operations.

Implementation sequence

Store the CleverTap regional host and credentials in secure environment configuration
Receive or retrieve source customer and activity data
Validate identity fields, event names, and property types
Map source objects to CleverTap request payloads
Call the appropriate CleverTap REST endpoint
Persist response identifiers and processing checkpoints

CleverTap Webhook Notifications

CleverTap supports webhook-style outbound delivery for selected engagement or campaign-related use cases. Coverage depends on the feature, channel, and account configuration and should not be treated as a universal event stream.

Martini implementation pattern

Martini exposes an inbound API or webhook workflow for the supported CleverTap notification. The workflow validates the request using the configured security approach, applies duplicate-event protection, maps the payload to an internal event model, and routes it to operational or analytical systems.

Implementation sequence

Expose a Martini inbound API for the supported CleverTap callback
Validate the request and configured authentication or signature
Create an idempotency key from the callback payload
Map the notification to the internal event model
Route the event to the target application or database
Record the result and retry transient downstream failures

CleverTap Batch Upload APIs

CleverTap upload APIs support multiple profile or event records in a request. They are useful for initial imports, scheduled synchronization, historical backfills, and replaying buffered events, subject to endpoint-specific limits.

Martini implementation pattern

Martini retrieves or receives source data, partitions it according to documented CleverTap request limits, and submits batches through a controlled workflow. The workflow tracks batch outcomes, separates rejected records, and retries only failures that are considered transient.

Implementation sequence

Retrieve the source changes or historical data window
Normalize records and divide them into accepted batch sizes
Validate each batch before submission
Submit profile or event batches to CleverTap
Capture successful and rejected item results
Persist the checkpoint and retry eligible failures

CleverTap Reporting and Export APIs

Selected CleverTap reporting or export capabilities can provide engagement and audience data for analytical destinations. Availability depends on the CleverTap product, account configuration, and subscription.

Martini implementation pattern

Martini runs a scheduled workflow that calls the applicable reporting or export API, handles endpoint-specific pagination or date windows, normalizes the response, and writes it to a warehouse or operational data store. Direct database access is not assumed.

Implementation sequence

Start the workflow on a schedule
Read the saved timestamp, cursor, or export identifier
Retrieve the next reporting or export window
Normalize the CleverTap response into the target schema
Write validated data to the warehouse or database
Store the new checkpoint and log reconciliation results

Common CleverTap integration patterns

Pattern 1: Sync customer profiles and events to CleverTap

When to use this pattern

Use this pattern when CRM, commerce, subscription, or support applications are the system of record for customer attributes and business activity that should influence CleverTap segmentation and engagement. The workflow keeps identity fields separate from event properties and prevents inconsistent identifiers from creating duplicate profiles.

Integration direction
Salesforce
Martini
CleverTap
Example Mapping
CleverTap FieldCanonical FieldTarget Field
Contact.Idcustomer_idIdentity
Contact.EmailemailEmail
Contact.LifecycleStatuslifecycle_statuslifecycle_status
Order.TotalAmountpurchase_amountamount
Martini implementation pattern

Martini receives changes through an event-driven or scheduled workflow, validates required identity fields, maps profile attributes and events independently, and submits the appropriate REST or batch requests. Business rules can exclude incomplete or sensitive records, while source identifiers and processing keys support idempotent retries and reconciliation.

Martini capabilities used
  • workflows
  • API consumption
  • data mapping
  • business rules
  • batch processing
  • error handling

Pattern 2: Process CleverTap engagement callbacks

When to use this pattern

Use this pattern when selected CleverTap campaign or engagement notifications must update a CRM, service platform, warehouse, or internal operational process. It is appropriate for supported callback events, not for assuming that every CleverTap profile or event mutation generates a notification.

Integration direction
CleverTap
Martini
Salesforce
Example Mapping
CleverTap FieldCanonical FieldTarget Field
campaignIdengagement_campaign_idCampaignId
eventNameengagement_typeEngagementType
identitycustomer_idContactId
timestampoccurred_atEngagementDate
Martini implementation pattern

Martini exposes an inbound API, validates the configured callback security, derives an idempotency key, and maps the CleverTap notification to the target model. Routing rules determine whether the event updates Salesforce, a service platform, or a database; transient target failures are retried while invalid payloads are quarantined.

Martini capabilities used
  • API exposure
  • webhook handling
  • data mapping
  • idempotency
  • conditional routing
  • error handling

Pattern 3: Run scheduled profile and event synchronization

When to use this pattern

Use this pattern for initial customer imports, recurring reconciliation, historical event backfills, or environments where real-time delivery is not required. Batch upload reduces request overhead, but the workflow must still respect endpoint-specific payload limits and track partial failures.

Integration direction
NetSuite
Martini
CleverTap
Example Mapping
CleverTap FieldCanonical FieldTarget Field
customerInternalIdcustomer_idIdentity
emailemailEmail
transactionIdsource_event_idtransaction_id
transactionDateoccurred_atevent_timestamp
Martini implementation pattern

A scheduled Martini workflow retrieves the next source window, validates and partitions the data, and submits CleverTap upload requests. It persists a high-water mark, records rejected records separately, preserves ordering where required, and retries rate-limit or temporary service failures without replaying successful batches.

Martini capabilities used
  • scheduled workflows
  • API consumption
  • batch processing
  • mapping and transformation
  • checkpointing
  • retry handling

Pattern 4: Load CleverTap reporting data into a warehouse

When to use this pattern

Use this pattern when an enabled CleverTap reporting or export API provides engagement, audience, or campaign data needed for enterprise analytics. It creates a governed extraction path without relying on direct CleverTap database access.

Integration direction
CleverTap
Martini
Snowflake
Example Mapping
CleverTap FieldCanonical FieldTarget Field
campaignIdcampaign_idcampaign_id
segmentNameaudience_namesegment_name
eventCountengagement_countevent_count
reportDatereport_datereport_date
Martini implementation pattern

Martini schedules incremental extraction, handles the reporting endpoint's pagination or time-window model, normalizes the response, and writes records to Snowflake. Reconciliation counts, checkpoint persistence, schema validation, and retry rules make the load repeatable and observable.

Martini capabilities used
  • scheduled workflows
  • API consumption
  • data transformation
  • database integration
  • checkpointing
  • monitoring

Applications commonly integrated with CleverTap

CleverTap can be integrated with customer, commerce, support, marketing, and analytics applications when profile attributes, behavioral events, campaign outcomes, or reporting data must move across enterprise systems. The exact integration method depends on the application and CleverTap account configuration.

Application Scenario Direction Martini Pattern
Salesforce Synchronize customer profile attributes, lifecycle status, sales ownership, and selected engagement activity between Salesforce and CleverTap. Salesforce → Martini → CleverTap A Martini workflow retrieves changed Salesforce data, separates identity and profile attributes from engagement events, validates the payload, and sends the appropriate profile or event requests to the regional CleverTap REST API. Selected CleverTap callback notifications can be mapped back to Salesforce through a separate workflow.
Shopify Send customer, order, product, and purchase activity to CleverTap for behavioral engagement and commerce-oriented campaigns. Shopify → Martini → CleverTap Martini receives or schedules Shopify data retrieval, maps customer and order identifiers into CleverTap User Profiles and Events, batches high-volume payloads where appropriate, and applies duplicate-event controls before ingestion.
Segment Forward normalized customer events and profile traits from Segment into CleverTap while preserving a governed customer-data pipeline. Segment → Martini → CleverTap Martini exposes an inbound API or consumes the available Segment delivery endpoint, validates the event contract, maps traits and event properties to CleverTap payloads, and routes malformed or unsupported events to an operational error path.
Zendesk Use support activity, ticket status, and service interactions to enrich CleverTap profiles and inform engagement decisions. Zendesk → Martini → CleverTap A scheduled or event-driven Martini workflow retrieves relevant Zendesk changes, maps customer identity and support events, filters sensitive or irrelevant fields, and submits profile or event updates to CleverTap with retry handling for transient failures.
HubSpot Coordinate marketing and lifecycle attributes with CleverTap so customer engagement journeys reflect current contact and campaign context. HubSpot → Martini → CleverTap Martini synchronizes selected HubSpot contact and lifecycle fields into CleverTap User Profiles, sends qualifying marketing events, and can expose a controlled API for downstream systems that need governed access to the integration.
Snowflake Consolidate CleverTap engagement, event, and reporting data with enterprise data for analytics, governance, and audience analysis. CleverTap → Martini → Snowflake Where the CleverTap account provides the relevant reporting or export API, Martini retrieves data on a schedule, normalizes response formats, tracks a timestamp or cursor checkpoint, and writes validated results to Snowflake through an approved database or ingestion interface.
BigQuery Store CleverTap event and engagement data for attribution, analytical workloads, and cross-system reporting. CleverTap → Martini → BigQuery Martini consumes the applicable CleverTap reporting or export endpoint, transforms records into the warehouse schema, handles incremental windows and replay protection, and delivers data to BigQuery using the target environment's supported ingestion method.
NetSuite Combine order, subscription, and customer lifecycle data with CleverTap profiles and behavioral events. NetSuite → Martini → CleverTap A Martini workflow retrieves changed NetSuite customer or transaction data, maps stable identity fields and transaction properties, validates event names and types, batches requests within CleverTap limits, and records rejected records separately from successful submissions.

How to build a CleverTap integration in Martini

Objective

Configure the CleverTap regional API host, account ID, and passcode without embedding secrets in workflow logic.

Instructions in Martini

  • Create environment configuration for the CleverTap regional endpoint
  • Store the account ID and passcode in secure configuration or secrets management
  • Apply the required X-CleverTap-Account-Id and X-CleverTap-Passcode headers
  • Confirm the account region and enabled API permissions

Objective

Select an event-driven, webhook-driven, or scheduled trigger based on the required freshness and the CleverTap mechanism available for the use case.

Instructions in Martini

  • Use an inbound API or webhook workflow for supported CleverTap callbacks
  • Use a scheduler for batch imports, reconciliation, or reporting extraction
  • Use an upstream application event where real-time profile or event delivery is available
  • Define the expected delivery and replay behavior

Objective

Collect source records or CleverTap responses while preserving the identifiers and checkpoints needed for reliable synchronization.

Instructions in Martini

  • Receive callback payloads through an exposed Martini API
  • Retrieve source changes or CleverTap reporting data through REST requests
  • Persist timestamps, cursors, source event IDs, or export identifiers
  • Handle endpoint-specific pagination and date-window behavior

Objective

Coordinate validation, transformation, business rules, API calls, target writes, and failure paths in a maintainable Martini workflow.

Instructions in Martini

  • Separate profile updates from event ingestion
  • Validate required identity fields and payload structure
  • Route records according to source, event type, or downstream requirement
  • Use reusable workflow logic for common CleverTap request handling

Objective

Convert source schemas into CleverTap User Profiles, Events, batch payloads, or reporting destination models.

Instructions in Martini

  • Map stable source identifiers to the CleverTap identity strategy
  • Normalize timestamps, property types, names, and null handling
  • Apply controlled event contracts and version material schema changes
  • Partition large datasets into acceptable upload requests

Objective

Prevent invalid data and unintended customer engagement side effects before writing to CleverTap or downstream systems.

Instructions in Martini

  • Filter incomplete, duplicate, sensitive, or out-of-scope records
  • Determine which events may influence campaigns, Segments, or Journeys
  • Apply idempotency checks for retried purchases, conversions, and callbacks
  • Distinguish retryable service failures from data-quality failures

Common CleverTap data objects used in integrations

ObjectTypical UseCommon target systemsMartini handling
User ProfilesStore customer identity information and profile attributes used for segmentation and engagement.Salesforce, HubSpot, Shopify, NetSuite, customer data platformsMartini validates stable identity fields, separates profile attributes from event properties, applies mapping rules, and sends profile updates through the regional REST or upload APIs.
EventsRepresent purchases, logins, registrations, renewals, support interactions, and other behavioral or business activity.CleverTap, data warehouses, Salesforce, Zendesk, BigQueryMartini validates event names and property types, adds source identifiers and timestamps where appropriate, applies deduplication logic, and submits individual or batched event payloads.
CampaignsRepresent configured engagement campaigns delivered through supported CleverTap channels.Salesforce, operational systems, reporting platforms, data warehousesMartini can retrieve or process selected campaign-related data where the relevant CleverTap API is enabled, applying account-specific response mapping and controlled downstream routing.
SegmentsDefine audiences using profile attributes, events, and behavioral criteria.Campaign operations, reporting platforms, data warehouses, internal audience servicesMartini can consume selected segment or audience data through documented APIs when enabled, normalize membership or metadata, and synchronize it to approved downstream systems.
JourneysCoordinate multi-step engagement flows involving audience entry, messaging, conditions, and actions.Operational systems, CRM platforms, reporting platformsMartini can process available journey-related API data or callback notifications, validate the account-specific schema, and route relevant engagement outcomes without assuming universal journey event coverage.
ProductsProvide catalog or product data for product experiences, recommendations, and commerce-related engagement.Shopify, NetSuite, product catalogs, data warehousesMartini maps product identifiers, attributes, and transaction relationships from source applications and sends supported product or event payloads according to the enabled CleverTap API.

Authentication and security considerations

Account credentials and regional endpoints

CleverTap server-side REST APIs generally use an account ID and passcode in X-CleverTap-Account-Id and X-CleverTap-Passcode headers. Requests must use the regional API host assigned to the CleverTap account rather than assuming a default region.

Secure configuration

Store the CleverTap account ID, passcode, and regional base URL in Martini environment configuration or secrets management. Do not embed credentials in workflow definitions, mappings, or source payloads.

Callback protection

For supported CleverTap webhook-style notifications, verify the authentication or signing behavior required by the specific feature, validate the payload, restrict the exposed endpoint where possible, and apply duplicate-event protection.

Operational considerations for CleverTap integrations

Throughput and batching

Confirm account and endpoint limits before designing high-volume ingestion. Use CleverTap batch upload APIs where applicable, split requests according to documented limits, throttle concurrency, and retry transient HTTP failures.

Pagination and checkpoints

Read and reporting APIs may use endpoint-specific pagination, cursors, date windows, or export identifiers. Persist a high-water mark and do not assume that every CleverTap endpoint uses the same retrieval model.

Identity and idempotency

Use stable identity fields to avoid unintended duplicate User Profiles. Apply source event IDs, deterministic keys, processing tables, or other deduplication logic when retries could repeat purchases, conversions, or callbacks.

Schema and side effects

Maintain controlled event names, property types, required fields, and versioning rules. Test changes in a controlled CleverTap environment because profile and event submissions may affect Segments, Campaigns, and Journeys.

Error handling and monitoring

Distinguish authentication, malformed payload, unsupported property, rate-limit, partial batch, and temporary service errors. Martini workflows can log outcomes, route data-quality failures for review, retry eligible failures, and persist reconciliation results.

Why use Martini instead of scripts or point-to-point integrations?

Orchestrated integration logic

Scripts and point-to-point calls often duplicate authentication, mapping, retry, and checkpoint logic. Martini centralizes these concerns in workflows that can receive events, call CleverTap, transform data, apply business rules, and write to multiple targets.

Reusable and governed APIs

Martini can expose a controlled API façade over CleverTap operations, allowing internal applications to use consistent contracts without embedding CleverTap regional endpoints and credentials throughout the estate.

Reliable synchronization

Batching, scheduling, idempotency, checkpointing, validation, and error routing can be designed as explicit workflow behavior. This supports repeatable profile and event synchronization and makes operational failures easier to diagnose than scattered scripts.

Flexible enterprise connectivity

Martini can combine CleverTap REST and callback integration with databases, files, messaging systems, and other APIs, allowing customer engagement data to participate in broader enterprise processes without requiring direct database access to CleverTap.

Frequently asked questions

How can CleverTap be integrated with enterprise systems?

CleverTap can be integrated through its regional REST APIs, profile and event upload APIs, and selected webhook-style outbound notifications. Enterprise workflows commonly synchronize User Profiles and Events, process campaign or engagement callbacks, and retrieve selected reporting or export data for operational systems and warehouses.

Can Martini integrate with CleverTap?

Yes. Martini can consume CleverTap REST APIs, submit profile and event payloads through the upload APIs, receive supported CleverTap webhook-style notifications through an exposed API, and orchestrate mapping, scheduling, validation, retries, and downstream processing.

Do I need a connector to integrate CleverTap with Martini?

No. A dedicated CleverTap connector is not required. Martini can use CleverTap's confirmed native REST APIs, batch upload endpoints, webhook-style callbacks, and account ID and passcode authentication through standard API and workflow capabilities.

Is there any extra Lonti cost to integrate CleverTap with Martini?

Lonti does not charge an additional per-connector or per-vendor fee to integrate CleverTap. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from CleverTap, cloud infrastructure, or other third-party systems based on subscription, usage, and deployment model.

Which CleverTap integration methods should be used for new projects?

REST APIs are the primary method for profile updates, event ingestion, selected platform operations, and reporting functions. Batch upload APIs are useful for initial loads and high-volume synchronization, while webhook-style callbacks should be used only for the selected engagement or campaign use cases they support. GraphQL and current SOAP APIs were not confirmed.

Can CleverTap send events to Martini through webhooks?

CleverTap supports webhook-style delivery for selected engagement or campaign-related use cases, but the reviewed documentation does not establish a universal event-change feed. Martini can receive supported callbacks, validate them, apply idempotency controls, and route them to downstream systems.

How should CleverTap synchronization handle identity, mapping, and duplicates?

Define a stable identity strategy before sending User Profiles or Events, keep profile fields separate from event properties, and use controlled event names and property types. Martini can map and transform payloads, persist source identifiers or checkpoints, and apply deduplication or reconciliation logic for retries and replays.

Can Martini expose an API façade for CleverTap?

Yes. Martini can expose a controlled API that internal applications call instead of connecting directly to CleverTap. The façade can validate requests, apply business rules, invoke the appropriate regional CleverTap REST endpoint, standardize responses, and centralize authentication, logging, and error handling.

Related Martini documentation

CleverTap APIs

Workflows

Data Processing

Security

Operations

Integrate CleverTap with Martini

Use Martini to build governed CleverTap integrations for profiles, events, batch synchronization, engagement callbacks, and reporting workflows.

EXPLORE MARTINI
BOOK A DEMO