Sensor Remote Control
The Sensor Remote Control tab supportsintelligent data gathering with remote post-integration updates for dynamic data collection changes:
By default, the Blocked Events section is displayed.
Blocked Events
Block event allows preventing irrelevant or meaningless events from sensor collection, ensuring the accuracy and relevancy of data ingestion. The Blocked Events list shows the events that are blocked along with the block rule, blocked by user, and blocked date. Use this section to perform various actions, such as searching, modifying, and unblocking previously blocked events.
Searching Blocked Events
-
To find a blocked event, click the search icon adjacent to the Custom Event column, enter part of the event's name in the search window, and click Search.
-
To find a blocked event by the blocked by user, click the search icon adjacent to the Blocked By column, enter part of the user's name in the search window, and click Search.
Editing Blocked Events
Change the block rule and note for an existing blocked event.
-
Click an event name under the Custom Event column to see details of the block events.
-
Click Edit in the event details section.
-
Change the block rule and/or update note, and click Save Changes.
Viewing Events in Block Panel
View a blocked event in Semantic Mapper page.
-
Click an event name under the Custom Event column to see details of the block event.
-
Click View in Block Panel in the event details section to see the blocked events related dimensions in the Semantic Mapper page.
Unblocking a Blocked Event
Unblock an existing blocked events to resume the event collection via Conviva DPI sensor.
-
Click the Unblock button corresponding to the blocked event, and click Yes on the confirmation message pop-up.
After unblocking an event, it is removed from the Blocked Events list and Conviva DPI sensor starts collecting the respective event data from the integrated app.
Configured Network Request
Configure Network Request allows defining the collection rules for conviva_network_request events. When the rules are configured, the Conviva sensor collects network request events accrding to the matched rules. Optionally, select the collected events as raw data for mapping.
Configure the network request data collection rules for multiple categories, such as metadata usage, EMP query fields, GraphQL, tag value, and metrics API.
Collection Rule Order
Network request collection rules are applied based on the most recently changed rules, and then rules following the displayed category order. If a network request does not meet any configured rules in a category, the collection rule matching process stops and that network request data is not passed to DPI.
There are two methods for collecting conviva_network_request events:
-
Blocked events: blocks events matching blocked event criteria and collects all other conviva_network_request events.
-
Collection rules: collects events matching allowed event criteria and blocks all other conviva_network_request events.
Note: Events matching the blocked events criteria are blocked even if they also match any collection rules.
Creating Collection Rules
-
Click Add New in the Browse Configuration section, on the left pane.
-
Set the collection rule in the New Configuration secion, on the right pane:
-
Condition Name: Type a name for the collection condition.
-
Define the URL Conditions by selecting:
-
All: Enables rules to take effect on all conviva_network_request events.
-
Contains: Enables rules to take effect on events containing the Target Urls.
-
-
Set collection rules using Request Header, Request Body, Response Header, Response Body, separately.
Note: Click Add to include more rules if necessary.
Capture Network Request Data
To gather information about the keywords users searched for and conduct in-depth analysis based on that information, collect the relevant conviva_network_request events data.
-
Configuration Name: Search Keywords
-
URL Condition: Select Contains and type search in the Target Urls field. This is required.
-
Set Collection Rules with:
-
origin as Request Heade.
-
keywords as Request Body.
-
Leve the Response Header field empty.
-
result.count, result.name, and result.category as Response Body.
-
-
-
Click Save. Conviva DPI sensor starts collecting the conviva_network_request events that match the rules.
Auto Collection of Clicks
Customize the user-click tracking across the application, beyond tracking the click events for buttons and links. This section consists of two tabs, Collect Attributes and CSS Selectors. Use the default attributes and CSS selectors, and also create additional custom tags, CSS selectors, and attributes to track user clicks for various purposes, such as defining Out-of-Box (OOB) metrics, resolving UX issues, and even creating meaningful user Flows.
Note: This feature is available only for the DPI Web (JavaScript) Sensor version 1.1.15 and above. Conviva recommends updating the sensor to its latest version.
Use the toggle button at the section header to enable/disable this feature for the DPI sensor.
Collect Attributes
Specify the non-standard HTML attributes (such as data-test-id or app-custom-button-id) using their key value. By default, DPI sensors support collecting user-click events for certain attributes, such as, id, class, name, type, placeholder, value, a.href, area.href, a.target, area.target, and xlink:href.
In the Custom Attributes section, click the Add Attribute button to track user clicks on more custom attributes such as, src, title, alt. Click the Save button to deploy.
Note: Sensors may take 30 minutes to reflect the changes.
CSS Selectors
Define tags, classes, IDs, or attributes to precisely target the elements you want to track. By default, DPI sensors support collecting user-clicks for the native clickable selectors, such as button, a, select, textarea, input:not([type="hidden"]), summary, video, and audio.
In the Default Virtual Clickable Selectors section, use the toggle button to enable/disable the pre-defined click tracking for the virtual selectors.
In the Custom CSS Selectors section, click the Add CSS Selector button to specify the custom CSS Tag or custom CSS attribute for click tracking.
-
To define custom CSS tag:
-
Click the Add CSS Selector button.
-
Select the option Tag from the drop-down list.
-
Specify tag name in the adjacent field.
-
Click Save to deploy.
-
Note: Sensors may take 30 minutes to reflect the changes.
-
To define custom CSS attribute:
-
Click the Add CSS Selector button.
-
Select the option Attribute from the drop-down list.
-
Specify attribute name in the adjacent field.
-
Select a condition (Starts With, Ends With, Equals, and Contains) from the drop-down list.
-
Specify the value to match based on the selected condition.
-
Click Save to deploy.
-
Note: Sensors may take 30 minutes to reflect the changes.
Sensor Remote Control Sensor Remote Control Sensor Remote Control Configured Network Request Configured Network Request Configured Network Request Blocked Events Blocked Events Blocked Events Click Tracking Click Tracking Click Tracking Click Tracking Custom Attribute Custom Attribute Custom Attribute CSS Selector CSS Selector CSS Selector Auto Collection of Clicks Auto Collection of Clicks Auto Collection of Clicks