Ringba collects data from multiple sources by using a variety of enrichment methods. Ringba stores this data in tags. Once it's in a tag in your account, this data is available for you to include in the information you send to third parties when you use tools such as pixels and ring trees.
To include the data, you add a "token" to the URL. A token is a placeholder for the data. When Ringba fires the pixel or pings the ring tree, it replaces the token with the actual information from the tag.
This article contains the following sections:
- Most Common Tokens by Source
- How to Find All Tags for a Specific Call
- How to Find the Token that Corresponds to a Specific Tag
- Most Common Tokens FAQ
Most Common Tokens by Source
The following sections show the most common tokens collected from a specific source.
Number Pools
Number pools collect information from you caller's session activity on your landing page prior to dialing your number. These are the most commonly used number pools tokens:
| Data in Tag | Token |
| State: | [tag:Geo:SubDivision] |
| State code: | [tag:Geo:SubDivisionCode] |
| City: | [tag:Geo:City] |
| ZIP Code: | [tag:Geo:ZipCode] |
| IP address: | [tag:Technology:IPAddress] |
| User agent string: | [tag:Technology:UserAgentString] |
Instant Caller Profile
Instant caller profile (ICP) pulls from a repository of caller information that is broad, consistently updated, and easy to use. These are the most commonly used ICP tokens:
| Data in Tag | Token |
| City: | [tag:Address:City] |
| State: | [tag:Address:State] |
| ZIP Code: | [tag:Address:Zip 5] |
| Email address: | [tag:Email Addresses:Email 1 Address] |
| Age: | [tag:Demographics:Age] |
Other Sources
Ringba contains many other useful data points as well. These are the most common tokens in the Ringba platform:
| Data in Tag | Token |
| Caller ID: | [tag:InboundNumber:Number] |
|
Caller ID with no plus: |
[tag:InboundNumber:Number-NoPlus] |
|
Caller ID without the country code: |
[tag:InboundNumber:AreaCode][tag:InboundNumber:Prefix][tag:InboundNumber:Suffix] |
| Inbound Call ID: |
[Call:InboundCallId] |
| Publisher Name: |
[tag:Publisher:Name] |
| Publisher ID: |
[tag:Publisher:Id] |
| Target Name: |
[tag:Target:Name] |
| Target ID: |
[tag:Target:Id] |
| State: |
[tag:InboundNumber:State] |
| Revenue Amount: |
[Call:ConversionAmount] |
| Payout Amount: |
[Call:ConversionPayout] |
| RTB ID: |
[tag:rtb:bidid] |
| Is Duplicate: |
[tag:CallInfo:IsDuplicate] |
| Google Click ID: |
[tag:Integration:googleClickId] |
|
Facebook Click ID: |
[tag:Integration:facebookClickId] |
How to Find All Tags for a Specific Call
The list above contains the tokens that correspond to the most common tags, but you can find a complete list of all tags on a specific call. Use the following steps:
- Navigate to Reporting > Default.
- Under Call Details, click the arrow icon on the left side of the call to expand it.
- Click the Tags tab:
How to Find the Token that Corresponds to a Specific Tag
You can find the token that corresponds to a specific tag by using Ringba's pixels tool.
- Navigate to Integrations > Pixels.
- Click the Create Pixel button.
- Click the Token button and search for the desired tag.
- Click the tag.
The token appears in the URL field:
Learn More: To create a custom tag, see our article on URL Parameters
Most Common Tokens FAQ
What enrichment sources does Ringba use to aggregate data?
Ringba currently uses these enrichment methods:
The data available through IDE and gather nodes in call flows depends on how you configure the feature.
Data from IDE appears under the User reporting menu name. When you open the Tags tab on the Call Details Report, you see this data under the User subsection.
For that reason, the tokens for this data are structured like this:
[tag:user:xxx]
In this token, xxx is the configured parameter name that stores the tag’s value.
Data from gather nodes appears under the Gather reporting menu name. When you open the Tags tab on the Call Details report, you see this data under the Gather subsection.
For that reason, the tokens for this data are structured like this:
[tag:gather:xxx]
Where xxx is the configured parameter name that stores the tag's value.
What options do I have for collecting ZIP Codes?
For more methods to collect the ZIP Code data, see our article Different Ways to Collect ZIP Codes.
What should I do if I need help with tokens?
If you have any questions or need additional help, please reach out to our support team via chat or email at support@ringba.com.