Ping and Postback Token Formats
TokensOverview
When TrackDrive pings a buyer or fires a postback, each token in the URL, body, or headers is replaced with a value from the call. Buyers and partner platforms often expect a caller's number in one exact format, so pick the token whose output matches what the receiver asks for.
Caller Token Formats
For a caller whose number is +1 206-555-0116 in
Seattle, WA 98101:
| Token | Output | Format |
|---|---|---|
[caller_number] |
+12065550116 |
Plus sign, country code, number |
[caller_id_short] |
2065550116 |
Ten digits, no country code |
[caller_id_plain] |
12065550116 |
Country code and number, no plus |
[caller_state] |
WA |
Two-letter state code |
[caller_zip] |
98101 |
Five-digit zip code |
How Values Are Encoded
-
In a ping or postback URL, token values are URL-encoded.
[caller_number]arrives as%2B12065550116, which the receiver reads back as+12065550116. -
In a body or a header, a token arrives as its plain value:
[caller_number]is+12065550116. - In an XML body (when a header names XML), token values are never encoded.
When a receiver wants a plus sign and country code, use[caller_number] rather than typing +1 in front of[caller_id_short].
Matching Other Platforms' Tags
A posting URL copied from another platform may carry that platform's own placeholders. TrackDrive does not fill those in; replace each with the TrackDrive token of the same meaning. Ringba tags use single brackets and CallGrid tags use double brackets:
-
[tag:InboundNumber:Number](Ringba), the caller's number: use[caller_number]. -
[[tag:CallerId]](CallGrid), the caller's number: use[caller_number]. -
[[tag:VisitorStateCode|tag:InboundStateCode]](CallGrid), the caller's state: use[caller_state]. -
[[tag:VisitorZipCode|tag:InboundZipCode]](CallGrid), the caller's zip code: use[caller_zip].
This list matches meaning only. Check the receiver's posting instructions for the format it expects, then
pick the token from the formats table above.
Related Articles
The "How to Ping from TrackDrive to CallGrid (RTB)" article walks through a CallGrid buyer that uses these tokens. The "How to Find the System Tokens Reference" article shows where to see every token and its value on one of your own calls.