About Signal

Signal is the AI-powered dashboarding surface in Amperity. It uses your unified data foundation to visualize the KPIs driving your business, and lets you interact naturally with them to gather actionable insights.

With the Signal assistant chat beside the dashboard, Signal helps you understand both what happened and why without having to toggle to a separate query editor or a reporting tool.

A Signal board, with the hero metric and its trend chart above the supporting metrics, and the Signal assistant chat docked alongside.

Key concepts

Boards and cards

A board is one view of the business: a set of related charts covering a single period of time. You land on your board when you open Signal. If you don’t have one set up, you will be prompted to do so.

Your tenant can have several boards. One board usually covers the business overall, and others narrow to whatever you look at separately—a brand, a region, a channel, a loyalty program.

A board reads one table. Every card on it measures that table over the same date column, so the period and filters apply to all of them. Its filters can also narrow every card by customer attributes held in other tables, such as loyalty tier, while the cards still read the board’s own table. To report on a different table, create another board.

A card is one chart on a board. Each one answers a single question about your customers. It says what to measure and where to measure it, and Amperity works out the number each time you look. Change the period you are reading, and every card on the board answers again for that period.

Cards come in two shapes, and between them they cover the two things you usually want to know:

  • How big is the number, and which way is it going? A card of this kind reports one number—revenue, orders, customers, average order value—and plots it across the designated time period, so you can see the level and the trend at once.

  • What is it made of, and what is shifting? A card of this kind takes the same kind of number and splits it into bands: revenue by brand, orders by channel, customers by type. It shows which bands are largest, and separately which ones moved the most, so a small band gaining fast does not disappear behind a large one standing still.

Every card, of either kind, reports its time period against the same span one year earlier. That comparison is always there and is the same on every card, so a board can be read for what changed without setting a baseline first.

The cards on a board are ordered so the page reads top to bottom: the headline metric first, the metrics that support it beneath, and the breakdowns last. Everything on the page is measured over the same period and the same filters, so the numbers are directly comparable.

Note

Where your tenant has more than one board, the board title at the top of the page becomes a switcher listing all of them, and Signal shows one board at a time. Opening Signal without naming a board shows the default board, and any board can be set as the default.

Runs via the Signal assistant

A Signal board is operated by conversation. The Signal assistant chat sits beside the board, and it is the best way to interact with the board.

Ask it what a metric means, or why one moved, and it answers from that card’s own definition and the numbers currently on screen. Ask it to add a card, remove one, retitle or reorder the cards, change what a card measures, or build a new board, and it writes those changes to the board and the page reloads itself.

You do not have to provide additional context when asking a question. The chat is already grounded in the board, its cards, the values on screen, and the filters you have applied, so a question about why a given metric is up or down knows what to look for.

A few things are handled in the user interface instead of the Signal assistant: renaming a board, setting which board opens by default, duplicating or deleting one, and saving filters. Everything that changes what a board measures should be a request to the Signal assistant.

Setup

Select Signal in the left navigation. A board opens with its own address, so a link to a board can be shared with anyone in your tenant.

Note

Signal requires AI Assistant features to be enabled for your tenant. When they are not, the Signal page offers to enable them, which a user assigned the DataGrid Operator or DataGrid Administrator policy can do. See Enable or disable AI Assistant features.

Prerequisites

For Signal to show anything, four things must be in place:

  • AI Assistant features enabled for your tenant.

  • A database containing the table the board reads. The table needs a date or datetime column.

  • Data loaded into that table. A table that reports no load date gives the board no window to measure, and the board reports that the window its cards measure cannot be resolved.

  • A board with at least one card on it. Until then, Signal shows an empty page offering to build one with the Signal assistant.

The Signal page on a tenant with no board yet, with a prompt to walk through building the first Signal board with the Signal assistant.

A board can read any table with a date column that has data loaded. On a tenant with Unified Transactions, a customer health board—revenue, orders, customers, and repeat behavior—reads UT_Analytics, an analytics table built from Unified Transactions. On a tenant without Unified Transactions, it reads the tenant’s transaction table directly. A board on any other table reads that table as it is, including data that describes tickets, stays, bookings, or other non-order events.

Access and permissions

What you can do in Signal depends on the policy assigned to you.

To do this

Policies that allow it

View the boards in your tenant and load their cards

AmpIQ User, Amp360 User, DataGrid Operator, and DataGrid Administrator

Create, change, or delete a board or a card

Amp360 User, DataGrid Operator, and DataGrid Administrator

The read-only policies—Amp360 User Read Only, AmpIQ User Read Only, and DataGrid Operator Read Only—can view boards and load their cards, but not create, change, or delete them.

To change what someone can do in Signal, change their policy or its options. See Policies.

Building or changing a board through the Signal assistant also requires access to the AI Assistant. A user whose policy has the Restrict AI Assistant access option can view boards but cannot use the Signal assistant.

Signal configuration is tenant-wide rather than scoped to a resource group, but running a card is additionally authorized against the resource group of the database that card queries. A user who can open a board may still be unable to load a card that reads a database they do not have access to.

Using AI to write a board

There are three ways to build a board:

Signal assistant

Open Signal and select Walk me through building my first Signal board. The Signal assistant starts on your first board.

Working with the Signal assistant
Pér

Ask Pér, Amperity’s AI agent, to build a Signal board for your tenant.

../per/what_is_per.html
Amperity MCP server

Connect an AI client, such as Claude, ChatGPT, or Copilot, to the Amperity MCP server and ask it to build one.

../api/mcp_overview.html

All three follow the same instructions, so a board built one way is a board you can read and change the other ways.

A build with the Signal assistant pauses for you to confirm:

  • The kind of board and its database. A board’s database cannot be changed after the board is created.

  • What it found. The table the board will read and the metrics it proposes. Nothing is written until you confirm.

  • Building the table and running the database. For a customer health board on a tenant with Unified Transactions, the build creates the UT_Analytics table, or brings an existing one up to date, and then runs the database. Creating the table and running the database require the DataGrid Administrator policy. It changes no other table. The run rebuilds every table in the database and takes 5 to 15 minutes in the fastest mode. Reload the page when it finishes.

Before it writes anything, the Signal assistant reads the custom prompt and the company context documents set for your tenant, so that card titles and metric definitions follow your own business rules and vocabulary rather than generic defaults. Where your own definition of a metric differs from the default, yours wins.

Working with the Signal assistant

Signal has an AI assistant chat docked beside the board. It is one ongoing conversation: pointing it at a card does not start a separate one.

Investigating a card or a board

Each card carries an Ask Signal assistant control. Selecting it re-grounds the docked chat in that card: its compiled SQL, the values currently on screen, the filters currently applied, and—if you have dragged across a run of buckets on the trend chart—the range you highlighted. It loads a question into the input box for you to edit or send. It does not send one for you.

The Ask Signal assistant control on a Signal card.

With no card selected, the chat is grounded in the board as a whole: its title, and every card’s kind, position, title, table, and measure.

The Signal assistant answers by querying the table the card reads rather than speculating.

When the conversation is empty, it offers a few questions to start from, and suggests follow-ups after each answer, drawn from what it just found.

Editing the board

Ask the Signal assistant to add, remove, retitle, or reorder cards, to change what a card measures, to offer customer attributes in the filter bar, or to point the board at a fiscal calendar, and it writes those changes to the board’s configuration. The page reloads itself when the run ends.

Several safeguards sit around those writes:

  • It validates before it writes. The Signal assistant checks a card against the table it will read, and reads a column’s real values rather than guessing their spelling or case. If it cannot validate a card—the table is missing, or has no rows yet—it does not write the card, and tells you what blocked the check.

  • It confirms before it deletes. Deleting a board deletes every card on it, so the Signal assistant lists those cards before it asks.

  • It confirms before it changes a table. Table changes and database runs are separate confirmations from card changes, and the Signal assistant touches only the analytics table the dashboard reads.

  • Every change is versioned. Boards and cards are recorded in your tenant’s configuration history alongside your other configuration, as Signal board, Signal metric viz, and Signal stacked bar viz, and a change can be reverted there.

A card belongs to the board it was created on. To move one to another board, ask the Signal assistant to delete it and create it on the other board.

The user interface handles a smaller set of changes directly: renaming a board and its description, setting the chart scale and fiscal view, saving filters, setting the default board, and duplicating or deleting a board. Adding a card, removing one, or changing what one measures is a request to the Signal assistant.

Tip

When Signal cannot do something you need—a chart type, a granularity, or a control it does not offer—say so to the Signal assistant. It can file the request with Amperity’s product team on your behalf, after you confirm.

How data is grounded

Card definitions

Every card carries a definition control that shows how its number is calculated.

A card whose author wrote a description shows that description in plain language on hover, with a View SQL link beneath it. A card with no description opens straight to the SQL instead. Opening the definition shows a dialog titled with the card name, containing whichever of these parts apply:

  • What this measures—the card’s description, in the language of your business.

  • Metric expressed as SQL—the aggregate the card measures.

  • Filtered to—the rows the card restricts itself to, where it sets its own restriction.

  • SQL—the statement Amperity compiled and ran for the values on screen.

That last part is the statement itself, not a description of one: the same period, granularity, and filters you are looking at, as they reached the query engine. A number that looks wrong can be checked by reading it, or run elsewhere to reproduce it.

A Signal card definition, showing what the card measures above the SQL statement that produced the values on screen.

Note

A card’s description is written when the card is authored. A card that has none shows its raw aggregate in place of a plain-language explanation. When you ask the Signal assistant to change what a card measures, ask it to rewrite the description in the same change.

Your definitions, not generic ones

The Signal assistant reads the custom prompt and the company context documents set for your tenant before it authors or changes a card. Where those define a metric, name something, or set a business rule, they take precedence over the defaults the Signal assistant would otherwise use. A board therefore reports your own definition of a metric under your own name for it, rather than a generic one that has to be translated every time someone reads it.

If the Signal assistant cannot read one of them, it says so in its reply and continues from the defaults, so you know when your own definitions were not applied.

Limitations

How a board measures

  • The year-over-year comparison is fixed. It cannot be changed to another baseline.

  • A period cannot be longer than a year.

  • Windows are measured back from the date your data is loaded through, not from today.

What it reads

  • Signal measures data already in Amperity. Bringing outside data in is a separate exercise.

  • Every card on a board reads the same table, over the same date column, in the board’s database. A board’s database cannot be changed after the board is created.

  • The card catalog the Signal assistant starts from is written for retail order data. On a table that describes tickets, stays, or other non-order events, the Signal assistant writes cards from that table’s own columns and tells you the catalog did not apply.

Filtering

  • The filter bar lists columns from the board’s own table first. It offers text and true/false columns with more than one and no more than 50 distinct values. Identifier columns are excluded, and numeric and date columns cannot be filtered.

  • A board can also offer customer attributes from other tables in its database, such as loyalty tier or home region. They are listed under the name of their table. Ask the Signal assistant to add them.

  • Attributes that change over time, such as loyalty tier, reflect each customer’s value today rather than at the time of each order.

Important

Anyone who can open a board can drop the filters it carries and read it unfiltered. A board scoped to one brand or one region is a convenience for the people who read it, not a control over what they can see.

Authoring

  • Adding a card, removing one, or changing what one measures is done by asking the Signal assistant.

  • A card cannot be moved between boards. It must be re-created on the other board.

  • The page does not passively refresh. The Signal assistant reloads the board after a change it made, but a change made from anywhere else is not visible until you reload the page or complete a change through the Signal assistant chat.