List filter definitions

Below, review the definitions for the filter type, property operations, and coalescing refine by and pruning refine by operations. 

FilterType options

The filterType parameter is used to define the filter within the filterBranch. There are 16 different types of filters.

ADS_TIME

Evaluates whether a contact has seen any ads in the timeframe defined by the pruningRefineBy parameter. 

{ "filterType": "ADS_TIME", "pruningRefineBy": PruningRefineBy }

ADS_SEARCH

Evaluates whether a contact has performed the ad interactions as defined by the filter. 

{ "filterType": "ADS_SEARCH", "entityType": "AD", "searchTermType": "ID", "searchTerms": ["hubspot", "hubspot developers"], "adNetwork": "LINKEDIN", "operator": "CONTAINS" }
Use this table to describe parameters / fields
ParameterDescription
entityType

The type of asset interacted with. Values include:

  • AD: a specific ad. Supports ID, NAME, and AD_TYPE as searchTermTypes. 
  • ADGROUP: a specific ad group. Supports ID and NAME as SearchTermTypes.
  • CAMPAIGN: a specific ad campaign. Supports ID and NAME as SearchTermTypes.
searchTermType

The searchTerms type. Values include:

  • ID - supports IS_KNOWN and IS_EQUAL_TO as operators. 
  • NAME - supports all operators
  • AD_TYPE -  supports IS_KNOWN and IS_EQUAL_TO as operators.

AD_TYPE cannot be used when entityType is ADGROUP or CAMPAIGN.

searchTerms

Required, unless the operator is IS_KNOWN.

adNetwork

The ad network. Values include:

LINKEDIN, ADWORDS, FACEBOOK

operator

The filter operator. Values include:

CONTAINS, IS_EQUAL_TO, ENDS_WITH, STARTS_WITH, IS_KNOWN

CTA

Evaluates whether a contact has or has not interacted with a specific CTA as defined by the filter. 

{ "filterType": "CTA", "ctaName": "b7988654-536d-4f7f-976b-8e9e2c7bb54", "coalescingRefineBy": CoalescingRefineBy, // Optional "pruningRefineBy": PruningRefineBy, // Optional "operator": "HAS_CLICKED_CTA" }
Use this table to describe parameters / fields
ParameterDescription
operator

The filter operator. Values include:

HAS_CLICKED_CTA, HAS_NOT_CLICKED_CTA, HAS_OPENED_CTA, HAS_NOT_OPENED_CTA, HAS_CLICKED_CTA_PLACEMENT, HAS_NOT_CLICKED_CTA_PLACEMENT, HAS_OPENED_CTA_PLACEMENT, HAS_NOT_OPENED_CTA_PLACEMENT

EMAIL_EVENT

Evaluates whether a contact has or has not interacted with a marketing email as defined by the filters. 

{ "filterType": "EMAIL_EVENT", "level": "EMAIL_API_CAMPAIGN", "emailId": "79019645", "appId": "2285", "operator": "OPENED", "clickUrl": string, // Optional "pruningRefineBy": PruningRefineBy // Optional }
Use this table to describe parameters / fields
ParameterAccepted Values
level

The email campaign level. Values include:

EMAIL_API_CAMPAIGN, EMAIL_API_CAMPAIGN_GROUP, HUBSPOT_CAMPAIGN

operator

The filter operator. Values include:

LINK_CLICKED, MARKED_SPAM, OPENED, OPENED_BUT_LINK_NOT_CLICKED, OPENED_BUT_NOT_REPLIED, REPLIED, UNSUBSCRIBED, BOUNCED,  RECEIVED, RECEIVED_BUT_NOT_OPENED,  SENT, SENT_BUT_LINK_NOT_CLICKED, SENT_BUT_NOT_RECEIVED

clickURL

Only allowed when operator is LINK_CLICKED.

pruningRefineBy

Only supports ABSOLUTE_COMPARATIVE and ABSOLUTE_RANGED.

EMAIL_SUBSCRIPTION

Evaluates whether a contact has or has not interacted with a marketing email as defined by the filters. 

{ "filterType": "EMAIL_SUBSCRIPTION", "subscriptionIds": ["4805877"], "acceptedStatuses": ["OPT_IN"], "subscriptionType": "SUBSCRIPTION" // Optional }
Use this table to describe parameters / fields
ParameterAccepted Values
acceptedStatuses

The email subscription status. Values include:

OPT_IN, OPT_OUT, NOT_OPTED

There can only be one acceptedStatus per filterType.

subscriptionType

The subscription type.

clickURL

Only allowed when operator is LINK_CLICKED.

pruningRefineBy

Only supports ABSOLUTE_COMPARATIVE and ABSOLUTE_RANGED.

EVENT

Evaluates whether a contact has or does not have a specific event as defined by the filter.

{ "filterType": "EVENT", "eventId": "123456", "operator": "HAS_EVENT", "coalescingRefineBy": CoalescingRefineBy, // Optional "pruningRefineBy": PruningRefineBy // Optional }
Use this table to describe parameters / fields
ParameterAccepted Values
operator

The filter operator. Values include:

HAS_EVENT, NOT_HAS_EVENT

FORM_SUBMISSIONS

Evaluates whether a contact has or has not filled out a specific form or any form as defined by the filter. 

{ "filterType": "FORM_SUBMISSION", "formId": "6f62a9c7-4200-4b50-9779-3db4d9e40eb2", // Optional "coalescingRefineBy": CoalescingRefineBy, // Optional "pruningRefineBy": PruningRefineBy, // Optional "operator": "FILLED_OUT" }
Use this table to describe parameters / fields
ParameterAccepted Values
operator

The filter operator. Values include:

FILLED_OUT, NOT_FILLED_OUT

If NOT_FILLED_OUT is selected, the  pruningRefineBy parameter must be null.

FORM_SUBMISSION_ON_PAGE

Evaluates whether a contact has or has not filled out a specific or any form on a specific page as defined by the filter.

{ "filterType": "FORM_SUBMISSION_ON_PAGE", "pageId": "397942088", "formId": "f62a9c7-4200-4b50-9779-3db4d9e40eb", // Optional "coalescingRefineBy": CoalescingRefineBy, // Optional "pruningRefineBy": PruningRefineBy, // Optional "operator": "FILLED_OUT" }
Use this table to describe parameters / fields
ParameterAccepted Values
operator

The filter operator. Values include:

FILLED_OUT, NOT_FILLED_OUT

If NOT_FILLED_OUT is selected, the  pruningRefineBy parameter must be null.

IN_LIST

Evaluates whether a record is or is not a member of a specific list, import, or workflow as defined by the filter.

{ "filterType":"IN_LIST", "listId":"42", // Optional "metadata":[ { "id":"56", "inListType":"WORKFLOWS_ENROLLMENT" } ], // Optional "operator":"InListOperator" }
Use this table to describe parameters / fields
ParameterAccepted Values
inListType

The list type. Values include:

WORKFLOWS_ENROLLMENT, WORKFLOWS_ACTIVE, WORKFLOWS_GOAL, WORKFLOWS_COMPLETED, IMPORT

operator

The filter operator. Values include:

IN_LIST, NOT_IN_LIST

INTEGRATION_EVENT

Integration event filters can be used to filter specific contacts based on whether or not they have interacted with integration events that have properties as specified by the filter lines.

{ "filterType":"INTEGRATION_EVENT", "eventTypeId":"4009", "filterlines":[ { "property" :string, "operation": PropertyOperation }, ]}
Use this table to describe parameters / fields
ParameterAccepted Values
operator

Refer to the property operations definitions section. 

PAGE_VIEW

Evaluates whether a contact has or has not viewed a specific page as defined by the filter. 

{ "filterType": "PAGE_VIEW", "pageUrl":"www.hubspot.com" , "enableTracking": true, // Optional "operator": "HAS_PAGEVIEW_EQ", "coalescingRefineBy": CoalescingRefineBy, // Optional "pruningRefineBy": PruningRefineBy // Optional }
Use this table to describe parameters / fields
ParameterAccepted Values
enableTracking

Must be a boolean property operation. Values include:

  • TRUE - can only be used if operator is HAS_PAGEVIEW_EQ or NOT_HAS_PAGEVIEW_EQ
  • FALSE 
operator

The filter operator. Values include:

HAS_PAGEVIEW_EQ,HAS_PAGEVIEW_CONTAINS,HAS_PAGEVIEW_MATCHES_REGEX, NOT_HAS_PAGEVIEW_EQ, NOT_HAS_PAGEVIEW_CONTAINS, NOT_HAS_PAGEVIEW_MATCHES_REGEX

PRIVACY

Evaluates whether a contact does or does not have privacy consent for a specific privacy type as defined by the filter. 

{ "filterType": "PRIVACY", "privacyName": "PRIVACY_CONSENT_APPROVE", "operator": "PRIVACY_CONSENT_GRANTED" }
Use this table to describe parameters / fields
ParameterAccepted Values
privacyName
PRIVACY_CONSENT_APPROVE, PRIVACY_CONSENT_DECLINE, PRIVACY_CONSENT_REVOKE
operator

PRIVACY_CONSENT_GRANTED, PRIVACY_CONSENT_NOT_GRANTED

PROPERTY

Evaluates whether a record's property value satisfies the property filter operation as defined by the filter. Property filters require an operation object, which you can learn more about below.

{ "filterType": "PROPERTY", "property": "name", "operation": PropertyOperation }
Use this table to describe parameters / fields
ParameterAccepted Values
property

The property name. 

operation

Refer to the property operations definitions section. 

SURVEY_MONKEY

Evaluates whether a contact has or has not responded to a specific Survey Monkey survey as defined by the filter.

{ "filterType": "SURVEY_MONKEY", "operator": "HAS_RESPONDED_TO_SURVEY", "surveyId": "305206406" }
Use this table to describe parameters / fields
ParameterAccepted Values
operator

The filter operator. Values include:

HAS_RESPONDED_TO_SURVEY, HAS_NOT_RESPONDED_TO_SURVEY

SURVEY_MONKEY_VALUE

Evaluates whether a contact has or has not responded to a specific Survey Monkey survey’s question with a specified value as defined by the filter.

{ "filterType": "SURVEY_MONKEY_VALUE", "operator": "HAS_ANSWERED_SURVEY_QUESTION_WITH_VALUE", "surveyId": "305677", "surveyAnswerRowId": null, // Optional "surveyAnswerColId": null, // Optional "valueComparison": PropertyOperation, "surveyQuestion": "423564" }
Use this table to describe parameters / fields
ParameterAccepted Values
valueComparison

Refer to the property operations definitions section. 

operator

The filter's operator. Value is HAS_ANSWERED_SURVEY_QUESTION_WITH_VALUE.

WEBINAR

Evaluates whether a contact has or has not registered or attended any webinars or a specific webinar as defined by the filter. 

{ "filterType": "WEBINAR", "operator": "HAS_WEBINAR_REGISTRATION", "webinarId": "95909203370" // Optional }
Use this table to describe parameters / fields
ParameterAccepted Values
operator

The filter operator. Values include:

HAS_WEBINAR_REGISTRATION, NOT_HAS_WEBINAR_REGISTRATION, HAS_WEBINAR_ATTENDANCE, NOT_HAS_WEBINAR_ATTENDANCE

Property operation definitions

When filtering for records with the PROPERTY, INTEGRATION_EVENT, or SURVEY_MONKEY_VALUE filter type, you'll include an operation object to define the parameters of the filter.

Each property operation definition has an operationType and operator field, and most operations use a value or values field to specify values to compare the property against. You can also include an optional includeObjectsWithNoValueSet parameter to include records with no property value set. 

  • operationType and operator: classify the type of operation and how it will operate against a property of value.
  • includeObjectsWithNoValueSet: defines how the operation should treat records that do not have a value set for the defined property.
    • If true, a record without a value for the evaluated property will be accepted.
    • If false (default), a record without a value for the evaluated property will be rejected.

ALL_PROPERTY

For all properties, use this filter to determine whether a property value is known or is unknown as defined by the property operation.

list-filter-anyproperty

"filters": [ { "filterType": "PROPERTY", "property": "email", "operation": { "operationType": "ALL_PROPERTY", "operator": "IS_KNOWN" } } ]
Use this table to describe parameters / fields
ParameterAccepted Values
operator

The filter operator. Values include:

IS_KNOWN, IS_UNKNOWN

BOOL

For boolean type properties, use this filter to determine whether a current (or historical) boolean property value is or is not (or has or has not) equalled a specific value.

list-filter-BOOLEAN

"filters": [ { "filterType": "PROPERTY", "property": "boolean_property", "operation": { "operationType": "BOOL", "operator": "IS_EQUAL_TO", "value": true } } ]
Use this table to describe parameters / fields
ParameterAccepted Values
operator

The filter operator. Values include:

IS_EQUAL_TO, IS_NOT_EQUAL_TO,
HAS_EVER_BEEN_EQUAL_TO,
HAS_NEVER_BEEN_EQUAL_TO
  • Calculated properties cannot use a historical operator.
  • INTEGRATION_EVENT filterType and UNIFIED_EVENTS filterBranchType parameters only support IS_EQUAL_TO and IS_NOT_EQUAL_TO.

 

ENUMERATION

For enumeration type properties, such as checkboxes and selects, you can use this operation type to filter based on the current or historical value.

list-filter-enumeration

"filters": [ { "filterType": "PROPERTY", "property": "checkbox_property", "operation": { "operationType": "ENUMERATION", "operator": "IS_ANY_OF", "values": ["true", "false"] } } ]
Use this table to describe parameters / fields
ParameterAccepted Values
operator

The filter operator. Values include:

IS_NONE_OF,IS_ANY_OF, IS_EXACTLY, IS_NOT_EXACTLY, CONTAINS_ALL, DOES_NOT_CONTAIN_ALL, HAS_EVER_BEEN_ANY_OF, HAS_NEVER_BEEN_ANY_OF, HAS_EVER_BEEN_EXACTLY, HAS_NEVER_BEEN_EXACTLY, HAS_EVER_CONTAINED_ALL, HAS_NEVER_CONTAINED_ALL
  • Calculated properties cannot use a historical operator.
  • INTEGRATION_EVENT filterType and UNIFIED_EVENTS filterBranchType parameters only support IS_ANY_OF and IS_NONE_OF.

 

MULTISTRING

For string properties, you can use this operation type to filter based on the current value.

list-filter-multi-string

"filters": [ { "filterType": "PROPERTY", "property": "email", "operation": { "operationType": "MULTISTRING", "operator": "CONTAINS", "values": ["hubspot", "hotmail"] } } ]
Use this table to describe parameters / fields
ParameterAccepted Values
operator

The filter operator. Values include:

IS_EQUAL_TO, IS_NOT_EQUAL_TO, CONTAINS, DOES_NOT_CONTAIN, STARTS_WITH, ENDS_WITH,
HAS_EVER_BEEN_EQUAL_TO,
HAS_NEVER_BEEN_EQUAL_TO
  • Calculated properties cannot have a historical operator.
  • INTEGRATION_EVENT filterType and UNIFIED_EVENTS filterBranchType parameters only support IS_EQUAL_TO,  IS_NOT_EQUAL_TO, CONTAINS, DOES_NOT_CONTAIN, STARTS_WITH, and ENDS_WITH parameters.

 

NUMBER

For string properties, you can use this operation type to filter based on the current value.

list-filter-number

"filters": [ { "filterType": "PROPERTY", "property": "hs_analytics_average_page_views", "operation": { "operationType": "NUMBER", "operator": "IS_GREATER_THAN", "value": "5" } } ]
Use this table to describe parameters / fields
ParameterAccepted Values
operator

The filter operator. Values include:

IS_EQUAL_TO, IS_NOT_EQUAL_TO, IS_GREATER_THAN, IS_GREATER_THAN_OR_EQUAL_TO, IS_LESS_THAN, IS_LESS_THAN_OR_EQUAL_TO,
HAS_EVER_BEEN_EQUAL_TO,
HAS_NEVER_BEEN_EQUAL_TO
  • Calculated properties cannot have a historical operator.
  • INTEGRATION_EVENT filterType and UNIFIED_EVENTS filterBranchType parameters only support IS_EQUAL_TO,  IS_NOT_EQUAL_TO, IS_GREATER_THAN, IS_GREATER_THAN_OR_EQUAL_TO, IS_LESS_THAN, IS_LESS_THAN_OR_EQUAL_TO operators. 

STRING

For string properties, you can use this operation type to filter based on the current or historical value.

list-filter-string

"filters": [ { "filterType": "PROPERTY", "property": "email", "operation": { "operationType": "STRING", "operator": "HAS_EVER_CONTAINED", "value": "hubspot" } } ]
Use this table to describe parameters / fields
ParameterAccepted Values
operator

The filter operator. Values include:

IS_EQUAL_TO, IS_NOT_EQUAL_TO, CONTAINS, DOES_NOT_CONTAIN, STARTS_WITH, ENDS_WITH,
HAS_EVER_BEEN_EQUAL_TO,
HAS_NEVER_BEEN_EQUAL_TO, HAS_EVER_CONTAINED, HAS_NEVER_CONTAINED
  • Calculated properties cannot have a historical operator.
  • INTEGRATION_EVENT filterType and UNIFIED_EVENTS filterBranchType parameters only support IS_EQUAL_TO,  IS_NOT_EQUAL_TO, CONTAINS, DOES_NOT_CONTAIN, STARTS_WITH, and ENDS_WITH parameters.

 

TIME_POINT

For date properties, you can use this operation type to filter based on if a property has been updated before or after a specific time. That time can be specified as a specific date or relative to the current day.

Use the timeType field to configure how the property will be compared against time:

  • PROPERTY_REFERENCED: compares the property to another date property.
  • DATE: compares the property to a specific date
  • INDEXED: compares the property to a date relative to the current day.

Inputs and validations differ on the timeType field: PROPERTY_REFERENCED, DATE, INDEXED

PROPERTY_REFERENCED

Compare the property update date against the value in another date property.

list-filter-date-reference

"filters": [ { "filterType": "PROPERTY", "property": "birthdate", "operationType": "TIME_POINT", "operation": { "operator": "IS_AFTER", "timePoint": { "timeType": "PROPERTY_REFERENCED", "timezoneSource": "CUSTOM", "zoneId": "America/New_York", "property": "hs_latest_open_lead_date", "referenceType": "UPDATED_AT" }, "endpointBehavior": "EXCLUSIVE", "propertyParser": "UPDATED_AT", "type": "TIME_POINT" } } ]
Use this table to describe parameters / fields
ParameterAccepted Values
operator

The filter operator. Values inclue:

IS_AFTER, IS_BEFORE

  • The property passed must be a valid datetime property.
timeType

PROPERTY_REFERENCED

propertyParser

Values include:

VALUE, UPDATED AT

  • If VALUE is selected, the comparison is the value of the property.
  • If UPDATED_AT is selected, the updated time of the property is used for comparison.
endpointBehavior

EXCLUSIVE

zoneID

The account's default time zone. 

DATE

Compare the property update date against a specific date.

list-filter-date

"filters": [ { "filterType": "PROPERTY", "property": "hs_lifecyclestage_customer_date", "operation": { "operationType": "TIME_POINT", "operator": "IS_AFTER", "endpointBehavior":"EXCLUSIVE", "timePoint": { "timeType": "DATE", "timezoneSource": "CUSTOM", "zoneId":"America/New_York", "year":"2024", "month":"1", "day":"1", "hour":"23", "minute":"59", "second":"59", "millisecond":"999" } } } ]
Use this table to describe parameters / fields
ParameterAccepted Values
timeType

DATE

propertyParser

Values include:

VALUE, UPDATED AT

  • If VALUE is selected, the comparison is the value of the property.
  • If UPDATED_AT is selected, the updated time of the property is used for comparison.
endpointBehavior

EXCLUSIVE

zoneID

The account's default time zone. 

operator

The filter operator. Values inclue:

IS_AFTER, IS_BEFORE

  • The date must be a valid date.
  • When the property is IS_AFTER, these fields must be set:
    • “hour”: 23
    • “minute”: 59
    • “second”: 59
    • “millisecond”: 999
  • When the property is IS_BEFORE, these fields must be set:
    • “hour”: 00
    • “minute”: 00
    • “second”: 00
    • “millisecond”: 000

INDEXED

Compare the property update date against a date relative to the current day.

list-filter-date-indexed

"filters": [ { "filterType": "PROPERTY", "property": "hs_lifecyclestage_customer_date", "operation": { "operationType": "TIME_POINT", "operator": "IS_BEFORE", "endpointBehavior":"EXCLUSIVE", "timePoint": { "timeType": "INDEXED", "indexReference":{"referenceType": "TODAY"}, "offset":{"days":-10}, "timezoneSource": "CUSTOM", "zoneId":"America/New_York" } } } ]
Use this table to describe parameters / fields
ParameterAccepted Values
timeType

INDEXED

propertyParser

Values include:

VALUE, UPDATED AT

  • If VALUE is selected, the comparison is the value of the property.
  • If UPDATED_AT is selected, the updated time of the property is used for comparison.
endpointBehavior

EXCLUSIVE

zoneID

The account's default time zone. 

offset

Offsets the comparative date in days relative to the current day.

operator

The filter operator. Values inclue:

IS_AFTER, IS_BEFORE


  • When the property is IS_AFTER, offset must be set at <=0.
  • When the property is IS_BEFORE, offset must be set at >=0.

TIME_RANGED

For date properties, you can use this filter to determine if a property has been updated between or outside of two specific times. Using the indexReference field, these times can be specified as a specific date (DATE) or relative to the current day (INDEXED).
 

INDEXED

Compares the property update date to a time range relative to the current day.

list-filter-date-range-index

"filters": [ { "filterType": "PROPERTY", "property": "hs_lifecyclestage_customer_date", "operation": { "operator": "IS_NOT_BETWEEN", "operationType": "TIME_RANGED", "includeObjectsWithNoValueSet": false, "lowerBoundEndpointBehavior": "INCLUSIVE", "upperBoundEndpointBehavior": "INCLUSIVE", "propertyParser": "UPDATED_AT", "lowerBoundTimePoint": { "timeType": "INDEXED", "timezoneSource": "CUSTOM", "zoneId": "America/New_York", "indexReference": { "referenceType": "TODAY" }, "offset": { "days": -10 } }, "upperBoundTimePoint": { "timeType": "INDEXED", "timezoneSource": "CUSTOM", "zoneId": "America/New_York", "indexReference": { "referenceType": "NOW" } } } } ]
Use this table to describe parameters / fields
ParameterAccepted Values
timeType

INDEXED

propertyParser

Values include:

VALUE, UPDATED AT

  • If VALUE is selected, the comparison is the value of the property.
  • If UPDATED_AT is selected, the updated time of the property is used for comparison.
lowerBoundEndpointBehavior

INCLUSIVE

upperBoundEndpointBehavior

INCLUSIVE

zoneID

The account's default time zone. 

operator

The filter operator. Values inclue:

  • IS_BETWEEN, IS_NOT_BETWEEN
When the property is IS_AFTER, offset must be set at <=0.
  • When the property is IS_BEFORE, offset must be set at >=0.
indexReference

 Values include: {“referenceType”:”NOW”},{“referenceType”:”TODAY”}

  • If indexReference is equal to {“referenceType”:”NOW”}, offset must be >=0
  • If indexReference is equal to {“referenceType”:”TODAY”}, offset must be <=0

 
Other validations: 
  • If propertyParser is VALUE and operator is IS_BETWEEN:
    • lowerBoundTimePoint.indexReference should be {“referenceType”:”NOW”}.
    • upperBoundTimePoint.indexReference should be {“referenceType”:”TODAY”}.
  • For all other combinations of propertyParser and operator:
    • lowerBoundTimePoint.indexReference should be {“referenceType”:”TODAY”}.
    • upperBoundTimePoint.indexReference should be {“referenceType”:”NOW”}.

DATE

Compares the property to a specific time range.

list-filter-date-range-date

"filters": [ { "filterType": "PROPERTY", "property": "hs_lifecyclestage_customer_date", "operation": { "operator": "IS_BETWEEN", "type": "TIME_RANGED", "operationType": "TIME_RANGED", "includeObjectsWithNoValueSet": false, "lowerBoundEndpointBehavior": "INCLUSIVE", "upperBoundEndpointBehavior": "INCLUSIVE", "propertyParser": "VALUE", "lowerBoundTimePoint": { "timeType": "DATE", "timezoneSource": "CUSTOM", "zoneId": "America/New_York", "year": 2024, "month": 1, "day": 17, "hour": 0, "minute": 0, "second": 0, "millisecond": 0 }, "upperBoundTimePoint": { "timeType": "DATE", "timezoneSource": "CUSTOM", "zoneId": "America/New_York", "year": 2024, "month": 1, "day": 27, "hour": 23, "minute": 59, "second": 59, "millisecond": 999 } } } ]
Use this table to describe parameters / fields
ParameterAccepted Values
timeType

DATE

propertyParser

Values include:

VALUE, UPDATED AT

  • If VALUE is selected, the comparison is the value of the property.
  • If UPDATED_AT is selected, the updated time of the property is used for comparison.
lowerBoundEndpointBehavior

INCLUSIVE

upperBoundEndpointBehavior

INCLUSIVE

zoneID

The account's default time zone. 

operator

The filter operator. Values include:

IS_AFTER, IS_BEFORE

  • The date must be a valid date.
  • In the lowerBoundTimePoint parameter, these fields must be set:
    • “hour”: 23
    • “minute”: 59
    • “second”: 59
    • “millisecond”: 999
  • In the upperBoundTimePoint, these fields must be set:
    • “hour”: 00
    • “minute”: 00
    • “second”: 00
    • “millisecond”: 000
Was this article helpful?
This form is used for documentation feedback only. Learn how to get help with HubSpot.