Global Filtering in Distributed
Updated
Global Filtering in Distributed is designed to streamline data management and enhance the user experience for clients managing multiple brands, stores, locations, or regions. This feature is particularly useful for clients operating in the hospitality and retail industries by providing a scalable solution to handle data segmentation and analysis efficiently.
User Persona: Store Marketing Managers, Distributed End Users
Use Cases
Regional Social Media Management: In case a user manages multiple stores or locations they can view separate reporting data for each location.
Customer Service Efficiency: A customer service team can filter messages and tickets by location, ensuring that inquiries from each region are handled by the appropriate team members, thereby ensuring better response times.
Benefits
Allows users to concentrate on specific regions or locations, reducing data clutter and increasing focus on relevant information.
Enables the creation of detailed, region-specific reports, making it easier to track and analyze local trends and metrics.
Note: This feature can be configured for the following entities:
Account (Messages) - The data will be filtered based on the Account level global custom field.
User - The data will be filtered based on the User level global custom field.
Reporting - The data will be filtered based on the Account level global custom field
Assets - The data will be filtered based on the Asset level global custom field.
Case - The data will be filtered based on the Case level global custom field.
Ads Reporting - The data will be filtered based on the Paid Initiative level global custom field.
Ads Manager - The data will be filtered based on the Paid Initiative level global custom field.
Steps to Apply Global Filtering
Log in to the Distributed environment.
Click the Global Filtering dropdown icon below the Sprinklr logo at the top of the menu bar to the left.
Select the preferred Custom Field (Store/Location) from the dropdown.
Based on the selected value, the data corresponding to it will be filtered in the entities mentioned above.
Note: For Ads Reporting/Ads Manager, the global Custom Field should be a mandatory value during the creation of the Paid Initiative. If the Paid Initiative is not tagged with that Custom Field, then corresponding data will not be available for DST users as the global filtering will be done based on the custom field associated with the Paid Initiatives.