Linking Marketstack as a source
Let AI connect your sources for you
Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.
This source is currently in alpha. The interface and available tables may change.
The Marketstack connector syncs eod, intraday, splits, and more into the PostHog data warehouse, so you can analyze them alongside your product data.
Prerequisites
Credentials that can read the data you want to sync. PostHog only reads data, so read access is enough.
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.
Enter your Marketstack access key to pull end-of-day, intraday, splits, and dividends data plus market reference tables (tickers, exchanges, currencies, timezones).
You can find your access key in your Marketstack dashboard.
Add one or more comma-separated symbols (e.g. AAPL,MSFT,TSLA) to sync the EOD, intraday, splits, and dividends tables - those endpoints require at least one symbol. The reference tables don't need symbols.
Note: Marketstack pricing is a monthly request quota tied to your plan. Some tables (e.g. intraday) require a paid plan.
You'll be asked for:
- Access key
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.
All Marketstack tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Type | Required |
|---|---|---|
Access key | password | Yes |
Symbols | text | No |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
eod | End-of-day (daily OHLCV) stock prices per symbol, including adjusted prices, split factor, and dividend. Requires symbols. Incremental on date. | Incremental, Full refresh | date | — |
intraday | Intraday (intra-day interval) stock prices per symbol. Requires symbols and a paid plan. Incremental on date. | Incremental, Full refresh | date | — |
splits | Historical stock split factors per symbol. Requires symbols. Incremental on date. | Incremental, Full refresh | date | — |
dividends | Historical dividend payouts per symbol. Requires symbols. Incremental on date. | Incremental, Full refresh | date | — |
tickers | Reference table of supported stock tickers with name, exchange, and EOD/intraday availability. Full refresh. | Full refresh | — | — |
exchanges | Reference table of supported stock exchanges with MIC/acronym codes, country, and timezone. Full refresh. | Full refresh | — | — |
currencies | Reference table of supported currencies with ISO code, symbol, and name. Full refresh. | Full refresh | — | — |
timezones | Reference table of supported timezones with abbreviation and daylight-saving abbreviation. Full refresh. | Full refresh | — | — |
Troubleshooting
- If the connection fails with an authorization error, the access key is wrong, expired, or has been revoked. Create a new one, then reconnect the source.
- If a table syncs no rows, the credential may not have access to that data. Check its permissions, then reconnect the source.
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.