DPI Integration FAQ

 

Overview

Conviva Digital Product Insights (DPI) sensor module consists of several basic scripts accessible from the Conviva GitHub Repositories with basic README instructions and the related script files for each the supported DPI application platforms. Lightweight integration of Conviva DPI sensor enables automatic, semantic-less data collection. Deploy custom events for advanced metrics and dimension analysis.

Use these FAQs to help answer common questions related to Conviva Digital Product Insights (DPI) sensors integration and the DPI platform support.

FAQs

Category

Question

Answer

Platform and Frameworks

Which platforms are supported by the DPI SDK?

Use these GitHub links to access the platform details.

Which frameworks and libraries are supported for auto-collection?

See the support details:

Web Apps with Multiple Sub-Domains and Native/Webview Hybrid Apps

How does Conviva preserve end-to-end user journeys across subdomains, native apps, and webviews?

When Conviva's DPI sensor initializes on an app instance for the first time, it generates a Client ID — a unique, Conviva-owned identifier used to attribute events to a single, continuous user. This ID contains no Personally Identifiable Information (PII) and exists only to distinguish one user's activity from another's inside Conviva's analytics. For more details, see Conviva Identity Sync Guide.

Conviva Cookies Usage What Conviva stores; why it is essential; and how it aligns with privacy frameworks? Conviva creates a limited set of cookies that are required for the core functionality of our service. These cookies are considered essential cookies and ensure accurate measurement, analytics, and reporting. Importantly, Conviva does not store any Personally Identifiable Information (PII) within these cookies. For more details, see Conviva Cookies Usage.
React Native app that uses Expo Router How do I track screen views in a React Native app that uses Expo Router? Expo Router does not work with Conviva's existing screen-view auto-tracking helper. Track screen views manually by calling trackScreenViewEvent() from your root layout. For more details, see Conviva Expo Router Screen Tracking.

Storage Requirement

What is the device local storage requirement of the DPI SDK?

Events will be dispatched with 250KB size limit or 5 seconds interval.

Initialization

When should I initialize the DPI SDK?

Conviva SDK should be initialized as early as possible, preferably before the first screen loads and first HTTP client object is created.

Events Auto-Collected

Which events are auto-collected by the DPI SDK?

Reference to DPI Metrics.

Events Video to DPI

How do I send events from the VSI SDK to DPI SDK?

With these VSI and DPI SDK versions, Conviva automatically sends video events to the DPI SDK:

  Minimum Version DPI SDK Minimum VersionVSI SDK
Android 0.5.2 4.0.30
iOS 0.2.10 4.0.31
JS SDK 0.3.17 4.5.13
C SDK 2.184.0.1 No
Roku 0.2.3 No
Rust 1.0.4 No
React Native 0.2.0 No
Flutter 0.3.9 No

For more details about event support, see Getting Started with Events.

Events and Tags

What is the difference between custom event and custom tag. When to use events or tags?

Custom events need to be used when a specific event needs to be reported from the app at a specific time and with all the details.

Custom tag is recommended when some specific information needs to be reported that remains static through the app sessions (such as device model).

Performance Impact

Will there be any performance impact if I include the DPI SDK in my app?

CPU Performance impact due to Android, iOS, and JS SDK's is 0.5-1%

Logging Levels

What is the recommended log level setting during testing vs production?

Conviva recommends:

* Disable logging in production

* Enable it on verbose mode in debug builds.

Performance KPI validation needs to be executed on Production builds.

Other Analytics Tools

We use other analytics in our app. Does the order in which we initialize them matter?

No, the order does not matter.

Validation

How do I verify if my instrumentation is correct?

Verify the basic integrations steps in the integration guide and then access Conviva Pulse to verify the metrics and metadata based on the integrated data.

Troubleshooting and Data Monitoring

Why is the DPI SDK not monitoring data after instrumentation?

Verify that the tracker is initialized with the correct customer key and app name.

Why are some of my network requests missing?

  • Verify the SDK point of initialization.

  • Verify the blocklist and feature enablement in the remote config.

After app startup, the app uses a remote config to decide which analytics to initialize. Is that a problem?

Not initializing the DPI SDK at the time of app launch may cause some events to not be reported.

Also, the app launch time values may not be reported accurately.

Which network requests does the DPI SDK block by default.

Check the default blocklists:

 

Android Support Details

iOS Support Details

Web (JS/React) Support Details

 

 

 

 

DPI integration FAQs DPI integration frameworks