code management for hybrid apps¶

Measurement of hybrid apps¶

With the measurement of mobile apps, INFOnline also offers the option of measuring hybrid apps. The definition of hybrid app according to IVW guidelines states that apps that have a native app part but also access one or more mobile-enabled website(s) for their content ("hybrid apps") are treated uniformly as an app with their entire usage when assigned and published in the category system 2.0 (Cat 2.0).

The INFOnline Measurement measuring system implements this guideline by assigning the traffic of a mobile-enabled website (MEW) generated in the WebView of a hybrid app at runtime to the site ID of the app rather than the site ID of the MEW when generating the measurement requests. MEW traffic that is not generated from a hybrid app, but from a standard mobile browser, will still be mapped to the MEW's offer ID as a regular practice.

The implementation of this policy has an impact on the management of the codes that classify the content of the content and that have to be assigned in the code management according to category system KAT 2.0.

Special case native app with hybrid measurement technology.¶

• This is a hybrid app whose web content cannot be accessed externally.
• The IVW guidelines cited at the beginning refer to mobile-enabled websites. One characteristic of MEWs is that they offer content under their own publicly accessible URL that is optimized for the browsers of mobile devices.
• In practice, there is a special form of hybrid app. These apps have a native app component and also use mobile-optimized web content, although this is not offered independently from the MEW. This web content is based on the same technology as MEWs, but cannot be accessed outside the hybrid app. This type of app is subsequently referred to as a native app with hybrid measurement technology.
• Code management for the special case of native app with hybrid measurement technology is described in section Code management for native apps with hybrid measurement technology.

Code management for hybrid apps¶

Initial situation¶

Hybrid apps are made up of two components in terms of content:

• Component 1 forms the native app framework.
• Component 2 is the content that is loaded from a mobile-enabled website (MEW) via the WebView integrated into the app.

The following prerequisites must be met for hybrid app measurement:¶

• Use the INFOnline Measurement Manager as the basis for use in the desktop / MEW area.
• The app has its own site ID (subsequently referred to as Site IDApp). Codes are assigned for content that is displayed via the native app frame. These page codes are assigned to OfferIdentifierApp in the INFOnline Measurement.
• Integrating hybrid app measurement as described in INFOnline's Integration Guides for app and for MEW measurement.

**If you are unable to use Measurement Manager, please contact Customer Service.

Allocation of the MEW share of hybrid app usage to the app (technical).¶

According to IVW specifications, the usage share of a hybrid app that results from calling up a MEW in the WebView must be assigned to the app. The technical implementation of this requirement is realized in the INFOnline Measurement system as follows:

• Measurement of the native app share: All usage processes that are measured within the native app app share are reported to the measurement system under the offer identifierApp. Those usage transactions that represent a mobile impression are assigned a page code defined by the app provider and to be assigned in the KAT 2.0 category system.
• Measurement of MEW share: If the WebView is called up within the app to display a MEW, the processes in the measurement are as follows:
• 1. the MEW web page called up contains an INFOnline measurement tag with the offer identifierMEW.
• 2. the iom.h script called up via the INFOnline Measurement tag independently recognizes that the call-up is taking place in a WebView of a hybrid app is taking place. It automatically rewrites the site ID for the measurement call to siteIDApp. 3.
• At the same time, a prefix is added to the page code that classifies the content. This reads: ___hyb___AngebotskennungMEW___

The following table compares the original MEW request and the dynamically adapted call in the hybrid measurement using an example:

???+ info "Note

1

The prefix of the code takes 20 characters. To ensure the uniqueness of the code derivations below the app identifiers, the code in the MEW must not be longer than 234 characters. If the MEW codes are longer than 234 characters, correct synchronization of the assignment cannot be guaranteed.

Code management¶

The dynamic adjustment of the measurement request in the MEW part of the hybrid app results in codes coming in under the offer identifierApp that do not originate there.

Code derivations¶

The MEW code Home1234 named in the example was created in the MEW and assigned to the category system 2.0 under the offer identifierMEW.

By calling it up in the context of a hybrid app, a derivation of the MEW code ___hyb___offer identifierMEW___Home1234 has been delivered to the INFOnline Measurement below the offer identifierApp.

Assignment of derived codes in code management according to KAT 2.0¶

In order to simplify the assignment of derived codes below the offer identifierApp and to save the customer the effort of maintaining the assignment of derived codes x times (a code would otherwise have to be maintained manually below the offer identifierMEW and below all offer identifiersApp that use the MEW in the hybrid share), INFOnline has set up automatic synchronization of the assignments in code management according to category system KAT 2.0.

This ensures that the category assignment of the MEW code in the example

Home1234 under the offer identifierMEW

to all derivations of the code

___hyb___AngebotskennungMEW___Home1234

to be transferred below all offer identifierApp.

Adjustment of the "App" category¶

In the following categories of the KAT 2.0 category system, the category assignments of a code are transferred unchanged to the derivations of the code.

1. format
2. language
3. producer
4. homepage
5. delivery
6. paid content / service*
7. content

The category "6th App" in the derivations of the codes below the offer identifierApp is always set to the value "App" as part of the synchronization.

Further information¶

This synchronization takes place daily at 0:00, so that a daily updated assignment of the derived codes is guaranteed analogous to the assignment of the MEW code.

Deactivation of synchronization¶

If you do not want the described automatic synchronization of the page codes, please contact Customer Service.

Code management for native apps with hybrid measurement technology¶

Initial situation¶

Native apps with hybrid measurement technology are made up of two components in terms of content, analogous to the structure of hybrid apps: Component 1 forms the native app framework and Component 2 represents the content that is loaded via the WebView integrated into the app. Unlike hybrid apps, the source of the web content is not public, but only accessible from the native app with hybrid measurement technology.

The following requirements for the measurement of native apps with hybrid measurement technology must be met:

• The app has its own site ID (hereafter referred to as siteIDApp). Codes are assigned for content that is displayed via the native app frame. These page codes are defined in the INFOnline Measurment system of the OfferIdentifierApp.
• Web content included via the WebView is tagged with INFOnline Measurement Manager. In INFOnline Measurement Manager, the site ID of the app that uses the content is used (subsequently referred to as Site IDWebContent). The web content contains codes that are used for categorisation of the content in the code management according to category system KAT 2.0.

Allocation of MEW share of hybrid app usage to app (technical).¶

According to the IVW specifications, the usage share of a hybrid app that is created in the WebView by calling up a MEW must be assigned to the app. The technical implementation of this requirement is realized in the INFOnline Measurement System as follows:

• Measurement of the native app share: All usage transactions that are measured within the native app share are reported to INFOnline Measurement under the offer identifierApp. Those usage transactions that represent a mobile impression are assigned a page code defined by the app provider and assigned in code management in accordance with the KAT 2.0 category system.

• Measurement of the share of web content: If the WebView is called up within the app to display web content, the processes in the measurement are as follows:

• 1. the web content accessed includes an INFOnline Measurement tag 2.0 with the OfferIdentifierWebContent.
• 2. the script called via the tag independently recognizes iom.h that the call takes place in a WebView of a hybrid app. It automatically rewrites the site ID for the measurement call to siteIdApp.
• 3. at the same time, it adds a prefix to the page code that classifies the content. This reads: ___hyb2___AngebotskennungWebInhalt___

The following table compares the original web content request and the dynamically adjusted request in the hybrid measurement:

Code management¶

The dynamic adaptation of the measurement request in the web part of the native app with hybrid measurement technology shown results in codes arriving under the offer identifierApp that have the prefix ___hyb2___offer identifierWebContent___.

Analogous to the codes from the native app frame, these are listed in the code management of the INFOnline Customer Center under the offer identifierApp and can be assigned there according to the KAT 2.0 category system.

To note¶

If several native apps with hybrid measurement technology use the same web content that is not publicly accessible, the assignment of the resulting codes with the prefix ___hyb2___offer identifierWebContent___ must be made separately in each app!