At a glance
CPC Spike Detection is a budget monitoring metric tracked from Amazon Ads data. It surfaces operational signal at the budget monitoring layer so merchants can spot regressions, opportunities, and structural patterns in their store performance. The card pairs with sibling metrics in the Budget Monitoring category to build a complete diagnostic picture; cross-reference the related cards listed below for context.
| What it counts | CPC Spike Detection as exposed by the Amazon Ads integration. The metric is computed from the latest available data and refreshed on the standard data refresh. |
| Sample type | Backend API data from Amazon Ads, refreshed on the standard data refresh. |
| Why it matters | The metric appears in the Budget Monitoring 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 | ama_cpc_spike |
| Roles | owner, marketing |
Calculation
Calculated automatically from your Amazon Ads 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 CPC Spike Detection for a typical merchant on Amazon Ads. 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 |
|---|---|
ama_budget_utilisation | Budget Monitoring sibling: Budget Utilisation. |
ama_overspending | Budget Monitoring sibling: Overspending Campaigns. |
ama_spend_by_campaign | Budget Monitoring sibling: Spend by Campaign. |
ama_spend_trend | Budget Monitoring sibling: Spend Over Time. |
ama_acos | Executive Overview sibling: ACOS. |
Reconciling against the vendor’s own dashboard
Where to look in Amazon Ads’s own dashboard: The Amazon Ads 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. |