Events, Postbacks & Pixels

Events

An “Event” is an action a user completes (for example, making a purchase, downloading and opening a mobile app, or filling out a survey). Once your advertiser records the action, it needs to fire the Pixel you have implemented on the advertiser’s end in order for the event to be tracked within your FOCUUS account.

 For more information about your Pixel, read “Generating Traffic Source Postback / Advertiser Pixel for implementation.

Transaction ID / {tid}

Every time a user clicks on a FOCUUS URL, he receives a Unique Click ID (which will be placed in the {tid} macro/token) which continues along with the user from this point forward. Using this ID enables connecting the user to any data received from the user’s further actions.

The {tid} Parameter is mandatory for event tracking. This value, generated by FOCUUS, is the value an advertiser will pass back inside the Pixel you have implemented.

Pixel / Postbacks

Generating Advertiser’s Pixel For Implementation

Click on your user setting menu, choose an “Event”, and then click on “Get Pixel” for the requested event. Please note that events are global, meaning you can use the same Pixel for a few campaigns/destination. For example, different app developers’ campaigns may use the same “CPI” Pixel to track an app installation and opening.





The URL generated is designated for implementation on your advertiser’s side, and will fire back to FOCUUS along with the {tid} unique value once an action occurs.



IMPORTANT!

Your advertiser must store the {tid} initially passed to it for each click, and must include this value inside the Pixel once it is fired.  Read more about this under “Managing your campaigns”.

 Example:

Pixel as implemented on advertiser’s side:

http://pixel.focuusing.com/event.php?type=conversion&tid={advtid}&eid=49796

Direct Link as implemented under the advertiser’s campaign (FOCUUS’ platform):  

http://coolgameapp.com/blue/focuus?advtid={tid}&advsid={sid

Multiple Event Tracking


FOCUUS allows tracking and analysis of multiple events (unlimited in number).  

When multiple events can be attributed on the advertiser’s side, you can fully integrate the group of events on FOCUUS side. You need to send the advertiser one Pixel per event.

 Example:

CPI Pixel (whenever a user installs and opens an app):

http://pixel.focuusing.com/event.php?type=cpi&tid={ADV_TRANSACTION_ID}&eid=1111  

Sale Pixel (whenever a user is buying on your site/app): 

http://pixel.focuusing.com/event.php?type=sale&tid={ADV_TRANSACTION_ID}&eid=2222

In the case where a user has completed more than one Event, FOCUUS will track and report all events for the user under the same {tid}. 




Feedback and Knowledge Base