Pulse - Internal

Art. no. 217065011

What is Pulse?

Pulse is Schibsted's proprietary platform for tracking user behavior in web and native apps. Schibsted has closely linked Pulse to Sourcepoint, a third-party platform for managing consent settings.

What is it used for? / What are its functions?

It’s fully created and owned by Schibsted and is currently not used by any other customer.
It is used throughout many Schibsted web sites across multiple countries.

Pulse is included since 2023 in the Swedish Prenly apps Aftonbladet and eSvD. From April 2024 it will be included in the Norwegian Prenly apps VG, Aftenposten, Bergens Tidende, Stavanger Aftenblad and Magasin+.

Technical details

For the web reader Schibsted has combined Pulse and Sourcepoint into one javascript repository. For the native apps there are two separate SDKs: Pulse SDK (created by Schibsted) and Sourcepoint SDK (owned by a third-party provider)

As of March 2024, only the two events “replica_page_open” and “article_open” are sent to Pulse.

Testing Pulse

At Textalk we have no access to Pulse’s database or visualization tools. We just ensure that our apps send events according to the schemas defined by Schibsted.

For the web it is easy to use the Chrome inspector to verify that the events are dispatched with the correct parameters.
For native apps it is more challenging. Our developers can include Schibsted’s own testing tool - Unicorn - in separately built debug apps. In Unicorn it is possible to verify each event and all of its parameters including the consent settings.

How is Pulse implemented? - What actions are needed from us?

How to add Pulse to web reader

To add Pulse to the web reader you first need to create the statistics module. Then you have to add the statistics module to the web client.

Create the Statistics module

Follow these steps to create the statistics module:

Go to Superadmin
Select the customer Schibsted
Scroll down to Statistics modules
Click on Add
Select type: Pulse
Type a clear name
Fill in the necessary fields: client ID, Realm, Commnon subscription name
Go down and enter the purpose IDs.
Save.

When the module is created you have to add it to the web client.

Add the Statistics module to the Web client

Go to Applications
Select the application
Select the Web client
Add the Statistics module to the Web client

Add Pulse to native apps: IOS + Android

You have to add the Pulse Statistics modules to the IOS and Android clients in Superadmin. This is to pass the Sourcepoint purpose IDs to the Pulse reporter.

When building the apps you have to add Pulse SDK to the project. Pulse SDK is created by Schibsted. Then you have to configure the ClientID and the Common subscription name. This is documented in GitHub. For reference the configuration for eSvd can be studied.

How is Pulse implemented? - What actions are needed from the customer?

When a new app is created, we need to have these configuration values from the customer to include Pulse:

Client ID
Realm
Common subscription name

We also need the CMP Purpose IDs to forward the consent values to Pulse. In Sweden’s titles we have ids for all purposes. In Norway’s titles purpose ids are only used for Advertisement.