The data should be sent continuously. However, for network login, we need our clients to filter the data to only Reserve users. The customer should send "new events" and not users who are "still logged in" to the network. If a user logs out and logs back on, then this would be considered a new event. This is similar to badge events when an employee leaves and comes back from lunch. One thing to note is that with our API Gateway, we will be able to meter/manage the customer access to avoid data saturation for events.
Additionally, for network login:
- Only send valid Reserve users
- Exclude Service Accounts
- Exclude devices (like copiers)
- Only send new events per person
- Only send events for locations that are live in Reserve.