Google Ads/Meta Ads LoomaScale

View saved version →

---
name: cross-source-insights
description: Explain marketing performance using relevant connected Google Ads, Meta Ads (Facebook Ads and Instagram Ads), LinkedIn Ads, Google Analytics 4 (GA4), Google Tag Manager (GTM), Google Search Console (GSC) and Google Merchant Center (GMC) evidence. Use for changing results, wasted spend, budget priorities, organic traffic, shopping eligibility, tracking, landing pages and funnels, including single-source questions. Grounds custom Google Ads queries in live metadata. Use the loomascale skill for account setup and campaign changes. Also use Meta Pixel (Facebook Pixel) events, Event Match Quality and Conversions API diagnostics to investigate tracking gaps.
---

# LoomaScale cross-source insights

Use LoomaScale to connect advertising delivery and cost to on-site behavior and
business outcomes, organic visibility, product eligibility and tracking configuration.
Answer the user's question with evidence, likely drivers and practical next steps.
The user's instructions take precedence
over this skill's workflow defaults; live tool schemas and server permissions
determine supported operations.

## Scope the question and choose sources

Identify the decision, business outcome, period and relevant accounts. Reuse the
conversation's context. If the period is unspecified, use the last 30 complete
days and the preceding equal-length period, stating the dates. When Search Console
is needed, use its finalized end date (normally three Pacific days ago) for a
direct cross-source comparison, or label differing windows explicitly. Ask only
when an unresolved business/account/property choice would materially change the answer;
continue independent reads while that choice is pending.

Choose sources by what they can explain, not simply because they are connected:

| Question | Evidence to combine when available |
|---|---|
| Why did leads, sales or ROAS change? | Relevant ad platforms' spend, delivery and reported outcomes; GA4 traffic, business events and revenue; then the largest changing campaign, device, geography or landing-page segments. |
| Where is spend being wasted? | Ad costs, search terms or creative performance; GA4 engagement and matching business outcomes. Distinguish poor traffic from on-site drop-off and missing measurement. |
| Which channel or campaign deserves budget? | Comparable ad costs and GA4 outcomes, current delivery/pacing and data volume. Treat platform-attributed results as a separate view. |
| Why do reports disagree? | Platform conversion definitions and attribution settings where exposed; GA4 event definitions, attribution, property settings and Google Ads links. |
| Where does the funnel break? | GA4 landing-page, device and ordered funnel reports; relevant ad campaign/source context. |
| Why did organic traffic fall, or which pages deserve work? | Search Console query/page changes and indexing evidence; GA4 organic landing-page behavior and business outcomes. Keep paid results separate. |
| Why did Shopping or Performance Max results decline? | Google Ads delivery and product performance where supported; Merchant Center account health, product issues and paid/free-listing performance. Verify the merchant relationship before attributing a campaign change to feed issues. |
| Is tracking configuration causing the discrepancy? | Relevant Google Ads conversion actions, Meta Pixel (Facebook Pixel) datasets/events, Event Match Quality and Conversions API diagnostics, GA4 events/property context and GTM's published tags, triggers, variables and pending workspace changes. Configuration alone does not prove runtime behavior. |

For concrete diagnostic patterns and join rules, read
[the analysis guide](references/analysis-guide.md) when combining sources.
For standalone GA4, Search Console, Merchant Center or Tag Manager procedures,
read the [measurement and commerce guide](../loomascale/references/measurement-and-commerce.md)
only for the relevant integration.

## Discover accoun

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 2 — file references are metadata, not package contents.

View saved version →

---
name: loomascale
description: Work with connected LoomaScale integrations for Google Ads, Meta Ads (Facebook Ads and Instagram Ads), LinkedIn Ads, Google Analytics 4 (GA4), Google Tag Manager (GTM), Google Search Console (GSC) and Google Merchant Center (GMC). Use to discover accounts, audit performance or tracking, research keywords, diagnose organic search or shopping issues, and carry out requested Google Ads or Meta Ads campaign changes. Use cross-source-insights for detailed performance and attribution analysis. Also use for Meta Pixel (Facebook Pixel) event activity, Event Match Quality and Conversions API diagnostics.
---

# LoomaScale integration workflows

LoomaScale connects advertising, analytics, organic search, shopping and tracking
data through its MCP tools. Use the smallest relevant set of integrations to
answer the question or complete the requested action. Google Ads and Meta Ads
support campaign changes; LinkedIn Ads, GA4, Search Console and Merchant Center
provide read-only reporting and diagnosis. Tag Manager reads by default and, once
the user has enabled editing on its connection, accepts draft changes to tags,
triggers and variables in an unpublished workspace; it never publishes.

## Start with the user's task

Identify the intended result: a report, diagnosis, recommendation, campaign draft
or authorized change. Reuse the conversation's accounts, dates and business goal.
Discover only the resources needed; do not run an account-wide audit for a narrow
question. Ask only for a missing choice that materially affects the result, such
as which of several client accounts to change.

Inspect the available tool descriptions and input schemas before calling them.
Names below are the server's tool names; a client may add a namespace prefix.
Live schemas and permissions take precedence over examples in this skill. Do not
invent tools, arguments or access to an integration that the client does not expose.

## Which integration answers the question?

| Integration and purpose | Discover the target | Begin with |
|---|---|---|
| Google Ads: paid search, Shopping, Performance Max, keywords, budgets and delivery | `gads_list_ad_accounts` | `gads_get_insights`, `gads_list_campaigns`, `gads_list_search_terms`; `gads_check_pacing` for today's delivery |
| Meta Ads: Facebook/Instagram campaigns, creatives, audiences and delivery | `meta_list_ad_accounts` | `meta_get_insights`, `meta_list_campaigns`, `meta_list_ads`, `meta_get_delivery_issues` |
| Meta Pixel (Facebook Pixel): received events, Event Match Quality and Conversions API health (read-only) | `meta_list_ad_accounts`, then `meta_list_datasets` | `meta_list_datasets` for 1-7 days of event counts; `meta_get_dataset_quality` for match quality and diagnostics |
| LinkedIn Ads: B2B campaign results, leads and professional demographics | `linkedin_list_ad_accounts` | `linkedin_get_insights`, `linkedin_list_campaigns`, `linkedin_analyze_demographics` |
| Google Analytics 4 (GA4): website traffic, business events, revenue and funnels | `ga4_get_account_summaries` | `ga4_get_property_details`, then the appropriate report |
| Google Search Console (GSC): organic queries, pages, search visibility and indexing | `gsc_list_sites` | `gsc_compare_periods`, `gsc_query_search_analytics`, opportunity tools or `gsc_inspect_url` |
| Google Merchant Center (GMC): product eligibility, account issues and shopping performance | `gmc_list_accounts` | `gmc_get_account_health`, then `gmc_query` |
| Google Tag Manager (GTM): published tracking configuration, pending changes and draft fixes | `gtm_list_containers` | `gtm_get_container`, `gtm_audit_tracking`, `gtm_get_workspace_status`; draft fixes with `gtm_create_tag`, `gtm_update_tag`, `gtm_create_trigger`, `gtm_update_trigger`, `gtm_create_variable`, `gtm_update_variable` |

Read only the guide needed for the task:

- [Advertising workflows](references/advertising.md): paid performance, keyword
  research, creative review, Meta Pixel

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 3 — file references are metadata, not package contents.