🚨 Alerts#

Alerts continuously watch whether everything Bidding Fox needs to run is working in your project: feed download, rule application in Mergado, active strategies, connections to data sources and credit on price-comparison sites. When something goes wrong, you find out before the problem shows up in your advertising performance.

General settings#

At the top of the Overview tab you decide where alerts should go:

  • Email for sending alerts: the address (yours, a colleague’s or a contact at the online store) that receives alerts on the Email channel.

  • Webhook URL: the address Bidding Fox sends alerts to if you want to process them in another system.

  • Also send a message when the problem is resolved: when turned on, you receive an alert at the moment a detected problem is fixed.

You save changes with the Save button.

Alerts overview#

The table contains all checks. For each one you see its status, name and a description of what the check verifies. If a check finds something, the specific finding is shown in red below the description.

The status can be:

  • OK: the check ran and found nothing,

  • Problem: the check found an error and you see the finding right in the row,

  • Skipped: the check could not be evaluated for a technical reason, for example the status of a connection cannot be verified,

  • Hidden: the alert is not shown in the app because you cleared the In app channel for it.

The checks include:

  • Mergado: XML feed download, rule application, products in the Bidding Fox rule and the synchronization interval with Mergado,

  • Strategies: the project has at least one active strategy,

  • Zboží.cz: connection to Zboží.cz, credit and downloading of data from reports and about competition,

  • Heureka: connection to Heureka including the API for conversion measurement, credit, conversion data, assortment report and competition data,

  • Google Analytics 4: connection to GA4 and data download,

  • CPC element in Mergado: it exists and is visible (MAX_CPC for Zboží.cz, HEUREKA_CPC for Heureka).

The credit checks verify that credit on the price-comparison site has not run out.

Channels and muting#

For each check you select by ticking where an alert about a problem should appear:

  • Email,

  • Mergado,

  • In app,

  • Webhook.

If the Email or Webhook channel needs an address in the general settings and it is missing, a red triangle next to the channel name points it out.

You mute an alert by clearing all its channels. The check is still evaluated, but no alert is sent. You cannot turn off the check itself.

How often it checks and alerts#

Checks are evaluated every hour. If a detected problem persists, the alert repeats at most once a week until you fix it. You cannot change the check interval or the alert interval.

History#

The History tab contains all detected alerts. You can see when and for which check a problem occurred and return to it later.

FAQ#

  1. How do alerts differ from Diagnostics? Alerts watch the technical state of the project (connections, feed, rules, credit). Diagnostics track problems in products and their performance.

  2. What does the “Skipped” status mean? The check could not be evaluated for a technical reason, for example the status of a connection cannot be verified.

  3. Where do I find older alerts? On the History tab, or on the Events page if you have the “In app” channel turned on.

  4. Do I need to set up alerts separately for each project? Yes, the settings are at the project level.

  5. How do I mute an alert? Clear all channels for the given check.

  6. How often is an alert about an unresolved problem repeated? Once a week.

Backward 🔔 Events ⚙️ Settings Forward