What goes in and what comes back
Every row below ends the same way: the decision lands in the tool where your team will act on it.
| System | What Squark takes in | What Squark sends back |
|---|---|---|
| CRM and fundraising systems | Donor records and gift history | Scores, next-best actions and audiences, ready for the donor record |
| Email and marketing automation | Engagement history | Audiences and suppression lists ranked by predicted response |
| Print vendors and mail houses | Direct mail history, package and cost data | Ranked mail files with the package and the ask for each donor |
| Ad platforms | Campaign and cost data, by file | Audiences built from predicted response |
| Data warehouses | The tables you choose | Predictions, model metrics and explanations, written back to Snowflake or SQL Server tables |
| Files | CSV and Excel | A file of every score and list |
| AI assistants | Your question, in plain language | Ranked results and the reasons behind each score |
Four ways to connect
- Files. Upload a CSV or Excel file and download the results.
- Connectors. Read from, and write back to, the CRM or warehouse you already run.
- Public APIs and microservices. Call Squark from your own workflows and send results onward.
- Model code export. Teams that build their own models can export the code and run it in their own pipeline.
Which connections come with which plan is on the pricing page.
Wealth screening and other data you already buy
Squark reads wealth screening, email engagement and direct mail history alongside your donor file and gift history. More of the donor record in means a sharper prediction out.
See how Squark works, the security page for how donor data is protected, or the Squark Agent for predictions inside your AI assistant.