hat
Boomtrain University
BME Guide

User Properties

Boomtrain Marketing Engine has a prebuilt set of User Properties:

email
first_name
last_name
name
last_seen
last_contact
last_opened
last_clicked
signed_up_at

Creating Custom Properties

You can also add your own set of User Properties. These will automatically be created when you send us user data, but we recommend manually creating them so you can have more control over the content coming in.

Creating Properties Via BME UI

  1. Navigate to your Boomtrain.net account and click Users > More > User Properties.
  2. Here you can view Default Properties (listed above) or view and update your Properties.
    Screen Shot 2016-02-05 at 1.57.17 PM
  3. When you choose to create a new Property, you’re met with a few options. If you want to set uniformity for user values being passed to us, you just need Name and Type (see the Property Types section below). If you’d like to match User Properties to an Activity, you can name the Activity and its Attribute here.
    Screen Shot 2016-02-05 at 1.57.26 PM

Once you save, you’re all set! you can now begin sending data using this property and also use it for interacting with activities and segments.

Property Types

Below are the property types you can choose when interacting with properties.

String

  • Holds – any single string of data
  • Constraints – none enforced
  • Activity Name – not used
  • Activity Attr Name – not used
  • Example Uses
    • first_name
    • user_id
    • favorite_color
    • zip_code

Number

  • Holds – any single numeric data
  • Constraints – max value: 9007199254740991 (enforced by JavaScript), generally this data type should only be used for values when you want to be able to do math or number logic on them.
  • Activity Name – not used
  • Activity Attr Name – not used
  • Example Uses
    • age
    • latitude

Date

  • Holds – any single date data
  • Constraints – ISO8601 format
  • Activity Name – not used
  • Activity Attr Name – not used
  • Example Uses
    • birth_date
    • sign_up_date
    • purchase_date

List

  • Holds – multiple data points, collected from activity attributes
  • Constraints
    • can hold strings, numeric, and dates
    • List mgmt tools have to be turned on in a per user basis
    • Ability to sum/average/etc. within the segmentation tool is turned on in the UI on a user by user basis
    • To upload lists via .csv file, you can replicate the same user into multiple rows with the value of the list property being different for each of the rows. For example, if you want to add the values, Harvard, Stanford, MIT into a list property called schools, you should first create this property and mark it of type list, then upload the file with three rows, where the user_id, email, first_name, last_name etc is all same but the schools property has the three different values.
  • Activity Name – used (ie. purchase)
  • Activity Attr Name – used (ie. order_total)
  • Example Uses
    • order_totals (can be used to calculate LTV, AOV, etc)
    • shopping_cart_items (used to hold all items currently in your shopping cart)

Counter

  • Holds – a single integer, automatically increments on a specified activity
  • Constraints – unknown
  • Activity Name – used (ie. purchase)
  • Activity Attr Name – not used
  • Example Uses
    • order_count (counts every purchase activity for each user)
    • view_count (count every view activity for each user)

Last Occurrence

  • Holds – a single date value, automatically updates on a specified activity
  • Constraints – ISO8601 format
  • Activity Name – used (ie. purchase)
  • Activity Attr Name – not used
  • Example Uses
    • last_purchase (date of last purchase activity for each user)
    • last_view (date of last view activity for each user)

Recur Date Every Year

  • Holds – a single month/day date value (with the year)
  • Constraints
    • ISO8601 format
    • Use the full date including year
    • When segmenting select your user property and use the “within last”, “within next”, “not within last”, or “not within next” operators
  • Activity Name – not used
  • Activity Attr Name – not used
  • Example Uses
    • renewal_date
    • birthday

Recur Date Every Month

  • Holds – a single day date value (without the month and year)
  • Constraints
    • ISO8601 format
    • Use the full date including month and year
    • When segmenting select your user property and use the “within last”, “within next”, “not within last”, or “not within next” operators
  • Activity Name – not used
  • Activity Attr Name – not used
  • Example Uses
    • billing_date
    • payment_reminder_date

Creating Properties Via CSV

  1. You can add your Custom User Properties through CSV uploads. Make sure you include an email column (which will double for a user_id column if that column is missing) and add the custom properties to the user. Workbook1 2016-05-11 01-10-18
    You can add as many Custom User Properties as you want. Make sure to use the same property name consistently in order to keep your users organized. Avoid using different property names with the same purpose such as locality, city, location, etc. This will prevent complications later.

Best Practices

Property names used in this section do not have to be exact.

  • Properties for segmenting: If you have multiple newsletters, you may want to divide your users into segments based on which newsletter(s) they subscribe to. By adding a custom user property, you can filter each user into the correct segment. Example: daily_newsletter:true, weekly_newsletter:false, beauty_newsletter:true, recipe_newsletter:false, etc.
  • Location: Aside from being able to segment users based on their city, locality can be used to view how many users signed up in the last month in which city, how many users you have for each location, how many of them opened the campaign you sent recently, etc.
  • Age/Gender: If you’re collecting these values from your users, you may find it useful to create reports based on the age range or gender of your active users.
  • Interests: If your users have provided you with these values, you can cater to their interests when sending campaigns or other communication.

For further recommendations based on your specific business needs, please consult your Boomtrain Customer Success Managers.

Updating Users & Properties

To update large groups of users, you can access our Developer Center at https://boomtrain.readme.io/docs. BME also allows you to update user information and user properties using the CSV upload method. For this process, you don’t need to include all the existing attributes, just the fields that need to be changed or added plus the user’s email address (duplicated as the user_id when that value is not included).

  1. In this example, we’ll update the State and First_name of a user.  Wendell has moved and also wants to add a middle initial to the system. Before the change, the user has this information already in BME: First name : Wendell , State: California . After the update, First name: Wendell J  , and State : Arizona.
    user
  2. Create a CSV with the updated values.
    sample_subscriber_upload_1 2016-02-12 15-43-50
  3. Upload the file from the Users page.
    User Upload_1
  4. When the upload completes, confirm the user’s properties have been changed.
    Boomtrain: Machine Intelligence Built for Marketers 2016-02-12 16-08-32
Shares
Share This