Shopify connector

Without Shopify, Atria sees your advertising: spend, impressions, clicks, and whatever Meta or TikTok reports back as a conversion. That's a lot — but it's one side of the story, and it's the side the ad platforms mark their own homework on.

Connect Shopify and Raya gets the other side: what actually happened in your store. She reads it, and she can draw on it when you ask her something.

That's the bit worth being precise about, so let us be blunt: this is a Raya connector. Your store data goes to Raya so she can answer questions with it. It does not flow into your Analytics dashboards, into Radar, or into custom reports — those stay Meta and TikTok. If you've been told somewhere that connecting Shopify gives you blended MER or "true ROAS" inside a dashboard, that isn't what this does, and we'd rather you heard that from us now than found it out on a Friday afternoon.

What it does do is make Raya genuinely useful on the questions media buyers actually care about. Once she can see the store, you can ask her things like:

How far she can go depends entirely on which permissions you grant her when you set the connection up — more on that below. Our rule of thumb is: grant the minimum you need for the analysis you actually want.

It's read-only, by the way. Every permission we ask for is a read_ one. Atria doesn't touch your products, orders, customers or settings — it reads, it never writes.

This is the bit our customers ask about constantly, so here's the shape of it.

A workspace can hold several brands. Each brand connects to its own Shopify store. So if you look after six clients, you set up six brands, and each one gets its own store connection — that's how you keep the data from bleeding between clients, and it's how Raya knows which store you mean when you ask her a question.

So: "can I connect more than one store?" Yes — one per brand. It isn't one store per workspace, and it isn't a free-for-all where six stores sit in a pile and you have to name the right one in every prompt. Connectors, tasks, skills and automations all sit under a brand now.

If you're setting up your first one and you're not sure which brand you're in, sort the brand out first and connect second. It's much less annoying than moving it afterwards.

You'll need admin access to the Shopify store you're connecting — enough to create an app in Shopify and generate an Admin API access token. If someone else looks after the store, this is a short job to hand them, and worth doing in one sitting because the token is only shown once.

Worth reading the In Shopify note below before you start — it'll save you a detour if your store hasn't got a custom app set up already.

In Atria:

You can also just ask her: @ Raya, I would like to connect to a new Shopify account — she'll walk you to the same place.

In Shopify. You need an Admin API access token. Here's how to get one — it's a few steps, but you only do it once:

One heads-up worth 30 seconds: do this under Develop apps inside your own store admin — not Shopify's separate Dev Dashboard.

The Dev Dashboard builds a different kind of app that never hands you a shpat_ token, and that's the single most common way people get stuck here. If you can't see a Develop apps option at all, or the token step won't play, message us and we'll get you connected another way rather than have you lose an afternoon to it.

The permissions to grant.

When you do get to the scope picker, these are the read-only scopes we recommend for analytics and reporting — this is Derek's list, and Shopify's own advice is to grant only the minimum you need:

read_orders · read_all_orders · read_products · read_inventory · read_locations · read_discounts · read_returns · read_customers · read_markets · read_draft_orders · read_marketing_events · read_shopify_payments_payouts · read_shopify_payments_disputes · read_reports

Pick based on the insights you actually want. Two worth calling out: read_all_orders is what lets Raya see orders older than 60 days — without it she's blind past two months, which catches people out on year-on-year questions. And the customer, payments and reporting scopes are only worth granting if you want those specific analyses.

A quick note on why it's a token and not a one-click sign-in: we tried standard Shopify sign-in previously and it didn't hold up for enough people. Longer to set up, steadier once it's up — that's the trade.

Reconnecting from the Connectors page clears most wobbles. Beyond that, here are the three things customers actually hit:

"Shopify won't give me a token" / the token isn't accepted. Two quick checks. First, make sure you built the app under Develop apps in your store admin, not the Dev Dashboard — only the former gives you a shpat_ token. Second, make sure you've pasted the Store Subdomain, not your custom domain. If you've done both and it still won't play, flag it to us.

The install button is greyed out, or you see "This app is under review". Send us the store URL and we'll get it escalated.

In all these cases: send us the store URL and what you're seeing on screen — a screenshot of the error is worth ten messages — and we'll get it in front of the team.