[Content]: Confusing Engage limits points

[050phy]

What article on segment.com/docs is affected?

https://segment.com/docs/engage/product-limits/#audiences-and-computed-traits

What part(s) of the article would you like to see updated?

In the table, we have 2 points that are confusing and contradictory.

1. Events Lookback History -- this point says Engage will only compute over events in the past 3 years.
2. Event History -- this point says Engage will backfill events from 1970-01-01 which is more than 3 years.

As a SA, I know that Engage will only compute over events in the past 3 years and Engage will not backfill or compute events beyond 3 years.

Having the line saying "Engage will backfill events from 1970" is contradictory and confusing. I suggest to remove the line about Event History. We had a customer who uploaded 8 years of events thinking Engage could compute over 8 years after reading the docs.

Additional information

No response

[github-actions]

This issue is stale because it has been open 60 days with no activity.

[pwseg]

@050phy Thanks for flagging this! We went ahead and updated the docs to make this clearer. Specifically:

• We removed the "Events Lookback History" row since we actually store events indefinitely.
• We updated the "Event History" row to clarify that Segment may not ingest events with timestamps earlier than 1970-01-01, but this doesn't affect how long data is stored.

This should clear up the contradiction between event history and storage. The confusion was coming from the fact that there are two different things at play:

• Storage: we keep data indefinitely.
• Event conditions: by default, Engage only evaluates events from the past three years, unless that limit is changed.

So if a customer uploaded 8 years of events and expected Engage to compute over all of them, it wouldn’t work because of that default time window (not because the data wasn’t stored).

Hopefully, this makes things clearer! Let me know if anything still seems off.