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

# Sending Data to Aampe

> See the following guides for instructions on how to send data to Aampe

## Supported Data Sources

Don't see your preferred data source? Send an email to [support@aampe.com](mailto:support@aampe.com) and we'll find a solution.

<Accordion title="API" icon="code">
  * [Aampe Streaming API](/developer-guide/data-ingest/data-sources/streaming-aampe-api)
</Accordion>

<Accordion title="Cloud Database" icon="database">
  * [Amazon RDS](/developer-guide/data-ingest/data-sources/database-aws-rds)
  * [Google Spanner](/developer-guide/data-ingest/data-sources/database-spanner)
</Accordion>

<Accordion title="Cloud Storage" icon="bucket">
  * [Amazon S3](/developer-guide/data-ingest/data-sources/cloud-storage-aws-s3)
  * [Google Cloud Storage](/developer-guide/data-ingest/data-sources/cloud-storage-gcs)
  * [SFTP](/developer-guide/data-ingest/data-sources/sftp)
</Accordion>

<Accordion title="Customer Data Platform" icon="user">
  * [Amplitude - batch](/developer-guide/data-ingest/data-sources/amplitude-batch)
  * [Amplitude - cohort](/developer-guide/data-ingest/data-sources/amplitude-cohort)
  * [Amplitude - streaming](/developer-guide/data-ingest/data-sources/amplitude-streaming)
  * [Clevertap](/developer-guide/data-ingest/data-sources/clevertap)
  * [Firebase Cloud Messaging](/developer-guide/data-ingest/data-sources/firebase)
  * [Mixpanel](/developer-guide/data-ingest/data-sources/mixpanel)
  * [Segment](/developer-guide/data-ingest/data-sources/segment)
</Accordion>

<Accordion title="Data Warehouse" icon="cloud">
  * [Databricks](/developer-guide/data-ingest/data-sources/data-warehouse-databricks)
  * [Google BigQuery](/developer-guide/data-ingest/data-sources/data-warehouse-bigquery)
  * [Snowflake](/developer-guide/data-ingest/data-sources/data-warehouse-snowflake)
  * [Redshift](/developer-guide/data-ingest/data-sources/data-warehouse-redshift)
</Accordion>

## Data Integration FAQs

<Accordion title="What should we include in our event feed?" icon="sparkles">
  Aampe needs a high-fidelity event feed that includes key conversion events *and* day-to-day engagement events.

  [Read more about what a "good" event feed looks like.](/developer-guide/data-ingest/data-ingest-help/what-events-should-i-send-to-aampe)
</Accordion>

<Accordion title="How often should we send data to Aampe?" icon="sparkles">
  For most customers, a daily sync is a good starting point. More frequent syncs will improve the accuracy of audiences, but introduces some cost and complexity.

  For real-time use cases (e.g. abandoned cart messages), you will want to [send events to Aampe via API](developer-guide/data-ingest/data-sources/streaming-aampe-api.mdx).

  [Continue reading about what to consider when deciding how frequently to send data to Aampe.](/developer-guide/data-ingest/data-ingest-help/how-often-data-sync)
</Accordion>

<Accordion title="Do we need to format data in a specific way?" icon="sparkles">
  Yes. Both event and user-attribute data should be formatted to be compatible with Aampe's system. Depending on where your data originates, this may not require any work on your part.\
  \
  [Continue reading about data formatting](/developer-guide/data-ingest/data-model). 
</Accordion>

<Accordion title="How does Aampe use event and attribute data?" icon="sparkles">
  Event data is central to how agents measure their success and learn what messages successfully influence user behavior.

  User attributes are primarily used to define which users are eligible for receiving a given message. Eligibility can also be based on events (we will send message ABC to users who have attribute X and performed Y action in the last week).

  [Read a more detailed explanation of why we built Aampe agents to learn from events instead of user attributes.](/user-guide/welcome-to-aampe/how-does-aampe-work/agent-help/events-vs-attributes)
</Accordion>