日期函式 date-functions

currentTimeInMillis()

傳回整數。

currentTimeInMillis()

傳回「1544712617131」。

兩個引數必須使用相同的資料型別；不支援混合型別（例如dateOnly搭配dateTime）。 引數可以是常值日期值、其他函式（例如now()）或內容屬性（事件裝載欄位、自訂動作回應欄位、設定檔或實體欄位以及變數），只要它們是dateOnly、dateTimeOnly或dateTime型別即可。

dateDiff(<dateOnly>,<dateOnly>)

傳回整數，代表兩個日期之間的天數。

dateDiff(<dateTimeOnly>,<dateTimeOnly>)

傳回代表兩個日期時間之間的毫秒數的整數。

dateDiff(<dateTime>,<dateTime>)

傳回代表兩個日期時間之間的毫秒數的整數。

dateDiff(toDateOnly('2023-12-15'), toDateOnly('2023-12-12'))

傳回3 （天）。

dateDiff(toDateTimeOnly('2023-12-15T00:00:00'), toDateTimeOnly('2023-12-12T00:00:00'))

傳回259200000 （毫秒，等於3天）。

dateDiff(now(), toDateTime('2024-12-25T00:00:00Z'))

傳回今天和2024年12月25日之間的毫秒數。

dateDiff(#{ExperiencePlatform.ProfileFieldGroup.person.birthDate}, toDateOnly('2023-01-01'))

傳回設定檔的birthDate欄位與2023年1月1日之間的天數，假設birthDate是輸入為dateOnly。

inLastDays(<dateTime>,<integer>)

傳回布林值。

inLastDays(toDateTime('2023-12-12T01:11:00Z'), 4)

傳回true。

inLastHours(<dateTime>,<integer>)

傳回布林值。

inLastHours(toDateTime('2023-12-12T01:11:00Z'), 4)

傳回true。

inLastHours(@event{MyEvent.timestamp}, 4)

傳回true。

inLastMonths(<dateTime>,<integer>)

傳回布林值。

inLastMonths(toDateTime('2023-12-12T01:11:00Z'), 4)

傳回true。

inLastYears(<dateTime>,<integer>)

傳回布林值。

inLastYears(toDateTime('2023-12-12T01:11:00Z'), 4)

傳回true。

inNextDays(<dateTime>,<integer>)

傳回布林值。

inNextDays(toDateTime('2023-12-12T01:11:00Z'), 4)

傳回true。

inNextHours(<dateTime>,<integer>)

傳回布林值。

inNextHours(toDateTime('2023-12-12T01:11:00Z'), 4)

傳回true。

inNextMonths(<dateTime>,<integer>)

傳回布林值。

inNextMonths(toDateTime('2023-01-12T01:11:00Z'), 4)

傳回true。

inNextYears(<dateTime>,<integer>)

傳回布林值。

inNextYears(toDateTime('2021-12-12T01:11:00Z'), 4)

傳回true。

now()

now("<timeZone id>")

傳回日期時間。

now()

傳回2023-06-03T06:30Z。

toString(now())

傳回「2023-06-03T06:30Z」

now("Europe/Paris")

傳回2023-06-03T08:30+02:00。

nowWithDelta(<delta>,<date part>

nowWithDelta(<delta>,<date part>,"<timeZone id>")

傳回日期時間。

nowWithDelta(-2, "hours")

nowWithDelta(-2, "hours", "Europe/Paris")

傳回2小時前的dateTime。

nowWithDelta(1, "months", "Asia/Tokyo")

在2026-01-31評估時，傳回2026-02-28T…；在2026-05-31評估時，傳回2026-06-30T…

nowWithDelta()使用行事曆月算術。 如果目標月份的天數少於當月當月，則結果會標準化為該月的最後一個有效日。 函式不會捲動至下個月。

setHours(<dateTime>,<hours>)

傳回日期時間。

setHours(<dateTimeOnly>,<hours>)

傳回日期時間，不考慮時區。

setHours(toDateTime('2023-12-12T01:11:00Z'), 4)

傳回2023-12-12T04:11:00Z。

setHours(nowWithDelta(1, "days"), 20)

傳回明天晚上8:XY，XY是目前時間評估的分鐘數。 如果評估在凌晨2:45進行，則傳回時間將會是晚上8:45。

setDays(<dateTime>,<days>)

傳回日期時間。

setDays(<dateTimeOnly>,<days>)

傳回日期時間，不考慮時區。

setDays(toDateTime('2023-12-12T01:11:00Z'), 25)

傳回2023-12-25T01:11:00Z。

setDays(toDateTimeOnly(@event{MyEvent.registrationDate}), 1)

• 時區id：字串
• dateTime

updateTimeZone(<dateTime>,<timeZone id>)

傳回日期時間。

updateTimeZone( toDateTime("2023-08-28T08:15:30.123-07:00"), "Europe/Paris"))

傳回2023-08-28T17:15:30.123+02:00。

updateTimeZone(@event{MyExpEvent.timestamp}, "Australia/Sydney")

如果時間戳記欄位的值為2021-11-16T16:55:12.939318+01:00，則函式會傳回2021-11-17T02:55:12.942115+11:00。

This section contains structured knowledge intended to support interpretation, retrieval, and question answering related to this topic.

For complete understanding, this information should be combined with the documentation on this page. Neither source is intended to stand alone; the page describes the feature, while this section provides additional context that helps disambiguate terminology, intent, applicability, and constraints.

• TL;DR: This page documents all date and time functions available in AJO journey expressions, covering how to get the current time, check whether a date falls within a relative time window, and modify date/time components.

Intents:

• Get the current datetime (with optional timezone) using now or nowWithDelta
• Retrieve the current time as an epoch integer using currentTimeInMillis
• Calculate the difference between two dates or date-times using dateDiff
• Check if a datetime falls within the last N days, hours, months, or years using inLastDays, inLastHours, inLastMonths, inLastYears
• Check if a datetime falls within the next N days, hours, months, or years using inNextDays, inNextHours, inNextMonths, inNextYears
• Force a specific hour or day of the month on a datetime value using setHours or setDays
• Convert a datetime to a different timezone while preserving the same instant using updateTimeZone

Glossary:

• dateOnly: A date value with no time or timezone information (product-specific)
• dateTime: A date-time value that includes timezone offset information (product-specific)
• dateTimeOnly: A date-time value with no timezone information (product-specific)
• epoch milliseconds: An integer representing the number of milliseconds elapsed since 1970-01-01T00:00:00Z
• delta: An integer offset (positive or negative) used with nowWithDelta to shift the current time by a number of years, months, days, hours, minutes, or seconds

Guardrails:

• now() is only available in journey expressions; for email personalization use getCurrentZonedDateTime() instead
• The timezone ID in nowWithDelta must be a string constant — field references and dynamic expressions are not supported
• The timezone ID in updateTimeZone must be a string constant
• dateDiff requires both parameters to be the same data type (dateOnly, dateTimeOnly, or dateTime); mixing types is not supported
• dateDiff returns null if either parameter is null
• dateDiff returns days for dateOnly parameters, but milliseconds (not days) for dateTimeOnly and dateTime parameters — convert accordingly when comparing results across types

Terminology:

• Canonical name: Date functions — Acronym: none — variants: date-time functions, temporal functions
• Synonyms: “now()” = “current datetime”; “currentTimeInMillis()” = “current epoch milliseconds”
• Do not confuse: “inLastDays” (looks back in time) ≠ “inNextDays” (looks forward in time)
• Do not confuse: “setHours” (replaces the hour component) ≠ “nowWithDelta” (offsets the current time)
• Do not confuse: “updateTimeZone” (same instant, different timezone representation) ≠ “setHours” (changes the time value itself)
• Do not confuse: the journey expression editor’s dateDiff (accepts dateOnly, dateTimeOnly, or dateTime; returns days or milliseconds depending on type) ≠ the personalization editor’s dateDiff (accepts only dateTime; always returns days)

FAQ:

• Q: Can I use now() in email personalization content? — No, now() is only available in journey expressions. Use getCurrentZonedDateTime() for email personalization.
• Q: How do I check if an event happened in the last 24 hours? — Use inLastHours(@event{MyEvent.timestamp}, 24).
• Q: How do I get the current time offset by 2 hours in the past? — Use nowWithDelta(-2, "hours").
• Q: What does updateTimeZone do differently from setHours? — updateTimeZone keeps the same instant in time but expresses it in a different timezone, while setHours actually changes the hour component of the datetime value.
• Q: Can the timezone parameter in nowWithDelta be a profile field? — No, the timezone ID must be a string constant; field references are not supported.
• Q: What happens when nowWithDelta() is used with months and the current date is a month-end date? — The function uses calendar-month arithmetic and normalizes the result to the last valid day of the target month. For example, adding 1 month to January 31 returns February 28 (not March 3).