Segmenting Customers by Inveterate's Membership Custom Attributes in Attentive

Once your integration is enabled, Inveterate automatically syncs important membership data (like membership status, current credits balance) to the corresponding Subscriber profiles in Attentive, using the Custom Attributes API. Among other things, this allows merchants to segment their subscribers based on membership data.

Custom Attributes List

Name	Description	Examples	Template Syntax
Inveterate: Credits	Number of credits available	24.99, 25, 1.4, 0	{{subscriber.custom['Inveterate: Credits']}}
Inveterate: Credits F	Credits value formatted for use in texts and email	$24.99, $25, $1.40 $0	{{subscriber.custom['Inveterate: Credits F']}}
Inveterate: Date Joined	Date customer joined membership program.	"March 14, 2023"	{{subscriber.custom['Inveterate: Date Joined']}}
Inveterate: Referrals Count	Number of times customer has been credited for program referral	2	{{subscriber.custom['Inveterate: Referrals Count']}}
Inveterate: Subscription Status	Status of membership	"active", "cancelled", "pending cancellation"	{{subscriber.custom['Inveterate: Subscription Status']}}
Inveterate: Tier Name	Tier name	"Gold", "Acme Plus"	{{subscriber.custom['Inveterate: Tier Name']}}

Segmenting Attentive Subscribers by their Membership Data

You can create "Dynamic segments" of customers based on the Custom Attributes Inveterate sends over.

Here are some examples:

When creating segments that use a text based value, such as "Subscription Status = ACTIVE", or "Tier Name = Paid Tier 1", you need to copy and paste the values exactly as they appear within the Attentive subscriber detail page. For example, "Subscription Status = ACTIVE" needs to be in all caps just like on the subscriber detail page, if you format the value as "Active" or "active" the segment will not populate. See the screenshot below for an example.

Be aware that because Attentive doesn't offer formatting options for template variables, most of the time, you'll want to use the Custom Event properties instead of a subscriber's Custom Attributes in your Journey templates.