> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stackshift.cloud/llms.txt
> Use this file to discover all available pages before exploring further.

# Define customer data and audiences

> Group customers by useful details or actions they have taken in your product.

<Note>
  This guide includes features awaiting release. If an option is not available in your workspace, contact StackShift Support.
</Note>

## 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 Segments

## Before you start

* Engagement author access.
* A developer for automatic event or trusted attribute collection from your product.

## Steps

<Steps>
  <Step>
    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.
  </Step>

  <Step>
    Define event types for meaningful actions such as completed\_onboarding. Review the required event fields and whether clients may send them.
  </Step>

  <Step>
    Use Customer data to inspect or submit permitted updates and events. Ask your developer to connect automatic collection using those definitions.
  </Step>

  <Step>
    Create a segment using all or any of the selected rules. Choose attribute, event or identity conditions and any time window.
  </Step>

  <Step>
    Preview the audience and check example customers before using the segment in a campaign.
  </Step>
</Steps>

## 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

<Check>
  Campaign audiences reflect declared, correctly typed customer data.
</Check>

## If something goes wrong

<Warning>
  * Customer missing: inspect the actual attribute value, event time and identity, then check all/any rules.
  * Update rejected: check the declared type, event schema and client-write permission.
</Warning>

## Related guides

<CardGroup cols={2}>
  <Card title="Create targeted campaigns and in-product guidance" href="/stackshift-support/engagement-campaigns">
    Show timely messages, tours, checklists or surveys to the right audience.
  </Card>

  <Card title="Control consent, quiet hours and message limits" href="/stackshift-support/engagement-limits">
    Prevent engagement from interrupting customers or sending too frequently.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.