AI Matching Agent & Saved Searches: What data can we actually trace in DataLink?

Hey everyone,

With Avionté rolling out the new AI Matching Agent update (2026-08-07), Saved Searches are about to become critical. Because the AI relies on them to rank candidates, our search quality directly dictates our match quality.

Before we build new workflows around this, I’m trying to see what we can actually track and measure on the backend inside DataLink.

Two main questions for anyone who has dug into the schema recently:

1. Saved Search Utilization: Does DataLink expose metadata on which Saved Searches internal users are actively running or saving? (Looking to audit usage, find top queries, or see adoption rates).

2. Attribution / Sourcing Path: Is there a clean way to join a Saved Search execution back to candidate placement data? Ideally, we’d love to track if a candidate was surfaced via a specific Saved Search and ultimately hired on that requisition to prove out sourcing ROI.

If anyone has identified the specific tables where search definitions/logs live—or if you’ve built a workaround in Snowflake to bridge this gap—I’d love to hear how you’re tackling it.

Thanks,
Rick