How StackXray works
From account creation to delivering a client report in under 10 minutes. Here is exactly what happens at each step.
Create an account
2 minutesSign up with your email or Google account. You'll be prompted to name your agency — this is used for white-label report headers on Agency and Pro plans.
- ›A subscription is required to run audits. Plans start at $149/month — see stackxray.io/pricing.
- ›Agency name appears in all client-facing PDF reports and delivery emails.
- ›Your account supports multiple clients — each client is a separate auditable entity.
Add a client
1 minuteClick "Add Client" and enter the client name and their primary domain. The domain is used by PageSpeed Insights for Core Web Vitals analysis — it's the URL StackXray tests for performance.
- ›Client name is internal — it labels the audit report and delivery emails.
- ›Domain should be the canonical homepage URL, e.g. example.com.
- ›You can create as many clients as needed. Audit limits apply per billing cycle, not per client.
Connect Google
3–5 minutesClick "Connect Google Account" on the client page. You'll be redirected to Google's OAuth consent screen, which shows exactly what StackXray is requesting access to. Click Allow.
- ›All permissions are read-only. StackXray cannot change anything in any Google property.
- ›The Google account used should have access to the client's GA4, GTM, GSC, and Google Ads properties.
- ›Tokens are encrypted with AES-256-GCM and stored securely. They are never logged or exposed.
- ›If the client's properties are spread across multiple Google accounts, use the account with access to the most platforms.
- ›You only authorize once per client. The token is stored and reused for future audits until revoked.
| Platform | Scope | What StackXray reads |
|---|---|---|
| GA4 | analytics.readonly | Properties, streams, events, conversions, traffic quality |
| GTM | tagmanager.readonly | Containers, tags, triggers, variables |
| GSC | webmasters.readonly | Performance, indexing coverage, Core Web Vitals |
| Ads | adwords.readonly | Campaigns, conversions, bidding, spend |
| GMC | content.readonly | Feed health, product quality, account status |
Select properties
2 minutesAfter OAuth, StackXray discovers all Google properties the connected account has access to. Select which specific GA4 property, GTM container, GSC site, and Ads account belong to this client.
- ›StackXray fetches the full list of accessible properties from each Google service.
- ›Select exactly one property per platform for this client.
- ›Platforms with no connected property are skipped during audits.
- ›You can change property selections later from the client page.
- ›PageSpeed Insights uses the client domain set in step 2 — no separate selection needed.
Run the audit
60–90 secondsClick "Run Audit." Optionally add notes for Claude — context about the client's business, recent changes, or specific concerns you want the AI to focus on. Then click Start.
- ›Data collection runs in parallel across all connected platforms simultaneously.
- ›Claude AI analyzes each platform independently first, then performs cross-platform synthesis.
- ›Cross-platform analysis finds discrepancies only visible when comparing data across platforms.
- ›You can navigate away — the audit runs in the background and you'll receive an email when done.
- ›If a delivery email is entered, the client receives an automatic notification with a link to the report.
Audit pipeline
Review the report
As long as neededThe completed audit opens automatically. Every finding is categorized as Critical, Warning, or Info, with a plain-English explanation of the issue, why it matters, and what to do about it.
- ›Overall health score (0–100) reflects the composite state of all connected platforms.
- ›Per-platform scores break down GA4, GTM, GSC, Ads, and PageSpeed independently.
- ›Critical findings represent active problems — misconfigured conversions, data loss, compliance risk.
- ›Warning findings are suboptimal configurations that create risk or reduce data quality.
- ›Info findings are best-practice observations and optimization opportunities.
- ›The executive summary is written by Claude in plain English, suitable for client presentation.
- ›The dollar impact statement estimates revenue exposure or cost waste from the highest-impact issues.
- ›Top 3 priorities give a clear starting point for remediation.
- ›Cross-platform findings appear in their own section — these are often the most actionable.
Health score scale
Deliver to your client
1 minuteDownload the PDF report or share the online report link. On Agency and Pro plans, the PDF is white-labeled with your agency name — no StackXray branding on client-facing deliverables.
- ›PDF is generated on demand — click "Download PDF" from any completed audit.
- ›PDF includes the full report: scores, all findings, executive summary, dollar impact, top priorities.
- ›Online report link is read-only and does not require the recipient to have a StackXray account.
- ›If a delivery email was provided at audit trigger time, the client already received a notification.
- ›Agency name on the PDF is set in Settings → Brand.
Track progress over time
OngoingEvery audit run is saved in the client's audit history. Run audits monthly to track score changes, confirm that fixes were applied, and demonstrate ongoing value to retained clients.
- ›All historical audits are accessible from the client page.
- ›Health score trend shows improvement (or regression) across audit runs.
- ›Compare findings between audits to see which issues were resolved and which are new.
- ›Monthly audits support retainer relationships — clients see measurable progress.
- ›Scheduled audits (auto-run monthly) are on the roadmap for Agency and Pro plans.
What gets checked
67+ checks across 5 platforms. Every check is run on every audit — nothing is sampled or skipped.
GA4
14 checks
- ›Conversion event configuration and deduplication
- ›Attribution model alignment with ad platform data
- ›Data retention risk (2-month vs 14-month setting)
- ›Referral spam and CRM traffic pollution detection
- ›Bounce rate by traffic source — paid vs organic quality
- ›BigQuery export status and raw data backup coverage
+ 8 more checks. See full check list →
Google Tag Manager
15 checks
- ›PII capture in variables — email, name, phone without hashing
- ›Consent Mode v2 implementation and blocking trigger coverage
- ›Google Ads conversion tag presence and configuration
- ›Duplicate tag detection across the container
- ›Dead triggers with no associated tags
- ›Tag proliferation — redundant tags for the same interaction
+ 9 more checks. See full check list →
Google Search Console
12 checks
- ›Indexing coverage — noindex, soft 404, crawl errors
- ›Core Web Vitals — LCP, INP, CLS by device
- ›Click-through rate by average position
- ›Top queries with impressions but zero clicks
- ›Mobile vs desktop performance gap
- ›Organic traffic trend — 90-day week-over-week
+ 6 more checks. See full check list →
Google Ads
18 checks
- ›Conversion action configuration and counting method risk
- ›Enhanced conversions implementation
- ›Campaign budget utilization and impression share
- ›Broad match keyword risk without smart bidding
- ›Search term irrelevancy and wasted spend signals
- ›Remarketing audience size and recency
+ 12 more checks. See full check list →
PageSpeed Insights
8 checks
- ›LCP (Largest Contentful Paint) — mobile and desktop
- ›INP (Interaction to Next Paint) — interactivity score
- ›CLS (Cumulative Layout Shift) — visual stability
- ›FCP (First Contentful Paint) — perceived load speed
- ›TTFB (Time to First Byte) — server response
- ›Performance score vs Google's scoring thresholds
+ 2 more checks. See full check list →
The cross-platform difference
Single-platform audit tools can tell you that your GA4 conversions look misconfigured. StackXray can tell you that your GA4 shows 200 organic sessions per day while Google Search Console shows only 20 clicks — a 10x discrepancy that suggests referral spam is inflating your GA4 numbers and making your organic channel look 10 times more valuable than it actually is.
Or that your Google Ads account reports 50 conversions last week, but GA4 key events show zero for the same period — meaning your Ads conversion tag is firing on every page load, not on actual conversions, and you've been optimizing campaigns against fabricated data.
These findings are invisible to tools that audit one platform at a time. They only become visible when the data from all platforms is compared together — which is exactly what StackXray does on every audit.
Still have questions?
The FAQ covers setup, billing, data privacy, and troubleshooting in detail.