CONNECT OMNISEND TO MUSE
Set up Omnisend 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 Omnisend in Adzviser
Connect Omnisend using an API key. 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 account. 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 OMNISEND REPORT
Find campaigns that earn a stronger click response
Build a report you can check
Select campaigns sent during a defined period and return sends, opens, clicks, click rate and unsubscribes with the campaign name and start date. Rank click response with send volume visible. Then request the separate A/B test fields for a chosen test, keeping test variants distinct from the overall campaign result.
Compare tests within the same experiment
The catalog exposes campaign and A/B test engagement measures, plus a field identifying the winning test. Inspect the observed rates and sample sizes before treating a small difference as meaningful. A campaign with a larger audience can generate more clicks while a smaller one has a higher rate.
Turn the result into a next-send hypothesis
Ask Muse to summarize the difference between test variants using the reported subjects, sends and click measures. Propose a follow-up test with one clear change and the outcome to evaluate. Keep any explanation about audience preference separate from the measured result.
Metrics for this report: Campaign sends; Campaign opens; Campaign clicks; Campaign click rate; Campaign unsubscribes.
Relevant breakdowns: Campaign name; Campaign start date.
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 Omnisend 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 Omnisend. List my workspaces and ask which connected account to use. Select campaigns sent during a defined period and return sends, opens, clicks, click rate and unsubscribes with the campaign name and start date. Rank click response with send volume visible. Then request the separate A/B test fields for a chosen test, keeping test variants distinct from the overall campaign result. Use these metrics in compatible reports: Campaign sends, Campaign opens, Campaign clicks, Campaign click rate, Campaign unsubscribes. Relevant breakdowns: Campaign name, Campaign start date. 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.
