Working with Sessions

Sessions are tracked automatically for each customer if sent to CrowdPower via the JavaScript tag or Beacon API.

Session Traits

There are 2 key traits that appear on each customer record pertaining to sessions:

• Last Seen - The date the customer was last tracked by the JavaScript Tag or Beacon API.

• Sessions - The total number of sessions logged for the customer over time.

A 3rd trait, First Seen, is the date the customer was first added to CrowdPower, and will always be populated. It is not related to sessions.

Session Timeout

All sessions are based on a 30-minute window by default. The session count is incremented only if the customer is inactive for more than 30 minutes before coming back to your website. You can adjust this window in Settings.

Updating Sessions

Sessions are updated by default, but you can prevent this from happening by passing in the update_session key on all Beacon API calls. Set the value to false to prevent logging new sessions. This could be useful if you're sending historical data in.

{
    update_session: false
}

The update_session key cannot be used with the Segment integration.