Skip to content
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.

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

[Content]: Confusing Engage limits points #6521

Open
050phy opened this issue May 9, 2024 · 1 comment
Open

[Content]: Confusing Engage limits points #6521

050phy opened this issue May 9, 2024 · 1 comment
Assignees
Labels
content When the bug is about content that needs to get fixed stale triage

Comments

@050phy
Copy link
Contributor

050phy commented May 9, 2024

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

@050phy 050phy added content When the bug is about content that needs to get fixed triage labels May 9, 2024
@pwseg pwseg self-assigned this May 11, 2024
Copy link
Contributor

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

@github-actions github-actions bot added the stale label Jul 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content When the bug is about content that needs to get fixed stale triage
Projects
None yet
Development

No branches or pull requests

2 participants