Skip to main content

Search

Pinnacle Series Spark

Spark

EP background

Managing Spark Notifications

Applies To: 

  • Pinnacle Series Administrators.
     

Common Causes/Issues:

  • You would like to learn about how the Pinnacle Series Spark notifications work.

 

Solution Overview:

Spark notifications help teams build habits with short, focused videos delivered on a consistent schedule. Admins manage the frequency per group and can tailor the two email templates to match the company's tone and brand. 

 

 

How Spark notifications work

  • Channels: In-App (always available) and optional Email.
  • Cadence (per group): Daily • Weekly • Monthly.
  • Scope: Users inherit the group’s channels and cadence. Use different groups for different schedules.
  • Language: Emails send in the language shown in the editor; they are not auto-translated.

In-App Notifications

  • SPARK reminders display in the notification bell in Pinnacle Series.
  • Shown Daily, Weekly, or Monthly depending on group settings.
  • Clicking the notification takes the user to the SPARK landing page.
  • Notification is generic (does not list each content item).

Email Notifications

  • Sent only if:
    1. The group has SPARK email notifications enabled.
    2. The user has email notifications turned on in their profile.
  • Batched every ~5 minutes, including unread notifications from the last hour. If the in-app notification is read, no email is sent.
  • Two templates are used:
    • Single notification email for one item.
    • “Recent Notifications” email when multiple items exist.

How to set it up

  1. Go to Administration Portal > Groups > (select a group) > Group Details.
  2. Ensure Features > SPARK is toggled ON (right panel).
  3. Scroll to SPARK Notifications and select In-App and/or Email.
  4. Choose the Frequency (Daily, Weekly, Monthly) and Save.

Tip: Start Weekly for broad audiences; use Daily for short pilots or focused skill pushes; Monthly for evergreen programs.

Note: 

  • Anytime the notification frequency is Updated and Saved, or when the SPARK setting for the Group is toggled ON and Saved, we restart the notification cycle, so the user will receive another notification, even if they already received one that day.
     
  • If the user belongs to more than one group where SPARK is enabled, and a different frequency is set on each of those groups. Our system will send a notification based on the most frequent setting e.g. if Group A has notification settings set to daily and Group B weekly, and the user belongs to both groups, the user will receive notifications daily.
     
  • If the user is in a Group with SPARK enabled, the SPARK Email notification setting is toggled OFF for all groups with SPARK enabled that the user is in, and the user profile setting for Send notifications via email is toggled ON, the user will receive the standard unread email notification template for that unread in-app SPARK notification.
     

  • This unread notification email can be sent as a single notification or grouped with other recent unread notifications.

     

    The user will not receive email notifications if:

  • The user is part of Group(s) where the email notification setting is toggled off for SPARK and the user profile setting for send notifications via email is toggled OFF
  • Or the system wide setting for sending notifications via email is toggled OFF
  • Or the user happens to read their in-app notification before the batch starts for sending out those unread notification emails, they will also not receive an email in that instance.

 

The two Spark emails you can customize

  • Welcome Email - sent when users first gain Spark access. Use it to set expectations and invite users to set their preferences.
     
  • New Spark Email - sent when new nano-learning is ready. Use it to drive quick “watch now” action.

Edit each template at Group Details > SPARK Notifications with Modify Welcome Email or Modify Notification Email.

 

 

 

Using the email text editor

  • Format text: bold, italics, underline, headings, alignment.
  • Lists: bullet or numbered lists for scanable content.
  • Links: insert CTAs such as “Log in to Pinnacle Series”.
  • Images: you may add simple images; for content thumbnails use the placeholder (see below).
  • Tool Link: optional quick-insert menu (if available) for common elements.
     
  • Code View (<>): If you prefer to use your own HTML code click code view and paste in your HTML code. Next click the 'eye' icon to view your code. Always test thoroughly and make sure important placeholder tags are in tact (see below).
     
  • Keep it short: Spark is nano-learning - aim for 60-120 words and a single, clear CTA.

 

Required placeholders; always keep these

Templates include system fields wrapped in square brackets. Do not remove or rename them. You may add your own wording before/after them.

Common placeholders

  • [Assignee] — recipient’s name.
  • [Content-Name] — Spark item title.
  • [Content-Description] — short description.
  • Rule: If you customize wording, keep the placeholders in place so personalization and images render correctly.

 

Troubleshooting & tips

  • Personalization missing? Confirm placeholders weren’t removed or altered.
  • Layout looks off? Reduce complex HTML; rely on inline styles and simple tables.
  • Images blocked? Ensure images are publicly reachable and sized conservatively; include alt text.
  • Users not receiving emails? Verify group has Email channel enabled and Spark feature toggled ON.

 

Still Need Help? 

Log a support ticket