Phonexa Updates: Sharper Bidding, Tag-Based Routing, Logic Links & Address Verification

A batch of updates landed across Phonexa this last month, touching LMS Sync, Call Logic, iClear, Form Builder, and Lynx. Here’s what changed.

Publisher Distribution by Tags (LMS & Call Logic)

Tag-Based Control Over Who Sees What Traffic

What’s New: You can now control publisher distribution by matching Allowed or Blocked Campaign Tags against the tags assigned to your campaigns.

Allowed tags limit a publisher’s leads to campaigns with a matching tag. Blocked tags do the opposite, keeping matching campaigns off-limits. Tag a publisher once, and it applies everywhere it matches, no need to open each campaign and add or remove that publisher one by one. If a tag shows up in both fields, Allowed takes priority.

Purpose: Allow/Deny Lists already control access at the campaign level, but that means touching every campaign a publisher should or shouldn’t reach. This flips it around: set the rule once on the publisher, and it applies wherever the tags line up.

How You Can Use It:

1. Turn the feature on in Project Settings, under Additional Components.
2. Once it’s enabled, a new Distribution by Tags section appears under Publisher, in the Advanced tab.
3. That’s where you set your Allowed or Blocked tags.

Traffic sorts itself from there, no manual campaign eligibility list required.

Learn More: Publisher Configuration: Advanced

Next Highest Bidder for Ping Post Calls

Turning Dead Calls Into Revenue

What’s New: When the highest bidder on a Ping Post Call doesn’t answer, the number is unavailable, or the call fails, Call Logic now redirects automatically to the next eligible bidder instead of dropping the sale.

For example, a winning bid at $100 goes unanswered, and the system instantly reroutes to the next bid that still covers the publisher’s $70 payout within the configured margin, turning what would’ve been a dead call into revenue.

In every scenario, the Publisher payout promise is honored; only the admin margin is adjusted.

Purpose: Calls get missed for ordinary reasons, a busy line, a slow pickup, a failed connection. Without a fallback bid, that’s a call written off completely. This gives it a next-best option instead.

How You Can Use It:

1. Enable Parallel Pings in the LMS Ping Tree, so the system can hold onto multiple bids per campaign instead of just one.
2. Go to the Publisher’s Rev-Share settings and set Enable Next Highest Bidder to Yes.
3. Fine-tune which fallback bids qualify using Loss Margin, Max Pub Payout %, and adjustable duration requirements per bidder.

If the highest bidder doesn’t answer, the call reroutes automatically to the next eligible bid.

Learn More: Publisher Configuration: Rev-Share

Expired Redirects Report (LMS Sync)

Catching Leads That Click In Too Late

What’s New: A new Expired Redirects report shows when someone tries to access a buyer redirect link after it has expired. By default, redirect links stay active for 15 minutes after a lead sells. If someone clicks that link after it expires (say, an hour later), that used to go unnoticed. Now there’s a report showing exactly when and where that’s happening.

Purpose: Reviewing expired redirect attempts can help you see what happens to leads after they’re submitted and spot issues that may be getting in the way of the user journey.

How You Can Use It: You can find the report under Analytics and Optimization > Deep Analytics > Traffic Flow. Just select the Expired Redirects tab to see attempts to access expired links and spot any unusual delays or patterns.

Learn More: Traffic Flow

Expanded Warning Log Coverage (LMS Sync & Call Logic)

One Place to See Both Ends of a Broken Lead Flow

What’s New: The Warning Log now captures two new types of errors:

• Lead Stash processing errors, including Rate Limit and Authentication errors, grouped by User IP
• Failed buyer integration responses, including 4xx and 500 errors, with details on which integration failed

Purpose: Give operations and technical teams a clear view of lead delivery from submission to buyer, so they can spot and fix issues before they impact lead flow or revenue.

How You Can Use It: To access the report, go to System Management > Logs > Warning Log.

Learn More: Warning Log

Lead Export Enhancements & New Buyer Lead Post Export (LMS Sync & Call Logic)

More Control Over What’s in Your Export

What’s New: You can now customize exactly which fields show up when you export lead data, choosing default or custom fields grouped by category, with your selections visible right in the export details. Lead Exports can also be filtered by Publisher. Besides that, there’s a new export type built specifically for buyer-side data, Buyer Lead Post Export, useful for resolving billing disputes with buyers.

Purpose: When a buyer questions an invoice, someone has to track down which leads were posted and how the buyer responded to each. That used to mean checking more than one place. Now it’s one export.

How You Can Use It:

1. Go to System Management > Export.
2. Click the Buyer Lead Post Export tab next to Lead Export.
3. Filter by Created date, ID, Product, Buyer, or Status to narrow down what you need.
4. Hit Export, or Add New Export to generate a new one.

Learn More: Lead Export

Multi-Level Bot Protection Redirect Settings (LMS Sync)

Deciding How Bots Show Up in Your Reporting

What’s New: The new Bot Protection On Redirects feature gives you control over how the system handles redirect link visits from non-human or high-risk traffic, including search engine crawlers, good bots, data center IPs, and devices with a high fraud score. You can choose to count these redirects, exclude them from reporting, or treat them as expired.

Purpose: Bot-clicks can mess with your numbers if you can’t separate them from the rest. This gives you a way to isolate them and decide exactly how they show up in your reporting.

How You Can Use It:

1. Go to System Management > General > Project Settings.
2. Open the LMS & Call Logic tab.
3. Click into the Redirects Bot Protection subtab.

That’s where the Bot Protection On Redirects block lives, with everything you need to view and adjust the settings.

Learn More: Bot Protection on Redirects

AddressVerify.io Integration in iClear (LMS Sync & Call Logic)

Rejecting Bad Addresses Before They Reach a Buyer

What’s New: iClear now integrates with AddressVerify.io to check addresses in real time during lead processing. Turn it on in Lead Processing Rules and it confirms each address is valid, residential, and serviceable, rejecting leads automatically based on invalid addresses, home type, or minimum home value. It can run synchronously, asynchronously, or on-demand, with sampling and caching to keep lookup costs in check.

Purpose: A bad address that slips through doesn’t just cost you the lead, it often turns into a return and a dispute with the buyer later. Catching it upfront avoids both.

How You Can Use It:

1. Go to Fraud and Anomaly > iClear > Lead Processing Rules, pick a Product, and click Select.
2. You’ll land on the Lead Processing Rules (iClear) subtab, also reachable via System Management > Products > Settings for that product.
3. In the Global Rules block, click Add Service.
4. Choose Address Verify under Select Third Party Service.

Learn More: iClear: Address Verify

Geo By Postal Code/Zip in iClear (LMS Sync & Call Logic)

Validating Leads by ZIP Before They Move Foward

What’s New: If a lead only has a ZIP code and no state or city, this new iClear feature can validate or reject leads in real time. It works for the US, UK, Canada, and Spain. It runs as a Global Rule in Lead Processing Rules, with synchronous, asynchronous, and on-demand execution options. Right now, it’s available by request.

Purpose: Ensure buyers receive only geographically valid leads by filtering out mismatched or invalid postal codes before distribution.

For example, if a lead includes a ZIP code but no state, iClear checks the ZIP against a valid location and accepts or rejects the lead accordingly. With the service set to Synchronous and “Reject the lead if the location was not found” enabled, any lead whose ZIP can’t be matched gets rejected.

How You Can Use It:

1. Go to Fraud and Anomaly > iClear > Lead Processing Rules, select a Product, and click Select.
2. You’ll land automatically on the Lead Processing Rules (iClear) subtab. You can also get there via System Management > Products, clicking Settings on the product you want.
3. Click Add Service in the Global Rules block.
4. Find the Geo By Postal Code/Zip block and click Add to iClear.

Learn More: iClear: Geo By Postal Code/Zip

HTML Editor for Form Builder (LMS Sync & Call Logic)

Full Code-Level Control Without a Developer Ticket

What’s New: Form Builder now has a new HTML-based builder type. It lets teams build fully custom forms (and the pages around them, like the waiting page or thank-you page) using actual HTML/CSS, without needing a developer for every small change.

Purpose: Every small design tweak shouldn’t need to wait in a developer’s queue. This puts that control directly in your hands, so you can go from custom markup to a live form the same day.

How You Can Use It:

1. Go to Publisher Management > Promo Materials > Form Builder.
2. Click Add New Record and select HTML under Builder Type.
3. Fill in the rest of the fields in the Add New pop-up and click Add.
4. Click Builder in the confirmation pop-up, or find your new form in the list and click Builder under Actions.

Learn More: Form Builder: HTML Editor

Logic Links in Lynx

One Link, Multiple Offers, Real-Time Selection

What’s New: Lynx now supports Logic Links. Instead of managing a separate tracking link for every single offer, you get one “smart” link that automatically routes clicks to the best available offer based on rules you set (geography, device, priority). If one offer caps out, traffic shifts to the next best one on its own.

Purpose: Managing a separate link per offer and manually shifting traffic between them is exactly the kind of busywork automation should absorb.

How You Can Use It:

• Go to Offers > Logic Links.
• Click Add Logic Link.
• Fill in the Name, Advertiser, Status, Publicity, and Order Strategy (Priority or Weight), then select a Tracking Domain.
• Click Add to confirm.

Learn More: Logic Links

Final Thoughts

Most of this batch comes down to giving teams more control with less manual upkeep. Whether that’s routing traffic by tag, recovering calls that would’ve gone dead, or catching lead delivery issues before they cut into revenue.

If you’re a Phonexa client, it’s worth a quick chat with your Customer Lifecycle Manager to see which of these fit into what you’re already running.