What is a Token?

Learn how Delpha uses tokens to evaluate records, and how data pipeline complexity determines whether a check consumes 1 or more tokens, depending on your initial data.

What Is a Token in Delpha?

In Delpha, a token represents a credit used to evaluate and enhance a single record (Account, Contact, or Lead). Token usage is tied to how frequently you assess or enrich your data, as well as the completeness of the starting data on that record.

How Token Consumption Works: The Pipeline Engine

Delpha's data quality engines are linked and run as pipelines. Token consumption depends on how seamlessly a record can progress through this pipeline without getting blocked by missing information:

• Single Check (1 Token): If the pipeline can run end-to-end because the base information is present, only 1 token is consumed.

• Multi-Step Check (2 or more Tokens): If a core element is missing and needs a recommendation to be fixed before the next engine can run, the system must perform two separate runs. Depending on the initial quality of your data, the system may require more than two runs if multiple core elements are missing and must be found sequentially.

ℹ️ Note: Token usage applies when Delpha performs a data quality evaluation, a field-level enrichment, or an update based on configured automation.

---

Token Consumption Examples

To help you understand how missing data impacts pipeline runs, here are common scenarios:

Accounts

• Account with a correct website (but no LinkedIn or Parent Company): The system uses the existing website to suggest a LinkedIn profile and the correct parent company in a single check. (1 Token)

• Account without a website and without a Parent Company: The system must first run a check to identify the correct website. Once the website is found, it must perform a second run to find the parent company. (2 Tokens)

Contacts

• Contact without an email: The system performs one check to retrieve the missing email address. (1 Token)

• Contact with an email (but no LinkedIn): The system performs one check to simultaneously validate the existing email and provide the missing LinkedIn profile. (1 Token)

• Job change alert: The system performs one check to identify the contact's new role (1 Token). If the new role requires the system to find a new email address, an additional run is required. (Total: 2 Tokens)

---

Managing Your Token Frequency

In addition to the pipeline rules above, token usage scales with how often you choose to schedule your data assessments. Each record may consume up to one token per day, depending on your schedule.

Frequency	Tokens per Record per Year
Daily	Up to 365
Monthly (every 30 days)	12
Quarterly	4
Biannually	2

The less frequently you refresh your data, the fewer tokens you'll use—allowing you to control costs and optimize efficiency.

💡 Learn More: Find more details on the Delpha.io Pricing Page.