Automate Google Playable Locations
HumDay reads Google Playable Locations’s own published API description and derives 3 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.
What HumDay can do in Google Playable Locations
3 documented operations change something in Google Playable Locations.
- POSTLogs new events when playable locations are displayed, and when they are interacted with.
/v3:logImpressions - POSTLogs bad playable location reports submitted by players.
/v3:logPlayerReports - POSTReturns a set of playable locations that lie within a specified area, that satisfy optional filter criteria.
/v3:samplePlayableLocations
How automating Google Playable Locations works
- Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
- Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
- See it proven. The program runs and shows you the result before it is allowed near your live Google Playable Locations account.
- Grant access, then go live. You approve the specific Google Playable Locations operations it may use — and only those.
Automate Google Playable Locations with these
- Gmail79 operations
- Google+9 operations
- Google Abusive Experience Report2 operations
- Google Accelerated Mobile Pages (AMP) URL1 operations
- Google Access Approval7 operations
- Google Access Context Manager9 operations
- Google ACME DNS2 operations
- Google Ad Exchange Buyer38 operations
- Google Ad Exchange Buyer II50 operations
- Google Ad Experience Report2 operations
- Google Admin SDK122 operations
- Google AdMob7 operations
Categories
Questions about Google Playable Locations automation
- Can HumDay connect to Google Playable Locations?
- Yes. HumDay reads Google Playable Locations's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 3 operations are documented.
- Do I need to write code to automate Google Playable Locations?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Google Playable Locations account.
- What can HumDay do in Google Playable Locations?
- 3 of the 3 documented operations change something in Google Playable Locations, and 0 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my Google Playable Locations account safe?
- Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Google Playable Locations is held behind that approval.
Where this came from
The operations above are read from a published API description for Google Playable Locations at playablelocations.googleapis.com/$discovery/rest?version=v3. Descriptions are the provider’s own words, not ours. Last published 2021-06-21.