CleverTap Adds Journey Estimated Reach, WhatsApp Max Price and Cloud Storage Imports
In October 2026, CleverTap introduced several updates to its marketing automation platform. Journeys gained an audience-size estimate before publication, WhatsApp Marketing Templates gained a way to cap the maximum price per delivered message, and customer data imports gained direct connections to Amazon S3, Google Cloud Storage, and Microsoft Azure Blob Storage. The company also expanded personalization for campaigns triggered when a user does not take an expected action.
Estimated Reach: Check Journey Audiences Before Launch
CleverTap added Estimated Reach directly to the Journeys editor. Marketers can now estimate how many users meet the entry conditions for an automation before publishing it.
Previously, checking audience size required creating a separate segment. The new feature calculates reach from the rules configured directly in Entry Segment.
Estimated Reach supports Past Behavior segments as well as Action and Inaction entry segments using Live Behavior with additional filters based on historical behavior and user properties.
For example, a marketer can build a Journey for customers who have purchased within the past 30 days, exclude certain audience categories, and check how many users match those conditions.
To generate the estimate, the user clicks Calculate. Changes to the segmentation rules do not automatically refresh the result; the calculation must be run again.
The feature estimates the audience at the point of entry into a Journey. It does not forecast message deliveries or future conversions, and it does not calculate a separate reach figure for every downstream node.
Its main practical use is to identify overly narrow or broad segmentation criteria before activation, when configuration mistakes could result in insufficient reach or the inclusion of unintended audiences.
Max Price for WhatsApp Marketing Messages
CleverTap also introduced Max Price for WhatsApp Marketing Templates in October. The feature allows advertisers to specify the maximum amount Meta may charge for delivery of a single marketing message.
When creating a new Marketing-category template, users see an additional Pricing step. They can enable a price cap and enter an upper limit in the currency of the connected WhatsApp Business Account.
This value is not a fixed per-message charge. Meta may charge less, and the actual price depends on WhatsApp Business Platform delivery mechanisms.
The selected cap can also affect delivery priority during periods of high demand. A higher limit may improve the chances of delivery, but it does not guarantee delivery.
For evaluating that trade-off, CleverTap added Price Trend. It displays estimated delivery rates at different price limits for selected countries, using Meta historical data.
Marketers can therefore compare their acceptable per-message price with the estimated delivery rate before starting a campaign.
Max Price is in private beta and is available to WhatsApp Direct customers. It applies only to new Marketing templates, not Utility or Authentication templates. Geographic restrictions also apply, including in certain European markets.
Adjusting Max Price for Individual Campaigns and Journeys
CleverTap supports price-cap adjustments not only at the WhatsApp template level but also within individual campaigns and Journeys.
This uses the Max Price Multiplier, a coefficient that changes the template maximum when the template is used in a specific campaign or Journey node.
The multiplier must be greater than zero and cannot exceed 10.
For example, if a template has a $0.015 per-message cap, a multiplier of 2 raises the maximum for the selected campaign to $0.030.
The original template does not need to be modified. The same template can be reused across campaigns with different price limits.
This enables different delivery priorities for different communication objectives. A time-sensitive offer might have a higher limit, while a less urgent message retains the standard cap.
Max Price should not be confused with a campaign budget. It limits the price charged by Meta for an individual delivered message but does not determine total campaign spending, audience size, or the final contractual cost of messaging through a provider.
Import Customer Data From Amazon S3, Google Cloud Storage, and Azure
Another major October update focuses on bringing data into CleverTap.
The platform can now import files directly from Amazon S3, Google Cloud Storage, and Microsoft Azure Blob Storage. Both CSV and Parquet formats are supported.
Imported records can update customer profiles or create events that subsequently become available in Segmentation, Journeys, and Campaigns.
The maximum file size is 5 GB for CSV and 1 GB for Parquet.
Connections use read-only access that can be restricted to an individual bucket or folder, allowing data transfers without giving CleverTap unnecessary permissions to modify source files.
When configuring an import, the user selects a cloud source, defines file matching rules, and maps columns to profile attributes or event properties.
Preview, Dry Run, and Sample Sync are available before activation to check file structure and field mapping.
For example, a retailer or mobile app developer can regularly transfer customer and event data from its own infrastructure to CleverTap without uploading each file manually.
Scheduled Imports and Data Quality Controls
The import workflow supports both manual execution and scheduled runs.
CleverTap uses filenames, prefixes, and timestamps to identify new data, allowing subsequent runs to process only files added since the previous import.
Execution history appears in Import Center. For each run, users can review processing statistics, record counts, and reasons for failed records.
The platform also provides dashboard and email alerts, role-based permissions, and audit logs.
File-based Imports shares Import Center with Data Warehouse Imports, which previously added support for Snowflake, BigQuery, Databricks, Amazon Redshift, and Microsoft Fabric.
The difference lies in the source: Data Warehouse Imports reads from analytics warehouses, while File-based Imports processes prepared CSV or Parquet files stored in the cloud.
For marketing teams, this creates another route for using first-party business data, such as transaction records from an internal system, refreshed customer attributes, and event data for segmentation and automation.
Import reliability still depends on the source files. A file must be fully written and closed before processing begins. If its contents continue to change during an import, the operation may fail.
Personalization for Inaction Campaigns After More Than 24 Hours
Another October enhancement concerns campaigns triggered when a user does not complete an expected action.
CleverTap extended Event Personalization to Inaction campaigns with delays longer than one day. Previously, the use of originating event data for personalizing these messages was limited to the standard 24-hour period.
Now, when Inaction conditions are met, the platform can build messages using the relevant user and event attributes even after a longer delay.
For example, if a customer adds an item to a cart but does not complete the purchase, a later reminder can use the details of the triggering event instead of generic copy.
When an Inaction condition occurs repeatedly, the system can generate a separate personalized message for each occurrence.
This is particularly useful in direct marketing workflows with long intervals between events, where the context of the original action should remain available when the message is sent.
The feature is in private beta. Its availability does not imply unlimited event history retention or support for arbitrary attributes outside the supported personalization mechanisms.
About CleverTap and Its Marketing Automation Platform
CleverTap provides customer engagement, behavioral analytics, and marketing automation tools. It serves organizations operating mobile applications and digital services, with support for push notifications, email, SMS, WhatsApp, in-app messages, and other channels.
The platform brings together customer profiles, behavioral events, segmentation, and Journeys, its visual tool for building automated customer communication flows.
The October releases address several connected workflows. Estimated Reach helps teams evaluate audience size before publishing a Journey. Max Price adds control over individual WhatsApp messaging charges under Meta delivery rules. File-based Imports brings first-party customer data in from cloud storage, while enhanced Inaction personalization makes event context available for longer-delay messages.
For marketers, the common theme is greater control across data preparation, audience definition, and message delivery.
Estimated Reach remains an audience estimate, and Price Trend remains a delivery forecast rather than a guarantee. Actual campaign performance still needs to be evaluated after launch.
Trust Us Transform Your Performance Marketing.
Connect customer data, refine lifecycle audiences, and measure the impact of your messaging and paid media.
Get in Touch




