Technical Reference

Mobile Table Reference


APA

Application Added

ParameterTypeDescription
utc_timestampbigintThe time that the message was received by Upsight. ts is the time the event happened. This (ts) is usually the system time set by the device and can be different from utc_timestamp especially if the application can be ran offline. For example if an application was running on day x (offline) , messages would be generated by the SDK but would not be sent to Upsight. These messages will be saved by the SDK and when the device comes online on day x+1, the SDK will fire off all of the stored messages to Upsight. In this situation, the 'ts' for these messages will say day x while utc_timestamp will say day x+1. We use 'ts' to calculate the metrics such as uniques and retention (as ts tells us when the event happened and that this user was an unique on day x)
typestringThis is the message type, will always be apa.
sstringThis is the user id.
ustringUsually empty. Legacy from the social platform used to match installs from stream posts and invites
sustringUnique tag used to match an install from an ad click from the UCC call
json_datastringThis is a JSON string which can contain any custom information about this message.
tsstringThe time that the event happened. This is usually based on the system time of the device.
monthpartitionA partition used to separate the files. All data received in the same month are stored within one partition. Extremely useful for speeding up your queries, try selecting only the partition that you need.

CPU

User Information

ParameterTypeDescription
utc_timestampbigintThe time that the message was received by Upsight.
typestringThis is the message type, will always be cpu.
sstringThis is the user id.
v_majstringThe application version.
v_minstringDeprecated
v_revstringDeprecated
osstringThe operating system.
mstringThis is the manufacturer of the device.
dstringThis is the device of the user.
json_datastringThis is a JSON string which can contain any custom information about this message.
client_ipstringIp address of the sender. If the message was sent client side, this will represent the location of the user. This parameter is automatically appended by Upsight after we receive the message.
tsstringThe time that the event happened.
acstringIf the application has been cracked.
jbstringIf the device has been jail broken.
monthpartitionA partition used to separate the files. All data received in the same month are stored within one partition.

jb This returns either "true" if the device is jailbroken. Otherwise it returns "false". Available for iOS applications only. This is because most devices are technically 'jailbroken' on Android due to changes made by carriers.

ac This returns either "true" if the application is cracked. Otherwise it returns "false".

EVT

Custom Event

ParameterTypeDescription
utc_timestampbigintThe time that the message was received by Upsight.
typestringThis is the message type, will always be evt.
sstringThis is the user id.
nstringThe name of the event.
vintThis value associated with the event.
lintThe level associated with the event.
st1stringThis first subtype of the event.
st2stringThis second subtype of the event.
st3stringThis third subtype of the event.
json_datastringThis is a JSON string which can contain any custom information about this message.
tsstringThe time that the event happened.
monthpartitionA partition used to separate the files. All data received in the same month are stored within one partition.

PGR

Page Request/User Location

ParameterTypeDescription
utc_timestampbigintThe time that the message was received by Upsight.
typestringThis is the message type, will always be pgr.
sstringThis is the user id.
ustringDeprecated. For social this is the URL of the page.
ipintAn ip address associated with this page request. Usually blank for mobile applications.
client_ipstringIp address of the sender. If the message was sent client side, this will represent the location of the user. This parameter is automatically appended by Upsight after we receive the message.
json_datastringThis is a JSON string which can contain any custom information about this message.
tsstringThe time that the event happened.
monthpartitionA partition used to separate the files. All data received in the same month are stored within one partition.

MTU

Monetization

ParameterTypeDescription
utc_timestampbigintThe time that the message was received by Upsight.
typestringThis is the message type, will always be mtu.
sstringThis is the user id.
vbigintThe amount of the transaction, in cents.
tustringType of transaction.
st1stringThis first subtype of the event.
st2stringThis second subtype of the event.
st3stringThis third subtype of the event.
json_datastringThis is a JSON string which can contain any custom information about this message.
tsstringThe time that the event happened.
monthpartitionA partition used to separate the files. All data received in the same month are stored within one partition.

UCC

Third Party Communication Clicks

ParameterTypeDescription
utc_timestampbigintThe time that the message was received by Upsight.
typestringThis is the message type, will always be ucc.
cstringCost of the ad click.
tustringType of ad click. For social applications, it could be ad or partner. For mobile, it's just ad.
istringDeprecated. For social applications, this indicates if the user who clicked on the ad already have the application installed. 0 indicates the user doesn't have the application already installed and 1 for those who have.
sstringThis is the user id.
sustringUnique id used to match with the install message.
st1stringThis first subtype of the event.
st2stringThis second subtype of the event.
st3stringThis third subtype of the event.
json_datastringThis is a JSON string which can contain any custom information about this message.
tsstringThe time that the event happened.
monthpartitionA partition used to separate the files. All data received in the same month are stored within one partition.

Example:

ParameterType
utc_timestamp1340316977
type"ucc"
c
tu"partner"
i1
s6575643
su21B95D9F
st1Subgroup1
st2Subgroup2
st3Subgroup3
json_data{"custom_parameter1":"55","is_whale":"true"}
ts1340316941
month201206

Social Table References


APA

Application Added

ParameterType
#1
utc_timestampbigint
typestring
sstring
ustring
sustring
json_datastring
monthpartition

APR

Application Removed

ParameterType
#1
utc_timestampbigint
typestring
sstring
json_datastring
monthpartition

CPU

User Information

ParameterType
#1
utc_timestampbigint
typestring
sstring
bstring
gstring
lcstring
lsstring
fstring
json_datastring
monthpartition

EVT

Custom Event

ParameterType
#1
utc_timestampbigint
typestring
sstring
nstring
vint
lint
st1string
st2string
st3string
json_datastring
monthpartition

INS

Invite Sent

ParameterType
#1
utc_timestampbigint
typestring
sstring
rstring
ustring
st1string
st2string
st3string
json_datastring
monthpartition

INR

Invite Response

ParameterType
#1
utc_timestampbigint
typestring
istring
rstring
ustring
st1string
st2string
st3string
json_datastring
monthpartition

GCI

Goal Counts

ParameterType
#1
utc_timestampbigint
typestring
sstring
gc1string
gc2string
gc3string
gc4string
json_datastring
monthpartition

MTU

Revenue Tracking

ParameterType
#1
utc_timestampbigint
typestring
sstring
vint
tustring
st1string
st2string
st3string
json_datastring
monthpartition

PGR

Page Request/User Location

ParameterType
#1
utc_timestampbigint
typestring
sstring
ustring
ipstring
client_ipstring
json_datastring
monthpartition

Tip What is the difference between the ip and client_ip column in the PGR table?

The column ip reflects the ip parameter sent from PGR messages. It is an optional parameter for PGR messages.

The column client_ip is recorded by Kontagent and it reflects the IP address from which the API message was sent.

If PGR messages are sent server side, the value of client_ip should stay the same for all PGR messages since they are being sent from 1 location. If you are interested in knowing the actual location of these users in DataMine, you can make use of the ip parameter and send Kontagent the ip address as well.

If PGR messages are sent client side, client_ip will reflect the actual location of the user.

PST

Stream Post

ParameterType
#1
utc_timestampbigint
typestring
sstring
ustring
tustring
st1string
st2string
st3string
json_datastring
monthpartition

UCC

Third Party Communication Click

ParameterType
#1
utc_timestampbigint
typestring
tustring
istring
sstring
sustring
st1string
st2string
st3string
json_datastring
monthpartition