Skip to content

Profile properties

Gro keeps a few custom properties on every subscriber’s Klaviyo profile. They let campaigns and segments use subscription details even when there is no event, for example “everyone with an active subscription” or a referral link in a newsletter.

Every property starts with gro_, so they never clash with your own.

Property Type What it holds
gro_has_active_subscription True/False True when the customer has at least one active subscription
gro_active_subscription_count Number How many subscriptions are active
gro_paused_subscription_count Number How many subscriptions are paused
gro_cancelled_subscription_count Number How many subscriptions are cancelled or expired
gro_referral_code Text The customer’s referral code, such as REF-7KQ2XM. Only when referrals are on
gro_referral_link Text The customer’s referral share link. Only when referrals are on
gro_credit_balance Number The customer’s store credit balance. Only once they’ve had credit
gro_credit_currency Text The currency of that balance, such as AUD
gro_portal_token Text Signs the customer into their portal from a link you build. Lasts 60 days and is refreshed weekly

A subscription whose payment failed and is being retried still counts as active. Once retries run out it is cancelled.

  • On every subscription event, for the customer the event is about.
  • Weekly, for everyone with a live subscription or one cancelled in the last 180 days. This keeps gro_portal_token fresh for customers who haven’t had an event in a while.

Test events never set these properties, so sample data can’t overwrite a real customer.

Build segments in Klaviyo with Properties about someone:

  • Active subscribers: gro_has_active_subscription is true
  • Paused, nothing active: gro_paused_subscription_count is greater than 0 and gro_has_active_subscription is false
  • Lapsed subscribers to win back: gro_cancelled_subscription_count is greater than 0 and gro_has_active_subscription is false
  • Multi subscription customers: gro_active_subscription_count is greater than 1

Then leave active subscribers out of a “subscribe and save” campaign, or send a win back offer to lapsed ones.

Campaigns have no event, so use the person fields.

A referral ask in a newsletter. Show it only to customers who have a link:

{% if person.gro_referral_link %}
Share {{ person.gro_referral_code }} with a friend and you both get a treat:
<a href="{{ person.gro_referral_link }}">{{ person.gro_referral_link }}</a>
{% endif %}

A link that signs them into their portal. Replace yourstore.com with your store’s domain:

<a href="https://yourstore.com/apps/gro/portal/link?token={{ person.gro_portal_token }}">
Manage my subscription
</a>

The subscription counts, referral code, referral link and credit balance are also saved on the customer’s Gro profile as custom properties, under the same names. Use them in Gro segments and merge tags, for example {{ person.properties.gro_referral_link }}.