Is app tagging validation needed for webview pages of app?

[DebanjanaBh1]

I would like to know if app tagging validation is needed for webview pages of app if web tags are validated? By design both the tags in web and app (webview) are same and should work similarly. However, can you please share instances/features/use cases where the same Adobe tags might work on web but not on app (web view page)? Also any specific app interaction on webview where the tags would break in app but work on web? 

Please help!

[EurosIMS]

Hi @DebanjanaBh1,

Is the App tagging done via Adobe Mobile SDK? As that shouldn't work at all on a Webview page; they are fundamentally different. In my experience, the Mobile SDK would be delivered/set via a Launch container to the App, then on transfer to Webview pages (Checkout usually), a separate, standard Web Launch container would handle that. 

[DebanjanaBh1]

No app tagging is not done via the mobile web sdk. We use Launch to deliver the tags on both app and web. Question was more on the app feature specific nuances where the same tags would still work on web but might not work on app. Are there such examples/use cases that you can share so that it becomes necessary to validate the tags both in web + app though by design they are the same and should work as expected on both.

Thanks for enlightening me! This is needed to convince the QA team the need to validate both.

[EurosIMS]

I imagine it's not in your purview, but I'd strongly recommend using Mobile SDK for the app or pushing your team strongly to do that. It offers so many app-specific features that will enhance reporting.

Failing that, depending on how your app is built, standard web tracking may not work correctly for downloads, exit links, button click-based rules, page loads (which can work very differently on apps), SPAs, screen scraping, data layer extracted data, & various other things including, but not limited to, 3rd party tags, extensions, & cookie classifications/checks. 

Essentially, you'd need a robust Q&A/testing regime for checking basically anything that is on web to see if it continues to work on the App. 

[Jennifer_Dungan]

Wow, that's kind of crazy...

Regardless of being the "same tag" or not, even on web you need to test code on different OS and Browser combinations to ensure that it's working... the same goes for the mobile app.. you need to test the app, and on iOS and Android... 

I am assuming that your mobile app, if it's being controlled by the same Launch, is something like a "website wrapped by a mobile app framework"... that the app is basically just a frame opening the website via a "webview"?

And while yes, this should act the same, the presence of the wrapper could cause interference... always best to check... even if it's only spot checking and confirming the most important flows...