Prepare your next client review with answers from connected Klaviyo data. Use Catchr MCP to ask ChatGPT about email click rates, SMS clicks and available order events.
For freelancers and agencies, start with the client account, discover its available fields and select the columns that answer your reporting question.
“Compare paid media performance across my client accounts and flag the biggest changes.”
Klaviyo
Google Ads
GA4
Used by the world's leading companies
Klaviyo uses a live schema, so discover the fields available for your connected account before building a query. Select supported columns and confirm that the requested metrics, dimensions and date basis work together.
Use available campaign details such as Campaign Name, Campaign Subject, Campaign Channel and Campaign Status to explain what you are reviewing. Campaign is part of flow and Campaign is segmented can add useful context where supported.
Campaign Created Date, Campaign Scheduled Date and Campaign Send Date describe different moments. Choose the date basis that matches the client question before comparing results.
Select Emails Clicked Rate and Emails Clicked Unique Rate for email engagement questions. For SMS reporting, discover whether Clicked SMS and Unique Clicked SMS are available, then query them with compatible dimensions.
Keep email reporting statistics separate from SMS results: Reporting API values cover email only. Do not cap returned rates or combine event dimensions with reporting counts without confirming compatibility.
Discover which commerce event fields are available in Klaviyo. These can include API placed orders and order value, Shopify placed, cancelled, fulfilled and refunded orders, and WooCommerce placed, cancelled, fulfilled and ordered-product events.
Select the event counts and values relevant to the client's setup. Keep each event family clearly labeled, and do not treat an order event total as proof that a particular email caused a purchase.
A focused Klaviyo analysis, a client report and a question through Catchr MCP serve different needs. Keep the selected account, columns and date basis consistent when moving between them.
Use source-focused analysis to investigate a Klaviyo result, reports to present a consistent client view, and Catchr MCP for follow-up questions on connected data. Preserve the same metric definitions and date basis so each answer remains comparable.
Connect Klaviyo to Catchr using API-key authentication and select the relevant client account. Choose ChatGPT or Claude through Catchr MCP, then discover the account's available Klaviyo fields.
Select your reporting columns, set the date range and choose the date basis. Event date is the default; campaign-send analysis needs Campaign Send Date, and flow export comparisons require Flow Send Date explicitly.
Replace the bracketed placeholders with your client account, dates and reporting choices. Each prompt starts with field discovery so the query uses columns available for that account.
Using Catchr, discover the available Klaviyo fields for [account]. Query my selected columns [email campaign columns], including Emails Clicked Rate and Emails Clicked Unique Rate where available, for [start date] to [end date] using campaign_send as the date mode. Include Campaign Name and Campaign Subject only if compatible. Which results have Emails Clicked Rate below [threshold]? Keep returned rates unchanged and identify any field combinations that cannot be queried together.
Copy promptUsing Catchr, discover whether Clicked SMS and Unique Clicked SMS are available for [account]. Use my selected compatible columns [SMS reporting columns] to compare [first date range] with [second date range] on an event_date basis. How did Clicked SMS change? Show Unique Clicked SMS only at a supported aggregation level, and do not sum daily unique counts into a period-wide unique total or use email-only reporting statistics for SMS.
Copy promptUsing Catchr, discover the available Shopify order event fields in the connected Klaviyo account [account]. For [start date] to [end date], query my selected columns [Shopify order event columns] on an event_date basis, using Shopify - Placed Order, Shopify - Placed Order Value, Shopify - Refunded Order and Shopify - Refunded Order Value where available. What counts and values are recorded for each selected event? Keep placed and refunded events separate and explain what these totals cannot establish about email attribution.
Copy promptUsing Catchr, discover the available Klaviyo flow-related fields for [account]. For [start date] to [end date], use flow_send explicitly and query my selected compatible columns [flow reporting columns]. What email click rates can I use to compare this report with a flow export? Use Campaign is part of flow where supported, state the account timezone and send-cohort basis when available, and omit date dimensions from Reporting API queries. Identify any missing information needed for a valid comparison.
Copy promptConnect Klaviyo in Catchr using API-key authentication, select the client account and choose ChatGPT through Catchr MCP. Discover the available fields before selecting the columns and date basis for your first query.
The reporting range and date basis are separate choices. Event date is the default. Use campaign_send for campaign-send analysis and flow_send explicitly for flow export comparisons. Reporting API values use send cohorts in the account timezone.
Keep them separate. Emails Clicked Rate and Emails Clicked Unique Rate describe email engagement; Clicked SMS and Unique Clicked SMS describe SMS activity. Reporting API statistics are email-only, so they should not be presented as combined email and SMS results.
The same person can appear on multiple days. Event aggregates count distinct openers per day, so adding them does not produce a period-wide unique count. Reporting API queries reject date dimensions because daily unique counts are also non-additive across days.
Connect your sources to Catchr, add the MCP server to your AI assistant, and ask about the work that matters now.
