Topics started by harshibanka
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 Make the buttons <a href=“https://app.aptrinsic.com/dashboard?launchGuideName=welcome” />. In www the are a couple of
Gainsight is joining Product-Led Hub Growth Academy this week. If you’re a Product Leader, Product Manger, Customer Marketing, Customer Adoption, a Customer Success Manager or a PX Customers, check out these sessions from our product experts: (Mention "Gainsight" as you sign up when asked how did you find us) Tuesday (12:00 pm PST): Creating the ultimate PLG strategy with @mickey [free]https://lnkd.in/gihcC5s Thursday (12:00 pm PST): Product-led growth for B2B with Yariv Zur from Anodot [free]https://lnkd.in/gv2hGNz Thursday (1:00 pm PST): Tech Touch Onboarding with Gainsight PX Harshita Banka [free]https://lnkd.in/g2Z6HFh Friday (12:00 pm PST): How to Drive Sustainable Adoption with Gainsight PX with Sarah Anderson from Email on Acid [free]https://lnkd.in/g-jMuRn Product analytics & instrumentation with @mickey [Paid]https://lnkd.in/eEHcWKp
Hi PX Peers, I trust this post will find your family and you in good health and spirits. I am sharing a few assets that Gainsight has produced which relate to product experience and will be relevant to anyone in the space (Product Leaders/ PMs/ Customer Adoption, etc). Please do share this with your product team as I think they will find this useful. Also, if there are any other products-related topics that you want to see/contribute content on any topic. Let us know what you think. Product Experience Webinars: How to Discover and Define Your Power Users Tuesday, April 14 | 11:00 a.m. PT Product Experience + Customer Success: Better Together, Now More Than Ever Wednesday, April 29 | 11:00 a.m. PT Powerful Product Positioning During Times of Economic Volatility Wednesday, April 29 | 8:00 a.m. PT Pulse Conference on 05/13 AND 05/14, details of the session/speakers of the “The Data-Driven Product Leader” 5 Human-First Product Management Considerations to Make During COVID-1 How to P
One of our PX Customers - Al Bsharah, VP of Product Strategy @ Seismic shared on Medium the process he follows in finding, buying the implementing the right tools in his 20 years of tech experience. The key take-aways, to read more, you can visit this link: Commit to your process, until the tool is absolutely necessary Select and commit to the tool evaluation process Build a shortlist and dig into the technologies Decide on — and commit to — the tool that wins Being one of Al’s vendors, we clearly passed this test of his ;) thanks for acknowledging Gainsight!
Whenever thinking of an Engagement, start with (you could even create a calendar, see pic below): Objective/ Problem Statement (Why) Metrics Improved (Why) Storyboard/ Engagement Type (What) Audience (Who) Duration (When) Using this Framework has the following benefits: Objectivises the need of an Engagement hence eliminating the ones not really needed Quanitfies the desired impact of an engagement Simplifies defining the audience criteria and rules Provides visibility to multiple teams into the planned engagements Enables various teams plan engagements in a way to avoid duplication/ overwhleming users with too many engagements
While there are multiple factors to be considered when launching an in-app Guide like launching it at the right time, at the right place and when the user needs it and making it more contextual based on the analytics, a quick addition which makes a motivating for the users to start/ navigate through a guide is knowing right off the bat- "how long is this guide/ tour!" In a multi-step Guide, "add steps in the title" (or place it whever you like) in each modal to make it obvious and motivating for the users to navigate through your guides until completion. Knowing how many steps are involved and being able to the progress made/ how much is left is always more exciting and motivating. For eg: <Step 1/5> Start KC Bot Integration <Step 2/5> Choose your integration so and so forth (see screenshots below) Let me know what you think.
While creating In-App Engagements, for the most part, you would want to test them before launching them to your users on Production. You may test your In-App Engagements in either of the following ways: If you have PX Tag installed on your non-production environment, you can create and test engagements on the Non-Prod environment; Or; Use “Preview” by going to Engagements> Editor> Edit in-app> Click on Preview (this will launch the engagement on your web app only as a Preview to you); Or; Create a Segment>Add Internal users who will be testing the engagement> Go to Create Engagement> Audience> Choose ‘Segment’ from the list of Trigger Rules available on the right> Choose your Test User Segment> Trigger the engagement with other criteria in place only to Test Users; Or; Go to Create Engagement> Audience> Choose ‘User’ from the list of Trigger Rules available on the right> Choose email attribute from the dropdown available> Set yo
You can use Retention Analytics and its different metrics to drive retention and growth. The ideal retention graph looks like a smile (curves back up) as customers re-engage over time. Following are some tips to focus on, to increase retention and strive for the smile effect :) 1. Identify Product Growth Opportunities by: -Reviewing User retention for each segment of users -Reviewing different usage patterns and identify the ideal customer segment 2. Discover Product-Market Fit by: - Aiming for a flattened retention curve over time - Avoiding Line trending towards zero as this leads to a Leaky bucket problem thereby indicating that users are not realizing value through your product 3. Identify users with best retentions and view their product journey by: - Using the Cohort Analysis metric - For the above cohort, look out for feature adoption and common characteristics Armed with all this information, you now can introduce personalized product experiences to guide all users
If you are attending Pulse'19 and are a PX Customer or looking to be one, we have a PX Workshop on 05/23 @ 10:30 a.m. in Room 2002 @ Moscone Centre covering the following agenda: PX Team Intro's + Ice Breakers 7 Principles ofr Product-Led Growth Strategy PX Product Plays in PX Product + Customer Success are #BetterTogether Introducing PX Community Q&A For a live demo, please visit the PX Booth!
Join Gainsight's VP of Product and VP of Product Growth as they answer your burning questions on building products that drive growth on May 17th, Friday @ 10 a.m. over a Webinar. Consultants cost money. Quora is a wildcard. What if you could get honest answers from trusted product professionals who’ve been in your shoes? Well, you’ve come to the right place. Join Gainsight's VP of Product and VP of Product Growth as they answer your burning questions on building products that drive growth.
Don't you think PX's Product Tree is a very cool model to track different areas of your product in an efficient way?
Why Product Hierarchy is the right model for your product tracking/analytics? We recommend instrumenting your product using a product hierarchy model as opposed to a flat/one-level model. This allows you to maintain a more sustainable/scalable tracking strategy without getting lost in hundreds of tagged features, as your product matures over time. This can be done by creating main modules, sub-modules and nesting features underneath. Some of the key benefits are: Product Tree/ Hierarchy: Eliminates the need for long/confusing names by having to rely on naming conventions Accurate and reliant Data as it eliminates: Double-counting due to a repetition of features in the flat/ one-level model and Unreliable statistics/data source caused by infinite feature list in a flat hierarchy. Unambiguous context on each distinct feature/sub-module/module. For example: Filters may be present on multiple pages. With the Product Tree model, one exactly knows whether it is Home > Dashb
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.