User consent support in Letterbox / Pillarbox

[defagos]

As a team member I need to better understand app needs regarding the new user consent support. As an app developer integrating SRG mobile libraries I need to be sure that my needs can be covered.

Acceptance criteria

• Needs expressed by SRG and SRF app development teams have been discussed.
• Corresponding player development tasks have been created.

Tasks

• [x] Discuss.
• [x] Create Letterbox Apple required tasks.
• [x] Create Pillarbox Apple required tasks.
• [x] Create Letterbox Android required tasks.
• [x] Create Pillarbox Android required tasks.

[defagos]

Play SRG needs

• Be able to apply user consent configuration changes for comScore and Commanders Act separately, i.e. be able to enable or disable these services on-the-fly at any time.
• Be able to forward a list of service consents to Commanders Act.

SRF needs

• Quite the same requirements as Play SRG.
• Be able to enable or disable Webtrekk / Commanders Act at runtime.

Pillarbox team questions

• How did RTS Info already implement these behaviors? This is a known issue on their side
• Is there a company standard for service consents sent to Commanders Act? Standard is WIP at ADI
• What happens if user consent is removed while a media session is opened? (probably not an issue with Commanders Act mandatory and comScore managing sessions well)
• Do we have to send the user consent list in all events (i.e. global labels)? Yes
• Are we allowed to have start events still sent so that the SDK can be initialized when appropriate (i.e. at launch time)? Probably possible to manage user consent with comScore native support
• Time constraints? Yes but not a hard constraint

Hints

• ~The situation changed several times recently (Commanders Act required vs not required, even if we send user consent per service through it), so having booleans for Commanders Act as well as comScore is probably more flexible.~ Only a Boolean for comScore, Commanders Act cannot be disabled (technical solution).

[defagos]

API proposal: Use the strategy pattern so that each constructed event gets the most recent consent list just before sending the event. IMHO this is better than having a property on the singleton Analytics instance since this avoids nasty dependencies, most notably when the SDK starts (depending on whether the consent information has been set before or after the result would be different).

On Apple platforms this could either be implemented with a delegate (likely a bit too much here) or a closure.

[defagos]

Tasks available for Apple platforms:

• Letterbox.
• Pillarbox.

All done.