Configuring and testing across different environments
In our setup, we have Development, Staging, Production, etc environments.
In Pendo, we can see the Draft, Staging, and Public states of the guide. And also, there is a Staging setting where we can specify domains enabled for the staging state.
Is there the same setup for the production?
Expectation:
1. Environments:
- Development: dev.domain.com
- Stage: stage.domain.com
- Production: www.domain.com
2. Guide page rule: //~contains:domain.com/**
3. Staging setting:
- dev.domain.com
- stage.domain.com
4. Missing:
- we need to be able to specify production domains, so we can move the guide across different environments
- to have a metrics breakdown by domain
p.s. I read Staging, but I feel like I'm missing how to use it properly
0
Comments
Hi Dmitry Reshetnik - thank you so much for your thoughtful breakdown here!
Setting up the Staging list for testing your guides is the correct way to go about it. For clarity, here is what will happen:
1) You identify your Staging environments for the Staging list
2) Test the guide by moving the guide status to "Staged"
3) Once you are ready for the guide to be live to your visitors, move the guide to "Public". This will then post the guide everywhere Pendo is installed (including Production).
You don't need to identify a "Production list" because Pendo assumes everything is Production outside of your Staging list.
If you'd like to see the metrics by domain, you can do so by creating a segment withe rules "Last Server Used equals production.environment.com (or whatever the domain is)"
Also, if you DON'T want to see data that is coming from your lower level environments ever, you can add those Dev and Staging domains to the "Exclude List". That means you won't have to create a segment, Pendo will just hide the data automatically.
Hope this helps - please feel free to reach out if you need more help!
thank you for the detailed explanation.
we decided to move with a solution similar to this (if someone has the same question):
1. Pre-requisites:
- 2 domains: dev.domain.com, www.domain.com
- Staging setting is configured for the dev.domain.com
- development segment Everyone Non-Production that has a rule Server is not equal to www.domain.com
- production segment Everyone Production that has a rule Server is equal to www.domain.com
2. Development:
- use a generic domain rule for guide pages e.g.: //~contains:domain.com/<whatever-you-need>. This enables guide on all enabled domains, so no reason to have multiple guides setup, etc.
- use Draft / Stage states of the Guide for the development and Everyone Non-Production segment
- optionally, setup a specific Staging domain e.g. (feature-branch.domain.com) for the testing in lower environments.
3. Release
- change the segment to the Everyone Production
- make the guide Public
As result, once the Guide is released, all metrics are shown for the production segment.
Please sign in to leave a comment.