Membership Conversion is 0 or 100?

George_SST
New Contributor III

We are having an issue with membership conversion rate reporting only being 0% or 100%.  We only offer auto renewal memberships, is this metric for renewals due?  Is there a way to accurately track how frequently we sell a new membership vs non-member visits who do not join?

1 ACCEPTED SOLUTION

Cortney_SPUD
ServiceTitan Certified Provider
ServiceTitan Certified Provider

Your tag name show as "Potential Mem."  Has it always been called that?  ServiceTitan looks for tag name "Potential Member" when counting membership opportunities.  The name "Potential Mem" would cause those jobs to not be counted as membership opportunities at all, and therefore not missed opportunities.

View solution in original post

4 REPLIES 4

Cortney_SPUD
ServiceTitan Certified Provider
ServiceTitan Certified Provider

George_SST - Yes, the membership conversion metric considers NEW memberships and RENEWED memberships.  The calculatin is based on your Tags.  If you don't want to count your membership renewals in that metric, you could edit your membership renewal tag so that it is not a conversion opportunity (see image).  If you uncheck the 'conversion opportunity' box for the membership renewal tag, the renewals won't be counted at all in your membership conversion metric (neither as opportunities nor as wins).membership_conversion.png

We do not do any renewals, only auto renewing memberships or non member customers.  We have a tag that is a conversion opportunity for the Potential Members but it does not seem to count them as a missed opportunity.

George_SST_0-1692648156269.png

 

Cortney_SPUD
ServiceTitan Certified Provider
ServiceTitan Certified Provider

Your tag name show as "Potential Mem."  Has it always been called that?  ServiceTitan looks for tag name "Potential Member" when counting membership opportunities.  The name "Potential Mem" would cause those jobs to not be counted as membership opportunities at all, and therefore not missed opportunities.

Thanks, that was the issue!