Up to 1000
Can have up to 4 goals
Can apply filters to each profile
Filters, 4 per profile, RegEx to narrow things down
Used to segment userbase into smaller chunks
Examples, Users who have clicked on a given link, Users who have deposited money, Users from Paraguay
A whole lot more parked domains, Are we doing anything with these?
Cookie, Tied to an image
302 Redirect to absolutebanking.com, Now a 301
Trying to move affiliates off of the banking system to reduce problems
Game server tags certain actions, Create new table, Change games
Omniture drops a cookie into IE in the client, Problems with FF users
None of this stuff works, currently
UB's client has a baked in IE client, Does it share cookies with primary browser?
Correlating users between multiple domains
Integrating reports across domains, MAC address
Hard to get resources to make changes
Multiple clients, Windows C++, Mac Java
I/O is very expensive
Nobody has come up with a use-case for realtime data yet
Nobody wants to use Regex to update profiles
Could be solved by creating a bank of pre-made filters and profiles
Custom Front End
With a dynamically changing amount
Sum For Life
Broken down by section of registration
Previous vs new depositors
Revenue for original campaign
Where in the cashier do people defect
How many of those go on to deposit?
DL rate for keyword
Reg for keyword
Deposit for keyword
Deposit split by Geography
$ per keyword
$ per player
x number of variables
Split even and odd IP addresses
Or some other workaround for the FF Windows users
Can we assign accurate lifetime values to segments?
Can we attach a username to a web viewer
Can we find problem points in our Golden Funnel
Fallout Reports, Segmented in a few ways, Page path
Tag download links, Track post-download behaviour
Back to the Golden Funnel
Good sense of sources
Two-segment reports, Keywords vs Geo
Can we accurately track A/B Testing?
Can we accurately track multivariate testing?
Data could be pulled from server logs
Nobody has seen it implemented in a poker client either
Doesn't have the ability to reprocess log files to access player data
Browsing the game client is similar to browsing a website, UI changes should be done in a similar way
How are users interacting with the client?, Click-path analysis, What about survey based approaches?, 100 person sample?, Segmenting information by gameplay attributes, Betting patterns?
Segment players navigation through the client based on these tests
Connect pre-registration to client data, Track all of the information cradle-to-grave, Segmenting player-base, Loyalty, Betting, Winner/Loser, Entry channel, Optimize keywords through client information
Heatmap analysis is important
Specific Tags, Pages of lobby, Buy-in Window, Table, ????, How many people fail to complete tasks?, Registering for a tournament, How much - in chips - are people bringing to the table?
3 Per Brand
Back-end connections are --we think-- the same, Common database
Mac client represents 5% of current users
A/B, Redirect 1/2 of traffic to a separate page, Google will track results, Define a goal page within GWO
Multivariate, Google will dynamically replace portions of HTML to test multiple changes on a page, Used to cause problems with complex layouts, I haven't heard of this happening recently., Does not work with CMSes which cannot support an unbalanced <noscript>
Disadvantages, Requires second set of tracking codes, Slight performance hit, Two interfaces, No access to Urchin profiles, filters, or reports