Overview

You can view your imports by selecting the Import center tab on the Partners page.

This page lists all imports created for the data warehouse. You can also access it from Settings > Partners > Import center, where you can filter the results by partner.

The Import Listing page displays the following:

Health Indicator

The health indicator provides an at-a-glance view of the success of each import run.

Stats

Stats provides a detailed view of each import run, including the number of records processed, sync success rate, and any records that need attention. You can track import performance over time, understand the quality of your source data, and make informed adjustments to your import configuration with the help of these stats.

To access Stats, go to Settings > Partners > Import center. Click an import to open its details, and then select the Stats tab.

The Stats table displays the following for each import run:

You can click a particular import to view the detailed record stats.

Detailed Record View

Detailed record data is available only for import runs completed within the last 30 days. You can inspect individual records from the run.

Each record displays the following details:

Using Stats to Improve Your Sync

Stats works best as a feedback loop to actively improve the quality and reliability of future imports. The following are recommended ways to get the most out of Stats.

• Track health trends across runs: Review the health percentage across multiple runs to spot patterns. A consistent green health indicates a stable, well-mapped import. A declining trend often signals a change in the source data structure, unexpected values in a column, or credentials that need updating.
• Use failed records to refine your mappings: When a run shows failed syncs, click into the run and review the error messages in the detail pane. If the same field fails across many records, the issue is likely in how it is mapped or formatted in the source. Addressing the root cause in the source data or remapping the field will improve health across future runs.
• Validate record counts after each run: Compare the Total Records count to what you expect from your source query. A significant mismatch may indicate that the source table was not up to date when we fetched it, or that the import was stopped before completion.
• Prioritize identity errors: Records without a valid identity cannot be linked to a user profile in CleverTap and will not be usable for segmentation or engagement. Resolve identity-related failures before addressing property-level errors.
• Compare runs over time: If health drops suddenly after a period of consistent performance, check whether anything changed in your source data around that time, such as a schema change in the warehouse table or updated credentials.

Best Practices

The following best practices help ensure your imports run smoothly and your data remains clean and reliable.

Before Import Runs

Before configuring and running your import to ensure your source data is ready for a successful sync, review the following:

• Validate your source data before configuring the import. Ensure that identity fields such as email, phone, or custom ID contain clean, non-null values, and that data types in your source columns match the mappings you intend to configure.
• Ensure phone numbers include a valid country code in E.164 format (for example, +919876543210) and that email addresses are properly formatted with the @ sign before the dot.
• Avoid including system event names, such as App Launched, in the event name column of your source data, as these cannot be imported from external sources.
• Remove or replace reserved or placeholder identity values such as null, 0, N/A, undefined, or none in the source before the import runs.
• Confirm that your data warehouse credentials are valid and have not been rotated or updated since the import was last configured.

While Monitoring Imports

Review the following practices to stay on top of your import health and catch issues early:

• Review Stats after each run, particularly for scheduled imports, to confirm the health percentage is at expected levels.
• For imports scheduled at short intervals, such as every 15 minutes, be aware that if a run takes longer than the scheduled interval to complete, the next run will be skipped automatically and resume from the one after. This will appear as a gap in the Stats table and is expected behavior.
• Stats are available for runs completed within the last 30 days. For long-term monitoring, note down or export health and record counts periodically if historical tracking is important for your team.
• If an import in a running state is manually stopped, stats will not be available for that run, even if some records were partially ingested. Allow imports to complete before stopping them where possible.

Error Reference

Use this section to identify and resolve validation errors that appear in the detail pane for failed records. Errors are grouped by import type.

Common Errors

The following errors apply to both user profiles and event imports:

User Profile Import Errors

The following errors may appear for failed records in a user profile import:

Event Import Errors

The following errors may appear in the detail pane for failed records in an event import.