For the complete documentation index, see llms.txt. This page is also available as Markdown.

Examples & Best Practices

Example use cases for agencies and brand operators

The Intelligems MCP server gives AI assistants access to your test results, personalization data, and Sitewide Analytics — all queryable in plain English.

The examples below are organized by how you use Intelligems: as a brand managing your own store, or as an agency managing tests and performance for clients.

For Agencies

1. Monthly Client Performance Review Use when preparing for monthly client calls

For [CLIENT NAME], give me a comprehensive analysis of all tests completed this month. Include:
1. Which tests reached statistical significance and their winners
2. The estimated revenue impact of implementing winners
3. Key insights to share with the client
4. Any tests that should be ended early or extended

What you'll get: List of completed tests with win/loss status, revenue per visitor and gross profit uplift percentages, statistical confidence levels, and actionable recommendations for client discussion.


2. Cross-Test Pattern Analysis Use to find winning strategies that work consistently

Analyze all completed tests for [CLIENT NAME] over the past 3 months.
What patterns appear across multiple winning tests?
What concepts (urgency, trust, social proof, simplification, etc.)
consistently win or lose for this customer base?

What you'll get: Patterns across winning variations, concepts that resonate with the client's audience, and strategic direction for future testing.


3. Customer Segment Intelligence Use to understand how different customer types respond

What you'll get: Conversion rates by device type, performance differences between new vs returning visitors, and recommendations for segment-specific optimization.


4. Profit Trap Detection Use to catch tests where more conversions = less profit

What you'll get: Tests where conversion went up but profit went down, warnings about implementing harmful "winners", and true profit-focused recommendations.


5. Quarterly Test Roadmap Use for strategic planning

What you'll get: Analysis of highest-performing test categories, untested areas, and a prioritized test roadmap for the next quarter.


6. Cross-client performance scan Use to quickly identify which clients need attention

What you'll get: A prioritized list of clients showing performance deterioration, so you can triage proactively rather than waiting for clients to flag issues.


For Brand Operators

1. Weekly Test Pulse Check Use for quick status instead of reviewing dashboards

What you'll get: Status of all running tests, statistical significance levels, clear winner/loser identification, and recommendations for early stopping or extension.


2. Profit Opportunity Scan Use to find biggest revenue opportunities

What you'll get: Ranked list of winners by revenue impact, un-implemented winners leaving money on the table, and a prioritized implementation list.


3. My Best Customer Segments Use to know where to focus optimization efforts

What you'll get: Performance breakdown by device type, new vs returning comparison, and recommendations for resource allocation.


4. Testing Strategy Health Check Use to evaluate testing program effectiveness

What you'll get: Test completion count, win rate analysis, test type distribution, and recommendations for improving your testing program.


5. Price Sensitivity Analysis Use to understand customer price tolerance

What you'll get: Price sensitivity insights from test data, segment-specific price response differences, and data-backed discount recommendations.


6. Store health check Use for a quick pulse on overall performance

What you'll get: Period-over-period comparison across core KPIs with automatic flagging of notable changes.


7. Channel quality ranking Use to understand which traffic sources are actually driving revenue

What you'll get: Channel-by-channel RPV and CVR breakdown, quality vs. volume analysis, and identification of any channels showing efficiency deterioration.


8. Mobile vs desktop gap Use to diagnose device-level conversion issues

What you'll get: Side-by-side device performance metrics, trend direction for each device, and context on where growth is coming from.


9. New vs returning customer analysis Use to understand retention health relative to acquisition

What you'll get: Segment-level performance metrics, new/returning mix trends, and signals on whether retention is keeping pace with acquisition.


10. AOV and discount trend

Use to catch margin compression early

What you'll get: AOV and units-per-order trend data, discount rate changes, and revenue-per-unit movement that can signal margin pressure before it shows up in reports.


Best Practices

Organization Context

  • Always specify the organization parameter when working with multiple organizations

  • Use getOrganizationsList first to see available organizations

  • Cache organization IDs in your workflow to avoid repeated lookups

Security

  • Never share your access tokens

  • Tokens are scoped to all organizations you have access to

  • Revoke access immediately if compromised

Last updated

Was this helpful?