BlogCase StudiesLogin

Addressable Pixel

In this guide, you'll learn how to set up the Addressable Pixel and custom events using the Google Tag Manager or JavaScript snippet.

The Addressable Pixel lets you track key actions on your website—like page views, signups, and wallet connections—and connect them to blockchain activity such as on-chain conversions. This helps you understand how users move from Web2 interactions to Web3 outcomes, giving you a clear view of your full marketing funnel.

Getting Started

Enabled By The Pixel

By setting up the Addressable Pixel and Custom Events, the following features become available depending your plan:

  • User Radar — Understand your users, enriched with Web2 attribution and Web3 on-chain activities.

  • Marketing Report – Understand the effectiveness of all your marketing efforts, even if it's not through Addressable.

  • Funnel Report – Understand how your users move through your conversion funnel (on and off-chain).

  • Campaign Manager – Understand visitor behavior, calculate ROAS, and attribute conversions to your Paid Campaigns.

Configuration Options

There are two primary ways to configure your Pixel

  • Google Tag Manager (GTM) – A quick and easy install method (Recommended) — Jump to Section

  • JavaScript Snippet (JS) – For adding the pixel directly to your website — Jump to Section

Using Google Tag Manager (GTM)

When to Use This Method

Use this option if any of the following are true (and is recommended):

  • You're already using Google Tag Manager

  • Your team has limited development resources

  • You want a fast and non-technical installation

GTM: Set Up Pixel

The Addressable Pixel is available as an official GTM Community Template called the Addressable Pixel. Once installed, you can configure tags and triggers to report events back to your Addressable account.

First, add the Addressable Pixel to GTM

Add the template for Addressable Pixel to your GTM workspace so it’s available during tag setup.

If you don't have Google Tag Manager set up yet, please refer to Google's docs before continuing.

To add the template:

  1. In GTM, go to Workspace > Templates

  2. Click Search Gallery

  3. Search for Addressable Pixel (or click here)

  4. Click Add to Workspace

This template fires the Addressable Pixel for each event you configure.

Then configure the Base Pixel in GTM

To send events to Addressable, you'll need to a Page View event with the following:

  • A Tag – defines what event you’re sending

  • A Trigger – defines when the tag should fire

Even if you already track these events for other platforms — such as Google Analytics, MixPanel, X, etc. — you’ll need to reconfigure them using the Addressable Tag.

Finally, Configure a Custom Tag (GTM)

  1. Go to Tags > New, and name it "Addressable - Page View".

  2. Click Tag Configuration and select Addressable Pixel from the "Custom" section.

  3. Enter your Pixel ID — which can be found in Addressable by selecting Data Sources then Addressable Pixel then click on Connect.

  4. Under Event Name, be sure "Pageview" is selected from the standard dropdown.

  5. Scroll down and click Triggering and select All Pages from "Chose a trigger".

  6. Click Save.

  7. Click Submit and then Publish.

GTM: Set Up Custom Events

After setting up the Addressable Pixel, we recommend setting up custom events to better understand how users interact with your website or dapp.

Custom events enable more in your Addressable dashboard by helping you measure meaningful user actions, identify drop-off points, and track conversions more precisely across your funnel.

You should define at least one custom event as a conversion event to get deeper insight into how users progress through key steps like signing up, booking a demo, or completing a purchase.

Step by Step

  1. Go to Tags > New, and give your tag a descriptive name — such as "Addressable - Signing Up".

  2. Click Tag Configuration and select Addressable Pixel from the "Custom" section.

  3. Enter your Pixel ID — which can be found in Addressable by selecting Data Sources then Addressable Pixel then click on Connect.

  4. Under Event Name, select Custom.

  5. Name your custom event — such as "Signing Up", "Booking a Demo", or "Completing a Purchase"

    Important: This will be the name that you will see in the Addressable Dashboard

  6. If the event is a conversion, check the corresponding box.

    What is an conversion event? Any meaningful action that represents progress in your funnel—such as completing a signup, starting a checkout, making a purchase, or submitting a lead form. These events are often used to measure the success of your campaigns or optimize ad targeting.

  7. Optionally, add Properties for added context [Advanced]

    1. Below the event type and name, you’ll see an Object Properties section.

    2. Click Add Row to define each property:

      1. Property Name → Use a clear name, such as "Amount" or "Transaction ID"

      2. Property Value → Select a dynamic variable defined in GTM using the brick icon.

    3. For more information on GTM's properties, see Google's docs.

  8. Click Save

  9. Click Submit and then Publish

Reminder: You do not need to manually configure a 'Wallet Connect' event — these events are tracked automatically when the pixel is installed across all pages.

Validate GTM Configuration

For proper funnel configuration, please configure at least two events:

  1. Standard Page View event.

  2. At least one Custom Event with Conversion checked.

You can validate events are coming in through our dashboard, by selecting Data Sources then Addressable Pixel then click on View Events then click Raw Events.

GTM: Revenue Reporting Configuration

New in June 2025, the revenue reporting feature gives you a clear view of campaign ROAS. This unlocks powerful insights into customer value, ROI, and user segmentation. Whether you’re tracking sales, subscriptions, or on-chain payments, revenue reporting helps you connect marketing performance to real business outcomes.

Proper revenue configuration depends on the type of conversion you aim to measure as a revenue event. Below are the transaction types currently supported for revenue reporting along with their required Object Properties:

Transaction type
Example uses
Required Object Properties

USD

  • Payments

  • Trading

  • Transaction unique identifier

  • Transaction amount

Token

  • Stablecoin payments

  • DeFi interactions

  • Transaction unique identifier

  • Transaction amount

  • Network (chain) ID

  • Token contract address

Native Token

  • Value transfer between wallets

  • Staking

  • Transaction unique identifier

  • Transaction amount

  • Network (chain) ID

Foreign Currency Exchange

Converting EUR to USD

  • Transaction unique identifier

  • Transaction amount

  • Exchange rate (USD) at time of transaction

A revenue event is structured nearly identical to any other custom event. So regardless of the transaction type, all revenue events will need to follow the steps for setting up custom events.

Where revenue events are different is that they require two additional configurations

  1. Checking the corresponding box confirming that the event is a conversion

  2. Adding the required Object Properties listed above for the desired transaction type

To add each Object Properties

  • Below the event type and name, you’ll see an Object Properties section.

  • Click Add Row to define each property:

    1. Property Name → Use a clear name, such as "Amount" or "Unique ID".

    2. Property Value → Select a dynamic variable defined in GTM using the brick icon.

  • For more information on GTM's properties, see Google's docs.

Please contact your Customer Service representative to ensure your revenue events are properly configured.

Using Javascript Snippets (JS)

When to Use This Method

Use this option if any of the following are true:

  • You’re not using Google Tag Manager

  • You already have other tracking code set up in your codebase

  • You want full control over how and where the pixel is deployed

JS: Set Up Pixel

You can install the Addressable Pixel directly on your website to track key user activity and report it to your Addressable dashboard.

Step by Step

  1. Copy the JavaScript snippet below.

  2. Paste the script inside the <head> tag on every page where you want the pixel to run.

  3. Replace <<replace this text with your pixel id>> with your actual Pixel ID (sometimes called your tenant ID).

NOTE: Your ID can be found in Addressable under Data Sources > Addressable Pixel.

JavaScript Snippet

<!-- Addressable Pixel base code -->
<script>
!function(w, d){
    w.__adrsbl = {
        queue: [],
        run: function(){
            this.queue.push(arguments);
        }
    };
    var s = d.createElement('script');
    s.async = true;
    s.src = 'https://tag.adrsbl.io/p.js?tid=<<replace this text with your pixel id>>';
    var b = d.getElementsByTagName('script')[0];
    b.parentNode.insertBefore(s, b);
}(window, document);
</script>
<!-- End Addressable Pixel base code -->

Once installed, the pixel will automatically trigger a Page View event on each page load — There's no need to track them manually.

JS: Set Up Custom Events

After setting up the Addressable Pixel, we recommend setting up custom events to track meaningful user actions in your website or dapp.

Custom events enable more in your Addressable dashboard by helping you measure meaningful user actions, identify drop-off points, and track conversions more precisely across your funnel.

You should define multiple custom events as conversion events to get deeper insight into how users progress through key steps like signing up, booking a demo, or completing a purchase.

Code Syntax

window.__adrsbl.run(event_name, is_conversion, properties)

  • event_name – (string) A clear name of the event

  • is_conversion – (boolean) Set to true if the event is a conversion; otherwise false

  • properties – (optional array of objects) Additional details about the event

Extra Details

  • Event Name: This is a clear name of the event that will be displayed in the Addressable Dashboard — for example "signup" or "download_app" .

  • Conversion Events: A conversion event is any meaningful action that represents progress in your funnel—such as completing a signup, starting a checkout, making a purchase.

  • Optional Properties: Each property is defined as an object with the keys of name and value. You can define up to 6 properties per event.

Note: You do not need to manually configure a 'wallet connect' event — these events are tracked automatically when the pixel is installed across all pages.

Code Examples

This sends a purchase event, marks it as a conversion, and includes two properties:

window.__adrsbl.run('purchase', true, [
    { "name": "transaction", "value": "VAC123D432" },
    { "name": "amount", "value": 50 }
]);

This sends a downloaded app event that is not a conversion, and one property without a value:

window.__adrsbl.run('downloaded app', false, [
  { "name": "navigation bar" }
]);

This sends a primary click event, marks it as a conversion, and did not include any properties:

window.__adrsbl.run('primary click', true, '');

Validate Configuration

For proper funnel configuration, please configure at least two events:

  1. Standard Page View event.

  2. At least one Custom Event with is_conversion set to true.

You can validate events are coming in through our dashboard, by selecting Data Sources then Addressable Pixel then click on View Events then click Raw Events.

JS: Revenue Reporting Configuration

New in June 2025, the revenue reporting feature gives you a clear view of campaign ROAS. This unlocks powerful insights into customer value, ROI, and user segmentation. Whether you’re tracking sales, subscriptions, or on-chain payments, revenue reporting helps you connect marketing performance to real business outcomes.

Proper revenue configuration depends on the type of conversion you aim to measure as a revenue event. Below are the transaction types currently supported for revenue reporting along with their required conversion properties and code example:

Transaction type
Example uses
Required properties
Code example

USD

  • Payments

  • Trading

  • Transaction unique identifier

  • Transaction amount

window.__adrsbl.run('purchase', true, [ { "name": "transaction_id", "value": "VAC123D432" }, { "name": "transaction_amount", "value": 50 } ]);

Token

  • Stablecoin payments

  • DeFi interactions

  • Transaction unique identifier

  • Transaction amount

  • Network (chain) ID

  • Token contract address

window.__adrsbl.run('payment', true, [ { "name": "transaction_id", "value": "VAC123D432" }, { "name": "transaction_amount", "value": 100 }, {"name": "network_id", "value": "8453" }, {"name": "token_address": "0x00..." } ]);

Native Token

  • Value transfer between wallets

  • Staking

  • Transaction unique identifier

  • Transaction amount

  • Network (chain) ID

window.__adrsbl.run('transfer', true, [ { "name": "transaction_id", "value": "VAC123D432" }, { "name": "transaction_amount", "value": 150 }, {"name": "network_id", "value": "8453" } ]);

Foreign Currency Exchange

Converting EUR to USD

  • Transaction unique identifier

  • Transaction amount

  • Exchange rate (USD) at time of transaction

window.__adrsbl.run('exchange', true, [ { "name": "transaction_id", "value": "VAC123D432" }, { "name": "transaction_amount", "value": 150 }, {"name": "exchange_rate", "value": "0.870132" } ]);

Please contact your Customer Service representative to ensure your revenue events are properly configured.

Content Security Policy (CSP)

If your website uses a Content Security Policy (CSP), you’ll need to allow Addressable’s scripts and images to load properly.

When Is This Needed

Use this if:

  • You have CSP headers configured on your site

  • You see blocked requests in the browser console related to adrsbl.io or adform.net

Required CSP Directives

To support Addressable and Adform tracking, update your CSP to include the following domains:

For scripts:

script-src
  https://*.adrsbl.io
  https://*.adform.net;
  
script-src-elem
  https://*.adrsbl.io
  https://*.adform.net;

For images:

img-src
  https://*.adrsbl.io
  https://*.adform.net;

These rules ensure the Addressable Pixel and Adform integrations function correctly without CSP-related errors.

If your policy uses a default-src directive with 'none', make sure to explicitly allow these sources in the appropriate directives above.

Last updated

Was this helpful?