How we test and verify every claim

Last updated: 15 July 2026 · Maintained by Luke Sandelands

Stack Architect exists because most Shopify automation advice is either vendor marketing or untested rehash. So every factual claim on this site follows one rule: if we can't source it or reproduce it, we don't publish it. This page documents exactly what that means.

Where our numbers come from

In order of preference:

1. Vendor pricing pages and official documentation. Make.com's plan limits come from make.com/en/pricing. Meta CAPI behaviour comes from Meta's developer documentation and Events Manager. Competitor prices (Elevar, Triple Whale, Klaviyo, Stape, Littledata) come from their own pricing pages, checked on the date shown beside each figure.
2. Working configurations, built as published. Every guide is written by building the setup it documents, step by step, and publishing the steps that worked — not by summarising vendor docs. Where a page shows a specific measured outcome (an Event Match Quality score, a deduplication result, an execution log), that figure is tied to a dated configuration; where a figure is an industry estimate rather than our measurement, the page says so and gives a range.
3. Platform announcements with dates. Deadline claims (Stocky's 31 August 2026 shutdown, Meta's 15 April 2026 one-click CAPI release, Klaviyo's February 2025 billing change) cite the announcement, not commentary about it.

We do not use: other blogs' figures, AI-generated statistics, or vendor claims we can't check against a pricing page or changelog.

How often figures are re-verified

Every pricing and plan-limit figure is re-checked quarterly, and immediately whenever a vendor announces a pricing change. When Make.com switched its billing unit from operations to credits in August 2025, and when its Core pricing changed, we updated every affected page from a single canonical facts file — so the same figure appears identically everywhere on the site. Comparison tables carry a "verified" date; if that date is more than a quarter old, tell us.

What our "tested" badges mean

A badge like "iOS 26 tested" means the documented setup was confirmed working under that environment on the date shown — not tested once and assumed fine since. This is the standard every badge on this site is held to: at each quarterly review, any badge that can no longer be re-confirmed is updated or removed. Where a claim is an estimate rather than a measurement (for example, typical recovery ranges like "20–40% of lost conversions"), we say so and give the range, not a single flattering number.

How this site makes money — and what that buys

Stack Architect is funded two ways, both disclosed:

• Affiliate links. Some links to tools we recommend (marked rel="sponsored" in the page code) pay us a commission at no cost to you. This never changes a recommendation: our core recommendation on most pages is the free tier of a tool, which typically pays little or nothing. Where a paid tool is genuinely better for a use case, we say so even when we have no affiliate relationship with it.
• The Complete Kit ($29 one-time). Pre-built versions of the same automations the free guides teach. The free guides are complete on their own — the kit buys time, not access.

We do not accept payment for placement, reviews, or rankings, and no vendor sees our content before publication.

Corrections

When we get something wrong, we fix the page, update its "last updated" date, and note material corrections in the text. If you spot an error — a stale price, a changed limit, a claim that didn't hold up in your setup — email support@stackarchitect.xyz and we'll verify and correct it, usually within a week.

Why this page exists

Search engines and AI answer engines increasingly reward sources that show their work; readers always have. Everything above is checkable: click any vendor price we cite and compare it to their pricing page today. If it doesn't match, that's a correction we owe you.