# Hubspot: Contact Lists ## Description * Each record represents a contact list in Hubspot. ## Supported Data Sources * HubSpot ## Columns | Type | Name | Description | | -------- | --------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | BOOLEAN | is\_contact\_list\_deleted | Boolean indicating whether a record has been deleted in Hubspot and/or inferred deleted in Hubspot by Fivetran; \_fivetran\_deleted and is\_deleted fields are equivalent. | | DATETIME | \_fivetran\_synced | Timestamp of when Fivetran synced a record. | | DATETIME | created\_timestamp | A timestamp of the time the list was created. | | BOOLEAN | is\_deletable | If this is false, this is a system list and cannot be deleted. | | BOOLEAN | is\_dynamic | Whether the contact list is dynamic. | | INTEGER | contact\_list\_id | The ID of the contact list. | | INTEGER | metadata\_error | Any errors that happened the last time the list was processed. | | DATETIME | metadata\_last\_processing\_state\_change\_at | A timestamp of the last time that the processing state changed. | | DATETIME | metadata\_last\_size\_change\_at | A timestamp of the last time that the size of the list changed. | | STRING | metadata\_processing | One of DONE, REFRESHING, INITIALIZING, or PROCESSING. DONE indicates the list has finished processing, any other value indicates that list membership is being evaluated. | | INTEGER | metadata\_size | The approximate number of contacts in the list. | | STRING | contact\_list\_name | The name of the contact list. | | INTEGER | portal\_id | The hub ID. | | DATETIME | updated\_timestamp | A timestamp of the time that the list was last modified. | | INTEGER | total\_bounces | The total number of bounce email events. | | INTEGER | total\_unique\_bounces | The total number of unique email sends with a bounce email event. | | INTEGER | total\_clicks | The total number of click email events. | | INTEGER | total\_unique\_clicks | The total number of unique email sends with a click email event. | | INTEGER | total\_deferrals | The total number of deferral email events. | | INTEGER | total\_unique\_deferrals | The total number of unique email sends with a deferral email event. | | INTEGER | total\_deliveries | The total number of delivery email events. | | INTEGER | total\_unique\_deliveries | The total number of unique email sends with a delivery email event. | | INTEGER | total\_drops | The total number of drop email events. | | INTEGER | total\_unique\_drops | The total number of unique email sends with a drop email event. | | INTEGER | total\_forwards | The total number of forward email events. | | INTEGER | total\_unique\_forwards | The total number of unique email sends with a forward email event. | | INTEGER | total\_opens | The total number of open email events. | | INTEGER | total\_unique\_opens | The total number of unique email sends with a opens email event. | | INTEGER | total\_prints | The total number of print email events. | | INTEGER | total\_unique\_prints | The total number of unique email sends with a print email event. | | INTEGER | total\_spam\_reports | The total number of spam report email events. | | INTEGER | total\_unique\_spam\_reports | The total number of unique email sends with a spam report email event. | | INTEGER | total\_unsubscribes | The total number of unsubscribe email events. | | INTEGER | total\_unique\_unsubscribes | The total number of unique email sends with a unsubscribe email event. | --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://endash-guidance-docs.gitbook.io/cigro-data-templates/data-model-templates/hubspot-contact-lists.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.