> ## Documentation Index
> Fetch the complete documentation index at: https://docs.userpilot.com/llms.txt
> Use this file to discover all available pages before exploring further.
# NPS Settings
> Configure NPS targeting, triggers, frequency, and localization in Userpilot to collect feedback from the right users at the right time.
## Overview
Net Promoter Score (NPS) surveys help measure customer loyalty by asking users how likely they are to recommend your product. Userpilot provides flexible settings to target, trigger, and localize NPS surveys based on user behavior and preferences.
## Targeting an NPS
### **To control where and to whom the NPS survey appears**
1. Navigate to the **Settings** tab. Configure the following:
* **Platform**
1. **Web app:** Select this option to target feedback collection specifically for your web app users.
2. **Mobile app:** Select this option to target feedback collection specifically for your mobile app users.
* **Environment**
1. **Production:** Triggers NPS in the live environment.
2. **Staging:** Enables testing before deploying to production.
* **Domain targeting**
1. **All Domains (Default):** Displays NPS on any site with Userpilot installed.
2. **Specific Domains:**
* **Matches:** Exact domain match.
* **Doesn’t Match:** Exclude certain domains.
* **Matches Regex:** Use wildcards (\*) for dynamic domains.
* **Page targeting**
1. **Any Page (Default):** NPS survey appears across all pages.
2. **Specific Pages:** Show NPS only on selected pages.
3. **Specific URL Paths:** Target NPS based on URL structure.
* **Audience Targeting:**
1. **All Users (Default):** Any identified user can see the survey.
2. **Only Me:** Limits the NPS to your Userpilot account for testing.
3. **Saved Segment:** Use pre-configured user segments.
4. **Custom Conditions:** Define rules based on user attributes, company data, or product usage.
### Triggering an NPS Survey
#### Sampling Rate
Control how often users see the NPS survey:
* **100% Sampling:** Every eligible user sees the survey.
* **Lower Percentages:** Reduces daily exposure for selective sampling.
**How does sampling work?**
Our sampling logic is very simple, it’s based on Probabilistic Sampling method. If an eligible user is going to see the survey for the first time ever, run a **x%** probability to trigger the survey, where **x** is the sampling rate. Please note that users who previously saw the survey before do not fall under sampling rate **(only applicable for NPS)**. They are guaranteed to see the survey after **Y** days based on their previous action (Frequency Settings - Asked Later Vs. Submitted).
In a healthy scenario, the population size shouldn’t be shrinking over time. There are a few aspects to think about:
* There will be new users entering the segment (e.g. new sign ups, changing properties…etc).
* Users who interacted with the survey are guaranteed to see it again after **Y** days.
This should ensure that there is a continuous flow of responses received by new and recurrent users.
**A good NPS strategy requires you to dive into the following aspects:**
* Target an audience with decent app usage to ensure you receive feedback with solid basis. E.g. Signed up more than 30 days, has more than 20 sessions, performed core events, visited pages…etc.
* Ensure that new users are entering audience population over time time. Try to estimate the population increase rate to help you determine the sampling rate (i.e. get daily responses from new users without depleting the population size too fast).
* Determine when it makes sense to ask someone for their feedback again after they already submitted the survey.
* Iterative experimentation with different settings and evaluation of data.
**Here is our general recommendations for NPS settings:**
* Trigger for users who have signed up more than 30-90 days ago.
* Use 10% sampling rate. I verified that they have a healthy inflow and retention of signed up users.
* “After the user submits the NPS survey, after how many days will they see it again?” → 90-180 days.
* If a user clicks ask me later, how many days should we wait until we show it again? → 30-60 days.
#### Behavioral triggers
Trigger NPS based on user activity:
* **Number of Page Visits** before showing the survey.
* **Time Spent on a Page** before triggering the survey.
#### Frequency settings
Adjust how often users encounter the NPS survey:
* **Completed Users:** Defaults to 90 days before reappearing (best practice: 60-90 days).
* **"Ask Me Later" Clickers:** Defaults to 7 days (best practice: 3-7 days).
## Localizing NPS content
**Setting Up Localization**
To accurately localize your NPS content, Userpilot uses a localization parameter:
* If you are passing user properties, use the **locale\_code** property following the ISO 639-1 standard.
* If no property is passed, Userpilot defaults to **Browser\_Language** to detect the user’s browser setting.
## Localization Methods
Switching between Automated and Manual translation will reset any previous translations
### Automated Translation:
1. Ensure locales are added in the **Localization** tab.
2. Select the desired language and click **Auto-Translate**.
3. Edit translations manually if needed.
4. Toggle **Live** to activate the translation.
5. Click **Publish** or **Publish Updates**.
### **Manual Translation:**
1. Fully build your content before enabling manual localization.
2. Export the translation file in CSV or XLIFF format.
3. Enter translations into the **Target** column.
4. Save the file as **CSV UTF-8 (Comma delimited)**.
5. Import the translated file back into Userpilot.
6. Toggle **Live** to activate the translation.
7. Click **Publish** or **Publish Updates**.
.png?fit=max&auto=format&n=4bTZyxkEsWzJ39h7&q=85&s=8f0d805675ba1ff72d4a3605e2867a89)
## Previewing and publishing
1. Click **Preview** to test how the NPS looks.
2. Adjust any final settings.
3. Click **Publish** to deploy the NPS survey.
## FAQs
The best practice is every 60-90 days for completed users and 3-7 days for those who clicked "Ask Me Later."
The translated content cannot be retrieved after switching methods.
* A **green dot** means the translated survey is **live and fully active** for end users.
* A **yellow dot** means the translation is **saved but not yet live**, requiring publishing to take effect.
For any questions or concerns please reach out to [**support@userpilot.com**](mailto:support@userpilot.com)