Hevo lets you load your CleverTap events to your data warehouse. Let's walk through steps for adding a CleverTap source.
You must have access to your CleverTap API credentials to provide Hevo access to your CleverTap account. Read more about Getting your CleverTap API credentials here. Please note that your email address is not the Clevertap Account ID.
1. Create a new Pipeline
Click on PIPELINES option in the left navigation bar and click on Create New Pipeline.
2. Select Source Type
Select CleverTap from the list on Select Source Type Screen.
3. Name the Source
Provide a unique name for this Source.
4. Provide CeleverTap's Account Credentials
Provide your CleverTap Account ID and Passcode from your CeleverTap account to download events. Check out Getting your account credentials for the detailed steps.
Please note that CleverTap APIs do not return an error when you provide a wrong Account ID. Hence, Test Connection might pass even if the Account ID is wrong.
5. Provide the List of Events you want to capture
CleverTap doesn't provide an API to list all distinct event names nor does it provide an API to download all events at one go. Hence, Hevo needs you to provide a comma-separated list of all events you want to capture.
6. Select the Destination
Select the Destination where you want to replicate Mixpanel Data or Click on NEW DESTINATION to create a new Destination. Check out How to add Destination tutorial for the detailed walkthrough on steps needed for adding new Destination.
7. Pipeline Created
Your Pipeline will be created when you enter this page and you will have an option to see Sample Data and Map Schema.
While Hevo tries to load your schemas, you can select CONTINUE IN BACKGROUND if it is taking too much time. Click on CREATE SCHEMA MAPPING to map Source and Destination Schemas, check out Introduction to Schema Mapper to learn about Schema Mapper or you can select DO IT LATER to directly head to Pipeline page. You can map schemas later on Schema Mapper page in your pipeline.
Please note that your data will not start replicating in Destination tables until you map source and Destination schemas.