data-extraction-patterns

This skill provides a comprehensive library of operational patterns for software agents tasked with analytics data engineering. It focuses on the standardized extraction of metrics and dimensions from Google Analytics 4 (GA4) and Google Search Console (GSC) via MCP server integration. Designed for data engineers and developers building automated reporting pipelines, this toolset ensures consistency in data retrieval, performance optimization, and API reliability. Users can leverage these patterns to build resilient data collection workflows that handle common challenges such as rate limiting, network volatility, and high-frequency data requests.

• Standardized operations for GA4 get_report and GSC search_analytics queries to simplify report generation.

• Built-in caching strategies for high-frequency metrics to minimize API costs and improve response times.

• Parallel execution patterns to optimize data fetching from multiple sources, reducing total execution time by up to 50%.

• Robust retry mechanisms with exponential backoff for handling 429 rate-limiting errors encountered during high-volume data extraction.

• Comprehensive reference for key SEO metrics like clicks, impressions, CTR, position, sessions, and bounce rate, facilitating quick data insight mapping.

• Modular session-based cache management to ensure data freshness while maintaining strict TTL (time-to-live) policies.

• Integrate these patterns when building automated SEO monitoring dashboards or consolidating marketing data into data warehouses.

• Utilize parallel fetching logic for multi-property audits where latency is a concern.

• Always define clear date ranges and dimension parameters to avoid sampling issues or excessive row counts in API calls.

• Use the provided bash-based utility patterns for local file system caching to reduce dependence on external API uptime.

• Note that while this skill is optimized for GA4 and GSC, the logic can be adapted to other REST-based reporting APIs by mirroring the suggested error handling and rate-limiting structures.