Pulse Change Log 2025
Pulse Change Log 2025
Explore all the new features, enhancements and changes made to Saras Pulse in 2025 below:
8th September 2025
Enhancements: Navigation and Dashboard Status
Section | Details |
---|---|
Purpose | To simplify how users track dashboard readiness and access dashboards more efficiently. |
What changed? |
The following improvements have been introduced: 1. Dashboard Status Dashboard status: Yellow: Dashboard is in progress. The source has been connected, the presentation table is being prepared, and the dashboard will be ready soon. ![]() This ensures users can easily track the readiness of each dashboard and take actions where needed. 2. Extra step removed while accessing dashboard Previously, clicking on a feature displayed a list of dashboards, requiring an additional selection before entering one.
Now, when users click on a feature, they are taken directly to the first dashboard in that feature. From there, they can use navigation controls to switch between dashboards effortlessly. |
16th July 2025
Enhancements: Navigation and Feature Tray
Section | Details |
---|---|
Purpose | To make navigation more intuitive and give users quicker access to features and dashboard. |
What changed? |
The following improvements have been introduced:
Details: 1. Features Panel ![]() Feature status indicators:
This ensures users can easily track the readiness of each feature and take actions where needed.
2. Shortcut to Add Features
Once activated, the new feature will appear in the Features panel. This makes it easier to expand functionality as the product catalogue grows.
3. Settings Moved to Profile Menu |
23rd May 2025
New Features Launch: Role-Based Access Control (RBAC)
Section | Details |
---|---|
Purpose | To give organizations greater control over who can access specific features, dashboards, and brands within Pulse, enhancing security and flexibility. |
How It Works |
Two roles have been introduced:
Currently, role assignments are managed via a provided RBAC User Access Sheet. The Customer Success team will handle backend setup and send invites with the specified access. |
Impact | Organizations can now manage user permissions more precisely, improving security and enabling tailored access for different team members and external partners. |
User Action | To assign roles, create a copy and fill out the RBAC User Access Sheet. Then share it with our Customer Success team. |
22nd May 2025
New Source Added: APPLOVIN
Section | Details |
---|---|
Category | Marketing |
Features Fuelled | Marketing Datasets |
User Action | Connect the mentioned source to enable reporting for the Features mentioned above. |
14th May 2025
New Source Added: Tiktok Ads
Section | Details |
---|---|
Category | Marketing |
Features Fuelled | Tiktok ads Datasets |
User Action | Connect the mentioned source to enable reporting for the Features mentioned above. |
6th March 2025
New Features Launch: Feature Addition Flow
Section | Details |
---|---|
Purpose | To ensure users have the flexibility to add important features even after onboarding, allowing their setup to evolve as their needs change. |
How It Works |
Users can access a dedicated flow from the homepage at any time after onboarding. Just click on “Activate New Feature” on the home page. ![]() This flow allows them to select additional use cases, features, and data sources—mirroring the brand onboarding experience. Any feature selected in this flow will be added to the user's list of feature and can be seen on the Navigation bar. |
Impact | Users can easily discover and enable new features and dashboards, keeping their Pulse experience relevant and comprehensive as their business requirements grow or shift. |
User Action | No action is required unless users want to add new features. To do so, simply access the feature addition flow from the homepage whenever needed. |
27th March 2025
New Source Added: SKIO
Section | Details |
---|---|
Category | Subscription Management |
Features Fuelled | Customer Cohorts |
User Action | Connect the mentioned source to enable reporting for the Features mentioned above. |
New Source Added: Blotout EdgeTag
Section | Details |
---|---|
Category | Pixel |
Features Fuelled | Attribution |
User Action | Connect the mentioned source to enable reporting for the Features mentioned above. |
26th February 2025
New Feature Launch: Personalized Onboarding Flow for Brands
Section |
Details |
---|---|
Purpose |
To provide a more tailored onboarding experience for brands by allowing them to select relevant use cases and activate only the features they need. |
How It Works |
During onboarding, users select use cases (sales, marketing, product, customer, etc.) and activate features within each use case. Each feature comes with a set of dashboards, and only the selected features will be visible in the UI.
![]() |
Impact |
Brands now enjoy a personalized onboarding process, seeing only the features and dashboards that matter to them, resulting in a cleaner and more relevant user interface. |
User Action |
No action required for users who have already completed onboarding. New brand users will experience the updated onboarding flow automatically. |
Enhancements: New UI for Brands
Section | Details |
---|---|
Issue | The old Pulse UI was single-tiered—all dashboards were visible to users regardless of their interests or needs. This made it difficult for users to focus on the dashboards most relevant to them. |
Solution |
The product has been restructured into a three-tier hierarchy:
Example: Marketing Use Case has the following Features and Dashboards
Customers Use Case has the following Features and Dashboards |
Impact | Users can now select and view only the activated use cases, features, and dashboards, resulting in a more personalized and relevant product experience. The interface is cleaner and easier to navigate, especially for brand users. |
User Action |
No action is required from users. The new hierarchy is automatically applied to brand users, particularly those who select "Brand" during onboarding. New brand users will see the updated three-tier hierarchy by default.
|