These updates span several modules within the Phonexa platform, including LMS Sync, Call Logic, iClear, and Lynx. This time around, our focus has been to improve product management, reporting visibility, and traffic quality controls across everyday workflows.
Here’s what’s new and how teams can use these updates in practice.
Product Builder (LMS Sync & Call Logic)
A Redesigned Product Builder Experience
What’s New: With the redesigned Product Builder, creating and managing product fields is now more streamlined. Key changes include:
- Product Configurationand Extra Fields tabs are now combined into a single tab
- Product field creation is more structured and easier to navigate
- Additional visual and usability improvements across the interface
Purpose: The redesign consolidates product setup into a clearer structure, reducing navigation between sections and improving how fields are configured and managed.
How Teams Use It: When configuring a product, teams now manage all product fields from the Product Configuration tab.
Learn More:
Referral Report (LMS Sync & Call Logic)
Improved Visibility & Filtering for Referral Data
What’s New: The Referral Report has been updated with clearer filtering and role-based views to make referral activity easier to analyse. Key improvements include:
- Clearer filters for referral data analysis
- Different report views for Admins and Publishers
- Improved visibility into referral relationships and commissions
Purpose: The update improves how referral activity is reviewed, helping teams analyse referral data faster while ensuring each user role sees the information most relevant to them.
How Teams Use It: The Referral Report helps teams review detailed statistics and understand the performance of their Publisher Referral Program. Role-based views ensure admins and publishers see the information most relevant to them, including referral relationships, registration dates, and commission data.
Learn More:
Publisher Report → Referral Report
Custom Report Columns (LMS Sync & Call Logic)
Role-Based Visibility for Custom Report Columns
What’s New: Custom columns in report templates can now be configured with role-based visibility, allowing admins to control which users can see specific data fields. The column creation workflow was also improved:
- Placeholders and available fields now load automatically when opening the column editor
- Available fields are filtered based on the selected user roles
- Validation prevents templates from including fields that are not available to those roles
- Columns automatically hide if a field is not accessible to the viewer
Purpose: This update improves control over report configuration while ensuring users only see the data fields relevant to their permissions.
How Teams Use It: When creating or editing a custom column in a report template, admins can select which user roles should have access to the column. Within the Add New Column editor, roles such as Global Admin, LMS Admin, Support, Accounting, or Publisher roles can be selected. The system then filters available placeholders accordingly and ensures the column only appears for users with the appropriate permissions.
Learn More:
Rule Conditions (iClear)
New Date-Based Conditions for Lead Processing
What’s New: New date-based conditions are now available within Product → Lead Processing Rules → Advanced Rules → Conditions.
Users can now apply a Date/Time Difference condition to evaluate the time gap between two dates using days, hours, or minutes. When configuring this rule, users can define:
- A date parameter from the lead data
- A reference date (input value, placeholder, or lead body field)
- A comparison operator
- A numeric threshold value
The system calculates the time difference between the selected dates and evaluates it against the defined condition.
Purpose: This update allows lead processing rules to incorporate time-based logic, helping teams filter or route leads based on date-sensitive criteria.
How Teams Use It: When creating Advanced Rules in iClear, users can select Date/Time Difference as a condition type. For example, a company handling moving service leads may use a moveDate field to filter leads where the requested move date is too close to the current date. A rule can automatically reject or reroute leads where the move date is less than four days away.
Learn More:
iClear → Advanced Rules → Conditions
Rule Caps (iClear)
New Action-Trigger Caps
What’s New: A new cap type has been added to iClear rules, allowing teams to limit how many times rule actions are actually triggered. Previously, rule caps counted how many times a rule was evaluated. The new action-trigger caps track how many times a rule’s actions are executed. Both cap types operate independently, meaning the existing global caps track rule evaluations while the new action-trigger caps track only when rule actions are executed.
Purpose: This update gives teams more precise control over rule limits by separating rule evaluation from rule execution.
How Teams Use It: When configuring an iClear rule, teams can now set Action Daily Caps and Action Monthly Caps within the Rule Caps section. These caps count only when the rule’s conditions are successfully met and the configured action is triggered. Leads that fail the rule conditions do not affect the action-trigger caps.
Learn More:
iClear → Advanced Rules Configuration
Offer Targeting (Lynx)
iClear IP Scoring for Fraudulent Click Detection
What’s New: iClear IP Scoring is now available for Lynx offers, allowing teams to evaluate click traffic quality using IP-based signals.
The system can check several indicators, including:
- Cloud and data centre IPs
- Proxy or VPN usage
- TOR traffic
- Fraud score
- Country of origin
Purpose: This update helps teams to use iClear’s IP Scoring integration within Lynx offers to identify and filter fraudulent or botted clicks.
How Teams Use It: When configuring a Lynx offer, teams can enable iClear IP scoring within Offer Targeting or Affiliate Rules. Traffic is evaluated using IP-based signals such as proxy or VPN detection, data centre indicators, fraud score, and country. The system stores IP score data alongside click records, allowing teams to analyse traffic quality and incorporate these signals into targeting rules, payout and revenue group logic, and other offer-level configurations.
Learn More:
Final Thoughts
From redesigning Product Builder and improving referral reporting to adding more control over lead processing rules and traffic quality, each change is designed to make workflows clearer and easier to manage.
If you’re a Phonexa client and haven’t explored these features yet, reach out to your Account Manager to start your setup and see how they can fit into your current workflows.
Get in touch! We are available 24/7.
