# Iterable: Users ## Description * Table that provides unique user enriched information. ## Supported Data Sources * Iterable ## Columns | Type | Name | Description | | -------- | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | STRING | user\_id | User identifier, for userID-based projects. | | STRING | \_fivetran\_user\_id | A Fivetran-created unique identifier for the new Iterable schema in Aug 2023, for users, derived from hashing user\_id and/or email, depending on project type. | | STRING | unique\_user\_key | The unique identifier of the user. With the new schema (Aug 2023), it is the \_fivetran\_user\_id. This is a hash of user\_id and/or email, depending on project type. If using the old schema, it is email. | | STRING | email | The user's email. User identifier, for email-based projects. Previously was the unique identifier for user records, for the old Iterable schema before the August 2023 updates. | | STRING | first\_name | First name of the user | | STRING | last\_name | Last name of the user | | DATETIME | signup\_date | Timestamp as epoch time in milliseconds of when the user signed up | | STRING | signup\_source | Source where the user signed up | | DATETIME | updated\_at | Last update timestamp as epoch time in milliseconds | | STRING | phone\_number | Phone number associated with the user | | STRING | email\_list\_ids | Array of all email lists associated with the user | | INTEGER | count\_lists | Total count of lists associated with the user | | INTEGER | count\_total\_campaigns | Count of all campaigns the user has been in | | DATETIME | first\_event\_at | The first event the user ever encountered | | DATETIME | last\_event\_at | The most recent event the user has encountered | | INTEGER | total\_emailclick | Total number of email clicks the user has performed | | INTEGER | total\_emailunsubscribe | Total unsubscription events the user has performed | | INTEGER | total\_emailcomplaint | Total email complaints the user has performed | | INTEGER | total\_customevent | Total custom events associated with the user | | INTEGER | total\_emailsubscribe | Total subscription events the user has performed | | INTEGER | total\_emailopen | Total email opened events the user has performed | | INTEGER | total\_pushsend | The push send events the user has experienced | | INTEGER | total\_smsbounce | Total sms bounces that are associated with the user | | INTEGER | total\_pushbounce | Total number of push bounces associated with the user | | INTEGER | total\_inappsendskip | Total in app send skips associated with the user | | INTEGER | total\_smssend | Total sms sends that the user has experienced | | INTEGER | total\_inappsend | Total in app sends the user has experienced | | INTEGER | total\_pushopen | Total push messages the user has opened | | INTEGER | total\_emailsend | Total emails that have been sent to the user | | INTEGER | total\_pushsendskip | Total push sends the user has skipped | | INTEGER | total\_inappopen | Total in app opens the user has performed | | INTEGER | total\_emailsendskip | Total email sends the user has skipped | | INTEGER | total\_emailbounce | Total number of emails that have bounced from the user | | INTEGER | total\_inappclick | Total in app clicks associated with the user | | INTEGER | total\_pushuninstall | Total push uninstall events the user has performed | --- # 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/iterable-users.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.