> For the complete documentation index, see [llms.txt](https://experience-digital-transform.gitbook.io/experience-digital-transformation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://experience-digital-transform.gitbook.io/experience-digital-transformation/analytics/analytics-building-block.md). # Analytics Building Block Turns raw government data into dashboards, scores and triggers decision-makers actually use — the shared layer that lets a government read what its own systems already know, and act on it. **Knowledge product** · Digital Public Infrastructure · 4 Components This section holds four components, each showing a different facet of the analytics story: the formal specification, a reference implementation, a national example from Kazakhstan, and a family-focused use case showing how analytics can support proactive social services.


	Technical Specifications The deep-reference resource: formal, technology-neutral requirements, interfaces, data structures, standards, Building Block interactions, and architectural expectations.	Technical Specifications
	Reference Implementation A concrete, deployable stack — Apache Airflow, ClickHouse and Apache Superset — showing what an Analytics Building Block implementation can actually look like.	Reference Implementation
	The Case of Kazakhstan A real national example showing how advanced government analytics and proactive services have been implemented in practice — the legal, security and architectural decisions behind it.	The Case of Kazakhstan
	Use Case: Digital Household Welfare Profiling and Proactive Social Support Analytics A worked, technology-neutral example of using analytics for household welfare profiling and proactive social support — vendor-neutral, so any government can adapt it.	Use Case: Digital Household Welfare Profiling and Proactive Social Support Analytics

## How the four fit together Start with the **Technical Specifications** for the formal, technology-neutral definition of the Analytics Building Block and how it fits into the wider DPI architecture. The **Reference Implementation** then shows what those ideas can look like in a concrete, deployable technology stack. **The Case of Kazakhstan** grounds the approach in a real national context, showing how advanced analytics and proactive government services have been implemented in practice. Finally, the **Digital Household Welfare** use case shows how the building block can be applied to a specific family-focused policy challenge in a reusable, vendor-neutral way. These four are complementary views of the same problem space, not a strict build sequence — each stands on its own, and none is presented as a direct implementation of another. --- # 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://experience-digital-transform.gitbook.io/experience-digital-transformation/analytics/analytics-building-block.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.

:file-contract:

:code-branch:

:globe:

:bullseye: