Activity

The activity section shows the details about events received for any user from different data sources and the actions received for different channels. These events are time-dependent and can be viewed in pre-defined time frames like Today, Yesterday, Last 7 days, Last 30 days, Last 60 days, and Last 90 days.

Step 1: Go to Customer One View

Step 2: Enter any of the credentials like hash Email, Policy number, or application number, in the search bar and click Fetch User

Step 3: Navigate to > Activity

Step 4: Set the time range accordingly.

Gif: Activity

Click the drop-down button beside each event to get details like technology, Event properties and page parameters about that particular event.

You can get more insights about the event by clicking on the detailed view and filtering the activities by event name, event properties, type of event, etc. You can only filter the events by segments and channels in the case of campaign events.

To apply Filters,

Select the campaigns Check box

To Apply filters,

Step 1: Select Channels

Step 2: Choose the property from the drop-down

Step 3: Choose the operator

Step 4: Select the input from the values from the drop-down

Step 5: Click Apply

Step 6: Select Fetch Events

The data will be displayed based on the filters you applied. You can filter the data based on Browser, Engagement, Segments and Actions.

Gif: Apply Filters

Event Types and Details

1. Track

The trackAPI call records the actions customers perform, along with the properties of the action. Click here to learn more about Track.

Event :Track

• Event Name: Shows the name of the event that the user has performed (For example, buttonClick, formSubmission,etc.)

• Technology: This section contains technology details like devices, browsers, meta fields, etc., which helps to know from which device/browser the engagement action was received. If any action does not provide the details of the technology, it will be displayed as NA (Not Available).

• Properties: Shows the custom event properties we’ve received, along with any user identifier that has been sent.

• Page Parameters:

  • Page Title: Shows the name of the page

  • URL: Shows the the page URL

  • UTM Params: Shows the UTM parameters to analyze the performance of your marketing campaigns.

2. Screen

Identifies the screen viewed by the user on the app. It helps create a customer funnel and identify which screen the user dropped. Know more about Screen here.

• Technology: This section contains technology details like devices, browsers, meta fields, etc., which helps to know from which device/browser the engagement action was received. If any action does not provide the details of the technology, it will be displayed as NA (Not Available).

• Properties: Shows the custom event properties we’ve received along with the event and the user identifier that has been sent.

• Screen Parameters:

  • Screen Name

  • Width

  • Height

  • Density

3. Page

Identifies the pages viewed by the user. It helps create a customer funnel and identify which page the user dropped. Know more about Page here.

Event: Page

• Event Name: Shows the name of the event that the user has performed (For example, buttonClick, formSubmission etc.)

• Technology: This section contains technology details like devices, browsers, meta fields, etc., which helps to know from which device/browser the engagement action was received. If any action does not provide the details of the technology, it will be displayed as NA (Not Available).

• Properties: Shows the custom event properties we’ve received along with the event and the user identifier that was sent.

• Page Parameters:

  • Page Title: Shows the name of the page

  • URL: Shows the the page URL

  • UTM Params: Shows the UTM parameters to analyze the performance of your marketing campaigns.

4. Identify

Identifies the user and merges the cookie ID with the existing profile. Example: Login, Subscription, etc. Know more about Identify here.

Event: Identify

• Event Name: Shows the name of the event that the user has performed (For example, buttonClick,formSubmission etc.)

• Technology: This section contains technology details like devices, browsers, meta fields, etc., which helps to know from which device/browser the engagement action was received. If any action does not provide the details of the technology, it will be displayed as NA (Not Available).

• Properties: Shows the custom event properties we’ve received along with the event and the user identifier that was sent.

• Page Parameters:

  • Page Title: Shows the name of the page

  • URL: Shows the the page URL

  • UTM Params: Shows the UTM parameters to analyze the performance of your marketing campaigns.

5. Campaign Events

Actions received from different channels

Channels	Actions Received
Web Push	Delivered, Clicked, Dismissed
App Push	Delivered, Clicked, Dismissed
Email	Delivered, Opened, Clicked, Unsubscribed, Spam Report
SMS	Delivered, Clicked
WhatsApp	Delivered, Read
On-site Notification	Delivered, Clicked
Banner Personalization	Delivered, Clicked

Details Shown

Event: SMS Delivered

Technology: This section contains technology details like devices, browsers, meta fields, etc., which helps to know from which device/browser the engagement action was received. If any action does not provide the details of the technology, it will be displayed as NA (Not Available).

Campaign Attributes:

• Engagement ID and Name: Shows the engagement ID of which the user is present

• Segment ID and Name: Shows the segment ID and name in which the user is present

• Journey ID: Shows the details of the Journey ID like the Journey name, versions, etc. only if the user action is related to the Journey.

• Message ID: Shows the ID of the message that you configured. (Applicable only for Email, SMS and WhatsApp)