CDP Event Alerts

overview cdp event alerts allow your team to stay informed when specific customer behavior or data events occur in your chord connected ecosystem whether you’re monitoring for conversion milestones, failed transactions, or custom triggers unique to your brand, event alerts provide real time visibility into what matters most no support for client side destinations chord does not provide monitoring for events sent directly from the browser to external tools (e g , client side destinations), since these events do not pass through the cdp what it does chord cdp event alerts notify you via email when a configured event alert is captured by chord’s data infrastructure this ensures you can take timely action—or simply stay aware—when high impact behaviors are observed via chord cdp event alerts give you peace of mind by making sure your data is always moving where it needs to go the first set of alerts covers two key failure points if no source events are recorded for an hour, or if no events are delivered to a destination for an hour while the timeframe isn’t customizable, these alerts act as an early warning system—helping your team catch issues quickly so you can trust that your data is complete and reliable additionally, users will only receive one notification per site (source) or connection (destination) every 24 hours if an issue is detected for example user subscribes to notifications for missing data on source a (or destination a) source a (or destination a) doesn't receive any events for over an hour chord cdp will send an email notification to the user who set up an alert for source a (or destination a) chord cdp will send another notification in 24 hours (assuming source a or destination a continues not to receive any events) note you will not receive an email confirming that the issue has been resolved once you receive an alert and resolve it, you will not receive any additional alerts (unless the source or destination error perists or occurs again) lastly, this version of cdp alerts does not include monitoring for unexpected spikes or drops in source event volume; or delivery drops or delays for events sent successfully to destinations getting started requirements your sites (sources) and destination connections must be instrumented on chord cdp you must have appropriate permissions to access alert configurations to access and set event alerts, follow the instructions below log into the chord data platform and navigate to the chord cdp page click on the notifications tab on the chord cdp page review the list of available sites (sources) and connections (destinations) that you’d like to receive alerts about as you check (or uncheck) the alerts you would like to receive, you will see a success message saving your preferences when no source events are ingested for more than one hour and/or when no events are successfully delivered to a destination within one hour for your chosen alerts, you will receive an email from chord cdp denoting which site or connection is experiencing issues