ga4-insights3.43 KB
View saved version →
---
name: ga4-insights
description: Explain changes in the user's Google Analytics 4 (GA4) traffic, engagement, key events, revenue and funnel performance using connected LoomaScale reports. Use for period comparisons, source/medium and landing page analysis, funnel drop-off investigations and GA4 attribution questions. Use loomascale-ga4 for property discovery and individual reports.
---
# Google Analytics 4 insights with LoomaScale
Turn the user's GA4 reporting question into evidence, likely explanations and
practical next steps. Use [GA4 reporting](../loomascale-ga4/SKILL.md) to resolve
the property, time zone, currency and compatible report inputs. Reports are
read-only. Eligible accounts may also have configuration-preview tools, governed
by that skill's explicit request, dry run and approval rules. This endpoint has
no advertising, Search Console or Tag Manager tools.
## Establish the comparison
Reuse the user's business goal, chosen property and date range. For an unspecified
historical comparison, use the last 30 complete property-local days against the
preceding 30 and state both windows. Honor a request for today or realtime instead
of forcing it into a historical comparison. Flag incomplete periods.
Read totals before selecting breakdowns. Choose the few metrics that answer the
question: sessions and engaged sessions for traffic quality, key events for
configured business outcomes, revenue for monetization, and ordered funnel users
for completion. Keep metric definitions and report filters consistent across
windows. Read `ga4_list_property_annotations` when investigating a dated change;
an annotation is context, not proof of the cause.
## Locate the drivers
For a traffic or revenue change, examine source/medium, channel, landing page and
device as relevant. Rank segments by their absolute contribution to the change,
then show percentage changes with their base counts. Use aggregate property
totals as the denominator; a row-limited report may not cover all segments.
For a conversion decline, distinguish fewer visits from a lower observed outcome
rate. For a checkout question, use ordered steps for events the property actually
collects, then compare completion and abandonment across devices. Realtime event
activity can support an investigation but cannot prove the whole tracking setup
works correctly.
Read [analysis patterns](references/analysis-guide.md) when calculating changes,
interpreting rates, diagnosing funnel losses or explaining attribution differences.
## Explain the result without overstating it
Separate observed changes from possible explanations and say what would test a
hypothesis. Do not claim causation, deduplicated sales, broken tag firing or a
specific campaign's spend from GA4 evidence alone. If the user supplies another
platform's figures, label their source and align dates, currency and attribution
before comparing them. Do not imply this plugin fetched that other source.
Lead with the answer, followed by the segments and numbers that support it. Give
specific next steps, their supporting evidence and any verification still needed.
State material sampling, thresholding, pagination, processing and alpha API limits.
Keep analysis read-only. For an explicitly requested settings change, follow the
configuration rules in [GA4 reporting](../loomascale-ga4/SKILL.md); if the needed
tool or permission is unavailable, explain where to apply it in Google Analytics.
Website tracking installation must be done elsewhere.
Referenced files: 2 — file references are metadata, not package contents.
loomascale-ga45.34 KB
View saved version →
---
name: loomascale-ga4
description: Analyze the user's connected Google Analytics 4 (GA4) properties with LoomaScale. Use for property discovery, website traffic, engagement, landing pages, events, key events, revenue, realtime activity, funnels and conversion attribution reports. Reports are read-only; eligible configuration-preview accounts can request supported settings changes. Do not invoke for general analytics definitions, installing tracking or changing ad campaigns.
---
# Google Analytics 4 reporting with LoomaScale
Use the user's connected Google Analytics 4 properties to answer a reporting
question with account evidence. This package connects to
`https://api.loomascale.com/mcp/ga4`. Reporting reads Analytics data and settings.
Eligible configuration-preview accounts may also have settings tools; follow
the configuration rules below. This package cannot install tracking or edit
campaigns, and it never deletes a property or stream.
## Resolve the property and reporting context
Reuse an already verified property from the conversation. Otherwise call
`ga4_get_account_summaries` to discover reachable accounts and properties. Use
`property_id` as the listed number or `properties/<number>`; never substitute a
Google Ads customer ID or a `G-...` measurement ID. Respect disabled properties.
If several properties fit and the task does not identify one, ask which to use.
Read `ga4_get_property_details` for the property's time zone and currency before
interpreting historical dates or money. Honor the user's period. If none is given,
use the last 30 complete days in that time zone; add a preceding equal-length
comparison when investigating a change. State the exact dates. Realtime questions
use their own last-30-minute window instead.
Inspect available tool descriptions and input schemas. Names here are the
server's tool names; a client may add a namespace. Live schemas and access
permissions determine supported inputs and reports.
## Choose the report that answers the question
| Question | Tool |
| --- | --- |
| Which GA4 accounts and properties can I access? | `ga4_get_account_summaries` |
| What time zone and currency does this property use? | `ga4_get_property_details` |
| Which sources, landing pages or devices bring traffic, key events or revenue? | `ga4_run_report` |
| What activity or events appeared in the last 30 minutes? | `ga4_run_realtime_report` |
| Where do users leave an ordered series of events? | `ga4_run_funnel_report` |
| What conversions, cost or ROAS does GA4 attribute? | `ga4_run_conversions_report` |
| What custom dimensions and metrics are registered? | `ga4_get_custom_dimensions_and_metrics` |
| What dated property annotations might explain a change? | `ga4_list_property_annotations` |
| Which Google Ads accounts are already linked? | `ga4_list_google_ads_links` |
Read [report inputs and limitations](references/reporting.md) for report shapes,
pagination, realtime compatibility, funnel steps and attribution. For a diagnosis
of changing results or a prioritized interpretation, use
[GA4 insights](../ga4-insights/SKILL.md).
## Handle an explicitly requested configuration change
Keep reporting read-only. Never change settings as a side effect of an analysis.
For eligible configuration-preview accounts, available tools may manage key
events, event create and edit rules, enhanced measurement, data redaction, and
create or update web streams. Event rules apply to future incoming events;
creating a rule does not emit an event immediately or rewrite historical data.
Creating a stream does not install a website tag.
Use only tools available to the connected account and their live schemas.
Before a write, show the exact property, stream or rule and proposed changes
using `dry_run=true`, then obtain the user's approval of those changes. Apply
only the approved change and report the verified result. If the preview tool or
required permission is unavailable, explain the limitation and direct the user
to
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 2 — file references are metadata, not package contents.
