Skip to main content
Solved

Comparing Date with "Today"

L
Helpful Hero
Forum|alt.badge.img

I would like to be able to compare a User Property Date to “today”. For example, if I want a cohort of users who are currently “subscribed”, there doesn’t seem to be a reliable and automated option to do that. If I were able to compare dates within User Properties to “Today”, then I would be able to create a cohort that is something like: “subscription expiry > today”, and I could keep a cohort of all my subscribed users. This works for a specific day, but if the day I’m comparing to is dynamic, then it seems I’m out of luck. 

Another example is for Experiment. I want user who are “subscribed” to see a specific variant. Again, I don’t think that’s really possible without sending an event to Amplitude when the subscription expires, which seems unscalable. 

Maybe it’s possible, and I missed it somewhere? 

Thanks in advance,

Justin

Best answer by Hadish

Hi Justin, currently, there isn't a direct way to compare a User Property Date to "today" within Amplitude. However, you can create a cohort based on a user property with a specific date range, such as "subscription expiry in the next 7 days". You can then update this cohort daily to keep track of all subscribed users whose subscription will expire in the next 7 days. As for your experiment example, you can use the same approach and create a cohort of subscribed users and target them with a specific variant. Alternatively, you can use an external tool to trigger an event in Amplitude when a user's subscription expires, and then use that event to target users in your experiment. I hope this helps!

View original
Did this topic help you find an answer to your question?

5 replies

H
Experienced
Forum|alt.badge.img+1
  • Hadish
  • Experienced
  • 11 replies
  • Answer
  • March 22, 2023

Hi Justin, currently, there isn't a direct way to compare a User Property Date to "today" within Amplitude. However, you can create a cohort based on a user property with a specific date range, such as "subscription expiry in the next 7 days". You can then update this cohort daily to keep track of all subscribed users whose subscription will expire in the next 7 days. As for your experiment example, you can use the same approach and create a cohort of subscribed users and target them with a specific variant. Alternatively, you can use an external tool to trigger an event in Amplitude when a user's subscription expires, and then use that event to target users in your experiment. I hope this helps!

Hadish
L
Helpful Hero
Forum|alt.badge.img
  • liukaichi
  • Author
  • Helpful Hero
  • 9 replies
  • March 23, 2023

This is how I thought the situation as well. Thanks for validating my understanding. Then I guess I would like to formally request this be a feature😀 I think it would be very useful, especially as Experiment being such an integral tool in the user experience. 

L
Helpful Hero
Forum|alt.badge.img
  • liukaichi
  • Author
  • Helpful Hero
  • 9 replies
  • April 3, 2023

I realized in the Govern Packing (which we do not have) you can specify Derived properties. I believe this would have the effect we want it to. 

Esther Trapadoux
1 person likes this
  • Esther Trapadoux
    Esther Trapadoux
K
  • Kevin Morrow
  • New Member
  • 2 replies
  • September 13, 2024

If you duplicate the timestamp value of the event as an actual event property, it will be available for chart filtering and grouping just like all other event properties. Then, you can then use a derived property to create a property whose value will be TRUE dynamically depending on the date today.

Heres an example I used as a filter on certain charts I needed to keep in sync with internal non-amplitude dashboards. It only returns TRUE of the timestamp and receivedAt values are both before the last time we sync data to the other dashboard. Hope this helps others.

 

IF(

    AND(

        TIME_TO_LONG(PROPERTY('timestamp', 'event')) <=

        SUBTRACTION(

            TODAY(),

            MULTIPLY(

                86400000, 

                SWITCH(EVENT_DAY_OF_WEEK(),

                    "Sunday", 7, 

                    "Monday", 8,

                    "Tuesday",9,

                    "Wednesday", 3,

                    "Thursday", 4,

                    "Friday", 5,

                    "Saturday", 6

                )

            )  

        ),

    TIME_TO_LONG(PROPERTY('receivedAt', 'event')) <=

        SUBTRACTION(

            TODAY(),

            MULTIPLY(

                86400000, 

                SWITCH(EVENT_DAY_OF_WEEK(),

                    "Sunday", 7, 

                    "Monday", 8,

                    "Tuesday",9,

                    "Wednesday", 3,

                    "Thursday", 4,

                    "Friday", 5,

                    "Saturday", 6

                )

            )  

        )

    ),

    "TRUE",

    "FALSE"

)

K
  • Kevin Morrow
  • New Member
  • 2 replies
  • September 17, 2024

If you can manage to pass the timestamp of your event as part of the property object, it will be available for chart filtering and grouping just like all other event properties. Then, you can then use a series of derived properties to create a filter you can apply to charts. 

Heres an example I built to return FALSE for timestamp or recievedAt values that were greater than a dynamically calculated date which based on what today() is and counting back the appropriate number of days to what the last weekly sync update was for our situation. 

 

IF(

    AND(

        TIME_TO_LONG(PROPERTY('timestamp', 'event')) <

            SUBTRACTION(

                TODAY(),

                MULTIPLY(

                    86400000, 

                    SWITCH(

                        DATE_TIME_FORMATTER(

                            LONG_TO_DATE(PROPERTY('todayHelperFunction', 'derived')),

                            "YYYY-MM-dd",

                            "E"

                        ),

                        "Sun", 6, 

                        "Mon", 7,

                        "Tue", 8,

                        "Wed", 2,

                        "Thu", 3,

                        "Fri", 4,

                        "Sat", 5

                    )

                )  

            ),

        TIME_TO_LONG(PROPERTY('receivedAt', 'event')) <

        SUBTRACTION(

            TODAY(),

            MULTIPLY(

                86400000, 

                SWITCH(

                    DATE_TIME_FORMATTER(

                        LONG_TO_DATE(PROPERTY('todayHelperFunction', 'derived')),

                        "YYYY-MM-dd",

                        "E"

                    ),

                    "Sun", 6, 

                    "Mon", 7,

                    "Tue", 8,

                    "Wed", 2,

                    "Thu", 3,

                    "Fri", 4,

                    "Sat", 5

                )

            )  

        )

    ),

    "TRUE",

    "FALSE"

)

 

Reply


Helpful Members this Week

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings