GCR (Goal Completion Rate)

A user lands on a site, starts placing an order - and leaves at the payment step. Or makes it all the way through. GCR (Goal Completion Rate) is the share of users who reached a target action out of those who had the chance to complete it

It's a metric from UX and web analytics: how many of those who started a task carried it through to the end. It differs from overall conversion - GCR is calculated from those who "started", not from all visitors. In SurveyNinja you can measure GCR through a survey after the target action: you ask whether the user managed to complete the task. Related to conversion rate and abandonment rate.

GCR isn't "how many bought". It's "how many of those who started the purchase process completed it".

Definition

GCR (Goal Completion Rate) is the share of users who reached a specific goal (a target action) out of the number of those who started the task or had the chance to complete it. Formula: (number who completed the goal / number who started or attempted) × 100%. It's used in UX research, usability testing, and web analytics. GCR shows how effective a flow is: if it's low, users "break down" on the way to the goal. Related to the completion rate in surveys - the same "started/completed" logic. More on UX in research.

In short: "how many of those who started reached the finish line" - registration, checkout, setup, form submission.

Formula and calculation base

GCR = (number of users who completed the goal / number of users who started the task) × 100%.

The key point is the denominator. "Those who started" are the ones who clearly began the task: opened the checkout form, navigated to the registration page, started the setup. Not all site visitors. If you count from all visits, that's already conversion rate. GCR narrows the funnel: we look only at those who had the intent and started acting. That makes it clear exactly where the flow "breaks" - before the start or along the way.

Examples of goals

Placing an order - added to cart, started checkout, paid. The goal is payment. Registration - went to the form, filled it in, confirmed the email. Newsletter subscription - entered an email, clicked "Subscribe". Finding information - entered a query, opened the right page. Product setup - opened the settings section, saved the configuration. Filling out a survey - started the survey, submitted the answers. Each goal has its own numerator and denominator. It's important to define them unambiguously.

GCR vs conversion - what's the difference

Conversion is the share of those who completed the goal out of all visitors (or out of traffic). The denominator is broad. "Out of 10,000 who landed, 200 bought - a conversion of 2%".

GCR is the share of those who completed out of those who started the task. The denominator is narrow. "Out of 800 who added to cart, 400 paid - a GCR of 50%". Conversion answers: "how many of those who came bought". GCR answers: "how many of those who started checkout carried it through". Both metrics are needed. Low conversion with high GCR points to a problem in acquisition or first impression. Low GCR with normal traffic points to a problem in the flow, UX, or form.

Why measure GCR

To find drop-off points - where users abandon the task. To assess how effective a flow is - form, onboarding, checkout. To compare variants - an A/B test of two form versions; the higher the GCR, the better. To prioritize improvements - a low GCR at the payment step matters more than at the "choose delivery" step. Benchmarks - industry norms for GCR help you judge whether "things are okay for us". Related to A/B testing - GCR is often the key success metric.

How to measure GCR

Analytics. Events in GA4: "started checkout", "paid". GCR = payments / checkout starts. You need correct tracking setup.

Usability test. You give a task to 10-15 participants: "place an order", "find an article about delivery". You count how many completed it. GCR = completed tasks / participants. A qualitative cut shows where they stumbled.

Survey. After the target action: "Were you able to [do X]?" - yes/no. Or after leaving the page: "Why didn't you complete checkout?" - you uncover the reasons for drop-off. In SurveyNinja you can set up a survey on the "thank you for your order" page - for those who reached the goal, and a pop-up survey when leaving checkout - for those who didn't. Hidden variables pass the stage (cart, payment) - so you can segment the answers.

Common mistakes

Counting from all visitors. Then it's conversion, not GCR. The base is only those who started the task.

A vague goal. "A good experience" isn't a goal. "Placed an order", "subscribed", "downloaded a file" are concrete actions.

Not accounting for repeated attempts. One user may start checkout three times and complete it once. Decide: one user - one fact (reached / didn't reach) or all sessions. For GCR it's more often one session, one outcome.

Mixing tasks. GCR for "place an order" and GCR for "find an article" are different metrics. Don't average them.

Relation to the funnel and abandonment

GCR is essentially a single funnel step: from "started" to "completed". Abandonment rate = 100% - GCR for the same flow. If GCR is 60%, abandonment is 40%. The sales funnel is a chain of steps: landing → catalog → product page → cart → payment. GCR can be calculated for each transition: from cart to payment, from product page to cart. That makes it clear at which step the biggest losses occur.

In SurveyNinja: surveys for understanding GCR

SurveyNinja doesn't calculate GCR directly - it's a metric of on-site behavior. But surveys help: after the target page you ask "Did you manage to [do X]?" - yes/no. The share of "yes" is an analog of GCR for the sample of respondents. For those who didn't reach the goal - a survey on exit: "What stopped you from completing checkout?" - options (price, complexity, error, other). That's how you find the reasons for a low GCR. Integration with analytics and passing events let you link survey answers to behavior.

Benchmarks by industry

GCR norms vary. E-commerce checkout: 60-80% is considered good, below 50% is a reason to dig in. Service registration: 40-70% depending on form complexity. Newsletter subscription: 70-90% - it's a simple action. Multi-step forms (questionnaire, application): 30-50% is a realistic benchmark. Compare with the previous period and with the benchmark for your niche, not with abstract "norms". Long forms always yield a lower GCR - shorten them or break them into stages.

Case study: GCR in checkout

An online store. Conversion to purchase 1.2% - low. They broke down the funnel: landing → add to cart 8%, cart → checkout start 60%, checkout → payment 35%. GCR from "started checkout" to "paid" = 35%. So 65% drop off at the checkout stage. A survey on leaving the checkout page: the main reasons - "expensive delivery" (40%), "confusing form" (25%), "wanted to compare prices" (20%). They simplified the form and added a delivery calculator on the first screen. A month later GCR rose to 48%, and overall conversion to 1.7%.

Relation to customer experience

Customer experience is shaped at every step. A low GCR is a signal of problems: the form is confusing, the process is long, errors aren't explained. Improving GCR is often tied to simplifying the flow, clear error messages, and reducing the number of fields. A customer journey map helps find stages with a low GCR and prioritize improvements.

Mobile and desktop

GCR on mobile is often lower than on desktop: a small screen, awkward input, more distractions. Calculate GCR separately by device. If mobile GCR is 30% and desktop is 55%, the priority is improving the mobile version. Segmentation by segments - new vs returning, by traffic source - gives a precise picture. The same flow can have a different GCR for different channels.

Track GCR over time: week over week, before and after interface changes. A sharp drop is a reason to urgently look at logs and surveys. Steady growth is a sign of successful improvements.

A/B test: you change one element (button, copy, number of fields) and see how GCR changed. Statistical significance is a must.

GCR (Goal Completion Rate) is the share of users who reached a goal out of those who started the task. It differs from conversion in its narrow base. It's used in UX and analytics to find drop-off points. In SurveyNinja - "did you manage to?" and "what stopped you?" surveys for understanding the reasons.