> ## Documentation Index
> Fetch the complete documentation index at: https://docs.quivly.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Choose how each usage metric adds up

> Usage API events can now specify how a metric should be combined.

export const ReleaseDate = ({date, dateTime, archive}) => <a className="release-date" href={archive}><time dateTime={dateTime}>{date}</time></a>;

export const ReleaseLabels = ({tags}) => <span className="release-labels" data-release-kind={tags.includes("Feature release") ? "feature" : tags.includes("Bug fix") ? "fix" : "improvement"}>{tags.map(tag => <span key={tag} className={`release-label release-label-${tag.toLowerCase().replaceAll(" ", "-")}`}>{tag}</span>)}</span>;

export const ReleaseHeader = ({title, description, date, dateTime, tags, archive, version}) => {
  const [copyStatus, setCopyStatus] = useState("");
  const copyLink = async () => {
    try {
      await navigator.clipboard.writeText(window.location.href.split("#")[0]);
      setCopyStatus("Link copied");
    } catch {
      setCopyStatus("Copy the page address from your browser to share this update.");
    }
  };
  return <header className="release-article-header">
      <a href="/changelog" className="release-back">
        <svg width="16" height="16" viewBox="0 0 24 24" fill="none" stroke="currentColor" strokeWidth="1.5" aria-hidden="true"><path d="m12 5-7 7 7 7M5 12h14" /></svg>
        Back to What's new
      </a>
      <div className="release-article-meta">
        <ReleaseDate date={date} dateTime={dateTime} archive={archive} />
        <ReleaseLabels tags={tags} />
        {version ? <span className="release-version" aria-label={`Release ${version}`}>{version}</span> : null}
        <button type="button" onClick={copyLink} aria-label={copyStatus === "Link copied" ? "Link copied" : "Copy link"} title={copyStatus === "Link copied" ? "Link copied" : "Copy link"}>
          {copyStatus === "Link copied" ? <svg width="16" height="16" viewBox="0 0 24 24" fill="none" stroke="currentColor" strokeWidth="1.5" aria-hidden="true"><path d="m5 12 4 4L19 6" /></svg> : <svg width="16" height="16" viewBox="0 0 24 24" fill="none" stroke="currentColor" strokeWidth="1.5" aria-hidden="true"><path d="m10 13 4-4M8 16l-1 1a4 4 0 0 1-6-6l4-4a4 4 0 0 1 6 0m2 1 1-1a4 4 0 0 1 6 6l-4 4a4 4 0 0 1-6 0" /></svg>}
        </button>
      </div>
      <h1>{title}</h1>
      {description ? <p className="release-summary">{description}</p> : null}
      <span className="release-copy-status" role="status">{copyStatus}</span>
    </header>;
};

<div className="release-article">
  <ReleaseHeader description={"Usage API events can now specify how a metric should be combined."} dateTime="2026-09-23" title="Choose how each usage metric adds up" date="September 23, 2026" tags={["Improvement"]} archive="/updates/2026-09" />

  <div className="release-article-body">
    Use **latest** for a current value, such as the number of active seats, or **sum** for a running total, such as API calls. Average, minimum, maximum, and count are also supported.

    Send test events to see the available metrics, check their settings, and publish. Reports use those published settings. Quivly rejects conflicting settings for the same metric so your reports stay consistent.

    [Set up the Usage API](/integrations/product-usage/api-overview)
  </div>

  <div role="navigation" className="release-related" aria-label="More product updates">
    <h2>More updates</h2>
    <a href="/updates/releases/2026-09-30-get-play-review-alerts-by-email">Get Play review alerts by email</a>
    <a href="/updates/releases/2026-09-30-keep-health-scoring-instructions-in-ai-created-skills">Keep health scoring instructions in AI-created Skills</a>
    <a href="/updates/2026-09">All September 2026 updates</a>
  </div>
</div>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.