Fuul's attribution methods

Fuul's main objective is to attribute events to the partners that bring the users.

Deterministic attribution

Deterministic attribution is Fuul's main attribution method. We create a unique identifier after a click and, receive the user's wallet address from projects when connecting them on the site.

After the transaction is made, we can attribute that event to the click. With a 100% accuracy rate, click-based wallet matching is the most reliable attribution method.

Fuul uses the following identifiers for deterministic attribution:

Fuul ID

Unique random IDs are created for every click.

After transactions, validators will match wallet addresses with IDs.

Wallet address

By using our SDK, projects report to Fuul the users' wallet addresses as soon as they connect them to their sites.

Then, we are able to match IDs to wallets and attribute events.

Probabilistic matching

Probabilistic matching is Fuul's secondary attribution method. We use browser information to attribute events to clicks with matching characteristics.

Fuul uses different parameters from the browser to create a fingerprint.

One fingerprint is generated and stored along with the click.

At the moment of transacting, another fingerprint is created on the project's website and sent along in the blockchain transaction.

Now when we find a fingerprint in a blockchain transaction, we will compare it with the fingerprints in our clicks database and attribute the event to publishers.

Attribution Examples

Follow these case examples to understand when each attribution type will be triggered.

Let's start by using the same browser and device.

Case	Deterministic	Probabilistic
Makes a Tx in the same session
Makes a Tx in another session
Connects wallet, does not transact, and erases local storage. In another session, makes a Tx with the connected wallet address
Connects wallet, does not transact, and erases local storage. In another session, makes a Tx with a never-connected wallet address
Does not connect wallet and erases local storage. In another session makes a Tx

Now let's look at what happens when using other browsers or devices.

Case	Deterministic	Probabilistic
Interacts with Fuul link and connects wallet in one browser/device, and then makes a Tx in another one with the same connected wallet address
Makes a Tx in another browser/device with a never-connected wallet address

For our v1 product, we are currently supporting deterministic attribution