> For the complete documentation index, see [llms.txt](https://docs.chord.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chord.co/connect-sources/data-sources/messaging-module.md). # Messaging module ## Messaging module ## Overview Chord's Messaging Module unlocks connections for various sources of messaging data, including sources like email and SMS platforms, and enables a robust Messaging Explore, a wide dataset populated with enriched data fields. The Messaging Explore allows the creation of custom reports and audiences or customer segments with granularity down to the campaign level. Sample fields available in the Messaging explore: * Number of sends * Number of opens * Number of clicks The module enables direct connections to the following sources: * Klaviyo * Iterable * Attentive (Coming Soon) ## Use cases * Brands create reports to track sends, opens, and clicks for various campaigns * Brands create reports to analyze subscribe and unsubscribe rates Please reach out to or your account executive for more information about or access to this feature. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.chord.co/connect-sources/data-sources/messaging-module.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.