Flow Analytics for WooCommerce
Flow Analytics for WooCommerce connects your store to Flow, a marketing analytics and attribution service for online stores.
Instead of asking you to wire up a tag manager and a data layer, the plugin reads WooCommerce directly. Prices, product ids, order totals, taxes, shipping and coupons come from the same objects WooCommerce uses to bill your customer, so the numbers in your reports match the numbers in your store.
What it reports
page_view— every page, handled by the Flow trackerview_item— a product pageview_item_list— shop and category pages (optional)search— a product searchadd_to_cartandremove_from_cart— including AJAX add to cartview_cart— the cart pagebegin_checkout— the checkout page, classic or blockspurchase— a completed orderrefund— a refunded order$identify— links an order or a signed-in customer to the visitor
Orders are never quietly lost
When a shopper comes back to your thank-you page, the browser reports the order, which is the richest signal available. When the shopper never comes back — a payment redirect that drops off, a closed tab, a blocked script, a gateway that confirms by webhook minutes later — your server reports the order instead, a few minutes after the fact.
Both paths recognise each other, so an order is reported once and only once.
Attribution keeps working
The plugin keeps the Flow tracker’s visitor id with the order, so an order reported by your server is still attributed to the campaign, ad click or referrer that originally brought the shopper in. Nothing is credited to «Direct» just because the shopper closed the tab.
Setup
Paste your Flow site key into WooCommerce → Flow Analytics, press «Test connection», and you are done. There is nothing else to configure.
Compatibility
- High-Performance Order Storage (HPOS)
- Cart and Checkout blocks, as well as the classic shortcode checkout
- WP Consent API, when a consent plugin provides it
- Do Not Track and Global Privacy Control browser signals
External services
This plugin connects to Flow (Databrief), the analytics service the plugin was built for. An account is required. Without a site key, the plugin sends nothing at all.
1. Flow tracker script — https://flow.databrief.sa/sdk/attr.js
Loaded in your visitors’ browsers. It assigns an anonymous visitor id, keeps a session, and records the campaign, click id and referrer that brought the visitor to your store.
2. Flow collect endpoint — https://flow.databrief.sa/collect
Receives the events listed above. Two senders use it: your visitors’ browsers, and your own server for orders and refunds.
What is sent: the site key you configured; an anonymous visitor id and session id; the page URL, referrer and campaign parameters (UTM tags and ad click ids); for each product, its id, name, SKU, chosen variant, category, brand, price and quantity; for an order, its order number, internal id, status, total, tax, shipping, coupon, payment method title, the shopper’s billing country and whether it is the customer’s first order; for a refund, the refund id and amount; and — for orders and signed-in customers — the customer identifier, name, email address and phone number, together with the SHA-256 hashes of the email and phone. The name, email address and phone number can be excluded in the plugin settings, in which case only the hashes are sent.
What is not sent: passwords, payment card data, and the contents of any WordPress or WooCommerce table beyond the fields listed above.
Service terms: https://flow.databrief.sa/terms?lang=en Privacy policy: https://flow.databrief.sa/privacy?lang=en
Both documents are published in English and Arabic; drop the ?lang=en for the Arabic version.
Because the plugin transmits customer data to a third-party service, tell your visitors about it in your own privacy policy, and gate it behind your consent banner if the law that applies to you requires consent for analytics.
