by Om RathodShort answer: native Shopify order and inventory data, direct connections to Meta, Google, and TikTok ads, a GA4 feed, email/SMS platforms like Klaviyo, and either an open API or a warehouse layer to tie it all together.
That's the checklist. Screenshot it before you sit through another demo.
Here's the problem. Most platforms nail two or three of those and quietly gap out on the rest. You get gorgeous ad spend charts and a Shopify revenue number, then hit a wall the second you ask "what's my blended CAC including email-driven revenue" or "what did returns actually cost me last month." That's when the spreadsheets come back out, and the whole point of buying an analytics tool evaporates.
So when someone asks what integrations does a good Shopify analytics platform need, the real answer isn't a feature list, it's a test: can this tool actually replace every tab you have open right now, or just some of them.
There's a real difference between a native app connection and a CSV upload dressed up as an integration.
A native connection pulls order, inventory, checkout, and refund data in real time, straight from Shopify's API. A CSV export is a snapshot. It's stale the moment you download it, and someone has to remember to re-upload it every week. That's not analytics, that's homework.
Refunds and discounts are where this gap shows up fastest. A lot of "connected" dashboards only sync order totals, not line-item detail. So a partial refund or a stacked discount code throws off net revenue, and your margin numbers look fine right up until they aren't. If a platform can't show you refund data down to the SKU level, it's not really connected, it's summarizing.
Setup time is a decent proxy for how deep the integration actually goes. A proper native install should take a few minutes, not a dev ticket and a week of back-and-forth. Installing Trivas AI on the Shopify App Store is a good example of what that should look like: connect the store, authorize access, and order and inventory data starts flowing immediately, no CSV, no waiting on IT. For more on how the sync itself works, see the Shopify integration overview.
Minimum viable set: Meta, Google, and increasingly TikTok. That's where most DTC ad budgets actually sit, so those three aren't optional.
Here's the catch. Platform-reported ROAS isn't trustworthy on its own. Meta counts conversions Meta wants credit for. Google does the same. TikTok's attribution window practically guarantees inflated numbers if you're running any kind of retargeting elsewhere. Add all three platforms' "reported ROAS" together and you'll often get a number well north of 100% of your actual revenue. That's not a bug in one platform, it's what happens when every platform grades its own homework.
A good analytics tool pulls raw spend, impression, and click data via each platform's API, not through a manual export someone runs on Mondays. That's the difference between numbers that update daily and numbers that are already a week stale by the time anyone looks at them. If your dashboard updates less often than your ad spend does, you're making decisions on old information without realizing it.
Ad platforms will always tell you their own channel drove the sale. GA4 doesn't have that bias, which is exactly why it still matters even after you've got Meta and Google wired in.
GA4 is the neutral layer. It sees the full session path, organic, direct, email, paid, all of it, instead of one channel claiming credit in isolation. That's the specific gap ad platform data can't fill on its own: you need something that shows how a customer actually moved through the funnel, not just the last click before checkout.
Without GA4 tied into the same dashboard, you literally can't reconcile blended CAC (what you're actually paying to acquire a customer across the whole business) against the CAC each ad platform claims. And those two numbers are almost never the same. If your platform doesn't pull GA4 alongside ad and Shopify data, you're stuck trusting whichever channel shouts loudest.
Retention revenue shouldn't live behind a separate login. If your team has to check Klaviyo's dashboard for email numbers and your analytics tool for everything else, you're not going to reconcile them consistently, and decisions get made on whichever number is easier to pull up.
Check for flow-level and campaign-level revenue specifically, not just a lump "total email revenue" figure. A single number tells you email works. Flow and campaign breakdowns tell you which flow is actually carrying the weight, so you know what to protect if you're ever cutting anything.
Klaviyo integration is the one to confirm first since it's the default for most DTC brands at this point. Mailchimp is worth checking too if you're a smaller brand that hasn't migrated off it yet. Either way, retention data needs to sit next to paid and organic in the same view, not off in its own silo.
Revenue minus ad spend isn't profit. It just looks like profit if that's all your dashboard shows you.
Real margin numbers need payment processor data (processing fees, chargebacks, disputes, all pulled from Stripe) and fulfillment cost data (shipping cost per order, from ShipStation or similar). Skip either one and you're working off a number that's cosmetically healthy and actually wrong.
Here's the failure mode in practice: ad spend looks controlled, revenue's climbing, everything on the dashboard says green. Meanwhile shipping costs crept up 15% because of a carrier rate change nobody logged into ShipStation to notice, and margin's quietly bleeding out underneath a chart that looks fine. A dashboard that only shows revenue and ad spend will never catch that. This is the actual line between a marketing dashboard and something that functions like a real P&L.
No platform covers everything natively. Custom loyalty programs, regional marketplaces, an in-house ERP nobody outside your ops team has heard of, something's always going to fall outside the standard integration list. That's where API and developer access becomes the actual answer, not a nice-to-have.
What to check for: a documented REST API, webhook support so data pushes in near real time instead of on a batch schedule, and a real track record on custom integration requests. Some vendors treat those requests as a roadmap item that gets shipped. Others treat them as a place where feature requests go to die.
The practical test is simple: ask the vendor directly how long a custom integration typically takes to ship, start to finish. A specific timeframe means they've done it before. A vague answer means you'd be the first. For the tools that don't fit anywhere else, it's worth understanding what broader data integration options look like before you sign anything, or submitting a request directly through /integration-request to see how they respond before you're a paying customer.
Run any platform against this list before you sign an annual contract:
If a vendor can't check off most of these, or gets vague when you ask about any single one, that's worth noting before you're locked into a contract, not after.
The best way to actually verify this is a trial, not a sales deck. Connect your real stack, your actual ad accounts, your actual Klaviyo account, and see what breaks or what's missing. Sales decks don't have refund edge cases or legacy fulfillment tools. Your Shopify store does.
If you're still early in narrowing down options, it's worth subscribing to keep tabs on how the integration landscape shifts. Ad platforms change their APIs more often than you'd expect, and what's a checklist item today can become a dealbreaker in six months if a vendor doesn't keep up.
explore more insights
3 min read
3 min read
3 min read
.d53b12e5.png&w=3840&q=75 "Trivas.ai")