Loading

Data 360: Lookback Window on Engagement Data in Segments

Julkaisupäivä: Feb 3, 2026
Kuvaus

The lookback window of a segment is briefly mentioned in Create a Standard Segment:

Enter the lookback period for your segment.
The default is 90 days. You can set the lookback up to 2 years.  If you select Days from the dropdown, you can set a period of up to 360 days, depending on your organization’s requirements.
When creating a segment, the lookback options are based on your organization's maximum allowed period, for example, up to 2 years. This setting defines the initial data range you can select. When you're in the segment, you can apply specific criteria in a container, which may differ from the default lookback period. So, if the segment-level lookback is set to 90 days and the container criteria specifies 60 days, the container criteria takes precedence, and data is pulled for only 60 days.

The impacts of the lookback window when configuring a segment are as follows:

  • If you do not configure a filter on an Event Time field but your segment references data in an Engagement category DMO, the query that populates the segment will automatically exclude records on the Engagement category data model where the Event Time field is not within the time period set as your segment's lookback window (i.e. 90 days). For example, if your segment is filtering on any fields of an Engagement category DMO or an Engagement category DMO is referenced in the Container Path of any containers, only records with an Event Time in the range of your lookback window are included.

Note: With Rapid Publish, you can use the last 7 days of engagement data in segmentation rules and publish to Marketing Cloud only, as documented in Create a Standard Segment.

Ratkaisu

The impact listed above is a common cause of segments receiving a count of 0 despite having records that appear to meet the defined filter criteria. If you notice that a segment's population is lower than expected or that some profiles are not included in a segment population that appear to meet the segment criteria, it is advised to review if profiles are being excluded due to the segment's lookback window.

For example, if your segment references an Engagement DMO (and uses a 2 year lookback window) and the segment is executed on March 20th, 2024 at 12:00PM, then only profiles linked to records on the Engagement DMO with an Event Time after 12:00 PM on March 20th, 2022 (that also meet the other criteria in the segment) will be included in the population. If the Event Time field is NULL or empty then profiles linked to the record will not be included in the segment population.

Use Data Explorer to ensure that desired segment records have recent data on all Event Time fields contained on the DMOs used in segmentation. Alternatively, if a mapping between an Engagement DMO field and a data stream Event Time field is not being used, removing the mapping will prevent the lookback window from being applied to that field.

Note: A date field on an Engagement category DMO is designated as an Event Time field when it is mapped to the Event Time field of an Engagement category data stream. When you are creating a segment container, the Event Time field on any Engagement DMOs has the text Event listed next to its name in the attribute library.

Lisäresurssit

Refer to the following Help documentation for more details:

Knowledge-artikkelin numero

000395460

 
Ladataan
Salesforce Help | Article