App Tracking: Offline Caching

It is crucial to ensure uninterrupted data tracking even when network connectivity is unavailable. Offline caching is a powerful solution that enables apps to temporarily store tracking data locally and synchronize it once internet access is restored.

This article explains how to enable offline caching in the JENTIS App SDK. You will need app development expertise for this.

Offline Caching with the App SDK

By default, the JENTIS App SDK uses a 1-hour timeout for offline caching. This ensures that tracking requests are retained for up to an hour during connectivity disruptions.

The typical timeout durations for app SDKs vary depending on the use case:

Short-term caching (hours): Common for most app SDKs, such as analytics or tracking tools, where data is retained for a few hours (e.g., 6–12 hours) until connectivity is restored.
Medium-term caching (days): Used in applications where data accuracy is critical, like in financial or e-commerce apps, extending up to 7 days.
Long-term caching (weeks): This is rare and specific to applications where data loss is unacceptable. Caching duration may extend from 14 to 30 days.

Some Factors can also influence the choice of timeout duration:

SDK Design: Some SDKs, like Google Analytics or Segment, allow developers to configure the caching duration.
Privacy Regulations: Longer caching periods may raise compliance concerns (e.g., GDPR, CCPA).
Storage Limits: Cache size or device storage capacity may impose constraints.
Data Sensitivity: Critical data may warrant longer caching compared to non-critical logs.

In the next topic, we’ll walk you through how to enable and configure offline caching with the JENTIS App SDK to ensure your tracking data is secure, compliant, and reliably synchronized—regardless of connectivity issues.

App Implementation

To enable offline caching in your app tracking with our App SDK, you must activate it during the initialization process. Optionally, you can override the default timeout of 1 hour during initialization.

When offline caching is activated, for each request sent to JENTIS, we add two additional properties to the information:

CACHED DATA	`app_offline_cached_data` = true `app_offline_resend_timestamp` = timestamp in milliseconds, when the data was resend to JENTIS
ONLINE DATA	`app_offline_cached_data` = false

iOS Implementation

CODE

$body

Android Implementation

CODE

$body

Offline Caching with the App SDK

App Implementation

iOS Implementation

Android Implementation

Read next