Documentation

# Signed In User Analytics

# Tracked Information

When user is logged in against Luminate we set a cookie that contains the following information:

  • consId - Luminate Online constituent id
  • donorId - BBIS donor id
  • firstName- User's first name, stored only for the purposes of personalization of content
  • isDonor - A flag that denotes if the user is a donor
  • isFaf - A flag that denotes if the user has engaged in friends asking friends (peer-to-peer) fundraising campaign, aka TeamRaiser in Luminate
  • isSponsor - A flag that denotes if the user is a sponsor
  • isPartner - A flag that denotes if the user is a partner for children
  • loginType - A variable that denotes how the users logged in

Additional information that's passed to analytics but not stored in the login cookie:

  • interactionLocation - A location where the user has signed in

# How Are the Values Assigned

The values for each parameter are set in the following manner:

  • consId - Assigned when the user is logged into Luminate, the value should always be set for logged in users
  • donorId - BBIS donor id, appears only after a sync with BBIS, this is read from the Luminate Online field Member ID
  • firstName- The value is retrieved from the Luminate profile
  • interactionLocation - The value is set by the page scripts when the analytics event is triggered; it will include a meaningful name of Luminate module, registration for the registration page and include social media suffix, if the users logged in via social media; social media login has been disabled on the login page in early 2020
  • isDonor - The value is read from a custom boolean field in Luminate which appears under Additional Donation > Donor: Ever Gave: in the user profile; the value is set after a sync with BBIS which looks at the Luminate and BBIS data as user could have donated outside of Luminate platforms
  • isFaf - The value is read from a custom boolean field in Luminate which appears under Additional Donation > Is Active FAF Participant in the user profile; the value is set after a sync with BBIS which looks at the Luminate and BBIS data
  • isSponsor - The value is read from a custom boolean field in Luminate which appears under Additional Donation > Is Active Sponsor in the user profile; the value is set after a sync with BBIS which looks at the Luminate and BBIS data
  • isPartner - The value is read from a custom boolean field in Luminate which appears under Additional Donation > Is Active Partner for Children in the user profile; the value is set after a sync with BBIS which looks at the Luminate and BBIS data
  • loginType - The value is computed based on the user's sign in history; if it's a first sign into Luminate and not an auto registration it will contain a value activation; if it's a repeated sign in sign in will be assigned; if it's an automatic registration upon a successful transaction autoregistration will be set

# How to Find and Edit Values in Luminate

  • Sign in to Luminate as an administrator
  • Locate the constituent record by name, email address, or cons_id; example (opens new window)
  • Scroll to the bottom of the page and locate section Additional Information
  • If there are no values next to fields, that means no values have been set
  • One can edit constituent profile and set those values manually for purposes of testing

# What Analytics Variables Are Values Stored In

  • consId - eVar79
  • donorId - eVar13
  • firstName- not stored in analytics, as it's a personally identifiable data
  • interactionLocation - eVar70
  • isDonor - eVar80
  • isFaf - eVar81
  • isSponsor - eVar83
  • isPartner - eVar82
  • loginType - eVar69

← Donation form configuration →