Disconnecting AI Visibility Integrations

Important

  • Disconnecting an integration from the Microsoft Clarity dashboard only removes the Bot Activity dashboard within AI Visibility. It doesn't stop data from flowing into Clarity by itself.
  • To fully stop data from flowing into Clarity, uninstall or remove the integration at the server or CDN level, depending on the provider used.
  • Disconnecting removes AI Visibility data from the dashboard only after provider-side removal. Historical data already ingested by Clarity is unaffected, and each disconnection step directly reverses the documented integration setup.

Overview

Microsoft Clarity AI Visibility integrations for the Bot Activity dashboard work by forwarding request-level traffic logs from your platform or CDN to Clarity. These logs allow Clarity to identify automated traffic such as bots and AI crawlers and separate it from human user activity.

Disconnecting an integration reverses this log forwarding and stops future data ingestion once the provider-side configuration is removed.

This document describes how to disconnect Microsoft Clarity AI Visibility integrations and outlines the required steps to reverse the configuration for the following supported servers and CDNs:

WordPress

Installing the Microsoft Clarity WordPress plugin created and linked a Clarity project to the WordPress site, enabled Clarity data collection including AI Visibility data for the Bot Activity dashboard, and sent site interaction and request data directly from WordPress to Clarity.

The goal of disconnecting is to stop bot activity data from being forwarded to Clarity. Microsoft Clarity is actively working on adding more granular controls to allow disabling only the forwarding of Bot Activity data.

At this time, the only way to disable Bot Activity data collection in WordPress is to disable Clarity entirely by uninstalling the Microsoft Clarity WordPress plugin, which stops all Clarity data collection for the site.

Steps

  1. Sign in to the WordPress admin dashboard.
  2. Go to Plugins.
  3. Locate Microsoft Clarity.
  4. Select Deactivate.
  5. Select Delete to uninstall the plugin.

Important

Uninstalling the Microsoft Clarity WordPress plugin removes the Clarity project associated with this WordPress site. Reinstalling the plugin might require reconnecting your old Clarity project or connecting a new Clarity project.

Fastly

The Fastly integration created an HTTPS logging endpoint that forwarded request and response logs from Fastly edge servers to Clarity, including metadata used to identify bot and AI crawler traffic.

The goal of disconnecting is to stop Fastly from sending request logs used by the Bot Activity dashboard. Disconnection is performed by removing the HTTPS logging endpoint created for Clarity, which stops Fastly from sending request logs to Clarity.

Steps

  1. Sign in to the Fastly Console.
  2. Select the Fastly service used for Clarity.
  3. Open Service Configuration.
  4. Select Edit configuration and clone the active version.
  5. Go to Logging.
  6. Locate the HTTPS logging endpoint configured for Clarity.
  7. Delete the logging endpoint.
  8. Save the configuration.
  9. Activate the new service version.

Note

Activation is required because Fastly uses versioned configurations. Removing a logging endpoint creates a new inactive version. Saving and activating the new service version is required for the disconnection to take effect and stop log delivery.

Amazon CloudFront

The CloudFront integration created an Amazon Data Firehose delivery stream that forwarded CloudFront standard access logs to Clarity through an HTTP endpoint, including request, response, and performance fields used for bot detection.

The goal of disconnecting is to stop CloudFront access logs from being delivered to Clarity for the AI Visibility Bot Activity dashboard. Disconnection is performed by removing CloudFront logging and deleting the associated Firehose delivery stream, which stops CloudFront request logs from being forwarded to Clarity.

Steps

Disable CloudFront logging

  1. Sign in to the AWS Management Console.
  2. Go to CloudFront.
  3. Select the distribution used for Clarity.
  4. Open the Logging tab.
  5. Edit the logging configuration.
  6. Remove the Kinesis Data Firehose destination.
  7. Save changes.

Delete the Firehose delivery stream

  1. Go to Amazon Data Firehose.
  2. Select the delivery stream created for Clarity.
  3. Delete the delivery stream.

Optional cleanup

Delete the S3 bucket created for failed delivery logs if it is no longer needed.

Cloudflare

The Cloudflare integration created a LogPush job for HTTP request logs that sent request, response, geographic, and performance data to Clarity, enabling Clarity to classify bot and AI crawler traffic using Cloudflare signals.

The goal of disconnecting is to stop Cloudflare from pushing HTTP request logs to Clarity for the AI Visibility Bot Activity dashboard. Disconnection is performed by deleting the Cloudflare LogPush job created for Clarity, which stops Cloudflare from sending HTTP request logs to Clarity.

Steps

  1. Sign in to the Cloudflare Dashboard.
  2. Select the domain used for Clarity.
  3. Go to Analytics & Logs > LogPush.
  4. Locate the LogPush job created for Clarity.
  5. Delete the LogPush job.

Akamai

The Akamai integration created a log delivery configuration that forwarded HTTP request logs from Akamai edge servers to Microsoft Clarity through a secure HTTPS endpoint. These logs included metadata such as request paths, user agents, and response information used by Clarity AI Visibility to detect automated traffic, including bots and AI crawlers.

The goal of disconnecting is to stop Akamai from forwarding edge request logs used by the Bot Activity dashboard to Clarity.

Steps

  1. Sign in to Control Center.
  2. Select ≡ > Common Services > DataStream to open the DataStream dashboard.
  3. On the DataStream page, find the stream that you want to manage, select ... from the Action column. Select Deactivate to turn it off.

Azure Front Door (AFD)

The Azure Front Door integration enabled access and request logging and routed these logs to Clarity by using Azure Diagnostic Settings. This logging pipeline forwarded edge request telemetry, including URL paths, response codes, and user agent data, used by Clarity AI Visibility to distinguish automated traffic such as bots and AI crawlers from human user activity.

The goal of disconnecting is to stop Azure Front Door from sending access logs used by the Bot Activity dashboard to Clarity.

Steps

Disable Azure Front Door log forwarding

  1. Go to your Front Door profile in the Azure portal.
  2. Select Diagnostic settings under the Monitoring section.
  3. Find the setting named forward-to-eventhub, and select Edit setting.
  4. Select Delete.

Remove Clarity AI Visibility resources

  1. Remove the clarityaivisibility-env resource.
  2. Remove the clarityaivisibility-func resource.
  3. Remove the clarityaivisibility-ehns resource.
  4. Remove the clarityaivisibilitysa resource.

Visit Clarity

Case studies

Demo

Sign in

Blog

Benchmarks

  • Last updated on