Skip to main content

Hi everyone,

I’m hoping to get some insight or suggestions from others who may have tackled a similar challenge.

Background

Our team previously used an in-house tool to display persistent messages via a ribbon at the top of our web app. These messages:

  • Lasted for a set period (typically two weeks)
  • Included buttons, CTAs, or a dismiss option
  • Reappeared on the homepage until dismissed or expired
  • Could be queued and prioritized (e.g., P2 shows after P1 is dismissed)

This approach was lightweight, non-intrusive (inline div), and respected user interaction.

Transition to PX

We’ve since adopted PX and want to replicate—and ideally enhance—this functionality using PX’s audience targeting and tools. However, we’re running into a few issues:

  • We need to maintain a non-blocking UI (no overlays, modals, or banners)
  • Users should be able to dismiss or revisit messages intentionally
  • Stakeholders dislike how PX guides can be dismissed by pressing Escape or clicking outside the guide (even though we’ve already used CSS to remove the close buttons)

To clarify: we still plan to use guides and dialogs where appropriate—especially for onboarding, walkthroughs, or more complex flows. But for lightweight, persistent announcements, emergency messaging, or CTAs, we want a more subtle, inline approach that doesn’t interrupt the user experience.

Current Approach

Right now, the only way we’ve found to replicate this is by:

  • Using an inline div while employing functions of the v1 editor (does not work with v2 from my understanding)
  • Manually adding custom buttons and events
  • Tracking dismissals via custom onclick events

This works—but it’s extremely manual. For every new message, we have to clone, reconfigure buttons, and set up new events.

The Ask

Is anyone aware of a more scalable or streamlined way to implement persistent messaging in PX that:

  • Doesn’t require all the manual setup for each message
  • Still respects user dismissals
  • Keeps the UI clean and unobtrusive?

We’re also expanding our Gainsight ecosystem:

  • Currently exploring Gainsight CC
  • Planning to implement Gainsight CS soon
  • Already using Skilljar for training and enablement

As the sole admin managing a platform with 100k+ users and multiple ongoing initiatives, this process is becoming a bottleneck. We’re eager to go all-in with PX, but the current friction is slowing us down.

Any advice, workarounds, or examples would be hugely appreciated!

Thanks in advance

Thanks for posting to PX Community ​@tyler.long!

 

I am surely interested to hear what other customers have done, but for this use case I would suggest moving to a single step Guide … the WYSIWYG editor is very much improved in Guides compared to the standard Dialog Engagement type. 

 

That Guide step can be displayed as a banner or dialog in a non-obtrusive way, plus you can use the Automation Settings for the Guide to have it delay to show and even go away after displaying for a few seconds or more, which is nice.  

 

You may also want to consider using Badges for some of these Engagements too, plus the Snooze button and Intervals Qualification Scope settings as needed. 

 

You may find some good ideas here too.

 

Happy PX-ing!!!

 

 

Terms & ConditionsCookie settingsAccessibility statement