Brand Loyalty Survey Template
Track loyalty the way you manage it: as a repeatable, comparable tracker. Use this brand loyalty survey to measure repeat intent, preference, switching risk, and advocacy, then segment results so you know where to act. The guide below helps you choose NPS vs CSAT vs CES, field the survey to the right groups, and score results into a trend-ready scorecard.
Trusted by 5000+ Brands
When to Run a Brand Loyalty Survey (3 High-Value Moments)
Use this section to pick your send timing so you can track loyalty shifts and tie them to real events.
Default: Run a stable tracker quarterly (or monthly if you have high volume).
Customize it by adding event-specific question modules - but keep your core loyalty questions unchanged across waves. Timing examples below are starter targets; adjust after your first wave based on response patterns and your buying cycle.
Recurring brand health tracking (monthly/quarterly)
Send on a fixed cadence so you get a clean trend line for repeat intent, switching risk, and advocacy. Do this: keep the same core question wording and scales every wave so you can compare results without re-benchmarking.
Right after a key experience (purchase, delivery, support)
Send a pulse after a meaningful touchpoint so you can connect experience performance to loyalty outcomes. Starter target: trigger an email 1-3 days after delivery (or within 24-48 hours after a support case closes), then add a short CSAT/CES insert specific to that interaction.
Before/after a major change (pricing, policy, redesign, rebrand)
Run a baseline before the change, then repeat after rollout to detect loyalty impact. Starter target: re-field about 2-4 weeks post-launch (earlier for high-frequency products, later for longer repurchase cycles). Do this: keep your core tracker stable, and add a small module about the change (clarity, fairness, perceived value) so you know what moved.
Next step: decide who you will survey - active, repeat, and lapsed customers need separate cuts.
Who to Send This To (Active vs Lapsed, and How to Avoid a Biased Read)
Use this section to choose your audience so your loyalty read is credible and actionable.
Default: Survey active customers and lapsed customers in the same program, then report them separately.
Customize it by defining "active" and "lapsed" for your business - but keep those definitions fixed while you trend.
Build your sample (and keep it comparable)
Sampling: start from a complete customer list (not just one channel) so you avoid over-surveying your happiest segment. Do this: pull from your CRM/order table and include every eligible customer, then stratify by key cuts (channel, tier, region) if needed. If you need a refresher on setting up an unbiased sampling plan, align your list rules before you invite anyone.
- Active customers: people who purchased or used the product within your "active" window (for example, last 30/60/90 days). Use this group to track brand-level loyalty outcomes and drivers.
- Repeat customers: people with 2+ purchases or renewals in a defined window. Use this group to validate that "loyalty" scores line up with repeat behavior.
- Loyalty members/subscribers: people enrolled in a program or on auto-renew. Use this cut to spot program friction (benefit clarity, redemption effort, perceived value).
- Lapsed customers: people who used to buy but have stopped (for example, no purchase in 6 months). Use this group to measure switching risk and collect churn reasons.
Do this to avoid a biased read
- Don't sample from one "happy" touchpoint: avoid only post-support surveys or only app users if you sell in multiple channels.
- Track invitations and completes by segment: report response rates by channel/tier so you can see who is under-represented.
- Use branching instead of a second survey: ask the same core loyalty outcomes first, then branch lapsed customers to a short "why you stopped" module.
Do this: watch for systematic differences between people who answer and people who do not (channel, tier, tenure, spend). Research shows response rates alone do not reliably predict nonresponse bias, so focus on who is missing, not just how many are missing, as summarized in Groves and Peytcheva's meta-analysis on nonresponse rates and nonresponse bias.
Next, pick the metric you will trend every wave - NPS, CSAT, CES, or a combo.
Choosing the Right Metric: NPS vs CSAT vs CES (and How to Use Them Together)
Use this section to pick the metric(s) you will trend and what each one will drive in your action plan.
Default: Trend NPS (advocacy) at the brand level, and use CSAT/CES as touchpoint diagnostics.
Customize it by adding one diagnostic metric per key journey step - but keep your primary trend metric consistent.
How to use this table: Choose one "headline" metric for your executive scorecard, then add one diagnostic metric only where you can act on it.
| Metric | Best for | Where it fits | Pros | Watch-outs | Use together (without double-counting) |
|---|---|---|---|---|---|
| NPS (recommend) | Tracking advocacy and referral potential | Brand-level tracker (quarterly/monthly) | Simple headline; widely understood; good for a single trend line | Does not tell you what to fix; can move slowly in mature categories; and it is not always a better predictor than other loyalty metrics (treat it as one indicator, not the whole program), as discussed by Keiningham et al. in their longitudinal evaluation of NPS vs growth. | Keep NPS as the outcome, then use CSAT/CES as drivers by touchpoint. If you need background on the original NPS framing, see Reichheld's Harvard Business Review article on NPS. |
| CSAT (satisfaction) | Grading a specific interaction | Touchpoint survey (checkout, delivery, support) | Directly tied to a team and workflow; easy to act on | High CSAT can coexist with weak preference; ceiling effects are common | Use CSAT as a diagnostic insert after a key event, then link it back to repeat intent or switching risk in analysis. |
| CES (effort) | Finding friction that suppresses loyalty | Journey step diagnostics (returns, onboarding, issue resolution) | Pinpoints process fixes; often moves faster than brand perception | Best asked right after the task; not a brand-level substitute | Use CES to prioritize friction removal, then check if switching risk drops in the next wave. For the "reduce effort" argument, reference Dixon et al.'s Harvard Business Review article on customer effort. |
Simple decision rules
- If you need a brand-level advocacy trend line, use NPS as the headline metric.
- If you are fixing a specific experience, use CSAT right after that touchpoint.
- If you suspect process friction is driving churn, use CES right after the task.
Next: lock your core questions and scales so your tracker stays comparable.
Deployment and Customization Best Practices (So Your Tracker Stays Comparable)
Use this section to lock your survey setup so each wave is comparable and easy to act on.
Default: Keep a small, fixed core (outcomes + key drivers) and rotate optional modules.
Customize it by adding modules for specific events - but keep your core wording and scales fixed across waves.
-
Freeze the core tracker: Keep your repeat intent, preference, switching risk, and advocacy questions unchanged. Use the same response options and the same Likert scale labels every wave so trend shifts mean something.
-
Use modular blocks (swap in, not rewrite): Add optional inserts for CSAT/CES, competitive context, or a one-off change (pricing/policy). Keep inserts short (3-6 questions) so completion stays stable.
-
Branch for lapsed customers: Ask the same core outcomes first when possible, then branch lapsed customers to churn reasons (price, availability, quality, service, "found a better alternative"). Report active vs lapsed separately so you do not average away risk.
-
Keep wording neutral: Avoid leading language ("How great was..."). Use simple time frames ("in the past 30 days") so customers answer the same question each wave.
-
Minimize PII and set expectations: Ask only what you will use (tier, tenure band, channel). Add clear consent and privacy language before any contact details.
-
Plan outreach, reminders, and incentives: Send from a recognizable sender, keep the invite short, and schedule 1-2 reminders to non-responders. If you use incentives, keep them consistent across waves; a randomized trial in Smith et al.'s study on incentives and follow-up to increase response rates found both can improve participation.
-
Document your field rules: Record who was invited, channel, dates, reminder cadence, and exclusions. Keep a simple "wave log" so leadership trusts the trend line.
Now score the outcomes and turn them into segments you can manage.
How to Score and Analyze Brand Loyalty Results (Segments, Drivers, and Trends)
Use this section to turn raw answers into loyalty segments, driver priorities, and a trend-ready scorecard.
Default: Report top-box rates and a 3-segment loyalty view (Loyal/At-risk/Likely to switch).
Customize it by choosing the segments your teams can act on (tier, channel, tenure) - but keep the segment definitions stable across waves.
-
Score your core outcomes the same way every wave
Do this: compute top-box % (and optionally top-2-box %) for repeat intent and preference items, plus switching risk % (for example, % choosing "likely to switch"). Keep your scoring rules fixed so you can compare month-to-month or quarter-to-quarter.
-
Create simple loyalty segments you can manage
Do this: use repeat intent + switching likelihood to assign customers to three groups:
- Loyal: high repeat intent, low switching likelihood
- At-risk: medium repeat intent and/or medium switching likelihood
- Likely to switch: low repeat intent and high switching likelihood
Interpretation: if "At-risk" grows while NPS stays flat, you are building hidden churn pressure.
-
Trend the right cuts (and keep them consistent)
Do this: trend outcomes by tenure (new vs established), purchase frequency, loyalty tier, and channel. Choose 3-5 cuts you will always report, then add one rotating cut when a business question changes.
-
Prioritize drivers with a lightweight analysis
Do this: start with correlations between key drivers (value, quality, trust, service, convenience) and your outcome (repeat intent or NPS). If you need a stronger read, run a simple regression with the outcome as the dependent variable and driver items as predictors.
Interpretation: treat this as a prioritization tool (association, not proof). Keep models simple, avoid throwing in dozens of overlapping predictors, and sanity-check results across waves; overfitting is a common failure mode in regression-type models (see Babyak's accessible overview in the Journal of Clinical Epidemiology).
Interpretation: act on the drivers with (1) strong relationship to loyalty and (2) low current scores.
-
Use open-ended answers to explain "why," not to replace scoring
Do this: place open-ended prompts after the rating questions, and keep them specific ("What is the main reason you might switch?"). Expect more skipping on open-ends than on rating questions, so treat themes as directional and validate them against your scored drivers.
Next: package results into a one-page scorecard (headline metric, segments, and top drivers).
Frequently Asked Questions
How often should I run a brand loyalty survey?
Default: run it quarterly so you can track a clean trend line without over-surveying. If you have high purchase volume, run monthly; then add event-triggered pulses after a pricing change, policy change, or redesign. Keep the core module consistent and use optional inserts for one-off diagnostics.
Can I measure brand loyalty with just NPS?
Use NPS to track advocacy, but do not stop there if you need to manage retention. Pair it with repeat intent (repurchase/renewal) and switching risk so you can separate "fans" from "quietly at-risk" customers. Add at least one driver block (value, trust, service, convenience) plus one open-ended prompt so you know what to fix.
Should I survey lapsed customers in the same survey or separately?
Default: keep one survey and use branching so you can compare groups with the same core outcomes. Send lapsed customers to a short churn-reasons block (price, alternatives, service issues) after the shared items. Report active vs lapsed separately, or you will hide churn risk in the averages.
How many responses do I need for reliable loyalty trends?
Do this: plan your sample size around the smallest segment you need to report (tier, channel, region), not just the overall total. For trend tracking, aim for a steady number of completes each wave so movement is interpretable; for segment cuts, prioritize enough completes to see directional change. If your response rate shifts, adjust invitations to keep completes per key segment stable.
What is the difference between loyalty and satisfaction?
Satisfaction tells you whether an experience met expectations at a moment in time. Loyalty adds preference and commitment: repeat intent, willingness to recommend, and low switching risk. Use CSAT/CES as drivers or diagnostics, and keep loyalty outcomes as the headline measures you trend.
How do I report brand loyalty results to leadership?
Do this: share a one-page scorecard with NPS (or your headline metric), repeat intent top-box %, and switching risk %, plus the trend vs last wave. Add the top 2 drivers that explain movement and 2-3 actions with an owner and a due date. Keep the format stable so leaders can scan changes quickly every wave.
Related Survey Templates
FREE TO START - NO CREDIT CARD REQUIRED