Help CenterSegment publishing is a push-based service that automates the delivery of player changes within a segment to a designated third-party endpoint (webhook).
How It Works
Once a segment publisher is activated, the system rebuilds the segment within a few minutes. At that moment, all players currently in the segment are sent to the specified endpoint(s). After this initial push, any players who enter or exit the segment will also be sent to the endpoint(s).
⚠️ Publishing is incremental—only newly detected changes (entries or exits) are sent. The entire segment is not re-sent each time.
Minimum Frequency
This setting defines the minimum number of days that must pass before the same player can be considered a valid entrant again. Since players may enter and exit a segment multiple times, this helps reduce repetitive entries.
ℹ️ For example, with a minimum frequency of 60 days, a player will only be re-published if they re-enter the segment after 60 days.
Start and End Dates
You can specify when publishing should begin and end. The publisher will start sending data from the defined start date and stop on the end date.
Webhook Endpoint Configuration
Endpoints are managed in the Webhooks section. Only webhooks marked as Published will be used by the publisher. Webhooks marked as Draft will be ignored.
✅ Suggested read: Create a Webook Endpoint
Limits
Each account has a limit on the number of active segment publishers. To request an increase, contact the product team.
Rebuild Intervals
Segments with active publishers are automatically rebuilt at intervals based on the refresh frequency of the Insight.
⚠️ The Publisher must be set to Active to publish segment changes.