What a trial-pass conversion rate misses when passes are shared

Published November 4, 2026

The conversion percentage that starts with a blurry denominator

A studio gives out trial passes at a community event, through a partner, or as a digital offer. Weeks later someone asks how many passes turned into memberships. The platform produces a number, the number goes into a report, and the report implies that the studio knows which acquisition effort worked. Often it does not.

The trouble is not the arithmetic. It is the denominator. A trial pass can be issued to one person and redeemed by another. It can be shared inside a household, forwarded to a friend, or used twice under two profiles. It can be counted as a lead, a visit, and a redemption at the same time, or it can expire without anyone recording that it was never opened.

This note describes a measurement review a fitness virtual assistant can prepare for a studio manager. It does not propose an industry conversion benchmark. It proposes a way to define the trial-pass population, separate the buyer from the redeemer, and publish a rate whose denominator can be reconstructed when someone asks how it was built.

Decide what counts as a trial pass

Before exporting anything, write down the object being measured. A trial pass may be a printed card, a promo code, a one-week app entitlement, a guest visit linked to a member, or a free class booked through the schedule. These are not interchangeable. A printed card can be handed to a stranger. A promo code can be posted publicly. A guest visit is usually tied to the member who invited the guest.

Choose one object and one issuance event. Record the date the pass was issued, the channel that issued it, the campaign or partner if one exists, and the identifier the platform uses. If the studio uses several pass types, report them separately before combining them. A blended rate across a printed card and an app entitlement will hide more than it explains.

Decide whether a pass is counted once per issuance or once per person. A household that receives one pass but sends two people is a different case from two separate issuances. The measure should state which rule it uses. Without that statement, two managers can calculate different rates from the same export and both believe they are right.

Separate the buyer from the redeemer

The person who receives a pass is not always the person who uses it. A parent may take a pass for a teenager. A member may give a guest pass to a training partner. A workplace may distribute a batch of passes to employees. In each case, the acquisition event belongs to the recipient of the issuance, while the attendance event belongs to the person at the door.

Keep two identifiers: the pass holder and the attendee. If the platform only stores one, use the booking or check-in record to identify the attendee and link it back to the pass. Do not overwrite the pass holder with the attendee. The comparison between the two is the evidence that sharing occurred.

This separation matters for follow-up. A studio that calls the pass holder about a membership may be calling someone who never visited. A studio that calls the attendee may be calling someone who never received the original offer and has no context for the call. The assistant should know which person is which before drafting any message.

It also matters for counting. If the same pass is redeemed by two people, the pass-level conversion rate can exceed one hundred percent. That is not a data error in every case; it may be a real sharing pattern. The report should say so rather than capping the result at a number that looks tidy.

Build a redemption table before the conversion rate

Start with a table of issued passes, not a table of memberships. Each row should carry the pass identifier, the issue date, the issue channel, the pass type, the expiration date, the pass holder identifier, and the household identifier if one exists. Add columns for the first redemption date, the attendee identifier, the number of redemptions, and the membership outcome with its date.

Build the table from the issuance record, then join the redemption and membership records. Do not build it from the membership list, because that list only contains people who converted. A rate calculated from converters alone describes the people who already said yes, not the population that received an offer.

Keep the join keys explicit. If the platform uses a different identifier for a lead, a member, and a booking, write down which key was used at each step. A join that relies on a phone number will merge family members, and a join that relies on a name will split people who share one. Neither failure is visible in the final percentage.

Record the extraction date and the data window. A pass issued near the end of the window has less time to convert than a pass issued at the start. Comparing the two without accounting for exposure time is one of the most common ways a trial-pass report misleads.

Treat shared households and duplicate profiles explicitly

Shared households are normal in fitness. Couples, parents and teenagers, and roommates often appear under one billing account. A household-level report can be useful for account conversion, but it is not the same as a person-level report. State which level the rate uses and keep the other level available beside it.

Duplicate profiles are also normal. A person may create a new profile when booking a trial, then create another when joining. The membership record and the trial record can point to different identifiers for the same human. Before merging, compare the contact details, the birth date if it is held, and the visit history. Do not merge on name alone.

The NIST Privacy Framework is useful as a structure for limiting the data used in this review to what the question requires. The review does not need payment details, health information, or full contact histories. It needs enough identifiers to link issuance, redemption, and membership without turning the report into a profile of every visitor.

If the studio cannot resolve duplicates reliably, report the uncertainty. A rate with a stated duplicate range is more honest than a precise number built on a merge that nobody can reproduce. The Small Business Administration's guidance on managing business records supports the same discipline: keep the source records and the method, not just the final figure.

Compare cohorts on the same redemption window

A trial pass needs time to be redeemed and time for a redemption to become a membership. Define both windows before comparing groups. For example, count redemptions within fourteen days of issuance and memberships within thirty days of the first redemption. Write the windows down and apply them to every cohort.

If the studio changes the window, the rate will move even if behavior did not. Mark the change on the trend line. A report that silently switches from a thirty-day window to a ninety-day window will show improvement that may be entirely an artifact of waiting longer.

Compare like with like. A pass issued at a paid community event may reach a different population than a pass offered inside the studio to existing members' guests. A digital code may be redeemed by people outside the studio's service area. These groups can be reported separately without claiming that one channel is better in general.

Report the number of passes behind each rate. A channel with twelve passes and one conversion is not comparable to a channel with four hundred passes. When the counts are small, show the counts and say that the rate is unstable. Precision without exposure is a false comfort.

A trial-pass conversion rate describes the passes in the frame during the window. It does not prove that the pass caused the membership, that the channel is efficient, or that the staff did a good or bad job. People join for reasons that the pass record cannot see: a move, a new job, a friend's invitation, or a class schedule that finally fit.

Look for the largest source of difference before drawing a conclusion. If redemptions rose but memberships did not, the issue may be the follow-up after the first visit rather than the pass itself. If memberships rose without more redemptions, the studio may be converting existing leads and attributing them to a pass they never used.

Keep the member conversation out of the aggregate report. Use counts and case keys, not names. If a manager needs to review a specific case, keep that file separate and restrict it to the roles that need it. The Federal Trade Commission's guidance on protecting personal information is a reasonable baseline for deciding what belongs in the aggregate and what does not.

Limits and sources

This note is a measurement method, not a claim about typical studio performance. The American College of Sports Medicine publishes professional resources on exercise science and health fitness, but it does not provide a universal trial-pass conversion benchmark for a single studio. The Centers for Disease Control and Prevention publishes physical activity guidance for the population, not pass redemption rates for gyms. The Small Business Administration offers general guidance on managing business records, which supports the documentation discipline described here but does not define a fitness metric. The NIST Privacy Framework and the Federal Trade Commission's privacy guidance inform the data-limiting choices in this review, not the conversion definition itself.

Use the method as a local protocol. Adapt the pass types to the studio's booking system, write down the version you used, and keep the issuance and redemption evidence with the case. A defensible rate is one whose denominator can survive a change in staff, a platform migration, or a manager's question six months later. A rate that cannot be rebuilt is only a number that happened to appear on a slide.