Linking BreezoMeter as a source
This source is currently in alpha. The interface and available tables may change.
The BreezoMeter connector syncs air-quality and pollen data for the locations you track into PostHog, so you can analyze environmental data alongside your product data. BreezoMeter is now part of Google Maps Platform, and this source uses its Air Quality API and Pollen API.
Prerequisites
You need a Google Cloud project with an API key, and both the Air Quality API and the Pollen API enabled for that project.
Adding a data source
- In PostHog, go to the Sources tab of the data pipeline section.
- Click + New source and click Link next to this source.
- Enter your credentials (see Configuration below) and click Next.
- Select the tables you want to sync, choose a sync method and frequency, then click Import.
Once the syncs are complete, you can start querying this data in PostHog.
When linking BreezoMeter, you'll need:
- API key – create an API key in the Google Cloud console and enable both the Air Quality API and the Pollen API for your project.
- Locations – there is no list endpoint, so enter one location per line as
lat,lon(an optional label is allowed:lat,lon,label), for example51.5074,-0.1278,London.
Sync modes
Each table can be synced in one of several modes, depending on what the source supports:
- Webhook (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
- Incremental – only new or updated rows are synced on each run, using a cursor field (such as an
updated_attimestamp). Cheaper than a full refresh, but deletes aren't captured. - Append only – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
- Full refresh – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.
See sync methods for a full explanation of how each mode works and how to choose between them.
Each sync polls every location once per table. To accumulate a history of point-in-time snapshots, pick the append sync method on the table.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Locations | textarea | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
air_quality_current | Current air-quality conditions (AQI indexes and pollutant concentrations) for each configured location. One row per location per sync; use append sync to accumulate a time series. | Append only, Full refresh | dt_iso | — |
air_quality_forecast | Hourly air-quality forecast (up to 96 hours ahead) for each configured location. One row per forecast hour. | Append only, Full refresh | dt_iso | — |
air_quality_history | Historical hourly air quality (the last 24 hours) for each configured location. One row per hour. | Append only, Full refresh | dt_iso | — |
pollen_forecast | Daily pollen forecast (up to 5 days ahead) for each configured location, covering pollen types and plant-level indexes. One row per day. | Append only, Full refresh | dt_iso | — |
Troubleshooting
- If the Air Quality API returns an error, check that your API key is valid and that the Air Quality API is enabled for your Google Cloud project, then reconnect.
- If the Pollen API returns an error, check that your API key is valid and that the Pollen API is enabled for your Google Cloud project, then reconnect.
- If access is denied, check any restrictions on your API key, then reconnect.
If your sync is failing or data looks wrong, see the Data warehouse troubleshooting guide. If that doesn't help, contact support – we're happy to help.