Agile

Overview

Signals reads deals and contacts from Agile on a schedule and sends the fields you mapped on to your ad platforms.

Two Agile modules are supported: Deals and Contacts. Contacts holds the details destinations match on, and Deals holds the outcome.

Supported destinations

Destinations supported by Agile

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

• An account in Agile holding the records you intend to sync, in the module you intend to read: Deals or Contacts. The fields you intend to map must already exist.
• Administrator access to your Agile account, on a plan that includes API access. You need it to generate the API key Signals connects with and to grant read access to the records you map.
• A single-select field on the module you sync holding each record’s stage, such as New, Contacted, Qualified, Won or Lost. 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 Agile tile. This connector authenticates with credentials you add manually. Enter the following, then click Validate Credentials.

Field	Where to find it
Email	The Agile user you are connecting as.
API Key	The developer or API settings screen in Agile.
Domain	Your Agile subdomain, the first part of your Agile address.

The Domain is your own Agile subdomain, so it decides which account is read. Check it before validating, since credentials from one account will not work against another.

The account you authenticate with must have the Admin role enabled. If it does not, ask your Agile administrator to enable it before you start, since the connection is made as that account.

Caution

The connection is made as the account you authenticate with, and that account needs the Admin role, so the API key carries administrator reach. Enter it on the Datahash connection screen only, and use a service account rather than a person’s login where you can.

Configuration

Instance Setup

Select the Integration Type based on where the data needs to be sent. The options are Offline Events, Audience, Meta CAPI CRM, Google Leads, TikTok Leads, Snapchat Leads and LinkedIn Leads. The choice decides which fields you are asked to map and which destinations the connection can feed, so settle it first. Then choose the Agile module Signals reads from, one of Deals or Contacts, and give the instance a name. Only modules the connection can see will appear in the list.

Field mapping

Map your Agile fields onto the schema Signals expects. Each field is a dropdown of your own fields, so nothing has to be renamed in the CRM. 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 credentials still work and that the mapped fields actually contain data, so a mapping pointed at an empty field 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 fields 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. Value, currency and product fields describe the conversion rather than the person, so they do not affect match rates.

Best practices

• If you map a platform lead ID such as the Meta Lead ID, keep that field as text. A numeric field truncates long IDs, which is the most common cause of lead conversions never matching.
• 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 Agile helps match rates: email addresses in lowercase, phone numbers in E.164 format, and no trailing spaces.

Troubleshooting & FAQ

A module or field is not listed. The connection cannot see it. Check access in Agile, then reopen the setup.

Validate Credentials fails. Check the email, API key and domain all come from the same Agile account, and that the account has the Admin role enabled.

Test Connection fails. A required field is unmapped, or a mapped field is empty.

Match rates are low. Map more identifiers and fix formatting at source. A hash only matches if both sides normalized the value the same way.