CONNECT BIGCOMMERCE TO MUSE
Set up BigCommerce reporting in Muse
Adzviser retrieves the source data through its MCP reporting tools. Muse uses those results to answer your questions. Connect the source in Adzviser, then authorize Muse to use that connection.
Connect BigCommerce in Adzviser
Connect BigCommerce using your store hash and access token. Add the source to the workspace you want to use in Muse.
Open Adzviser setup →Authorize Adzviser in Muse
Open Muse.ai and send: “Can you connect to custom Adzviser MCP at https://mcp.adzviser.com/http?” Select Connect on the Adzviser card, sign in to Adzviser, and select Complete Authorization via MCP. Return to Muse.
https://mcp.adzviser.com/httpVerify the first result
Ask Muse to list your Adzviser workspaces and their sources. Choose the workspace and confirm the store. Request a small report for a known period before expanding the analysis.
The Adzviser reporting connection is read-only. It can retrieve data for analysis; it cannot edit source records or campaigns.
A USEFUL FIRST BIGCOMMERCE REPORT
Compare sales using a consistent order population
Build a report you can check
For one store, compare two complete 30-day periods. Define the included order statuses, then request orders, subtotal, discount and total amounts. Show whether tax is included. Ask for product detail separately and rank the largest product-sales changes without duplicating order-level totals across multiple line items.
Avoid double-counting totals in product detail
An order can contain several products. If an order-level amount repeats on each line, summing those rows would overstate sales. Keep order totals and item-level measures in separate summaries unless the aggregation is explicit. Also distinguish tax-inclusive and tax-exclusive fields before reconciling with another report.
Inspect whether discounting explains the change
Ask Muse to compare the movement in subtotal, discounts and order totals before attributing a sales change to demand. For the products contributing most, request the supporting item-level quantities or values available in the connector.
Metrics for this report: Orders; Order subtotal; Order discount; Order total; Order total (ex tax).
Relevant breakdowns: Order ID; Order status.
These are starting fields, not a promise that every combination belongs in one report. Use separate requests for different reporting levels and check the full field catalog for additional coverage.
COPY INTO MUSE
Run your first BigCommerce analysis
Paste this after connecting. Change the period or research subject to match your question, and let Muse confirm the selection before retrieving results.
Use Adzviser to analyze BigCommerce. List my workspaces and ask which connected store to use. For one store, compare two complete 30-day periods. Define the included order statuses, then request orders, subtotal, discount and total amounts. Show whether tax is included. Ask for product detail separately and rank the largest product-sales changes without duplicating order-level totals across multiple line items. Use these metrics in compatible reports: Orders, Order subtotal, Order discount, Order total, Order total (ex tax). Relevant breakdowns: Order ID, Order status. Check field compatibility and use separate tables for different reporting levels. State the actual reporting dates or observation window. Show the supporting rows, then give a short conclusion and one next investigation. Label missing data and separate observed changes from possible explanations.
