Bot Detection Preventing Statistics Increment and Automation Execution

Bot Detection: Preventing Statistics Increment & Automation

Execution Keep your email engagement metrics honest. This feature identifies bot-driven opens and clicks and stops them from inflating stats or triggering automations — so your data reflects real people.

Adaptive AI Email & Adaptive AI Email Users Only

This feature is available only for sub-accounts using the Adaptive AI Email system or Adaptive AI Email. Other SMTP providers are not supported.

Table of Contents

Overview

To combat this, Adaptive AI introduced the Bot Detection – Preventing Statistics Increment and Automation Execution feature. It silently filters out non-human activity so your analytics and workflows stay trustworthy.

What Does This Feature Do? When a bot is detected opening or clicking an email, the following actions are taken automatically:

Preventing Statistics Increment

Email open and click counters will not increment for bot activity, ensuring engagement metrics reflect only genuine user interactions.

Preventing Automation Execution

Any automation events triggered by email opens or clicks will not execute when a bot is detected — maintaining the integrity of your workflows.

How to Enable / Disable Bot Detection Settings

By default, the Bot Detection Prevention feature is turned off. You'll need to enable it from your Business Profile settings.

Open Business Profile Settings

Navigate to Settings → Business Profile.

Locate the General Section

Scroll to the General section — this is where the Bot Detection Prevention toggles live.

Check or Uncheck the Settings

Check the box to enable, or uncheck to disable. Changes apply immediately to future sends.

Before you begin

“Bot Detection Preventing Statistics Increment and Automation Execution” is part of the Reporting → Reporting Dashboard area in Adaptive AI. Use the central reporting view and saved reporting settings. Automation changes can affect many records at once, so the safest approach is to define the intended entry condition, action, and stopping point before publishing anything. The objective is not merely to save a setting; it is to confirm the result works for the staff member or customer who will depend on it.

• Write down the exact trigger, filters, expected action, and condition that should stop or bypass the automation.
• Use an internal test contact with complete sample data, a valid communication channel, and consent appropriate to the test.
• Confirm that every connected account, custom field, pipeline, calendar, or template referenced by the automation still exists and is available.
• Record the current published status and settings so you can compare behavior or restore the earlier configuration if necessary.
• Choose a quiet test window when a controlled enrollment cannot interfere with active customer communication.

Verify the result

After completing the instructions in this guide, use a controlled test before treating the setup as finished. A saved screen or success message confirms configuration, but only an end-to-end test confirms the business outcome.

1. 1Save the configuration, review every branch from top to bottom, and publish only after required fields and warnings are resolved.
2. 2Run one controlled test using known inputs and note the exact time the test record entered the automation.
3. 3Open execution history and confirm that the record followed the expected branch in the correct order.
4. 4Verify the intended message, task, field update, or status change occurred once and contains the correct merged information.
5. 5Run a negative test that should not qualify; it should remain outside the automation without producing side effects.

Troubleshooting checklist

If the result differs from what you expected, preserve the current state and isolate one variable at a time. Start with the checks below before deleting the configuration or rebuilding it from scratch.

• Confirm the automation is published and that the trigger filters match the test record exactly, including capitalization and date conditions.
• Review re-entry settings to determine whether the same record is allowed to enter again or is being correctly excluded.
• Check the first failed or skipped step in execution history instead of changing several steps at the same time.
• Verify wait steps, account time zone, business-hour windows, and scheduled-send rules when an action appears delayed.
• Reconnect or reauthorize any external service that reports an expired credential, missing scope, or unavailable resource.

Best practices

• Use names that state the audience, trigger, and outcome so another administrator can understand the automation without opening it.
• Keep entry filters narrow and add explicit stop conditions to prevent duplicate messages, tasks, or opportunity changes.
• Respect contact consent, do-not-disturb status, quiet hours, and channel-specific opt-out requirements in every communication path.
• Change one behavior at a time, test it, and document the result before expanding the automation to more records.
• Review execution errors and unexpected enrollments after launch, then again after any connected integration or template changes.