troubleshooting-data-issues

Diagnose data discrepancies and configuration errors in Whatagraph reporting environments.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/whatagraph/whatagraph-skills --skill troubleshooting-data-issues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: troubleshooting-data-issues
Source: https://github.com/whatagraph/whatagraph-skills/tree/main/skills/troubleshooting-data-issues
Command: npx skills add https://github.com/whatagraph/whatagraph-skills --skill troubleshooting-data-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves data discrepancies, missing metrics, and connection errors within Whatagraph by systematically auditing sources, blends, and widget configurations.

Core Features & Use Cases

  • Root Cause Analysis: Identifies whether issues stem from source connection errors, timezone mismatches, or incorrect report types.
  • Data Validation: Compares raw data fetches against native platform metrics to pinpoint discrepancies.
  • Use Case: When a user reports that their Facebook Ads spend in Whatagraph does not match the native platform, this skill guides the user through checking report types, currency settings, and attribution windows to find the source of the mismatch.

Quick Start

Use the troubleshooting-data-issues skill to diagnose why the data for source ID 12345 is showing as missing in my report.

Frequently Asked Questions about troubleshooting-data-issues

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why does my marketing data in Whatagraph not match the native platform metrics?

Data discrepancies often stem from source connection errors, timezone mismatches, or incorrect report types. Systematic troubleshooting audits sources, blends, and widget configurations to pinpoint whether the mismatch is caused by currency settings or attribution window differences.

How do I troubleshoot missing metrics in my Whatagraph reporting environment?

To troubleshoot missing metrics, you need to perform root cause analysis on your data sources. This involves checking source connection failures, auditing blend logic, and verifying widget-level filtering to identify where the data integration is breaking down.

What is the best way to diagnose a source connection failure in marketing analytics?

The best way to diagnose a source connection failure is to systematically audit the source configuration and fetch raw data. Comparing raw data fetches against native platform metrics helps validate data integrity and isolate the connection error.

Can I validate data integrity by comparing raw data fetches against native platforms?

Yes, data validation involves fetching raw data and comparing it against native platform metrics. This process isolates configuration errors and identifies whether issues originate from blend logic, widget-level filtering, or the source connection itself.

Do I need specific tools to perform root cause analysis on data discrepancies?

Yes, systematic root cause analysis requires access to list-sources, fetch-data, and list-widgets tools. These tools allow you to audit marketing data integration, inspect blend logic, and verify configurations to resolve errors.