Token Overview

Token

A Token is a named placeholder that gets replaced with a concrete value at runtime. Tokens let you write one routing response, one SMS body, one conversion URL, or one webhook payload and have it automatically populated with caller-specific data when a call or lead comes in.

Every call and lead in TrackDrive carries a collection of token values. When the system renders a template that contains a token reference like [caller_id] or [loan_amount], the literal token name is swapped for the value on the current call or lead.

Token Syntax

Token references use square brackets: [token_name]. The token name inside the brackets may contain only lowercase letters, digits, and underscores. The platform also supports an optional default-value suffix written in curly braces immediately after the brackets:[token_name]{default if blank}. The default is emitted only when the token has no value on the current call or lead.

Two Classes of Token

TrackDrive distinguishes between system tokens and custom tokens.

• System tokens are built into the platform. They describe universal properties of a call or lead: caller_id, total_duration, payout, geo_state, buyer_name, and many more. System Tokens cannot created, renamed, or deleted. Their values are computed automatically by the platform at render time.
• Custom tokens are defined on the Account. They capture business-specific data like loan_amount, interest_rate, campaign_id, or anything else submitted with a lead or set via the API.

Where Tokens Are Used

Tokens appear in many places across the platform:

• Conversion URLs when a call converts.
• Outbound Webhook Payloads.
• SMS and email bodies sent by schedules.
• Key press prompts and IVR menus.
• Lead import mappings.

Anywhere you can enter free text in a form field that might need caller-specific substitution, tokens are
supported.