Changes is Smartlist Results | Community
Skip to main content
C
cadalmas
New Participant
January 31, 2024
Solved

Changes is Smartlist Results

  • January 31, 2024
  • 1 reply
  • 831 views

1) I ran a smartlist with these filters: 

-Person was created between 01/26/2024 and 01/28/2024

-Not person was created 01/29/2024

-Updated between 01/26/2024 and 01/28/2024

 

I compared the lead record results to a smartlist that queries a specific date instead of a date range 

 

2) The smartlist filters are

-Person was created date of activity is 01/26/2024

-Not person was created 01/27/2024

-Updated at is 01/26/2024

 

I ran the #2 smartlist and changed the dates for 01/27/2024 and 01/28/2024 then added the 3 days results together. The results that I got if I queried a specific day and added them together is different when I queried the same date ranges. I tried to run the scenario #1 and scenario #2 over several days and the results are always different even if I am querying the same dates. Why do you think is the reason for the difference in lead record results? There have been no major changes to the database as far as more records added or deleted.

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Darshil_Shah1

Well, in past two days, the operator looks at the last 48 hours; if it is set as "in past 3 days," it would look at the last 72 hours, etc. Unlike the exact date operators (in between 2 dates), it doesn’t look at the last two calendar days from midnight to midnight based on the timezone specified in your instance. In the first case, a lot of people wouldn’t have qualified for the in past x days criteria- likely, a lot of people might have imported/created at a specific time (which if you are able to verify in your instance, then it would answer the drop in the count of people qualified for the smart list), and that wouldn’t have made the cut for your in past criteria when you refreshed the list after some time the same day. In the 2nd case, you might be seeing a difference due to the difference mentioned in the beginning regarding how operators with natural language (e.g., in past x days) work and how operators with exact dates work (e.g., in between x and y dates).

1 reply

Darshil_Shah1
Darshil_Shah1Accepted solution
Community Manager
January 31, 2024

Well, in past two days, the operator looks at the last 48 hours; if it is set as "in past 3 days," it would look at the last 72 hours, etc. Unlike the exact date operators (in between 2 dates), it doesn’t look at the last two calendar days from midnight to midnight based on the timezone specified in your instance. In the first case, a lot of people wouldn’t have qualified for the in past x days criteria- likely, a lot of people might have imported/created at a specific time (which if you are able to verify in your instance, then it would answer the drop in the count of people qualified for the smart list), and that wouldn’t have made the cut for your in past criteria when you refreshed the list after some time the same day. In the 2nd case, you might be seeing a difference due to the difference mentioned in the beginning regarding how operators with natural language (e.g., in past x days) work and how operators with exact dates work (e.g., in between x and y dates).

Terms & ConditionsAccessibility statement

Loading footer...