Pixel validation Chrome extension

The Axon Pixel Helper is a Google Chrome extension that helps you debug and validate your Pixel installation. It allows you to see the events your site produces and to check that they are present.

You can find and install the Axon Pixel Helper here.

Usage

Axon recommends that you pin the extension to your search bar. After you install it, you can navigate around your site (including by clicking to a new page) and the extension will track all events sent to Axon.

The plugin will indicate each event with a status:

  • Green: Payload is structured correctly, and all required and recommended fields are present.
  • Orange: Payload is structured correctly, but is missing recommended fields.
  • Red: A required field is missing or the payload is improperly structured.

Axon Pixel Helper. Clear button. 3 Pixels. 12 Events. 4 green, 2 red, 2 orange. Pixel_name. Event Key. 6 Events. Most recent events table.

You can click an event to see which specific fields are missing.

Review a sample flow

Axon recommends that you review a sample flow that captures the events you configured your website to trigger. Verify that each event is sent correctly by using the Pixel Helper extension.

Example purchase flow (for purchase sites):

  1. Open the homepage.
  2. View an item, which triggers the view_item event.
  3. Add the item to the cart, which triggers the add_to_cart event.
  4. Start checkout, which triggers the begin_checkout event.
  5. Make a purchase, which triggers the purchase event.

Also, the page_view event should fire when you visit any page during the flow.

Example generate lead flow (for lead generation sites):

  1. Open the homepage.
  2. Complete the desired flow (for example, finish a quiz).
  3. Register with email or phone, which triggers the generate_lead event.

Also, the page_view event should fire when you visit any page during the flow.

Preserving Axon Click Tracking Parameters in Destination URL

Overview

When a user clicks an Axon ad, two tracking parameters - aleid and alart - are automatically appended to your destination URL. These parameters allow Axon to connect each page load and conversion back to the originating click. If they are dropped before your destination URL loads, Axon cannot attribute the resulting activity to your campaign.

Impact of Dropped Parameters

When aleid and alart are missing on page load, Axon is unable to:

  • Attribute conversions to the correct campaign or creative
  • Optimize bidding toward high-intent users
  • Measure accurate campaign performance

The most common symptoms are an extremely high bounce rate and near-zero downfunnel event conversions despite a normal click-through-rate (CTR).

Best Practices When Setting Up a Destination URL

Use a direct destination URL

Set your campaign's destination URL to a page that loads directly, without redirecting users to another URL. Users should land on the final destination page in a single step from the ad.

Avoid redirects whenever possible

Redirects are the most common cause of dropped tracking parameters. If a redirect is unavoidable, configure it to forward the original query string to the destination URL. Make sure every URL in the redirect chain has the Axon pixel installed correctly.

  • Correct: https://redirectFrom.com/landing?utm_source=axon&alart=456&aleid=123https://redirectTo.com/landing?utm_source=axon&alart=456&aleid=123
  • Incorrect: https://redirectFrom.com/landing?utm_source=axon&alart=456&aleid=123https://redirectTo.com/landing?utm_source=axon

Keep tracking parameters intact

Do not strip, rewrite, or modify the aleid and alart parameters anywhere in your site's URL handling logic.

Verify before launching

Always verify that the Axon pixel fires correctly and that aleid and alart remain in the destination URL before launching your campaign.

Was this article helpful?
search