> ## Documentation Index > Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt > Use this file to discover all available pages before exploring further. # Spend Anomaly, The Trade Desk > Spend Anomaly for The Trade Desk stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it. **Metrics type:** [Supporting Metrics](/nerve-centre/overview#metrics-types-explained) • **Category:** [Ad Platform](/nerve-centre/connectors#connectors-by-type) ## At a glance > **Spend Anomaly** is a alerts & anomalies metric tracked from The Trade Desk data. It surfaces operational signal at the alerts & anomalies layer so merchants can spot regressions, opportunities, and structural patterns in their store performance. The card pairs with sibling metrics in the Alerts & Anomalies category to build a complete diagnostic picture; cross-reference the related cards listed below for context. | | | | --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **What it counts** | Spend Anomaly as exposed by the The Trade Desk integration. The metric is computed from the latest available data and refreshed on the standard data refresh. | | **Sample type** | Backend API data from The Trade Desk, refreshed on the standard data refresh. | | **Why it matters** | The metric appears in the Alerts & Anomalies category and complements the sibling cards listed below. Track movement over time to identify regressions or opportunities. | | **Reading the value** | Compare the current period to the prior period to identify direction. Cross-reference siblings for the full diagnostic picture. | | **Currency** | currency | | **Time window** | `24H` | | **Alert trigger** | `>2σ vs 30D baseline` | | **Sentiment key** | `the_spend_anomaly` | | **Roles** | owner, marketing, finance | ## Calculation Calculated automatically from your The Trade Desk data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading. ## Worked example *A representative reading of **Spend Anomaly** for a typical merchant on The Trade Desk.* The card reports the current period value alongside a comparison against the previous period. Direction matters: rising values may be healthy or concerning depending on the underlying metric. Cross-reference the siblings below to triangulate cause when the value moves outside expected range. For deeper investigation, use Vortex Mind to trace upstream causes; for natural-language exploration, ask Ask Viq. ## Sibling cards merchants should reference together | Card | Why merchants reach for it | | ------------------------------------------------------------------------------------- | -------------------------------------------------- | | [`the_conversion_drop`](/nerve-centre/kpi-cards/the-trade-desk/conversion-drop-alert) | Alerts & Anomalies sibling: Conversion Drop Alert. | | [`the_cpc_anomaly`](/nerve-centre/kpi-cards/the-trade-desk/cpc-anomaly) | Alerts & Anomalies sibling: CPC Anomaly. | | [`the_ctr_decline`](/nerve-centre/kpi-cards/the-trade-desk/ctr-decline-alert) | Alerts & Anomalies sibling: CTR Decline Alert. | | [`the_impression_share`](/nerve-centre/kpi-cards/the-trade-desk/impression-share) | Alerts & Anomalies sibling: Impression Share. | | [`the_all_conversions`](/nerve-centre/kpi-cards/the-trade-desk/all-conversions) | Funnel & Conversion sibling: All Conversions. | ## Reconciling against the vendor's own dashboard **Where to look in The Trade Desk's own dashboard:** The The Trade Desk dashboard surfaces this metric (or its components) under the relevant report section. Confirm period boundaries and filter settings match the Vortex IQ profile to reconcile cleanly. **Why the Vortex IQ value may legitimately differ:** | Reason | Direction | What to do | | ---------------------------------------------------------------------------------------------------------- | --------- | ------------------------ | | **Period boundary.** Vortex IQ uses 30-day rolling by default; vendor dashboards may use calendar periods. | Variable | Match the period range. | | **Time zone.** Vendor uses account time zone; Vortex IQ aligns to merchant reporting time zone. | Marginal | Confirm time zone match. | | **Filter scope.** Profile-level filters (channel, B2B, test orders) may narrow the Vortex IQ view. | Variable | Match filter settings. | **Cross-connector reconciliation:** complement with sibling cards in the same category for the full diagnostic picture. For divergence investigations, use Vortex Mind. ## Known limitations / merchant FAQs **Q: How often does Spend Anomaly update?** The card refreshes on the standard data refresh (typically every 30-60 minutes for live integrations). For real-time signals, force a manual refresh from the dashboard. **Q: Why does my The Trade Desk dashboard show a different number?** The most common reasons are period-boundary differences (Vortex IQ uses 30-day rolling vs vendor's calendar months), time-zone alignment, and filter scope (profile-level vs vendor's all-account view). Match these settings before assuming a real divergence. **Q: How does Spend Anomaly relate to other alerts & anomalies metrics?** Track this card alongside the siblings listed above to build a complete picture. Single-metric reads can mislead; the diagnostic value is in the cross-reference. **Q: Can I customise the alert threshold?** Yes, alert thresholds are configurable per profile in the Alert Rules tab. Adjust to match your business baseline rather than relying on the generic default. *** ### Tracked live in Vortex IQ Nerve Centre *Spend Anomaly* is one of hundreds of KPI pulses Vortex IQ tracks across The Trade Desk and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English. [Start for free](https://app.vortexiq.ai/login) or [book a demo](https://www.vortexiq.ai/contact-us) to see this metric running on your own data.