This guide includes features awaiting release. If an option is not available in your workspace, contact StackShift Support.
What you can do
Group customers by useful details or actions they have taken in your product. Where to find it: Engagement → Attributes, Event types, Customer data and SegmentsBefore you start
- Engagement author access.
- A developer for automatic event or trusted attribute collection from your product.
Steps
1
Define an attribute with its name and data type, such as plan as text or joined_at as a timestamp. Decide whether browser code may update it.
2
Define event types for meaningful actions such as completed_onboarding. Review the required event fields and whether clients may send them.
3
Use Customer data to inspect or submit permitted updates and events. Ask your developer to connect automatic collection using those definitions.
4
Create a segment using all or any of the selected rules. Choose attribute, event or identity conditions and any time window.
5
Preview the audience and check example customers before using the segment in a campaign.
Example
A segment selects customers who joined recently but have not completed onboarding in the chosen time window.Things to know
- A segment is a rule-based audience, not a message.
- A trusted server-only attribute should not be made browser-writable just to bypass an error.
- Collect only data you need and explain that collection to your customers.
What happens next
Campaign audiences reflect declared, correctly typed customer data.
If something goes wrong
Related guides
Create targeted campaigns and in-product guidance
Show timely messages, tours, checklists or surveys to the right audience.
Control consent, quiet hours and message limits
Prevent engagement from interrupting customers or sending too frequently.