We are excited to reveal our new dashboard as part of our commitment to enhancing your experience with the Larky platform. These changes include a refreshed navigation menu, updates to our analytics, and new insights designed to better align with our recent research and feedback from clients like you. Below, we outline what you can expect with these updates.
NEW Navigation Menu
The dashboard's navigation menu has been thoughtfully redesigned to simplify and optimize your nudge creating experience. It now highlights three key categories:
-
Alert Messaging (previously referred to as Time-Based nudges)
- Purpose: For push notifications that must be sent in emergent situations or are only valid for a single day.
- Example Use Cases: Branch closures due to severe weather alerts, system outages, or other time-sensitive reminders.
-
Campaign Messaging
- Purpose: For push notifications that are valid for longer than a single day, with options for single or multi-nudge campaigns.
-
Engagement Insights:
- Single-nudge campaigns can increase engagement by 10-20% compared to alert messages on subsequent days.
- Multi-nudge campaigns drive up to 50% more engagement on subsequent nudges compared to single-nudge campaigns.
- Example Use Cases: Promoting ongoing events, product launches, or multi-day sales campaigns. Learn more on Why Campaign Messages Get More Engagement Than Alert Messages.
-
Location Messaging
- Purpose: For push notifications tied to a specific location or locations.
- Example Use Cases: Branch-specific promotions, location-based reminders, or geofencing alerts.
Note: Many of our clients have been using Time-Based nudges (now called Alert nudges) to send simple, single-message campaigns. You are free to continue using the platform in this way! We only changed the labeling to help highlight our recommended best practice: sending nudges as Campaigns, even if the campaign only includes a single nudge, really helps drive higher engagement because it allows the system to fine-tune the delivery of that nudge on a per-recipient basis. Remember that an important element of the platform is our built-in “message capping,” preventing the system from over-messaging any given recipient. A campaign message will be queued and attempted again the next day if an account holder has already received a nudge earlier in the day, perhaps from location messaging or even another campaign.
Adoption Overview & Additional Insights
Larky clients thrive on data, and we’re excited to deliver even more actionable insights! You now have access to detailed adoption statistics. Client feedback inspired these updates, and we’re thrilled to make them available:
-
What to Expect:
- Adoption Overview: This new section will keep you informed of the total number of recipients you can message.
- Active Nudges and Campaigns: Easily see the total number of active nudges and campaigns. Quickly navigate to your active nudges or campaign with preset filters.
Updated Analytics
We are updating your analytics to align more closely with the research we conducted this year. These changes may shift some of your primary metrics, such as total impressions and engagements. Here’s what you need to know:
-
What to Expect:
- Potential Metric Adjustments: The updated calculations may cause most clients to notice a change in their reported impressions and engagements.
- Improved Data Consistency: These updates will ensure that your Larky analytics better match the metrics seen across other communication channels. If you notice a change in the values you’ve previously been tracking, this is only a result of the new calculation, and not an indication that your actual count of impressions or engagements went up or down.
We’re confident these updates will elevate your experience with Larky, providing you with deeper insights into Larky functionality and data to drive more impactful engagement. We value your feedback, please don’t hesitate to share your thoughts with us at support@larky.com. Thank you for choosing Larky as your trusted engagement partner!
Comments
0 comments
Article is closed for comments.