This detection was added in Anti-Beacon 6.7.
Anti-Beacon treats this as telemetry because Avo Inspector is used for event collection and event-data validation. Tealium’s Avo Inspector connector documentation describes the connector action as “Send Event Data” (Tealium Docs: Avo Inspector Connector). Avo’s own security page says Avo “only collects the shape and type of data, not values” and uses that metadata to validate and monitor event-data quality (Avo Security).
Anti-Beacon blocks Avo tracking endpoints. Avo states that its Inspector data is metadata about event shape and types, not event values, but it is still telemetry because it collects event-related data from software integrations.