Webeyez Analytics

View saved version →

---
name: investigate-conversion-drop
description: Investigate sudden conversion drops, checkout friction, JavaScript errors, and failed API calls using Webeyez analytics and session replays.
---

# Investigate Conversion Drop

Use 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.

## Workflow

1. **Identify Organization and Domain**
   - Call `get_organizations_list` to find the user's accessible organizations and `organizationId`.
   - Call `get_organization_domains` with the `organizationId` to identify the target store `domain` if not already specified by the user.

2. **Query Conversion and Funnel Diagnostics**
   - 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).
   - If `start_webeyez_query` returns `status: "processing"` with a `jobId`, poll `check_webeyez_status` until the query completes.

3. **Retrieve Session Replay Examples**
   - 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.

4. **Present Findings Ranked by Impact**
   - **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.
   - **Top Issues by Revenue/Conversion Impact:** List the specific page paths, error messages, affected browsers/devices, and affected session counts.
   - **Session Replays:** Include direct links from `get_session_recording_links` for immediate verification.
   - **Recommended Fixes:** Provide prioritized, actionable next steps for engineering or product teams.

View saved version →

---
name: weekly-performance-summary
description: Generate an executive weekly performance summary of eCommerce conversions, top revenue-impacting issues, UX friction signals, and site health using Webeyez.
---

# Weekly Performance Summary

Use this skill when a user asks for a weekly performance report, executive summary, store health check, or prioritization of issues from the past week.

## Workflow

1. **Resolve Target Store**
   - Call `get_organizations_list` to get the user's `organizationId`.
   - Call `get_organization_domains` to determine the store `domain` to report on.

2. **Gather Weekly Analytics & Top Friction Points**
   - Call `start_webeyez_query` asking for a comprehensive summary of the past 7 days covering overall sessions, conversion rates, top revenue-costing issues, checkout drop-offs, JavaScript/API errors, and UX friction signals (rage clicks, dead clicks, slow page loads).
   - If `start_webeyez_query` returns `status: "processing"`, use `check_webeyez_status` with the returned `jobId` until completed.

3. **Fetch Representative Session Recordings**
   - If specific high-impact sessions are returned in the data, call `get_session_recording_links` for up to 10 session IDs to provide concrete replay examples.

4. **Structure the Weekly Report**
   - **Key Metrics Overview:** Summarize traffic, conversion trends, and overall digital experience health over the past 7 days.
   - **Top Revenue-Impacting Issues:** Highlight the highest-cost bugs, failed API requests, or checkout blockers.
   - **UX & Performance Breakdown:** Note any device, browser, or page-path anomalies (including rage clicks and page load issues).
   - **Prioritized Action Plan:** Recommend the top 3 fixes the engineering or UX team should tackle first, accompanied by session replay links where available.