Field management
Control and customize incoming field structures and validations for all traffic sources globally.
Overview
Pingtree (PT) allows users to generate individual API posting specifications for any and all traffic sources.
To ensure the correct fields are presented—based on what a campaign requires from the source—we have introduced the Field Management tab.
Field Management Features
The Field Management tab provides a user-friendly interface to control which fields are included in the API specs. Through this section, users can:
-
Enable/Disable Fields
Control which fields are displayed or hidden in the posting specs for sources. -
Set Required or Optional Fields
Mark fields as either required (mandatory for submission) or optional, depending on campaign needs. -
Apply Data Type Validations
Define validations on fields to ensure the correct data types (e.g., string, integer, date format) are submitted. -
Values Rejection can be enabled per field.
- By default, all values for a field are accepted.
- If this feature is enabled, you can define a list of acceptable values — similar to an ENUM constraint.
- Example: For a field like
consent
, you may allow onlyyes
orno
. - Any incoming lead with a field value outside the defined list will be rejected.
-
Edit Field Descriptions
Add or update field descriptions to guide sources on the expected data format and purpose. -
Apply Changes to All Sources
After making edits in the Field Management tab, users have the option to apply those changes globally across all sources for consistency and ease of management.
Key Benefits
- Customize posting specifications per campaign needs
- Maintain data quality and integrity by enforcing validations
- Simplify onboarding for new affiliates and partners
- Ensure consistency across multiple sources effortlessly
Note: Users can access the Field Management tab from the top navigation bar and manage system fields like
Transaction Id
,Lead Id
,First Name
,Phone
, and many more critical data points.