> For the complete documentation index, see [llms.txt](https://help.gleantap.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.gleantap.com/scorecards/add-custom-metrics.md).
# Add Custom Metrics
A **Custom Metric** is a saved count or aggregate that you can drop into any Scorecard. Under the hood it's just a segment-style filter with a specific date field for time filtering — but it lets you build reports on any slice of your data without rebuilding the filter every time.
Examples: "New leads added in the last 30 days", "Members with a birthday this week", "Contacts with a bounce complaint in the last 7 days".
***
## Where to build one
Two entry points:
* **From a Scorecard** — click **Custom Metric** while configuring a scorecard tile.
* **From Settings** — **Settings → Custom Metrics → Add Custom Metric**.
Both open the same builder.
***
## The three ingredients
Every Custom Metric has three parts.
### 1. Metric Name
Internal label for the metric. Choose one that makes it obvious how the metric is used. If you plan to reuse this metric in multiple Scorecards, a clear name matters — e.g., `Leads added (last 30 days)`, `Active members with a birthday this week`, `Members who no-showed a class in the last 7 days`.
### 2. Date Filter Field
**This is the field the Scorecard's date-range filter operates on.** When you view a Scorecard filtered to "last 30 days", the Scorecard applies that range to whatever Date Filter Field you configured on the metric.
Pick the field that matches your metric's meaning:
| Metric measures... | Use as Date Filter Field |
| ---------------------------------- | ------------------------ |
| When someone was added to Gleantap | `Add Date` |
| When they became a member | `Membership Start Date` |
| When they last visited | `Last Visit` |
| When they last purchased | `Last Purchase Date` |
| A form submission | `Form Submission Date` |
| An appointment | `Appointment Date` |
If you pick the wrong Date Filter Field, the Scorecard will filter to time periods that don't match what you meant. **Rule of thumb:** the Date Filter Field should be the moment the *thing you're counting* happened.
### 3. Custom Filter
This is the actual criteria — same builder as [Creating Segments → Filter Options](/audience/creating-segments/filter-options.md).
You combine filters just like segments:
* Attribute (e.g., `No. of Visits`)
* Operator (e.g., `Greater Than`)
* Value (e.g., `5`)
Combining multiple filters uses AND logic. To model OR logic across groups, use the segment builder's group functionality.
***
## Worked example: "New leads added in the last 30 days"
**Goal:** count how many new leads (not yet members) were added to Gleantap over a rolling 30-day window.
1. **Metric Name:** `New leads (rolling)`
2. **Date Filter Field:** `Add Date` — because you're counting people by when they joined Gleantap.
3. **Custom Filter:**
* `Type — Is Equal To — Lead` (or your equivalent for "not a member yet")
Save. Then in your Scorecard, add a tile using this metric, and set the Scorecard's date range to Last 30 Days. The count updates as you change the date range.
## Worked example: "Members who bought a Summer Camp product but haven't visited in 30 days"
**Goal:** find summer-camp buyers who have gone quiet — potential re-engagement targets.
1. **Metric Name:** `Camp buyers, 30-day dormant`
2. **Date Filter Field:** `Last Purchase Date` — the moment they bought the summer-camp product.
3. **Custom Filter:**
* `Purchase Info → Has Purchased Item → Summer Camp 2026`
* `Visit Info → Last Visit → Over Days: 30`
Save. In a Scorecard tile, this shows the count as of the date range you filter. Combined with a "compare to previous period" toggle on the Scorecard, you can see whether dormant camp buyers are growing or shrinking.
## Worked example: "Bounced emails in the last 7 days"
**Goal:** monitor deliverability health week over week.
1. **Metric Name:** `Email bounces (weekly)`
2. **Date Filter Field:** `Email Bounce Date` — when the bounce was recorded.
3. **Custom Filter:**
* `invalid_email — Is Equal To — 2` (bounce state — see [Understanding Suppression](/audience/understanding-suppression.md))
If this count spikes, something changed in your sending or the receiving side — investigate.
***
## Using a Custom Metric in a Scorecard
Once saved:
1. Open **Scorecards** → the scorecard where you want to display it.
2. Click **Add Tile** or edit an existing tile.
3. Pick your Custom Metric from the list.
4. Choose the tile format (count, trend line, comparison to previous period, etc.).
5. Save.
The tile now shows the metric's current value against the Scorecard's date range. When you change the Scorecard's date range, the tile recalculates.
Deep dive: [Configure a Scorecard](/scorecards/configure-a-scorecard.md), [Popular Scorecards](/scorecards/popular-scorecards.md).
***
## Editing and reusing metrics
A Custom Metric is reusable across Scorecards. If you edit the metric definition (change a filter, rename it, change the Date Filter Field), every Scorecard using it will pick up the change on next view.
To edit: **Settings → Custom Metrics** → click the metric to edit.
To delete: same location → three-dot menu → Delete. You can only delete a metric that isn't currently used in a Scorecard; remove it from Scorecards first.
***
## Common scenarios
### "My Scorecard shows the wrong count for the time range"
The likely cause is the **Date Filter Field**. If you set it to `Add Date` but you're counting purchases, the Scorecard is filtering by when the person was *added*, not when they *purchased*. Edit the metric and pick the correct date field.
### "I want a metric that combines two OR conditions"
Custom Metrics use the same segment builder as segments — group your filters and use OR at the group level. See [Filter Options](/audience/creating-segments/filter-options.md).
### "Can a Custom Metric count events, not contacts?"
Today, Custom Metrics count contacts matching filters — not raw event volume. To count events (e.g., "total SMS sent last week"), use campaign-level reports rather than a Custom Metric. See [Email Campaign Stats](/campaigns/email-campaign-stats.md) and [SMS Campaign Stats](/campaigns/sms-campaign-stats.md).
### "How do I sum a numeric field rather than count contacts?"
Not directly supported in Custom Metrics today. If you need a sum (e.g., total dollar value of a campaign), use dedicated dashboard tiles or your CRM's reporting. Reach out to if this is a repeated need.
***
## Related pages
* [Scorecard Overview](/scorecards/scorecard-overview.md) — what Scorecards are
* [Configure a Scorecard](/scorecards/configure-a-scorecard.md) — building a Scorecard with metrics
* [Popular Scorecards](/scorecards/popular-scorecards.md) — pre-built examples
* Creating Segments — the segment builder that powers Custom Filter
* [Filter Options](/audience/creating-segments/filter-options.md) — operator reference for building filters
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://help.gleantap.com/scorecards/add-custom-metrics.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
