How to avoid performance blind spots

Adalysis ships with sensible defaults. But "sensible" doesn’t mean one-size-fits-all. We'd recommend using the performance monitor templates for a fast setup, but customizing them for your accounts. Here are some examples:

Small account — minimums too high Example: At least 20 conversions/week Result: If the account average is lower, the minimum is rarely met and the alert never fires.

Large account — default change thresholds too high Example: 25% increase in spend Result: Smaller shifts aren’t flagged, even though they’re relevant.

Four decisions to get right

1

Choose the right campaigns

Brand vs. non-brand, top-funnel vs. bottom-funnel — set monitors where a change would require action. Using labels means new campaigns are always included.

2

Decide on your key metrics

What actually matters for this account — conversions, revenue, ROAS, CPA?

3

Set a relevant % change and time frame

For example: 10% over 7 days, or 25% over 14 days.

4

Set minimum thresholds

If the account gets 20 conversions/month, a threshold of 10 over 7 days is too high. Consider the account size and data volume.

The cascading drop trend

Here's a scenario that often catches people off guard. The performance monitor looks for a 10% drop over 7 days. Each week’s data is under the threshold, but the cumulative drop is a problem.

The fix: Duplicate your alert and set a second version for the 30-day window. You’ll catch both sudden drops and slow bleeds.

Agree with your team on who should receive notifications and act on them. This helps avoid unneeded messages while ensuring control and speed of response.