Quick start
Start in three steps: add a site, connect data sources, read the reports — plus when data arrives and what to do next.
Start in three steps#
metricsKit brings several sources into one place: Google Search, on-site behaviour, ad revenue, performance, a second search engine and edge network. Getting started takes three steps:
- Add a site (domain only)
- Connect data sources (Google authorization; GA4 + GSC recommended)
- Open the reports
Note: Connections are "account-level authorization + site-level binding": one Google authorization can serve multiple sites, and each site binds its own resources. See "Site connections & authorization".
Step 1: add a site#
- Console → Connect (or Sites → Add site)
- Enter the site name and domain (domain is required and globally unique)
- A site entry is created; every report and authorization hangs off it
Tip: Use the real primary domain (with or without www) — it is used to auto-match your data sources.
Step 2: connect data sources#
Tick the services you want in the connect wizard, then complete Google authorization:
| Service | Default | What you get |
|---|---|---|
| GA4 | Pre-checked | On-site behaviour: sessions, users, pageviews, channels, realtime |
| GSC | Pre-checked | Search performance: queries, pages, CTR, position, index checks |
| AdSense | Optional | Earnings, impressions, clicks, RPM |
| GTM | Optional (read-only) | Container checks and import-file generation |
| PageSpeed Insights | No authorization | Performance score, lab metrics, real-user data |
After authorization, a unique domain match binds automatically; with several candidates you pick one in Settings.
Note: Only need search data for now? GSC alone is fine — you can authorize more later without losing existing data.
Step 3: read the reports#
- Overview / Visitors: the traffic and audience basics
- mKit features: ecommerce attribution, conversion tracking, realtime, dimension reports, bot traffic and more
- Data sources page: what is connected, which resource is bound, last fetch time
Tip: Right after connecting, reports may show "waiting for data" — that is normal upstream latency (next section).
When data arrives#
| Source | Typical delay |
|---|---|
| GA4 | 24-48 hours (realtime is the exception: within ~30 minutes) |
| GSC | 1-2 days |
| AdSense | 24-48 hours |
| PageSpeed Insights | Refreshed roughly every 6 hours |
| Bing Webmaster | Daily |
Metric definitions, quotas and "why numbers disagree" are covered in "Data latency & metric definitions".
Next steps#
- To bring in ecommerce/form/outbound events: see the GTM console guide and your platform docs
- To configure the container item by item: /wordpress/gtm, /shopify/gtm
- Trouble connecting or no data: see the FAQ in "Site connections & authorization"