# Ruby

TIP

Before you begin, please read Preparation before Data Ingestion.

Latest version: 1.2.0

Update time: 2020-08-28

Resource download: Source Code (opens new window)

# SDK Integration

1.1 Please use gem command to get the SDK package.

# install SDK
gem install thinkingdata-ruby

1.2 Logbus Integration

We recommend using SDK+LogBus to track and report data on server. You can refer to the following documents to complete the installation of Logbus: LogBus User Guide

# Initialization

The following is the sample code for SDK initialization:

require 'thinkingdata-ruby'
consumer = TDAnalytics::LoggerConsumer.new(LOG_DIRECTORY)
te = TDAnalytics::Tracker.new(consumer)

LOG_DIRECTORY is the local folder path.

# Common Features

In order to ensure that the distinct ID and account ID can be bound smoothly, if your game uses the distinct ID and account ID, we strongly recommend that you upload these two IDs at the same time, otherwise the account will not match, causing users to double count. For specific ID binding rules, please refer to the chapter on User Identification Rules.

# 3.1 Sending Events

You can call track to upload events. It is suggested that you set event properties based on the data tracking plan drafted previously. Here is an example of a user buying an item:

event = {
  'event_name' => 'test_event',
  'account_id' =>'ruby_test_aid',
  'distinct_id'=>'ruby_distinct_id',
  'ip' => '202.38.64.1',
  'properties' =>{
    'prop_string' =>'hello world',
  },
  # skip_local_check: true,
}
te.track(event)

Key is the name of the property and refers to the string type. It must start with a character, and contain numbers, characters (insensitive to case, and upper cases would be transformed into lower cases by TE) and underscores "_", with a maximum length of 50 characters.
Value, the value of the property, supports string, numbers, Boolean, time, object, array object, and array

The requirements for event properties and user properties are the same as that for super properties

# 3.2 User Properties

You can set general user properties by calling user_set API. The original properties would be replaced by the properties uploaded via this API. If no user properties are set before, user properties will be newly created. The type of newly-created user properties must conform to that of the uploaded properties. User name setting is taken as the example here:

user_data = {
  'account_id' =>'ruby_test_aid',
  'distinct_id' => 'ruby_distinct_id',
  properties => {
    'user_name' => 'te'
  }
}
te.user_set(user_data)

# Best Practice

The following sample code covers all the above-mentioned operations. It is recommended that the codes be used in the following steps:

require 'thinkingdata-ruby'
consumer = TDAnalytics::LoggerConsumer.new(LOG_DIRECTORY)
te = TDAnalytics::Tracker.new(consumer)

event = {
  'event_name' => 'test_event',
  'account_id' =>'ruby_test_aid',
  'distinct_id'=>'ruby_distinct_id',
  'ip' => '202.38.64.1',
  'properties' =>{
    'prop_string' =>'hello world',
  },
  # skip_local_check: true,
}
te.track(event)

user_data = {
   'account_id' =>'ruby_test_aid',
   'distinct_id' => 'ruby_distinct_id',
  properties => {
    'user_name' => 'te'
  }
}
te.user_set(user_data)

te.flush