Snowplow WebView plugin released, plus Android and iOS v6.1

Announcements New releases
1

We’ve released a set of updates to improve the hybrid app tracking experience. Hybrid apps are mobile apps that in addition to a native interface, provide part of the UI through an embedded webview.

The new WebView plugin for the JavaScript tracker (v4.3.1) automatically forwards all events to a Snowplow Android (v6.1+), iOS (v6.1+), or React Native (v4.2+) tracker.

Read more about how the plugin works in the documentation.

JavaScript tracker v4.3.1
Enhancements

  • Add WebView plugin (#1402)

Android tracker v6.1.0
Enhancements

  • Add new WebView interface (#700)

iOS tracker v6.1.0
Enhancements

  • Add new WebView interface (#913)

Under the hood

  • Fix typos in internal Structured event constants (#911)

WebView tracker v0.3.1
Enhancements

  • Integrate with new mobile interfaces (#19)

Snowplow JavaScript tracker version 4.3.1 is available as @snowplow/browser-tracker on npm, or as the tag based javascript tracker - available on GitHub Releases, jsDelivr or unpkg.
The project’s source code can be found here.

Snowplow Android Tracker version 6.1.0 is available on Maven Central.
The project’s source code can be found here.

Snowplow iOS Tracker version 6.1.0 is available on Cocoapods.
The project’s source code can be found here.

Snowplow WebView tracker’s source code can be found here.

1 Like
2

Great update! To make sure I understand it correctly:

Does „…any configured mobile context entities will also be added…“ mean that ANY context (including custom global contexts) will be attached from the native app tracker ? If so, is there a way to exclude mobile native global contexts?

I am asking because global context are usually set in the WebView AND in the native app. It would generate redundancy if all global context are added again from the native tracker.

3

Hi @davidher_mann,

Good question! Yes, by default all global context will be applied to these events (both on the JS tracker side and also on the mobile trackers side).

However, if you are using context generator on mobile trackers, you can check the payload properties of the events and see if the tracker version in the payload is JS tracker (starts with js-) and avoid adding them in this case.

We could think about a more OOTB solution to filter out Web view events from global context in the mobile trackers!

1 Like