wesaw
FRGet started

From your Shopify order to a readable receipt.

Connect your source, verify the collection setup and follow a real conversion. Each step tells you what has been observed and what still needs attention.

wesaw receives Shopify order webhooks and browser observations, prepares eligible conversion events, and records Meta delivery responses. A conversion receipt brings those observations together. Diagnostics direct you to missing ingestion, rejected deliveries or a connection that needs attention.

What you need before connecting a store

You can create your workspace before connecting a shop. To activate tracking, have the following access ready:

  • A Shopify store you are authorised to connect, with access to its published theme's app embeds.
  • The appropriate access to a Meta dataset. Available connection options depend on your permissions and the Meta app's configuration.

1Connect Shopify and Meta

Authorise your commerce source and connect the Meta destination you want to observe.

Authorise wesaw to read orders, install its Web Pixel and read customer events. The app registers the signed order webhook. Connect your Meta destination in the integrations area; permission to read advertising reports is separate from permission to send conversion events.

Scopes requested from Shopify: read_orders, write_pixels and read_customer_events.

2Verify your collection setup

Enable the wesaw app embed, check browser collection and review existing purchase senders.

Enable the wesaw app embed in the published Shopify theme and save. The setup checks whether collection is present. Review other purchase senders so they do not create unrelated duplicate events; the collection check does not automatically audit every third-party pixel.

The browser and server paths controlled by wesaw use the same purchase event identifier. Meta decides the final merge.

3Follow an observed conversion

Open its receipt to inspect consent, delivery attempts and the destination response.

Follow a store order in the conversion list and open its receipt. Inspect its timestamp, recorded consent, available matching fields and destination response. Rejected, pending and excluded events keep their own states and explanation.

Server-side Meta dispatch requires granted consent. A successful response proves acceptance, not purchase attribution.

Do I need to configure a custom domain?

No custom DNS change is required to continue the current setup. The application shows the collection address already in use.

A custom collection domain is an advanced option; automatic activation and DNS verification are not available in the current setup. A custom domain would not guarantee that a browser or blocker allows tracking.

What changes on the storefront?

The app installs its Web Pixel, and you enable the wesaw app embed for storefront collection. These are Shopify extension mechanisms rather than a manual theme-code edit. Review your existing purchase tracking configuration so independent senders do not create duplicates.

When does a receipt appear?

A receipt appears once an order has been observed. Delivery adds its own recorded status and timestamp. A missing response stays pending or unconfirmed, and a destination's later advertising reports follow its own reporting and attribution rules.

Questions about the setup

Can I explore wesaw before connecting a store?

Yes. Creating a workspace does not require connecting a shop or completing onboarding. You can add your first store later.

Will every observed order be sent to Meta?

No. Server-side dispatch requires recorded consent to be granted. Identity and event age can also exclude an event. The recorded outcome remains visible instead of being counted as a successful delivery.

Can I keep another purchase pixel running?

Review it during setup. Browser and server events need compatible identifiers to be deduplicated by Meta. wesaw does not automatically prove that an independent purchase sender uses the same identifier.

Does this work on WooCommerce too?

The WooCommerce connector is planned but not implemented. The current commerce source is Shopify and the implemented advertising destination is Meta.

The terms on this page

Last reviewed: