Tracking ObservabilityConnect Inspector to Adobe Tag Extension

Avo Inspector Adobe Tag Extension

Overview

The Avo Inspector Adobe Tags Extension allows you to monitor and validate your Adobe Client Data Layer by sending only data schemas (no personal data) to Avo Inspector. This helps ensure data consistency and catch schema violations in real time.

💡

Currently, we only support Web tag extensions for Adobe.

Features

  • Watches the Adobe/Google Data Layer for changes
  • Filters events and properties based on configured prefixes
  • Automatically extracts & sends schema structures to Avo Inspector
  • Ensures tracking consistency without exposing user data

Prerequisites

Get API key

Installation

  1. Go to Adobe Experience Platform Tags.
  2. Navigate to the Extensions catalog.
  3. Search for “Avo Inspector”.
  4. Click Install and follow the setup instructions.

Extension Configuration

These settings apply to the Avo Inspector extension globally across your Tag property.

SettingDescription
API KeyYour Avo Inspector API Key for authentication.
EnvironmentDefines the environment (dev, staging, prod).
App VersionThe application version being tracked. (defaults to 1.0.0)

Install extension

Rule-Specific Configuration

These settings apply to individual rules where the extension is used.

SettingDescription
Event Name PrefixesFilters out events that start with specific prefixes.
Property PrefixesFilters out properties that start with specific prefixes. (only works for top level properties)

Setting Up a Rule in Adobe Tags

Create new rule

Step 1: Configure the Event

  • Go to Rules → Create a new rule.
  • Click Add Event → Select Adobe Client data layer extension or Google data layer extension.
  • Under eventType select Data Pushed
  • In the settings, select
    • Listen to: All Events
    • Time Scope: Future
  • Click Save

Configure event

Step 2: Configure the Action

  • Add an Action → Select Avo Inspector extension
  • Choose on Adobe DataLayer Push as the action type.
  • Configure the Rule-Specific Configuration (Event Name Prefixes & Property Prefixes).

Configure Action

Step 3: Save and Publish

  • Click Save Rule.
  • Publish your changes in Adobe Tags.
  • Once live, the extension will start tracking schemas automatically.

How It Works

Event & Property Filtering

  • The extension listens for changes in the Adobe Client Data Layer.
  • Events and properties are filtered based on prefix rules (configured in settings).
  • Unwanted prefixes are ignored, while only schema structures are processed.

Sending Schemas to Avo Inspector

  • Once an event passes the filter, the extension extracts its schema and sends it to Avo Inspector.
  • The schema is structured according to Avo’s schema validation.
  • This helps identify tracking inconsistencies in real time.

When events are being sent successfully, Avo Inspector events view will start to receive your events, whether you have them in the Avo Tracking plan or not. If you receive events that are not defined in your tracking plan, the Inspector will offer you to add them to the tracking plan with a single click.

Inspector Events

Troubleshooting

No Schemas Being Sent?

  • Check if the Adobe Data Layer has events in the browser console.
  • Ensure event prefixes are not blocking schema extraction.
  • If the Avo inspector tag Extension is set to dev environment, the extension will be logging to the console to help you debug.
💡

The Extension will do no logging if the environment is set to prod.

Getting Errors in Avo Inspector?

  • Validate the schema in Avo Inspector.
  • Check the API key and environment settings.
  • Look at network requests (F12 → Network) to see what’s being sent.

Support

For any questions, reach out to Avo Support or check our documentation.

Next Steps