← PilotCONTENT HISTORY
WHAT CHANGED
Update to Pilot
Snapshot Nov 3, 2026 · 12:13 UTC · version 0.1.0
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Pilot and check future changes in Following.
Up to 10 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Compares two periods across ad platforms and analytics through the Pilot MCP server: spend, results and ratios for Google Ads and Meta Ads, sessions and key events in Google Analytics 4, clicks in Search Console, with the change for each and its main drivers. Use when the user asks to compare two weeks, months, quarters, or this year against last year. Triggers: compare periods, month over month, year over year. Déclencheurs : comparer deux périodes, ce mois contre le mois dernier, évolution sur un an, comparaison de périodes.",
"included_files": [],
"name": "period-comparison",
"skill_md_contents": "---\nname: period-comparison\ndescription: \"Compares two periods across ad platforms and analytics through the Pilot MCP server: spend, results and ratios for Google Ads and Meta Ads, sessions and key events in Google Analytics 4, clicks in Search Console, with the change for each and its main drivers. Use when the user asks to compare two weeks, months, quarters, or this year against last year. Triggers: compare periods, month over month, year over year. Déclencheurs : comparer deux périodes, ce mois contre le mois dernier, évolution sur un an, comparaison de périodes.\"\ncompatibility: \"Requires the Pilot MCP server (https://app.pilot.braike.com/mcp) connected in the client and authorized on a workspace with at least one platform attached.\"\nmetadata:\n pilot-mcp-server: \"https://app.pilot.braike.com/mcp\"\n pilot-mcp-tools: \"pilot_cross_platform_overview google_list_accounts google_get_campaign_performance meta_list_accounts meta_compare_periods_performance google_analytics_run_report google_search_console_get_search_analytics\"\n pilot-mcp-read-only: \"true\"\n---\n\n# Period comparison\n\nPut two periods side by side, platform by platform, and explain what drove the difference. Answer in the user's language.\n\n## Requirements\n\n- **Required MCP server:** Pilot MCP (`https://app.pilot.braike.com/mcp`), authorized on the workspace concerned.\n- **Optional MCP servers:** a file storage server or spreadsheet server to keep the table. None is needed.\n- **Read-only:** never call a tool that creates, updates, pauses or deletes anything.\n\n## Tools\n\n- `pilot_cross_platform_overview`: consolidated spend and results for a window of days.\n- `google_list_accounts`: the Google Ads accounts attached to the workspace.\n- `google_get_campaign_performance`: Google Ads campaigns for any start and end dates.\n- `meta_list_accounts`: the Meta ad accounts attached to the workspace.\n- `meta_compare_periods_performance`: Meta results for two preset periods.\n- `google_analytics_run_report`: GA4 figures for two date ranges in one call.\n- `google_search_console_get_search_analytics`: organic clicks and impressions for a date range.\n\n## Steps\n\n1. Fix the two periods with exact dates. They should have the same length; if not, say so and compare daily averages.\n2. Google Ads: `google_list_accounts`, then `google_get_campaign_performance` with `start_date` and `end_date` for each period.\n3. Meta Ads: `meta_list_accounts`, then `meta_compare_periods_performance` with the closest presets (for example `last_7d`, `last_30d`, `last_month`); say when a preset does not match the dates exactly.\n4. GA4: `google_analytics_run_report` with both periods in `dateRanges` and the metrics that matter (`sessions`, `keyEvents`, `totalRevenue`).\n5. Search Console: `google_search_console_get_search_analytics` for each period, ending two days ago at most.\n6. Use `pilot_cross_platform_overview` for a consolidated view when the periods end today.\n\n## Output\n\n1. **Table**: one row per platform and metric, with period A, period B, the change in value and in percent.\n2. **Drivers**: the campaigns, channels or queries behind the largest changes.\n3. **Caveats**: unequal lengths, presets that differ from the dates, data delays.\n\n## Rules\n\n- Never add amounts in different currencies.\n- A change on an empty base is not a percentage: write the values instead.\n- Name the exact dates of both periods.\n\n## Examples\n\n- \"Compare September with August across Google Ads and Meta.\"\n- \"Compare ce trimestre au même trimestre l'an dernier.\"\n- \"Qu'est-ce qui explique l'écart entre les deux dernières semaines ?\"\n"
}SHA-256 of public snapshot: 0359eeb83c3c8a6f56148a676817388d11200d3537c161c97a9778e837ee22ea