Skip to main content

​
Definition

In TWICE there is no separate Group object. Customer segmentation is implemented through customer tags. A “Customer Group” is a named tag that you reuse across publishing, checkout, reporting, and workflows. Tags are flat, free-form, applied manually, and consistent across the platform.

​
Where do I use it?

  • Charging wholesale customers a different price than retail
  • Restricting a Listing so only staff or members can see it
  • Hiding or revealing checkout fields based on customer type
  • Triggering a Workflow when a customer with a specific tag places an order
  • Reporting on revenue, retention, and order frequency per segment
  • Bulk-emailing or exporting a segment

​
Key Properties

​
Tags

A Tag is a string label attached to a Customer. Tags are flat — there is no hierarchy and no parent/child relationship. Plan tag names with care: short, lowercase, hyphenated values (wholesale, vip, corporate-acme, staff) read well in filters and stay stable as you add more segments.

​
Attributes vs Tags

Membership in a “group” is manual: a staff member (or your API integration) sets the tag on the Customer record. There is no rule engine that applies or removes tags automatically.

​
Relationships

  • A Tag is attached to a Customer Profile.
  • A Price Table on a Listing can target one or more tags so the matching customer sees a different price.
  • A Listing’s Publishing settings can restrict visibility to tagged segments.
  • A Workflow can branch on the customer’s tags.
  • The Customers table can filter, group, and export by tag.

​
Lifecycle

​
Where Customer Groups are referenced

Customer tags surface anywhere TWICE needs to vary behavior by audience:
Price Tables are not scoped by customer tags — pricing does not vary by customer group. For customer-specific pricing, target a discount code at a tagged segment instead.
On the Listing Publishing tab, the Customer tags card lets you restrict a Listing to specific tagged segments. A Listing flagged staff is only visible at checkout for customers carrying that tag.This is useful for staff-only rentals, internal demo gear, and member-exclusive listings.
Combine tags with required Documents in your own processes — for example, only confirm orders from a wholesale-tagged customer once a signed contract is on file.
Workflows can branch on customer tags — for example, send an extended welcome email when a customer with wholesale places their first order, or notify a sales rep when a corporate-account-acme booking lands.
The Customers table can be filtered and grouped by tag. Order reports can be filtered by the customer’s tags at the time the order was placed, so you can analyse revenue, retention, and order frequency per segment.

​
Tag taxonomy and management

A few practical rules for keeping tags useful as the catalog grows: Tag changes are written to the customer’s Activity Log, so you can see when and why a tag was applied or removed.

​
FAQs

No. The “group” is the tag itself. Query customers by tag instead, or fetch the Customers table filtered by tag.
Yes. A Customer can carry multiple tags simultaneously. The pricing engine and publishing rules each decide how to combine them — see Price Tables for the precedence model.
No. There is no tag rule engine — tags are applied and removed manually in admin or via the API. To automate tagging, drive it from your own integration through the customers and tags endpoints.
Not through Price Tables — pricing is not scoped by customer tags. Create a discount code for the negotiated rate and limit it to that customer or tagged segment instead.
Tags are a flat, free-form list — there is no hierarchy. Plan your tag names with care: short, lowercase, hyphenated values (e.g. wholesale-tier-1) read well in filters and stay stable as you add more segments.

​
Developer Reference

Customer segments are powered by tags. Manage tags via the tags endpoints and apply them via the customers endpoints.

API: Tags

Open the endpoint in the API reference.

Customer Profiles

The record a tag is attached to.

Price Tables

Reusable listing pricing (not customer-scoped).

Listings

Tag-driven visibility and publishing.

Workflows

Tag-driven automation.