Tip on: Rolling our Sequenced Guide Nurturing Program based on the In-App CTAs/ Buttons

  • 23 July 2020
  • 0 replies

Userlevel 5

Hello PX Tribe!  

I want to share a topic that has been frequently coming up from our customers  and which I think could be useful to this group - How to trigger sequential in-app guides from In-App CTAs/ Button clicks.  

As most of us know, today PX allows us to trigger In-App guides based on "views/ completions" of other guides; however, there is no In-App Audience Rule to trigger based on unique CTA clicks on the In-App Guide.  


But.... we can still do this 🙂  


See below solutions for various scenarios: These can be used for various use cases like Customer Onboarding or Feature Activation or guiding the customer through the Adoption Journey/ Prescriptive Value Path


Scenario 1 - Based on CTA/ Button Clicks on In-App Guide # 1, trigger sequential guides one after another (Using Query Parameter)  


  • Start with an In-App Dialogue with a CTA/ Button
  • In the linked/follow-up In-App Guide >Go to Audience rules > Choose "Query Parameter" Rule > Query Param Name (launchGuideName) -> Add the value welcome.
  • This next In-App Guide would trigger if the user clicked on the button of the first guide, as it matches with the Query Param on your linked guides.

Scenario 2 - Based on CTA/ Button Clicks on In-App Guide # 1, trigger sequential guides after xx days (Using Custom Events).

This method is also preferred in cases where the links are outside of your app, where the PX Tag is not installed.

  • Start with an In-App Dialogue with a CTA/ Button
  • Use Custom Events to track this button click
  • Map it as a feature in the Product Mapper
  • Trigger Guide nurturing program after xx days using the Custom Event or Product Mapped Feature Rule from the Engagement Audience Rules


Scenario 3 - Collect Survey Responses (Eg. User Role) and serve In-App Guide nurturing programs based on the Ideal Customer Profile (ICP) (Using PX Rest API)


 This community post here from @link_black is a great, detailed explanation to achieve the above. Note, the post talks about SFDC Integration, but this use case can be achieved without it as well.  Please let me know your thoughts/ questions/ any other ideas.

0 replies

Be the first to reply!