In the Google ML Kit web documentation it discusses that usage metrics will be uploaded but does not give a lot of detail: https://developers.google.com/ml-kit/terms#privacy
Does anyknow know (or know a contact) as to whether the metrics upload uses an HTTPS protocol? Also if someone knows more details about the metrics that are uploaded.
PM for ML Kit here. Correct, the metrics are encrypted in transit using SSL (Https). We'll add this clarification to the privacy page.
Related
enter image description hereI'm having trouble configuring the conversions API, I can't do it automatically and I can't do it manually either
Follow print below
This Google bug. Google already knows about it.
You can try sGTM hosting from Stape.io
I have some questions about uploading images to cloud storage, I wish someone could help me. I would like answers according to best practices:
Which is better, send the images to my API with all other form information and then send them to the cloud or upload them to the cloud directly via Frontend and separate from other form information?
Do I need to make a request for each image or is it better to upload all images directly?
Backend generates a signed url at which the client uploads the video directly - this requires solid authentication
Depends if the client has a good internet connection or not but batching is usually good
We're in the process of trying to get our Google Data Studio connectors' OAuth Client Verified and the process requires a video of the application in use (as per https://support.google.com/cloud/answer/9110914), however the documentation mentions:
Note that the video must clearly show the app's details such as the
app name, OAuth Client ID, etc. as applicable. The demo video must
show usage of sensitive and restricted scopes on each client.
But we are not in control of GDS, only our connectors. We only use the /auth/script.external_request scope to make calls to our own API.
What should we include in our video to show this information?
Reference:
screengrab of the e-mail we received listing requirements
This is a Google OAuth verification requirement. You should ideally reach out to the OAuth verification team for clarifications.
However, for the video, you can try just opening up Data Studio and installing your connector using the direct deployment link. Then you can create a data source using the connector and draw a table to demonstrate how data is fetched from your API using the external_request scope.
my dev and I would like to implement the google picker on our website. It will allow the web-visitor to upload their files from their Google drive to our website.
My dev is now trying to get the API for the google picker however they are asking for a "demo video that showcases the process to request an OAuth token" and we were wondering how we should do it when we don't have the API from google.
We are doing all of this on the staging site and we were wondering how are we suppose to do this demo video when the API is not provided and not installed.
please enlighten us, thank you!
See the question How can I make sure the verification process is as streamlined as possible? in the FAQ. It explains what the verification team is looking for with the video. Mostly it's just about showing how your product uses OAuth and the various APIs -- in your case how it asks for access to Drive, how the picker is used, etc. You're showing the integration from the user perspective.
Recnetly, I have seen a video.js plugin (https://github.com/videojs/videojs-contrib-ads) that provides common functionality needed by video advertisement libraries.
Since I'm pretty new to this area, not sure what kind kinds of video networks can be used here, in addition to Google Video Adsense.
Could you list all possible (and well-known) video networks that can be used with this library?
Thanks!
videojs-contrib-ads is just a framework for ad support, you do need an additional plugin that builds off that to interact with the ad server and act on the response. Google's IMA plugin is an example of that, and should work not only with DFP but with other VAST-compliant ad servers.