📈Destination Monitoring

Destination Monitoring enables users to verify destination setup correctness and monitor integrations for event delivery issues or misconfigurations. This capability provides real-time visibility into integration health, helping your team quickly identify and resolve problems to maintain reliable data flow across your marketing and analytics tech stack.

With Destination Monitoring you can:

• Validate your destinations are set up correctly

• Monitor to catch event transmission failures

You'll see destination monitoring metrics at the top of every Destinations section. Use the side nav on the left to filter for destination type. You can use the date picker at the top to choose the time range for the metrics.

For each destination type, you'll see the status of the configured destination instance and total amount of delivered and failed events for each destination for the same time period that was chosen on the date picker above. If you'd like to investigate further, or edit the configuration of the destination, click "Details" next to the desired destination.

Going to the individual configured destination instance page allows you to edit any details associated with the configuration, including disable the destination. You can investigate delivery failures in by going to Event Verification to look at the verification logs. Connected event instance metrics will show for the desired destination for the time period chosen on the date picker. If you'd like to view the configuration details of a specific event, click the "Details" button on the right hand side next to each event.

What do the event statuses mean?

• Delivered: The event was successfully received by the intended destination's server, which confirmed successful delivery with a status 200 response

• Dropped: The event payload was inspected by Freshpaint and not sent to the destination. A certain volume here is expected and can include reasons such as a lack of a click id. In this example, not every instance of the event is expected to have a click id, and therefore there will be an expected number of dropped events.

• Failed: This event was sent by Freshpaint to the destination's server, but was rejected from the destination. In order to investigate event failures further, you can use our Event Verification tool or reach out to [e-mail]