Docs
Integrations
The tools Signal over Noise reads for a D2C subscription brand, what it reads from each, and what it leaves out.Read this page as MarkdownOnce a workspace’s nightly build is on, Signal over Noise reads its connected tools every night, rebuilds the figures from them, and checks those figures against each platform’s own reports. Each tool below feeds the named metrics on Metrics and definitions. An admin connects them from Settings → Integrations.
What each tool is read for
Connections only read. Each reads what the figures and their recommendations need. Personal fields are removed before anything is stored, or replaced with a one-way key where a customer has to be matched across tools; the exceptions are named in the table.
| Tool | Category | What we read | What we leave out |
|---|---|---|---|
| Google Ads | Advertising | Daily spend and delivery by account, campaign and ad, spend by search term and by Shopping product, campaign settings such as budget and bid strategy, and the account’s change history. | Account names, audiences, keywords and creative. A search term that could name a person or an order is withheld before it is stored. In the change history, who made a change is kept only as a pseudonym and, for a company email, its domain. |
| Google Analytics 4 | Web analytics | Sessions by channel and landing page, each purchase with the channel it arrived by, and the checkout steps shoppers took. | Anything at the level of a visitor: no user or client IDs, cities or device models. |
| Gorgias | Customer support | Ticket states, channels, response and resolution times, and satisfaction scores. | Message text, subjects, tags, survey comments, and agents' and customers' names and email addresses. A customer's email is kept only as a one-way key, to match them across tools. |
| Klaviyo | Email and SMS | Campaign and flow performance reports, and how each flow is set up: its steps, trigger and status. | Profiles, lists, events and message content. No recipient is read. |
| Meta Ads | Advertising | Daily spend and delivery by account, campaign, ad set and ad, each ad's status, campaign and ad set budgets, bids and optimisation events, and the account's change history. | Account names, audiences, targeting, lead forms and creative content. In the change history, who made a change is kept only as a pseudonym. |
| Microsoft Clarity | Site behaviour | Daily page friction: dead clicks, rage clicks, error clicks and script errors, by page. | Recordings and anything that identifies a visitor. |
| Omnisend | Email and SMS | Campaign and automation performance. | Contacts and message content. |
| Shopify | Store | Orders, refunds, products and collections, customers, open fulfilment orders and stock levels. | Customers' names, email addresses, phone numbers and notes. Addresses keep only country and region. An email is kept only as a one-way key, to match a customer across tools. |
| Skio | Subscriptions | Subscriptions and their lines, subscription events such as pauses, cancellations and failed payments, cancel-flow sessions with the reason a subscriber typed, and pricing. | Subscribers' names, phone numbers, addresses, payment details and notes. An email is kept only as a one-way key, and any email address in a typed cancel reason is removed. |
| Triple Whale | Attribution | Orders, revenue and new-customer orders credited to each channel under each attribution model, and ad spend. | Individual orders, customers and visitors: every figure is a total by day, channel and attribution model. |
| WooCommerce | Store | Orders, refunds, products and categories, customers, and the revenue report. | Customers' names, email addresses and phone numbers. Addresses keep only country and state. An email is kept only as a one-way key. |
Measured without a connection
Each night your store’s home page and its busiest landing pages are measured for speed on a phone and a desktop. This reads your public pages only.
Other tools
More tools can be connected from the integrations catalogue. They do not feed the named metrics above.
How data is protected
Where your data is hosted, who processes it and how long it is kept are set out in our Privacy Notice and in your data processing agreement with us. Who can connect a tool, and what needs approval, is on Roles, approvals and access.