Google Places
v0.0.0
Check out the API docs here for more information.
Set up
To get set up with the Google Places connector, you will need an API Key for the Places API (New).
If you do not already have a Google Cloud Project, you will have to create one before you can generate API Keys for the API. Instructions on how to do this can be found here.
After creating your Google Cloud Project and enabling billing you can create API Keys by following the steps here.
Please note that the connector makes calls to the API, which will be billed against your Google Cloud Project. Information on usage and billing can be found here.
Features
Feature | Support | Notes |
---|---|---|
Backfill | ✅ | Full backfill on all reports |
Incremental | ❌ | Incremental not supported |
API reliability | 🟢 | Reliable |
Reports detail
⬇️ Report | 🔑 Incremental key | 🔑 Primary key | 📄 Link to API endpoint |
---|---|---|---|
Places Data | N/A | ID | Place Details |
Places Data (with table) | N/A | ID | Place Details |
Requested fields
Both reports allow you to provide a comma-separated list of fields, that are requested for the each place. On the extract setup page you can give this list in the mandatory
Requested fields
input field.It defaults to
*
, which means all available fields will be requested. Doing this can result in higher charges for each API call.A list of acceptable fields can be found here.
Place IDs
Both reports need a list of place IDs, which will be used in the API calls, that the connector makes.
Places Data
report requires you to give a comma-separated list of IDs on the extract setup page (in thePlace ids
field).
Places Data (with table)
report requires you to point to a table in the Data Warehouse and a column in the table that contains the valid place IDs.
Updated 21 days ago