'ga4' 검색 결과

Plan, set up, audit, and debug analytics tracking with GA4 and Google Tag Manager. Define events and their parameters, configure conversion tracking, and investigate missing or duplicate data using structured checks and prioritized fixes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Building an event tracking plan from scratch
• Auditing existing tracking for gaps and duplicate events
• Debugging events missing from GA4

Plan, implement, and audit website or app analytics with GA4 and Google Tag Manager. Define meaningful events, standardize campaign tags, and validate data collection so marketing and product decisions use consistent measurements.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Plan tracking for signups and purchases
• Review existing GA4 and GTM tracking
• Standardize UTM campaign naming

Audit how advertising platforms, GA4, and app measurement tools assign credit for conversions. Compare event definitions, reporting windows, and duplicate handling to explain discrepancies and produce an evidence-based measurement improvement plan.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating discrepancies between Meta and Google conversions
• Checking GA4 against advertising platform reports
• Reviewing app conversion measurement

Use gog to list Google Analytics 4 account summaries and run reports through the Analytics Data API. Explicit account selection and read-only options help agents retrieve information from the intended account.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Check available GA4 accounts
• Retrieve a GA4 report
• Read Analytics data without making changes

Turn Matomo analytics into reports on organic traffic, landing pages, devices, countries, referrers, and search keywords. Use data from a self-hosted instance or Matomo Cloud to support reporting alongside GA4 or as an alternative.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review organic traffic trends in Matomo
• Identify popular landing pages
• Compare visits by device, country, and referrer

Plan, implement, and audit website or app tracking for marketing and product decisions. Covers GA4, Google Tag Manager, event naming, campaign tracking parameters, and validation to check that important user actions are recorded correctly.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Plan tracking for signups and purchases
• Review GA4 and Google Tag Manager settings
• Standardize campaign tracking parameters

Plan and validate tracking for marketing and product decisions. Define events, configure GA4 and Google Tag Manager, standardize campaign link labels, and calculate metrics using matching time periods to produce dependable measurement plans and findings.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Design a tracking plan for signups and purchases
• Investigate missing or duplicate events
• Standardize UTM labels across campaign links

Use Google's APIs to review search performance, page speed, indexing status, and organic traffic. Combine real visitor measurements with search and analytics data to identify SEO issues and create reports.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing search clicks, impressions, and rankings
• Tracking page experience metrics over 25 weeks
• Checking whether Google has indexed specific URLs

Helps developers send conversion and event data to Google Ads, Google Analytics, and Floodlight through the Data Manager API. It covers destination setup, data formatting, validation, migration from other APIs, and checking processing results.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Implement offline conversion uploads to Google Ads
• Send recommended or custom GA4 events
• Migrate event ingestion from another Google API

Google API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

When the user wants to set up, audit, or optimize analytics tracking (GA4, events, conversions). Also use when the user mentions "Google Analytics," "GA4," "event tracking," "conversions," "attribution model," "gtag," "data layer," "GA4 setup," "conversion tracking," "event setup," "User ID tracking," or "CTA attribution." For traffic insights, use traffic-analysis.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Designs and implements website analytics tracking with Google Analytics 4 and Google Tag Manager: a written tracking plan, event and parameter names that pass GA4's rules, gtag.js or data-layer code, key events, consent mode, UTM conventions, and a verification pass. Use when someone says "set up GA4", "add conversion tracking", "track this form or button", "write a tracking plan", "GTM data layer", "UTM parameters", "why are my events missing or counted twice", or "audit our analytics setup".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Google API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Query Google Analytics 4 (GA4) data via the Analytics Data API. Use when you need to pull website analytics like top pages, traffic sources, user counts, sessions, conversions, or any GA4 metrics/dimensions. Supports custom date ranges and filtering.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Assess how marketing channels contribute to conversions and revenue. Compare attribution models, which assign credit to customer interactions, reconcile conflicting reports, and design first-party tracking that connects browsing history to bookings or purchases.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reconciling conversion counts across advertising tools, analytics, and CRM
• Comparing first-touch and last-touch credit
• Designing surveys to capture word-of-mouth discovery

Design and audit analytics tracking so recorded actions support business decisions. Define events and conversions, investigate duplicate or missing records, and document tracking rules, traffic sources, consent checks, and validation steps.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Designing events around business decisions
• Investigating mismatched purchase counts
• Reviewing traffic source tracking

Analyze Google Analytics traffic, visitor engagement, and conversions, such as purchases or goal completions. Compare periods, identify strong and weak pages or traffic sources, and receive prioritized recommendations with implementation guidance.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing website performance over the last 30 days
• Identifying the main traffic sources
• Finding pages with high bounce rates

Generate consistent UTM parameters, GA4 event naming, and conversion tracking specs following taxonomy best practices. Use when describing campaign structure, requesting UTM links, needing GA4 event names, or wanting to standardize tracking nomenclature across marketing channels. Platform: Google and Meta.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Analyze connected Google Analytics 4 traffic, acquisition, engagement, landing pages, ecommerce, events, and conversions, and safely manage supported GA4 key events or custom dimensions through NotFair MCP. Use for GA4, Google Analytics, traffic or conversion drops, channel attribution, realtime activity, report requests, measurement configuration, or Analytics MCP setup.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when platform-reported conversions disagree with GA4/ecommerce, when you suspect Meta and Google are double-counting the same sales, or for a standing (monthly) reconciliation workbook that de-dups stacked credit against an order-ID truth set, normalizes attribution windows and currency, compares attribution models, and reads incrementality from a geo/holdout test. Not for the point-in-time R2 veto or RQS gate — use ad-account-auditor; not for the ROI/ROAS ratio math itself — use roi-calculator; not for organic dark-social share attribution or GA4 direct-traffic decomposition — use dark-social-attributor. 付费广告归因对账/去重/增量

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Google SEO APIs: Search Console (Search Analytics, URL Inspection, Sitemaps), PageSpeed Insights v5, CrUX field data with 25-week history, Indexing API v3, and GA4 organic traffic. Provides real Google field data for Core Web Vitals, indexation status, search performance, and organic traffic trends. Use when user says "search console", "GSC", "PageSpeed", "CrUX", "field data", "indexing API", "GA4 organic", "URL inspection", "google api setup", "real CWV data", "impressions", "clicks", "CTR", "position data", "LCP", "INP", "CLS", "FCP", "TTFB", or "Lighthouse scores".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Google SEO APIs: Search Console (Search Analytics, URL Inspection, Sitemaps), PageSpeed Insights v5, CrUX field data with 25-week history, Indexing API v3, and GA4 organic traffic. Provides real Google field data for Core Web Vitals, indexation status, search performance, and organic traffic trends. Use when user says "search console", "GSC", "PageSpeed", "CrUX", "field data", "indexing API", "GA4 organic", "URL inspection", or "real CWV data".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to track AI traffic." For AI SEO strategy, use generative-engine-optimization.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Google SEO APIs: Search Console (Search Analytics, URL Inspection, Sitemaps), PageSpeed Insights v5, CrUX field data with 25-week history, Indexing API v3, and GA4 organic traffic. Provides real Google field data for Core Web Vitals, indexation status, search performance, and organic traffic trends. Use when user says "search console", "GSC", "PageSpeed", "CrUX", "field data", "indexing API", "GA4 organic", "URL inspection", "google api setup", "real CWV data", "impressions", "clicks", "CTR", "position data", "LCP", "INP", "CLS", "FCP", "TTFB", or "Lighthouse scores".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.