> For the complete documentation index, see [llms.txt](https://addressable.gitbook.io/knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://addressable.gitbook.io/knowledge-base/integrations/data-sources-and-integrations/engagement-data-tracking.md).

# Engagement Data Tracking

This document outlines the different methods we utilize to collect, process, and store website and application engagement data.

{% hint style="info" %}
While we support a range of ingestion methods, we strongly recommend you install the Addressable pixel or Server to Server API for both efficiency and ease of integration.
{% endhint %}

## **Website Tracking Methods**

### Installing the Addressable pixel

The Addressable pixel allows you to track Web 2 activity, such as page views, signups, wallet connect events etc. and to associate these with blockchain actions such as conversions. Simply put, it enables a full Web2 **›** Web3 user funnel view, to better understand the impact of your marketing efforts.<br>

* [Addressable pixel installation via Google Tag Manager ](/knowledge-base/event-tracking/addressable-pixel.md#addressable-pixel-gtm)\
  Ideal when you are already using GTM and have limited development resources
* [Addressable pixel installation using a website code](/knowledge-base/event-tracking/addressable-pixel.md#addressable-pixel-website-code) \
  Ideal when you prefer to manage and report your first party data directly

### Installing the Ad Network Pixel or API

When you have an Ad network pixel or API installed (either Twitter (X) or Reddit) that report events back to the Ad network, Addressable will collect these events when they are attributed (by the network) to an Addressable campaign.\
Once collected, you will be able to leverage them within the Addressable platform.

Keep in mind, that while such events can be leveraged for targeting and optimization purposes using the Addressable platform, unlike the Addressable pixel they cannot be used to provide a full attribution funnel since they are only received for campaigns you launch on the network using Addressable.

***

## Mobile Application Tracking Methods

### Integrating your MMP&#x20;

If you are using one of our supported Mobile Measurement Partners, you can share with Addressable your installs as well as significant in-app events to build a full Web2-App-Web3 funnel view & maximize Addressable's targeting and optimization capabilities.<br>

* [AppsFlyer Integration](/knowledge-base/integrations/appsflyer-integration.md)
* Singular Integration (ask your Customer Success Manager)

### Installing the Ad Network mobile tracking

When you have an Ad network mobile conversion tracking installed (either Twitter (X) or Reddit) and report events back to the network, Addressable will collect these events when they are attributed (by the network) to an Addressable campaign. \
Once collected, you will be able to leverage them within the Addressable platform.

\
Keep in mind, that while such events can be leveraged for targeting and optimization purposes using the Addressable platform, unlike the Addressable pixel they cannot be used to provide a full attribution funnel since they are only received for campaigns you launch on the network using Addressable.

***

## Server to Server Tracking Methods

### Implementing Addressable's Events API (Server to Server)

Addressable’s Conversions API is a secure server-to-server solution that enable you to share your user engagement and conversion event data with the Addressable platform when you cannot implement a website code, and when your user funnel is fragmented across multiple platforms.

* [Addressable Event Tracking (Server-to-Server) API](/knowledge-base/event-tracking/addressable-event-api/events-api-reference.md)\
  Use this when you have a complex customer journey that include user engagement across 3rd party platforms (e.g. Telegram/Discord chatbot, Mobile sandboxed WebApp, Telegram Game, Discord).

&#x20;


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://addressable.gitbook.io/knowledge-base/integrations/data-sources-and-integrations/engagement-data-tracking.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.