Overview

You are expecting to see ACTIVITY_DELETE_USER events in the DES Analytics Export and in the data returned from the Analytics API.

• You have deactivated a user in Jive (you have not deleted the user).
• In your API CURL request, you are filtering by USER, using the deactivated user’s username. E.g.
  • &filter=user(name@email.com)

Solution

When you delete a user from Jive, DES Analytics gets an entry for activity type ACTIVITY_DELETE_USER. However, when you deactivate a user, DES Analytics does not get this entry. Instead, they get an entry: ACTIVITY_UPDATE_USER.

In the API request, you are filtering by username. This filters by the user who performed the deactivation action. Since the affected user (name@email.com in the above example), who got deactivated, was deactivated by someone else, the API request will not find the ACTIVITY_UPDATE_USER event when filtering by the deactivated user.

Instead you have to change the filter to: &filter=match(activity.actionObject.email, name@email.com)

This filters on the affected user, rather than the user who performed the deactivation action.

Your correct API query should look something like this:

curl -XGET -H "Authorization: aaaabbbb-cccc-dddd-eeee-deleted" 'https://api-aws.jivesoftware.com/analytics//export/activity/?count=10000&after=2020-12-31T00%3A00%3A00%2B00%3A00&before=2021-01-10T00%3A00%3A00%2B00%3A00&filter=name(ACTIVITY_UPDATE_USER)&filter=match(activity.actionObject.email,name%40email.com)&fields=name&friendly=true'

This will return results like:

{"name":"ACTIVITY_UPDATE_USER","timestamp":1609607681470}