Playerize Integration Guide - Facebook Games

How It Works

When we send a player to your game, we first record some basic information in our system, and assign them a cookie.  We then redirect them to you, using a URL something like this:

 

https://apps.facebook.com/yourgame/?source=playerize&subsource=123&transaction_id=10385284f49370de22be97868a1c44


We can use other field names if you require, but we're letting you know three things: 

  • source: that this traffic came from Playerize.  You likely have  a field that you use to separate traffic from ads or other sources.
  • subsource: a Playerize internal code that identifies our traffic source for this visitor, so that performance metrics can be done based on our sources if you are able, allowing us to optimize on those factors
  • transaction_id: a unique ID assigned by Playerize to this visitor.  

Once the player has accepted the Facebook permissions, we consider an install to have been completed, and you will include a pixel on the next canvas page to alert us of the completed install.  

Cookie-Based Tracking

 In this method, the tracking is based on the cookie that was assigned to the visitor by Playerize.  The offer_id field is required, and will be assigned by Playerize.

 

<iframe src="https://track.playerize.com/aff_l?offer_id=12345" scrolling="no" frameborder="0" width="1" height="1"></iframe>
Have more questions? Submit a request

0 Comments

Article is closed for comments.