The post purchase survey (PPS) is launched in Qualtrics via Salesforce. Currently, any time a sales assisted contract is confirmed in Salesforce, Qualtrics is triggered to send out a survey to the customer contact on that subscription. The feature list in Qualtrics is maintained via monthly issues which leverage the feature by tier page. The feature by tier page is auto generated from features.yml. The quarterly scores from the PPS read-outs below flow into features.yml via the process outlined here, which is owned by Product Operations. We are working on flowing web direct and renewal subscriptions into this survey as well in FY22.
PPS
dataIt is important we keep pricing related data in features.yml
up to date because it affects pricing decisions and auto-generated pages that are referenced across various teams at GitLab, including Product Pricing, Marketing and Sales. Post-purchase survey (PPS) data is taken monthly via Qualtrics. The output should come in the form of a spreadsheet which should look something like this (internal only) and is shared out via the quarterly analysis issues.
In that spreadsheet, the feature
column matches to a feature in data/features.yml
. That's what needs to get updated. There are two fields which we are updating here:
pps_aggregate
represents the total of all PPS scores from all time.pps_recent
represents the most recent PPS result. If a feature is not listed in the results, the "recent" value should be marked as 0
.Every feature in features.yml
should have both entries. If it's a brand-new feature, it hasn't been surveyed in a PPS yet, the values are still zero.
data/features.yml
pps_aggregate
value to match that new value.features.yml
, find-and-replace all the values to zero. In an IDE, you can use a regular expression like pps_recent: \d*
and replace it with pps_recent: 0
.pps_recent
value to match that new value.Submit your MR, and merge! To see a sample, check out the diff in the FY22 Q1 update MR here.
## Post purchase survey
PNPS
users