Skip to content
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

Analytics updates #403

Merged
merged 7 commits into from
Nov 6, 2024
Merged

Analytics updates #403

merged 7 commits into from
Nov 6, 2024

Conversation

olivier-lando
Copy link
Member

@olivier-lando olivier-lando commented Oct 25, 2024


This was referenced Oct 25, 2024
- `true` means that a single user watchig multiple times counts as 1 unique viewer
- `false` means that all views count, even if from the same user.

The API accepts this parameter only when you use the `ccv-peak`, `ccv-average`, or `view` metric.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure this description applies to metrics routes too, but if so, maybe you should also list the ccv metric?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice catch, fixed! For this route, the sentence should be:

The API accepts this parameter only when you use the ccv or view metric.

TODO
Use this query parameter to define how many seconds a view has to last to be counted in analytics data.

- You can only use this parameter together with the `view` metric.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd remove the with maybe?
"You can only use this parameter with the view metric."
Or maybe "You can only use this parameter along the view metric." ?

(i'm forgetting how to English)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed: removed "together".

@@ -13335,7 +13365,7 @@ paths:
- `device-type`: Returns analytics based on the type of device used by the viewers. Response values can include: `computer`, `phone`, `tablet`, `tv`, `console`, `wearable`, `unknown`.
- `operating-system`: Returns analytics based on the operating system used by the viewers. Response values can include `windows`, `mac osx`, `android`, `ios`, `linux`.
- `browser`: Returns analytics based on the browser used by the viewers. Response values can include `chrome`, `firefox`, `edge`, `opera`.
- `referrer`: TODO
- `referrer`: Returns the URL where the view originates from, for example a website where the video is embedded. View events from Android and iOS return empty strings as referrer.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Last sentence should maybe be: "View events from Android and iOS return empty strings as the [or a] referrer."

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed as:

View events from Android and iOS return empty strings as the value for referrer.

TODO
Use this query parameter to control how viewer data is counted:

- `true` means that a single user watchig multiple times counts as 1 unique viewer

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

watching

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice catch!

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed ✅

TODO
Use this query parameter to control how viewer data is counted:

- `true` means that a single user watchig multiple times counts as 1 unique viewer

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

watching

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed ✅


- If you do not set a value for `interval`, and the period you set using the `from` and `to` parameters is less than or equals to 2 days, then the default assigned value is `hour`. Otherwise the API sets it to `day`.
- When you set `minute` as interval, the timeframe you define with the `from` and `to` parameters should be less than 60 minutes.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"must be" instead of "should be"

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Corrected to must

@@ -17004,6 +17148,7 @@ components:
- `operatingSystem`: Returns analytics based on the operating system used by the viewers. Response values can include `windows`, `mac osx`, `android`, `ios`, `linux`.
- `browser`: Returns analytics based on the browser used by the viewers. Response values can include `chrome`, `firefox`, `edge`, `opera`.
- `tag`: Returns analytics for videos using this tag. This filter only accepts a single value and is case sensitive. Read more about tagging your videos [here](https://docs.api.video/vod/tags-metadata).
- `referrer`: Filters data based on the URL where the view is originating from. Accepts an empty string as a value to filter view events where no referrer is available.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe it's worth specifying two things:

  • this is an exact match; even forgetting a slash (for example) at the end of the referrer string will end up in no results showing up
  • the value of this filter needs to be URL encoded; for example https%3A%2F%2Fmy-awesome-videos.com

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added missing specifications. Thanks Mio!

@olivier-lando olivier-lando marked this pull request as ready for review November 6, 2024 08:42
@olivier-lando olivier-lando merged commit 216b719 into main Nov 6, 2024
14 checks passed
@olivier-lando olivier-lando deleted the analytics-updates branch November 6, 2024 08:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants