← Webeyez AnalyticsCONTENT HISTORY

Update to Webeyez Analytics

Snapshot Nov 7, 2026 · 00:09 UTC · version 1.0.3

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save Webeyez Analytics and check future changes in Following.

Up to 3 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Investigate sudden conversion drops, checkout friction, JavaScript errors, and failed API calls using Webeyez analytics and session replays.",
  "included_files": [],
  "name": "investigate-conversion-drop",
  "skill_md_contents": "---\nname: investigate-conversion-drop\ndescription: Investigate sudden conversion drops, checkout friction, JavaScript errors, and failed API calls using Webeyez analytics and session replays.\n---\n\n# Investigate Conversion Drop\n\nUse this skill when a user asks why conversions dropped, reports checkout failures, or wants to find the root cause of lost revenue on their store.\n\n## Workflow\n\n1. **Identify Organization and Domain**\n   - Call `get_organizations_list` to find the user's accessible organizations and `organizationId`.\n   - Call `get_organization_domains` with the `organizationId` to identify the target store `domain` if not already specified by the user.\n\n2. **Query Conversion and Funnel Diagnostics**\n   - Call `start_webeyez_query` with a targeted question about the conversion drop, funnel drop-offs, checkout failures, JavaScript errors, and failed network calls for the relevant time period (e.g., last 24 hours or today vs. previous baseline).\n   - If `start_webeyez_query` returns `status: \"processing\"` with a `jobId`, poll `check_webeyez_status` until the query completes.\n\n3. **Retrieve Session Replay Examples**\n   - If the query results include affected `Session Id`s, call `get_session_recording_links` (up to 10 session IDs) so the user can watch the exact sessions where friction or errors occurred.\n\n4. **Present Findings Ranked by Impact**\n   - **Executive Summary:** State clearly whether the drop is driven by a technical issue (JS error, failed API call, slow page load) or funnel/traffic shift.\n   - **Top Issues by Revenue/Conversion Impact:** List the specific page paths, error messages, affected browsers/devices, and affected session counts.\n   - **Session Replays:** Include direct links from `get_session_recording_links` for immediate verification.\n   - **Recommended Fixes:** Provide prioritized, actionable next steps for engineering or product teams.\n\n"
}

SHA-256 of public snapshot: 8021965fde529b5fe044a358f6b7663b1cf0645f84951b77933732fb4820658c