-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
comScore analytics open questions #25
Comments
General questionsQuestion 1
comScore collects the IDFA, otherwise only the IDFV. The IDFA is not used to track the user between different vendors. Question 2
Not possible at the moment. The SDK will buffer the events that could not be sent. Page view questionsQuestion 1
There are implementation guides that we will receive (guide and intake form). The GD should have this documentation. No special handling or encoding should be required for special characters, the SDK takes care of that. Question 2
The expected labels are provided in the specification, other labels would be ignored anyway, so no arbitrary labels needed anymore. Question 3
For apps what Mediapulse measures is foreground time. This means not every page view is actually needed to get correct measurements for Mediapulse. A single page view at the beginning would suffice but Mediapulse observed that data is more accurate if we record each and every page view following user interaction. So more is better. Question 4
In a single app a split screen should not be a problem since it should not affect the foreground time. So measuring two page views is not an issue. Question 5
From a regulatory perspective we are allowed to measure the app when in foreground. It would in fact be better to not track a car UX from a comScore perspective. Question 6
Streaming questionsQuestion 1
Yes, but also for heartbeats. There are effects in internal state, time measurements. Question 2
We should not use these methods in Mediapulse context. Useful only for app background usage which Mediapulse is not interested in. Question 3
If we are able to provide accurate positions near the live edge then yes, no rounding is needed. Question 4
Kantar is doing timestamp matching based on the live offset to find which content was played. Question 5
Probably within the 5 seconds after SDK initialization, not after play. Question 6
See remark below: A video should not be tracked if < 50% visible. Depending on the platform we can partially implement this behavior but it is likely we cannot cover all cases (e.g. PiP), see SRGSSR/pillarbox-apple#447. Additional remarks
|
We received access to a documentation SharePoint with several documents about Mediapulse integration. |
All questions answered and dedicated tasks created. Done. |
As a Pillarbox developer I need to have some comScore-related questions answered so that I can provide a compliant implementation.
Acceptance criteria
Tasks
General questions
Page view questions
ns_category
and provide just a name, not a full path built client-side)c8
?Streaming questions
notifyUxActive
andnotifyUxInactive
reference counted?ns_st_ldo
taken into account in measurements? Is there a problem if DVR playback starts at the live edge with a non-zero value?Resources
Some resources might be outdated:
The text was updated successfully, but these errors were encountered: