tap-google-play
Singer tap for Google Play Reviews. Built with the Meltano Singer SDK.
Based on hotglue/tap-google-play.
Capabilities
catalogstatediscoveraboutstream-mapsschema-flatteningbatch
Settings
| Setting | Required | Default | Description |
|---|---|---|---|
| app_id | False | None | The app ID to extract reviews from. |
| app_id_list | False | None | A list of app IDs to extract reviews from. |
| start_date | False | None | The date to start extracting reviews from |
| stream_maps | False | None | Config object for stream maps capability. For more information check out Stream Maps. |
| stream_map_config | False | None | User-defined config values to be used within map expressions. |
| flattening_enabled | False | None | 'True' to enable schema flattening and automatically expand nested properties. |
| flattening_max_depth | False | None | The max depth to flatten schemas. |
| batch_config | False | None |
A full list of supported settings and capabilities is available by running: tap-google-play --about
Usage
You can easily run tap-google-play by itself or in a pipeline using Meltano.
Executing the Tap Directly
tap-google-play --version
tap-google-play --help
tap-google-play --config CONFIG --discover > ./catalog.json
Developer Resources
Initialize your Development Environment
Install uv if you haven't already.
Create and Run Tests
Create tests within the tests subfolder and then run:
uv run pytest
You can also test the tap-google-play CLI interface directly using uv run:
uv run tap-google-play --help
Testing with Meltano
Note: This tap will work in any Singer environment and does not require Meltano. Examples here are for convenience and to streamline end-to-end orchestration scenarios.
Your project comes with a custom meltano.yml project file already created. Open the meltano.yml and follow any "TODO" items listed in
the file.
Next, install Meltano (if you haven't already) and any needed plugins:
# Install meltano
uv tool install meltano
# Install meltano
meltano config meltano set venv.backend uv
# Initialize meltano within this directory
cd tap-google-play
meltano install
Now you can test and orchestrate using Meltano:
# Test invocation:
meltano invoke tap-google-play --version
# OR run a test `elt` pipeline:
meltano run tap-google-play target-jsonl
SDK Dev Guide
See the dev guide for more instructions on how to use the SDK to develop your own taps and targets.
Metadata
Release files for tap-google-play 0.6.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| tap_google_play-0.6.5.tar.gz | 75.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| tap_google_play-0.6.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 85.5 kB
Release files / tap_google_play-0.6.5.tar.gz
| Download URL | tap_google_play-0.6.5.tar.gz |
|---|---|
| Size | 75.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4825501131dfb1f4c66f76f8b473b6b7bc314669470276b29d2408504e774e91
|
|
BLAKE2b-256 checksum How to use checksums |
2a4fb841d41ed7cbb07275641ee5f3af9b1f0e7c41ea4d8740789617db2ec4ae
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 24, 2025.
Transparency logRelease files / tap_google_play-0.6.5-py3-none-any.whl
| Download URL | tap_google_play-0.6.5-py3-none-any.whl |
|---|---|
| Size | 9.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2c53d83e18ae7c65781abc19d5238d2c38e2c2e9ee5d753151382c2c24587dbe
|
|
BLAKE2b-256 checksum How to use checksums |
becc9167ebe9caa31457195081ea8cb9c69b30a90644e298dafdecbfee5cc110
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 24, 2025.
Transparency log
