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.

Where Squark connects, what it reads and what it returns
System What Squark takes in What Squark sends back
CRM and fundraising systemsDonor records and gift historyScores, next-best actions and audiences, ready for the donor record
Email and marketing automationEngagement historyAudiences and suppression lists ranked by predicted response
Print vendors and mail housesDirect mail history, package and cost dataRanked mail files with the package and the ask for each donor
Ad platformsCampaign and cost data, by fileAudiences built from predicted response
Data warehousesThe tables you choosePredictions, model metrics and explanations, written back to Snowflake or SQL Server tables
FilesCSV and ExcelA file of every score and list
AI assistantsYour question, in plain languageRanked 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.