Webview - Double calls

Silver Contributor
Silver Contributor


we are implemeting Tealium SDK on an hybrid app which have native pages (with the Tealium SDK and hidden webview, so the mobile.html library) and webview pages (with Tealium utag.js deployed).

I have read this documentation and from what I understand there is an interaction between utag.js and mobile.html so all the webview data are sent to the app data collection as well.

As we are planning to use the same Adobe Analytics report suite for both app and web, doesn't it mean that every webview will generate 2 entries? One as web page and one as app page?

Is there anyway to stop the web one?





Webview - Double calls

Gold Contributor
Gold Contributor

Hi Davide,

Yes, you are correct. If you are using the Tealium SDK and utag.js on the same hybrid app, then every webview will generate two entries in Adobe Analytics: one as a web page and one as an app page.

This is because the Tealium SDK and utag.js are both tracking the webview, and they are both sending the data to Adobe Analytics.

There is a way to stop the web one from being sent to Adobe Analytics. You can do this by setting the allowAppTracking property to false in the utag.js configuration.

Here is an example of how to do this:

utag.config.allowAppTracking = false;

This will prevent the webview from being tracked by utag.js, and it will not be sent to Adobe Analytics.

However, it is important to note that this will also prevent the webview from being tracked by the Tealium SDK. This means that you will not be able to track any events that occur in the webview, such as clicks or page views.

If you are not tracking any events in the webview, then you can safely set the allowAppTracking property to false. However, if you are tracking events in the webview, then you will need to decide whether you want to track the webview as a web page or as an app page.

I hope this helps!

Let me know if you have any other questions.

Shivam Joshi

shivam joshi