Webhooks Configured, Adyen

Webhooks Configured for Adyen. Tracked in the Vortex IQ Nerve Centre — how to read it, why it matters, and how to act on it.

Metrics type: Supporting Metrics • Category: Configuration & Health

Webhooks Configured as reported by the Adyen integration.

At a glance

Webhooks Configured is a configuration & health metric tracked from Adyen data. It surfaces operational signal so you can spot regressions, opportunities, and structural patterns. Cross-reference the sibling cards below for the full diagnostic picture.

What it counts	Webhooks Configured as reported by the Adyen integration.
Sample type	Backend API data from Adyen, refreshed on the standard data refresh.
Why it matters	The metric appears in the Configuration & Health 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 read direction. Cross-reference siblings to triangulate cause.
Format	number
Time window	RT
Alert trigger	0 (no event delivery)
Sentiment key	—
Roles	owner, finance

Calculation

Calculated automatically from your Adyen data on the standard refresh. See the At a glance summary for what it tracks and the worked example below for a typical reading.

Worked example

A representative reading of Webhooks Configured for a typical Adyen account. The card reports the current value alongside a comparison against the previous period — direction matters. When it moves outside the expected range, cross-reference the siblings below to find the cause; use Vortex Mind to trace upstream causes and Ask Viq for natural-language exploration.

Sibling cards merchants should reference together

Card	Why merchants reach for it
ad_active_payment_methods	Configuration & Health sibling: Active Payment Methods.
ad_stores_count	Configuration & Health sibling: Stores / Accounts.

Reconciling against the vendor’s own dashboard

Where to look in Adyen’s own dashboard: find this metric (or its components) under the relevant report/section. Confirm the period boundaries and any filters match the Vortex IQ profile to reconcile cleanly. The Vortex IQ value may legitimately differ due to period definition, time zone, sampling, or how the vendor buckets the underlying records.