How wesaw connects your store to your ad platforms

What you need before you start

Nothing to buy, nothing to uninstall. Two things have to be true, and if either is not, the setup will not finish and it is better to know now.

• Access to the DNS settings for your shop's domain, or someone who has it. This is usually wherever you bought the domain.
• An ad account you already run campaigns from. wesaw reports to it; it does not create it.

1Install the app

One click from the Shopify app store. It only reads your orders, it can't touch your store, your theme or your prices.

The app asks for permission to read your orders, and for nothing else. It cannot edit your products, your prices, your theme or your customers, because it never requests those permissions. Shopify shows you the list before you accept, and that list is the whole of what wesaw can do inside your shop.

What it reads: the order, its value, its currency, and the customer details already attached to it.

2Copy-paste one line

We give you one line to paste in your domain settings, with a guide that shows exactly where. That's the whole "technical" part. Five minutes, done once, and we're on call if you want us to do it with you.

You add one DNS record pointing a subdomain of your own shop, something like `t.yourstore.com`, at wesaw. That subdomain is where your visitors' events are collected, which is the whole reason this step exists: a request to your own domain is part of your site, and blockers work from lists of shared vendor domains rather than from yours.

This is the only step that touches anything outside your shop, and it changes nothing your visitors can see.

3That's it. Watch the sales come back.

Your current setup keeps running exactly as it is. wesaw works alongside it, catches the sales your platforms were missing, and you watch them land in your dashboard.

Your existing pixel keeps running exactly as it did. wesaw does not replace it and does not ask you to migrate anything. The two run alongside each other, and the ad platform matches the pair on a shared event identifier so that a sale seen by both is counted once rather than twice.

Switch wesaw off and your setup is exactly as it was before. Nothing is rewritten on the way in.

What that DNS record actually does

The DNS record points a subdomain you own at wesaw's collection endpoint. Visitors' browsers then send events to an address on your own domain instead of to a shared vendor domain, which is what keeps the request from matching a blocker's list.

It is a single record and it affects only the subdomain named in it. Your shop, your email and your existing subdomains are untouched: DNS routes each name independently, and nothing about the record changes where yourstore.com itself points. Removing the record undoes the whole thing.

What changes on your store

Nothing a shopper can see. No script slows the checkout, no banner appears, no theme file is edited. The visible change is on the reporting side: sales that were happening but never reaching your ad platforms start arriving there.

How long before you see something

The DNS record usually resolves within minutes, occasionally longer depending on the provider. After that, events arrive as sales happen. Ad platforms do not update their reporting instantly, so the numbers in your ad account move over hours rather than seconds.

Questions about the setup