Skip to main content
After linking a destination with an Audience, Zeotap CDP sends segmented data to the destination based on the configured refresh frequency. The total end-to-end process typically ranges from a few minutes for smaller datasets to a maximum of 48 hours for larger ones, depending on the platform’s processing capacity. Several factors influence the latency of this process on both the Zeotap CDP side and the destination platform. The table below outlines these factors:
FactorImpact on Data UploadLatency Considerations
The volume of User DataThe amount of user data that qualifies for the Audience criteria.Larger data volumes take longer to process and transmit, increasing latency.
Data Type and ComplexityThe type and structure of user data, including strings, integers, timestamps, arrays of primitives, objects and arrays of objects.Simple data types process faster. Complex structures like arrays of primitives, objects and arrays of objects requireadditional computation, increasing segmentation time.
Backend Resource AllocationZeotap CDP backend resources handle multiple tenants.Our standard backend resources are shared, leading to queue-based processing. Opting for the Audience Highway premium service allocates dedicated resources, reducing processing time. Reach out to your Zeotap POC to know more about this premium service.
Connection StabilityThe connection between Zeotap CDP and the destination platform.Unstable or misconfigured connections can delay data transmission. A properly established integration connection ensures data reaches the destination within the expected timeframe.
Destination Processing TimeThe time the destination platform takes to process and reflect the received data.Even after Zeotap CDP uploads data, the destination platform may take additional time to process and display it.
Last modified on February 26, 2026