Addressable Pixel
Last updated
Last updated
Addressable’s pixel allows you to track Web2 activity, such as page views, signups, wallet connect events and associate them with blockchain activities, conversions and other on-chain behaviors. Simply put, it enables a full Web2 › Web3 user funnel view, to better understand the impact of your marketing efforts.
There are two installation methods:
Select this method when: you are already using GTM and/or are limited in development resources. This implementation will have you up and running quickly.
To simplify the implementation process, we integrated with the Google Tag Manager Platform. Our pixel is published as an official template of the GTM community called Addressable Tag. You can install our tag and configure events to report back on to your Addressable account.
If you already have GTM in place, you will find that the implementation steps below do not require technical know-how. With that said, the Addressable CS team will gladly assist you in navigating the process.
Add the Addressable template to your gallery. The Addressable template triggers our pixel for each configured event. In order to have the template available during the configuration process, you will first need to add it to your template gallery. Go to: Tag manager › Workspace › Templates › Search gallery › Tag template › Addressable template
Configure tags & triggers. For each event you want to report back to Addressable, you will need to configure a tag (the event you want to track) and a trigger (the condition in which this event is to be 'fired'). You may have these already in place for your GA or other 3rd party solutions. However, to report these to Addressable, you must re-configure them using the Addressable template.
To configure a tag:
Enter the Tag tab › New › Name the tag.
Click on Tag configuration › select Addressable under your custom template (or search for it in the community gallery if you have yet to add Addressable to your workspace). Once the Addressable pixel is selected - this will produce the ‘schema’ in which you will report events back to Addressable.
Plug your pixel id - This is the same as your tenant ID, which can be found in your Addressable account settings.
Specify the event type. Select a standard (out of the box) event such as page views, purchase, or lead. If it's a conversion event, make sure to tick the appropriate box. Note: there is no need to configure a 'wallet connect' event. These are captured automatically when you implement the Addressable pixel across all pages.
To configure the trigger:
Enter the Trigger tab › New OR click on ‘Triggering’ to select a pre existing trigger.
When creating a new trigger, select the trigger type (e.g. page view, click, engagement) and set the firing conditions. For example, set the trigger on 'click' for any button/element with a ‘Download App’ text.
In order to make sure Addressable properly reports on your user funnel, make sure to configure page view & conversion events.
As a recommended step post installing your pixel, define custom events. Custom events are events that you would like to measure, to understand deeper what your users are doing on your website or app, where they are dropping off or converts. You can also define multiple conversion events as custom events to have better visibility into your funnel.
To configure a custom event:
Enter the Tag tab › New › Name the tag.
Click on Tag configuration › select Addressable under your custom template (or search for it in the community gallery if you have yet to add Addressable to your workspace). Once the Addressable pixel is selected - this will produce the ‘schema’ in which you will report events back to Addressable.
Plug your pixel id - This is the same as your tenant ID, which can be found in your Addressable account settings.
Specify the event type: Select "custom"
Select a name for your event (e.g book a demo, download app). If it's a conversion event, make sure to tick the appropriate box. Note: there is no need to configure a 'wallet connect' event. These are captured automatically when you implement the Addressable pixel across all pages.
Add properties to your event as needed. See instructions here