---
title: "How to send intent data in MadKudu from your data warehouse Snowflake, BigQuery or via S3?"
slug: "how-to-send-intent-data-in-madkudu-from-your-data-warehouse-snowflake-bigquery-or-via-s3"
updated: 2025-12-30T13:34:52Z
published: 2025-12-30T13:34:52Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.madkudu.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How to send intent data in MadKudu from your data warehouse Snowflake, BigQuery or via S3?

Previous article: [How to integrate intent data to MadKudu?](/v1/docs/how-to-integrate-intent-data-to-madkudu)

Whether this data already sits in your data warehouse or in other tools, the way to send it to MadKudu is through our native integration with [Snowflake](/v1/docs/snowflake-1), [BigQuery](/v1/docs/bigquery-1), or [Amazon S3](/v1/docs/amazon-s3-1).

# **Format**

To ingest Intent data, MadKudu needs the same format as other tracking tools like

email | event | event_timestamp | event_key

which represent "**someone** did **something** on that **date**" that shows intent.

If there is no date associated with the intent data it won't be usable since the intent is related to a point in time.

With intent data, you usually don't get the email of the person, but just the domain associated with the IP.You'll need to transform the domain to "anonymous@domain.com" to send an email to Madkudu.

# **Step by step**

We're here to help! Our support team will be happy to walk you through these steps, please contact the team.

## Step 1: Format your data

> [!NOTE]
> Different sources have different format requirement.
> 
> It’s possible to upload a single table to your Amazon s3 bucket, while Snowflake and Bigquery require creating 2 separate tables (Contacts & Events) to get intent data into Madkudu. Make sure to check the exact requirements from the pages below!

- [Snowflake](/v1/docs/snowflake-1)
- [BigQuery](/v1/docs/bigquery-1)
- [Amazon S3](https://help.madkudu.com/docs/amazon-s3-how-to-format-and-send-data-to-madkudu-via-a-bucket?highlight=s3)

## Step 2: Connect your source (Snowflake, BigQuery or S3) to MadKudu

- [Snowflake](/v1/docs/snowflake-1)
- [BigQuery](/v1/docs/bigquery-1)
- [Amazon S3](https://help.madkudu.com/docs/amazon-s3-how-to-format-and-send-data-to-madkudu-via-a-bucket?highlight=s3)

## Step 3: Map these events in the Event Mapping

Once MadKudu is pulled data from your source you'll be able to add these events to the Event mapping.

Here's the [article](/v1/docs/how-to-create-or-edit-the-event-mapping) to learn how.

## Step 4: Start leveraging your data!

#### **In MadKudu Copilot**

Once the event mapping is published, these intent events will automatically show in MadKudu Copilot in the

- Account Intelligence: in the activity feed
- Playbooks & Explore: available to use as filters to create playbooks or views

#### **In MadKudu Scoring**

If you have an Account Engagement model pushed to Salesforce, the signals field will also update automatically. To assign weight to these events, follow the usual steps to include new events to the Account Likelihood to buy model:

1. Duplicate your live Account Likelihood to Buy model
2. Load a fresh dataset
3. You should now see the new events in the Insights and Event Weights section. You can adjust the weight and decay.

-