Before you connect anything, it helps to know which way in fits the data you have. What visitors do on your site arrives as a live stream of events; what’s in a spreadsheet arrives as an upload; what sits in a database or data lake can be synced or read where it lives. Find your data in the table below and follow the link.
Pick your route
| Your data | Route | Plan |
|---|---|---|
| What visitors do on your website or web app | Google Tag Manager tag | every plan |
| What shoppers do in your Shopify store | Shopify pixel | every plan |
| Anything you can export — orders, ad spend, reviews, listings | Upload a file | every plan |
| A database behind your firewall | On-prem sync connector | Team |
| Tables already in your Postgres or Iceberg data lake | Your own data lake | Team |
“Behind your firewall” means a database on your own servers or private network that the internet can’t reach directly. A data lake is a large store of tables your team already keeps, often for other analytics tools.
Ask across all of it
Everything lands in your own workspace, so you can ask one question that spans several sources — your site’s sign-ups next to your ad spend, say. See Two datasets, one question.
Good to know
- Heads up: the tag and the pixel need a verified domain before any event is accepted. It’s worth starting that step first.
- Tip: no ad-platform connector yet? Your spend comes in as an export — see Bring in your ad spend.
Related
- Website & ad ROI — the tag plus a spend export, worked through.
- Shopify & e-commerce — the pixel plus your store’s exports.
- Any dataset — one uploaded file, start to finish.