Source
Ticket shop, checkout & registration — found from sitemap — vivenu
Checked for vivenu on 29 Oct 2026
- Page
- https://vivenu.com/entitlements-benefits-at-checkout
- Checked
- 29 Oct 2026, 22:27 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:25c404eb4db545b8a05f36e06b9e143ee250736227ad3c9dbc9e3014a6acb943
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Entitlements definition Report an error
“Entitlements are vivenu's rule-based benefits engine. They apply discounts and fee waivers automatically at checkout, based on who the buyer is or what's in their cart. No promo code needed.”
-
Entitlements conditions Report an error
“Conditions decide who qualifies: The customer belongs to a specific Customer Segment The customer holds an active Membership A specific product is already in the cart The sale happens through a particular sales channel The event carries a specific attribute”
-
Entitlements condition logic Report an error
“Combine conditions with AND/OR logic to scope a perk as narrow or as broad as your use case needs.”
-
Entitlements modifiers Report an error
“Modifiers decide what they get: A nominal discount, a fixed amount off, like $10 off a ticket A variable discount, a percentage off, with an optional maximum cap A fee waiver, which removes add-on service fees from the order”
-
Entitlements config location Report an error
“You configure Entitlements in Customers → Entitlements in your vivenu dashboard.”
-
Entitlements not default Report an error
“The module activates separately. It isn't on by default in your vivenu account. It sits alongside other engage capabilities, like Email Campaigns, and Consents as an individually enabled module.”
-
Entitlements stacking Report an error
“Entitlements are built to stack. A buyer who qualifies for more than one sees all of them apply, and Entitlements work alongside promo codes layered on top.”
-
Segment basis Report an error
“Build a segment around: Total spend. Buyers who've crossed a set amount across all events. Ticket volume. Buyers who've attended more than a set number of times. Specific attendance. Buyers who've shown up to particular events or ticket types. Geography. Local fans versus out-of-market buyers. Engagement. Buyers who've opened campaigns but haven't purchased yet.”
-
Segment refresh interval Report an error
“Segments refresh automatically in the background, roughly every hour.”
-
Pos support Report an error
“At the box office. Scoping an Entitlement to the POS sales channel is the recommended way to deliver automatic discounts at the box office.”
-
Secret shop Report an error
“Behind a QR code. You can pair a Secret Shop (a dedicated, shareable shop link) with an Entitlement scoped to that sales channel recreates the experience.”
-
Fee waiver scope Report an error
“The fee waiver modifier removes service and add-on fees. It doesn't remove a price component already built into the ticket price itself.”
-
No per customer cap Report an error
“There's no native per-customer cap. If a perk should only apply once per buyer, manage that through Customer Segment rules, for example by excluding buyers from the segment after their first qualifying purchase.”
-
Membership upsell Report an error
“Pair an Entitlement with a membership product, and adding a season membership to the cart can unlock a ticket discount in the same transaction.”
-
Reporting location Report an error
“Usage lives in Reports → Discounts, so you see which segments actually convert on their perks and adjust the rules behind them.”
-
Loyalty no points Report an error
“vivenu doesn't run a traditional points-balance loyalty program. It doesn't need to. Loyalty status is earned through buyer behavior, tracked in Customer Segments, and rewarded automatically through Entitlements.”
Scores citing this record
- The Venue Promoter Attendee data & the customer relationship