datasets.yml

The dataset configuration file datasets.yml defines the buckets into which analytics data is collected, and how that data is treated.

Field	Description	Example
token	The dataset token is included with every analytics request, and indicates which dataset to use. This token is given out to each client integration	4avsed3ju87239091mweqe323
google_analytics -> record	A boolean value indicating whether the hits should also be streamed to google analytics	true or false
google_analytics -> tracking_id	The GA tracking id for the analytics property, of the form UA-XXXXXXX-X. The property must be a “universal analytics” property.	UA-58395143-1
google_analytics -> custom_dimensions	A list of the custom dimensions that should be recorded with each google analytics hit. These correspond to recorded user attributes sent with the PROFILE command. The dimensions must be configured in the analytics property, and their indexes must match those in this configuration.	age, gender ..etc

Example

This file defines three different datasets, each for collecting analytics for three different environments. The production dataset is configured to forward events to GA, while the lower environments are not.

# datasets.yml (sample)
production:
  token: afc0a6c8c73211e3aaf844fb42fffe8c
  google_analytics:
    record: true
    tracking_id: UA-1234567-1
    custom_dimensions:
      age:
        index: 1
      gender:
        index: 2
      segment:
        index: 3

staging:
  token: b6822676c73211e3aaf844fb42fffe8c
  google_analytics:
    record: false

development:
  token: c2e02c92c73211e3aaf844fb42fffe8c
  google_analytics:
    record: false