Agent skill · data analytics · adobe
aa-segment-performance-comparator
Compares the performance of two or more audience segments across key metrics side by side. Use this skill when someone wants to compare audiences or visitor groups — for example, "how do mobile visitors compare to desktop on conversion," "compare new vs. returning visitors," "show me the difference between these two segments," "compare these audiences on our KPIs," or "which segment performs better." Also trigger for "segment comparison" or "audience comparison.
Why this skill is useful
Provides specific commands and workflows for comparing audience segments in Adobe Analytics that the AI wouldn't reliably generate on its own.
What it needs
Requires adobe account access. About 6k tokens when loaded. Last updated 2026-08-06. 160 stars on the source repository.
What this skill does
Segment Performance Comparator (Adobe Analytics) Compare the performance of two or more audience segments across key metrics side by side to understand how different visitor groups behave. Uses direct segment-vs-segment comparison to determine a winner, loser, and spread for each metric, with a separate context panel showing segment sizing. AA Call Budget: AA's runReport accepts a single segmentId per call. For N segments × M metrics the comparison requires N×M calls, plus 1 baseline call for the segment-size context panel. For 3 segments × 5 metrics = 16 calls. Limit to 4 segments and 6 metrics for practical performance. Always confirm the segment/metric list with the user before starting. --- AA MCP Tools Used findReportSuites — select report suite setSessionDefaults — set session context (reportSuiteId + globalCompanyId) findSegments — discover and select comparison segments findMetrics — resolve metric IDs runReport — one call per segment per metric, plus one unsegmented call for sizing context --- Phase 0 — Setup 1. Confirm report suite with findReportSuites / setSessionDefaults. --- Phase 1 — Select Segments Ask the user which segments to compare. If not specified, prompt: "Which visitor audiences would you like to compare? For example: Mobile vs. Desktop, New vs. Returning, Paid Search vs. Organic, or specific named segments from your library." Search for and confirm each segment: Note: findSegments does not accept a searchTerm parameter. Retrieve all segments and filter by name locally. Built-in template segments have short IDs like "PaidSearch" that can be passed directly as segmentIds in runReport. If the user requests a segment that doesn't exist by name, offer to build it first using the aa-segment-builder skill, or suggest the closest existing segment from search results. Limit: 4 segments maximum per comparison. Advise this limit upfront. --- Phase 2 — Select Metrics Ask the user which metrics to compare. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills adobe/aa-segment-performance-comparator