Integrations
All picoask connectors are read-only. Every credential on this page grants read access only: picoask reads reporting data and never writes to, creates or manages anything through a connector.
Changing something in a connected account — pausing an ad set, shifting budget — is a separate capability with its own permission, never part of connecting a source. You grant it explicitly per account, it is stored apart from the read credential, and you can revoke it at any time. Actions wait for your approval, are logged, and are reversible. See how actions work.
1Available today
| Source | What picoask reads | Status |
|---|---|---|
| Meta Ads | Campaign, ad set and ad performance across Facebook and Instagram, with spend, impressions, clicks and conversions. Setup guide → | Available |
| Google Ads | Campaign and ad performance: spend, impressions, clicks, conversions and conversion value. You supply your 10-digit Customer ID and approve a manager-account link request from inside Google Ads — there are no tokens to copy. Field by field → | Available |
| Google Analytics 4 | Sessions, users, traffic sources and conversions, joined to the campaigns that drove them. Setup guide → | Available |
| Google Analytics 4 — BigQuery export (raw events) | Raw, event-level GA4 — every page view, session, add-to-cart and purchase with its items — read from your property's own BigQuery export. Forward-only from the day you link it; the regular GA4 connector keeps the history. Setup guide → | Available |
| Shopify | Orders, line items, refunds, discounts and customers — so revenue can be read against the advertising that produced it, and a refund stays dated to the day it happened. Setup guide → | Available |
| WooCommerce | Orders, refunds, products, discounts and customers from your WooCommerce store — refunds dated to the day they happened, promo-code performance from real redemptions, and your catalog's current prices and stock so 'what's out of stock' is answerable. A read-only REST key; picoask never needs write access. Setup guide → | Available |
| Superleap | Leads, contacts, deals and activities from your Superleap CRM, so pipeline can be read next to the marketing that fed it. Setup guide → | Available |
| Stripe | Payments, refunds, invoices, subscriptions, payouts and customers — refunds dated to the day they were issued, Stripe's own fee and net amounts on every payment, and a read-only restricted key so picoask never holds your secret key. Setup guide → | Available |
| PayPal | Payments, refunds, chargebacks and bank transfers — PayPal's own fee and net on every transaction, refunds dated to the day they happened and kept distinct from chargebacks, and bank movement separated from revenue so 'what reached the bank' never inflates sales. A REST app with only Transaction Search enabled; picoask can never move money. Setup guide → | Available |
| Cashfree | Payments, settlements and refunds from Cashfree — collected revenue with Cashfree's own fees, refunds dated to the day they happened, and settlement tracking for money actually reaching the bank. Setup guide → | Available |
| PayU | Payments and refunds from PayU — transaction-level revenue with status and payment-mode breakdowns, and refunds kept refund-dated so monthly numbers tie out. Setup guide → | Available |
| Shiprocket | Shipments and courier performance from Shiprocket — delivery and return status over time, courier-level comparisons, and shipping cost against the orders it fulfilled. Setup guide → | Available |
| Myntra | Orders, order lines and returns from your Myntra seller account — SKU, MRP, seller and marketplace discount, and amount received on every line, with returns and RTO dated by the return so return rate is answerable. Read-only via MMIP. Setup guide → | Available |
| Nykaa | Orders, order lines and returns from your Nykaa marketplace account — SKU, quantity, price, tax and status, with returns and RTO dated by the return. Read-only via Nykaa's Vinculum API. Setup guide → | Available |
| Google Sheets | The tabs of any sheet you share with your project's robot account — budgets, targets, manual trackers — readable next to your live data. Setup guide → | Available |
| File uploads | One-off CSV and export files, dropped straight onto a project and queried like any other table. Setup guide → | Available |
2Your own database
picoask connects read-only to the database you already run, so your orders, subscriptions and customers can be analysed alongside your advertising data.
| Database | Status |
|---|---|
| PostgreSQL | Available |
| MySQL | Available |
| Amazon Redshift | Available |
| Snowflake | Available |
| Google BigQuery | Available |
Connection details are encrypted and used only to run the queries that answer your questions. See the docs for what picoask needs and how to grant least-privilege access.
3On the roadmap
155 more sources are on the picoask connector roadmap. Every one has a page — and requests drive our build order, so if yours is here, start free and request it from your project's Data → Connectors tab.
No source matches — tell us what you use.
4How the data is handled
- Your own warehouse. Connector data lands in a warehouse schema belonging to your account — never pooled with another customer's.
- Encrypted in transit. All platform API traffic and all warehouse connections use TLS.
- Reported separately. Each platform's figures stay attributable to that platform, so you can view any source on its own as well as blended with other channels.
- Disconnect at any time. Removing a connector in picoask stops all further reads immediately; you can also revoke access from the platform itself. On request we delete the synced data within three business days.
Email contact@picoask.ai and tell us what you use. See also the picoask docs.