View
 

Adding User Based Tracking Packet

User Based Tracking allows the association of user accounts from merchants websites with affiliates. It provides True Recurrence since it doesn't use cookies.

 

If a consumer arrives on the merchant’s website coming from an affiliate and creates a new account then that user can belong to the affiliate for a predefined period of time.

 


Implementation

 

Step 1 - Add User Based Tracking to your Campaign

The first step is to add the Packet in your Campaign. Go to the Campaign Settings page and find Thematic Packets. Click on add packet and find User Based Tracking. Add the packet and save the new settings.

 

Step 2 - Configuring User Based Tracking

In your campaign page a new green box will appear called User Based Tracking. Click on Integration and a new page will appear that guides you through the reminder of  the setup.

  

Step 2.1  - Integration in 'Account Confirmation' page

A code will be given which needs to be added in the Account Confirmation page. It will look like:

 

<iframe height='1' width='1' scrolling='no' marginheight='0' marginwidth='0' frameborder='0' src='http://event.2performant.com/events/client_tracker_check?confirm=02253688a&user_token=__ADD_UNIQUE_USER_TOKEN__'></iframe>

 

It must be added in your website in the page that marks the success of the account creation.

 

Replace __ADD_UNIQUE_USER_TOKEN__ with a unique and hard to guess value that identifies the user in your system (minimum 7 characters). For example the moment in which the user creates the account down to the nanosecond: 1240154340. We recommend a MD5 hash from "user_email_AND_SECRET_PASSPHRASE". Where SECRET PASSPHRASE is something only you know.

 

Alternatively, you can create a new field in the user DB table where you generate an unique token.

 

Step 2.2  - Modify 'Action Code'

The Action Code also suffers a modification, it has to send a new argument UNIQUE_USER_TOKEN from Step 2.1.

The new Action Codes are regenerated in your Campaign page. Make sure you send the same UNIQUE_USER_TOKEN from Step 2.1