MetricFabric.io · SEO and paid search reporting

Marketing performance intelligence, powered by your data.

MetricFabric.io is a reporting tool for website owners and marketing agencies. With your permission it reads your Google Search Console, Analytics 4 and Google Ads reporting data, keeps it in one place, and joins it so you can see organic and paid performance for the same page and the same query side by side. Access is read-only: the app cannot change anything in your Google accounts.

Connect Search Console — free How we use Google data

At a glance

Application nameMetricFabric.io

Operated byPlatform Foundry Ltd

Google APIs usedSearch Console, Analytics Data, Google Ads

Access levelRead-only, revocable at any time

Data locationGermany (EU)

Used for advertising or model trainingNo

What the application does

Three steps, all of them visible in your own account once you connect.

01 You choose what to connect You sign in with Google and grant read-only access to the Search Console properties, Analytics 4 properties and Google Ads accounts you select. Nothing is read until you complete that consent, and you can connect one source without the others.

02 We collect the reporting data daily Aggregated performance rows — queries, pages, sessions, search terms, clicks, impressions and cost — are copied into your workspace each day and kept so you still have last year's numbers when Google's own reporting window has moved on.

03 You get one dashboard and a list of actions Because all three sources sit in one place, the app can report things no single Google console shows — for example, paid search terms where the site already ranks first organically, queries a few positions away from page one, and pages whose impressions have been declining for months.

Example of a joined report

A paid-versus-organic overlap report lists each Google Ads search term next to the organic position for the same query from Search Console and the cost recorded against it. Where a site ranks in the top three organically and is still paying for the click, the report flags the term so the account owner can decide whether to keep bidding. This requires Google Ads and Search Console data in the same place, which is why the app asks for both.

Google user data

The scopes we request, and what each one is for

Each scope below is requested only to deliver a feature you can see in your own account. We request the narrowest read-only scope that makes the feature work, and we do not request any write scope.

ScopeData accessedWhy the app needs it

.../auth/webmasters.readonlySearch Console property list and aggregated search performance rows (query, page, country, device, clicks, impressions, CTR, position)To show organic search performance in the dashboard, retain it beyond Google's 16-month window, and join it to Ads and Analytics data. Read-only: we never submit sitemaps or change property settings.

.../auth/analytics.readonlyAnalytics 4 property list and aggregated report rows (landing page, channel, sessions, engaged sessions, key events / conversions)To attach outcomes to the same landing-page URLs that Search Console reports on, so the dashboard can show which organic pages actually convert. No user-level or event-level export is requested.

.../auth/adwordsGoogle Ads accounts the user can access, and aggregated search-term, campaign and cost reportsTo report paid spend next to organic ranking for the same query, find search terms with cost and no conversions, and flag campaigns losing impression share to budget. The app only runs reporting queries; it does not create, edit, pause or bid on anything.

openid · email · profileEmail address, name and profile pictureTo create and identify your MetricFabric.io account, send account and report emails, and show who is a member of a workspace.

Limited Use disclosure

MetricFabric.io's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We use Google user data only to provide and improve the features described on this page, we do not transfer it to others except as needed to provide those features or as required by law, we do not use it for advertising, we do not sell it, and we do not use it to develop, train or improve generalised artificial-intelligence or machine-learning models.

How we store, share and delete it

The full detail is in the Privacy Policy and the Data Processing Addendum. The summary:

Storage

Ingested Google reporting data is stored on servers in Germany operated by Hetzner Online GmbH. It is encrypted in transit with TLS 1.2 or later and at rest with AES-256, including backups. Every row carries a tenant identifier and isolation between customers is enforced in the database.

OAuth tokens

Refresh and access tokens are held in a dedicated secrets store with envelope encryption, are excluded from all logs, and are used only by the scheduled collection jobs for your workspace. They are never shared with any third party and never sent to an AI provider.

Who else sees it

Only the sub-processors needed to run the service: Hetzner for hosting, Cloudflare for DNS and TLS, Resend for transactional email and report delivery, and Stripe for billing — Stripe receives billing identity only, never Google data. We never sell data or use it for advertising.

Revoking and deleting

You can disconnect any source in the app, or revoke access at any time from your Google Account permissions page. Deleting a connection deletes its data. Deleting your account deletes everything and revokes our tokens; data is otherwise removed 90 days after cancellation and is exportable in full until then.

Where AI features are involved

Every finding the app reports is produced by a deterministic rule run over your own stored rows, not by a language model. Two optional features can send data onward, and both are off until you turn them on and are described in the Privacy Policy:

01Written summaries. If you enable them, the numbers for the finding being summarised are sent to our language-model provider under a zero-retention, no-training agreement. Credentials and tokens are never included.

02Your own MCP endpoint. If you create a workspace-scoped, read-only token and configure it in an AI client of your choosing, that client can query your stored reporting data. Data then reaches that provider at your instruction, under your agreement with them. No write operations are exposed, and the endpoint never exposes your Google credentials.

Plans

A free tier covering one Search Console property, and paid tiers billed in GBP. Every plan uses the same read-only access described above.

PlanPriceIncludes

Free£0One Search Console property, unified dashboard, SEO recommendations

Warehouse£29 / moThree properties, daily collection, CSV and Parquet export

Warehouse + MCP£79 / moTen properties, Google Ads and Analytics 4 joined to Search Console, hosted MCP endpoint

Agency£249 / moUnlimited properties, 25 client workspaces, per-client endpoint and white-labelled reports

Paid plans start with a 14-day free trial. Full terms in the Terms of Service.

Who operates this application

MetricFabric.io is built and operated by Platform Foundry Ltd, a company registered in England and Wales. The application, this website and the OAuth client all belong to that company.

MetricFabric.io is an independent product. It is not affiliated with, sponsored by or endorsed by Google LLC. Google, Google Ads, Google Analytics and Google Search Console are trademarks of Google LLC.

Legal entityPlatform Foundry Ltd

Registered office128 City Road, London EC1V 2NX, United Kingdom

JurisdictionEngland and Wales

Websitehttps://metricfabric.io

Privacy contact{{ privacyEmail }}

Support contact{{ supportEmail }}