CONNECTIONS / Attio
Attio + Datahash: activate a fully custom object model.
Attio is built around objects and lists you define yourself, not a fixed deals-and-contacts shape. Signals reads whatever object model you built and maps the record changes that matter to conversion events and audiences on every connected platform.
- ● attio :: signals live
- > read objects object=deals status=won rows=2,214
- > read lists list=customers
- hash sha256(email,phone) scope=objects.read,lists.read
- route meta · google · tiktok · snap
- ✓ 4 destinations synced · match 82%
The signal Attio yields, and receives.
Every kind of signal that moves between Attio and the platforms, through one hashed, deduplicated route.
- Offline conversions
- A record on any Attio object reaching a status you define posts as a conversion event, whatever you named the object or the stage.
- Lead conversions
- List membership leaves Attio hashed and becomes a scheduled audience segment, so a saved list stays a live audience instead of a one-time export.
- Custom audiences
- Custom attributes on a record travel with the event, so a field unique to your Attio setup still reaches the destination as usable data.
- Lead generation inbound
- Deal or opportunity value attached to a record reaches the ad platform as a valued offline conversion tied to its source campaign.
Pick your platform. Every use case for it, in one place.
Every way Attio data moves, grouped by platform and ranked by how many use cases Attio supports.
Google 5 
Meta 4 
Snap 4 
TikTok 4 
LinkedIn 3 
OpenAI 1 - Offline conversions Google Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Offline conversions Google Store Sales Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions Google Enhanced Conversions for Leads Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Custom audiences Google Customer Match Contact segments refreshed as hashed, scheduled audiences.
- Lead generation Google Forms Campaign lead submissions created as records in real time, deduped before creation.
- Offline conversions Meta Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions Meta Conversions API for CRM Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Custom audiences Meta Custom Audience Contact segments refreshed as hashed, scheduled audiences.
- Lead generation Meta Lead Ads Campaign lead submissions created as records in real time, deduped before creation.
- Offline conversions Snapchat Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions Snapchat Leads Conversions API Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Custom audiences Snapchat Custom Audience Contact segments refreshed as hashed, scheduled audiences.
- Lead generation Snapchat Lead Generation Ads Campaign lead submissions created as records in real time, deduped before creation.
- Offline conversions TikTok Offline Events API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions TikTok CRM Events API Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Custom audiences TikTok Custom Audience Contact segments refreshed as hashed, scheduled audiences.
- Lead generation TikTok Lead Generation Campaign lead submissions created as records in real time, deduped before creation.
- Offline conversions LinkedIn Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions LinkedIn Leads Conversions API Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Lead generation LinkedIn Lead Generation Forms Campaign lead submissions created as records in real time, deduped before creation.
From authorization to delivered signal.
-
Connect
Connect with a scoped Attio API key, revocable any time.
-
Map objects
Map the objects, lists, and attributes you built in Attio to platform events.
-
Hash and consent
Identifiers are hashed and consent flags applied before anything leaves Attio.
-
Deliver
Delivery runs by webhook or on a schedule, with per-destination match reporting.
Attio questions, answered.
We built a fully custom object model in Attio. Does Signals still work?
Yes, that is the case it is built for. Attio does not force a fixed deals and contacts shape, so the mapper works against whatever objects, statuses, and attributes exist in your workspace rather than assuming standard CRM field names. You map your object model to platform events directly.
Does Signals read Attio in near real time?
Where Attio exposes webhooks for an object, Signals reads changes in near real time. Where it does not, a scheduled read covers the gap on a cadence you set. Either way, the debugger shows per-destination match feedback so you can confirm a specific record change actually reached a platform.
What if we rename an object or add a new attribute later?
The mapping is attached to the object and attribute names at the time you set it up, so renaming or adding fields in Attio does not silently break a live connection. You revisit the mapper to point the new field at an event, and existing mappings keep running until you choose to change them.
NEXT STEP
See your Attio data working in every ad platform.
Ready to enable a use case, or still mapping what Attio data could do? Our team helps you find the right place to start.
