Skip to main content
Store order and refund delivery is separate from browser tracking. Use Websites → [your site] → Destinations to inspect the commerce connections. A website owner or editor can manage them; viewers have read-only access.

​
Connect WooCommerce in Test

  1. Prepare the intended store’s webhook setup with its administrator. Use the webhook URL displayed by AutoAdy and a private signing secret for that store.
  2. In WooCommerce orders and refunds, enter the store identifier and WooCommerce webhook secret, then choose Connect in test mode.
  3. Configure the store’s paid-order and refund webhook deliveries to the displayed URL using the matching secret. Keep the secret private; it is not a browser analytics key.
  4. Send a controlled test order and refund from the store, then inspect the receipts and Confirmed revenue for the same site, environment, currency, and dates.
Check the order and refund identities and amounts against the source store. A saved connection alone does not prove webhook delivery or that a particular payment has been received. Do not use a checkout-button click as a substitute for an actual confirmed test outcome.

​
Existing Shopify sources

Settings → Shopify is marked Coming soon for new setup. The website Shopify card requires an already connected Shopify account ID; entering an unrelated store name cannot create that connection. If an existing source is available, inspect its account and store before connecting it in test mode. The checkout-event pixel and paid-order/refund webhooks are different data sources. Confirm the actual connection result and test each source you intend to use. If no connected account exists, contact support about availability rather than following an invented new-account setup.

​
Recover or stop a source

For a failed WooCommerce delivery, compare the endpoint, store identifier, secret, event type, order identity, environment, and receipt. Retry the same source delivery where appropriate rather than creating duplicate paid records. Keep errors and references, with credentials redacted. The connection list identifies each store and its mode. Disconnect removes that store connection; it does not prove that browser collection stopped. The current card connects in Test and does not provide a general Production-promotion button. Do not assume a test connection is live; resolve the required production setup with support before relying on live revenue. See confirmed revenue for reporting checks.