Attio

Overview

Signals reads records from an Attio workspace on a schedule and sends the fields you mapped on to your ad platforms.

Two Attio modules are supported: People and Deals. People holds the contact details destinations match on, and Deals holds the outcome, such as a deal reaching closed won.

Supported destinations

Destinations supported by Attio

Category	Supported
Offline Conversions	Google Offline Conversions API Google Store Sales LinkedIn Offline Conversions API Meta Offline Conversions API OpenAI Offline Conversions API Snapchat Offline Conversions API TikTok Offline Events API
Lead Conversions	Google Enhanced Conversions for Leads LinkedIn Leads Conversions API Meta Conversions API for CRM Snapchat Leads Conversions API TikTok CRM Integrations
Custom Audience	Google Customer Match Meta Custom Audience Snapchat Custom Audience TikTok Custom Audience

Prerequisites

• The Attio workspace and module holding the records you intend to sync, People or Deals, with the attributes you intend to map already present.
• Administrator access to your Attio workspace, on a plan that includes API access. You need it to generate the workspace access token Signals connects with and to grant read access to the records you map.
• A single-select attribute holding each record’s stage, such as New, Contacted, Qualified, Won or Lost, or a list status if that is where stage lives in your workspace. Each value maps to a conversion event, so a record left on a stale stage reports the wrong one.

Authentication

In Studio, open Sources, find the CRM category, and click the Attio tile. This connector authenticates with a token you add manually.

Field	Where to find it
Workspace Access Token	Generated in the developer section of your Attio workspace settings.

Caution

The workspace access token grants access to the whole Attio workspace. Enter it on the Datahash connection screen only, and revoke it in the workspace developer settings once it is no longer in use.

Configuration

Instance Setup

Select the Integration Type based on where the data needs to be sent. The choice decides which attributes you are asked to map and which destinations the connection can feed, so settle it first. Then choose the module Signals reads from, either People or Deals, and give the instance a name. Only modules the token can see will appear in the list, because Attio scopes access per module, so a workspace can expose People and withhold Deals from the same connection.

Field mapping

Map your Attio attributes onto the schema Signals expects. Each field is a dropdown of the attributes on the module you selected, so nothing has to be renamed in the workspace. What you are asked to map depends on the integration type.

Group	Fields
Configuration	Event name, event time, last modified date, lead lifecycle stage.
Personal information	Email, phone, first name, last name, city, state, country, postcode, gender, date of birth, Facebook click ID, Google click ID, OpenAI identifier, source URL.
Product	Total value, currency, product type, name, category, ID, brand, price, quantity, transaction ID, number of items.

Test connection

Click Test Connection before finishing. It checks both that the token still works and that the mapped attributes actually contain data, so a mapping pointed at an empty attribute fails here rather than silently later.

Manage instance

One instance is configured for one module. To read another module, configure it on a new instance from the Manage existing instance table. To change an existing one, open it from the Manage existing instance table, click the edit option in the menu to the top right, update the fields and click Finish.

Data & identifiers

Only the attributes you map are read. Personal identifiers are normalized and SHA-256 hashed before they are sent to any destination.

Email, phone, name and location are what destinations match on. Deal value, currency and product attributes describe the conversion rather than the person, so they do not affect match rates.

Best practices

• Decide which value to use on multi-value attributes such as email address and phone number, and apply the same rule across every connection reading the workspace. Attio does not mark one value as primary.
• Confirm where the outcome you want to report is held before mapping. In Attio this is often list membership rather than an attribute on the record.
• Ensure the module holds personal information such as email address and phone number. Destinations weight these highest, so records without them match at a much lower rate.
• Maintaining consistent formatting in Attio helps match rates: email addresses in lowercase, phone numbers in E.164 format, and no trailing spaces.
• Name each instance for the module and integration type it serves, since a workspace often ends up with several.

Troubleshooting & FAQ

The wrong email address is being sent. The attribute holds several values, and Attio does not mark one as primary, so the value to send is set by the mapping.