> For the complete documentation index, see [llms.txt](https://docs.talkfurther.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.talkfurther.com/integrations/data-lake-integrations/snowflake.md).

# Snowflake

Further’s Snowflake integration gives your team **direct, secure access to rich lead and visitor data** in a modern data warehouse. Instead of waiting on manual reports, your analysts and agency partners can plug directly into Snowflake and combine Further data with your CRM, ad platforms, and financial systems for deeper, always‑up‑to‑date insights.

***

### How it Helps You

* **Faster, self‑serve reporting**\
  Your data team can query Further data directly in Snowflake, then plug it into tools like **Domo, Power BI, Databricks, or other BI platforms**—no custom exports or ad‑hoc CSVs required.
* **Unified view of performance**\
  Combine Further’s **lead and website interaction data** with your CRM, marketing, and financial data to answer questions like:
  * Which campaigns and partners are actually driving move‑ins?
  * How do different communities or service lines compare over time?
* **More flexibility for your analysts and agencies**\
  We expose clean **Prospects** and **Visitors** tables designed for analysis, so your internal team or agencies can slice data by community, channel, campaign, care type, and more, without depending on the Further UI.
* **Enterprise‑grade security**\
  Access is locked down with **read‑only roles, IP allow‑listing or reader accounts, and warehouse‑level controls**, so your team gets only the data they should see—nothing more.

***

### How it Works

1. **We provision a Snowflake database for your account**\
   Our team creates a **customer‑specific database** in Further’s Snowflake environment, scoped to your communities and configured for analytics (typically starting with two core tables: **PROSPECTS** and **VISITORS**).
2. **We populate 60 days of historical data and keep it fresh**\
   Stored procedures and scheduled tasks:
   * Backfill **\~60 days** of historical lead and visitor activity.
   * Run on a regular schedule (e.g., nightly) to keep your tables up‑to‑date as new leads and conversations flow through Further.
3. **We create a secure, read‑only Snowflake user (or reader account)**\
   You receive:
   * A **Snowflake login URL** specific to your account.
   * A **username and temporary password** (with MFA as needed).
   * Access limited to **your database/schema/tables**, with the option for **row‑level security** if you operate multiple brands.
4. **Your team or partners connect their tools**\
   Your data team or agency:
   * Connects their **BI or data platform** (e.g., Domo, Databricks, Power BI) directly to your Snowflake database using the provided credentials.
   * Builds dashboards, models, and reports using the **raw lead and visitor data** from Further alongside your other sources.

***

### In Closing

The Snowflake integration is designed to make Further **play nicely with your existing data stack**—giving you trustworthy, analysis‑ready data without manual exports or custom one‑off reporting. If your team or agency is interested in setting this up, your CSM can coordinate a quick technical scoping call and provide the exact connection details your data team needs to get started.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.talkfurther.com/integrations/data-lake-integrations/snowflake.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.