Skip to content

Add performance and warehouse guidance to Linked Audiences limits #7558

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Apr 10, 2025
Merged

Add performance and warehouse guidance to Linked Audiences limits #7558

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a1f985e
add performance guidance section
pwseg Apr 10, 2025
d310467
Update src/engage/audiences/linked-audiences-limits.md
pwseg Apr 10, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions src/engage/audiences/linked-audiences-limits.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,3 +40,20 @@ Entity columns | Up to 1000 unique values | The maximum number of entity propert
Run frequency | 15 minutes (this is the fastest time) | You can’t configure more frequency syncs. You can select **Run Now** to trigger runs, but you’re limited by Profiles Sync for when new data syncs back to the data warehouse.
Destination Mappings | Up to 100 mappings | You can set up to 100 action destination mappings per destination instance.

## Warehouse setup and performance guidance

To get the best performance from Linked Audiences at scale, Segment recommends setting up a dedicated warehouse cluster. This helps avoid resource contention and makes query performance more predictable, especially when running frequent or complex audience syncs.

Most workloads running on a dedicated cluster should complete within 60 minutes per sync cycle. Staying under this threshold helps keep audiences fresh and aligned with downstream activation schedules.

Segment has tested Linked Audiences at enterprise scale with over 30 audiences running concurrently, each targeting millions of entities. However, actual performance and cost varies based on how your Data Graph is structured, how many audiences you run at once, and how frequently they sync. Complex joins, deep relationships, and high concurrency can all increase query time and warehouse usage.

To improve performance and manage compute costs, follow these best practices:

- Use materialized views when configuring Data Graph to reduce compute overhead.
- Keep your Data Graph focused by avoiding unused entities or overly deep relationship chains.
- Simplify audience conditions and avoid high-cardinality joins when possible.
- Run on a dedicated warehouse cluster if you're operating at enterprise scale.
- Stagger audience sync schedules to reduce concurrency and avoid bottlenecks.

Following this guidance will help you keep audience syncs running efficiently even as your scale grows.
Loading