SRGSSR / pillarbox-documentation

Technical cross-platform documentation for Pillarbox

3 stars 0 forks source link

Discuss RTS Commanders Act analytics needs #33

Closed defagos closed 11 months ago

defagos commented 12 months ago

As a Pillarbox developer I need to better understand RTS analytics needs (other BU needs have been identified more clearly, see #26).

Acceptance criteria

Open questions have been discussed with RTS analytics team and answered:

How are user_id and user_is_logged used at RTS?
How are device types (phone, tablet, TV) used at RTS? Is the current diagonal-based criterium sufficient even if not perfect?
How is source_id used? Is it used outside legacy products? Do we have to keep it?

Tasks

[x] Discuss with Martin and Vincent (7th floor, Digital Analysts).

defagos commented 11 months ago

Currently RTS does not use user_id and user_is_logged in reports. So we won't offer official fields in Pillarbox analytics. If RTS products later need these fields we might introduce custom label support in Pillarbox. Maybe when this is thee case maRTS will have disappeared anyway.
We can keep the current rules for Android (diagonal length). Not a problem that the criterium is different from iOS (where the information is exact).
sourceId is not used by RTS teams but maybe only forwarded to the RTS recommendation engine. If this is the case maybe we could send this id to the recommendation engine directly, not through Commanders Act? /c @pyby