Table of Contents
Tower Coverage Integration: Overview
Updated
by Mitchell Ivany
Read Time: 8 mins
TowerCoverage is a third party RF propagation and coverage mapping service for wireless, fiber, and cable providers. You supply your tower and antenna data, TowerCoverage builds a coverage map, and you embed their End User Submission (EUS) form on your website. When a prospect submits that form, TowerCoverage checks their location against your coverage map and pushes the submission to Sonar as a lead, along with the network sites that give that address the best signal.
This article covers the Sonar side of that integration: configuring it, and working the leads once they arrive. Building your sites, coverages, and maps happens inside TowerCoverage, and their own documentation is the source of truth for that work.
Prerequisites
- A TowerCoverage account on a paid tier. The Basic (free) tier includes zero API calls, and the integration depends on the EUS API, so it cannot function on a free account. See Account Tiers & Upgrades.
- Sites, Coverages, and at least one Multi Map built in TowerCoverage, with the EUS data collection form enabled on that map.
- Network Sites built in your Sonar instance. See Network Sites: Management View Overview.
- A user role with the permissions below.
Permissions
Before getting started with the feature, your user roles will need to be adjusted to account for the permissions required to use the Tower Coverage integration feature.
Feature Details
Configuring the integration in Sonar
Use this step once your TowerCoverage account is active and your coverage maps are built.
- Click Settings.
- Expand the Integrations section.
- Click Tower Coverage.
Complete the fields on the page:
- Enabled turns the integration on. Enabling it adds a Tower Coverage Submissions tab to the Accounts page, alongside Accounts and Archived Accounts.
- API Key acts as a shared password between TowerCoverage and your instance. Click Generate API Key to create one, then copy it somewhere safe.
- Type sets the default account type applied when a submission is converted. It can be changed per lead. See Account Types: Overview & Example Use Cases.
- Status sets the default account status applied on conversion. A status such as Lead suits most workflows, and it typically advances as the prospect moves through onboarding. See Account Statuses: Overview & Example Use Cases.
- Phone Number Type controls how the prospect’s contact number is stored. See Phone Number Types: Overview and Use Cases.
- Note the push URL displayed at the bottom of the page. It is unique to your instance and follows the format
https://your-instance.sonar.software/api/towercoverage. - Click Save.
Providing your credentials to TowerCoverage
The API key and push URL from the previous step both need to be entered in your TowerCoverage account, under the account’s API settings, where Sonar is selected as the receiving billing system.
Because TowerCoverage controls that interface and updates it independently, follow their documentation for the current steps: EUS API & Integrations.
How Tower Coverage works in Sonar
Once both sides are configured, each submission follows the same path:
- A prospect completes the EUS form embedded on your website.
- TowerCoverage captures the submission and identifies the network sites that provide the best coverage at that address. These are not always the closest sites, which is expected. TowerCoverage weighs signal quality rather than distance.
- TowerCoverage pushes the prospect’s name, address, contact details, and coverage results to your instance through the API.
The results appear under Accounts → Tower Coverage Submissions.
Working the submissions list
- The filter icon opens the filter panel, where you can apply the Valid and Visibility Status filters, use a saved filter, or browse the full filter list. See Filtering: Overview.
- Date Received is the date and time the submission reached your instance.
- Full Name, Email Address, and Phone Number are the details the prospect entered on the form.
- Valid indicates whether the submission contained everything required. Invalid submissions can still be converted, but expect to fill in the gaps manually.
- Address is the serviceable address the prospect submitted.
- Assignee populates with the account name once the submission has been linked and converted.
- The action column is where you link a serviceable address, convert the lead to an account, and hide or show the submission.
Linking the serviceable address
Do this first on any new submission. Until an address is linked, you cannot convert the lead or view the coverage data attached to it.
Click Link Serviceable Address in the action column. The modal that opens lets you enter the address and geocoding details, and correct anything the prospect entered incorrectly. See Serviceable Addresses: Overview and Usage.
Reviewing the coverage information
Click the linked serviceable address to open its management page. From there you can view each coverage image at full size and open the detailed site report Tower Coverage generated for that location.
This data stays attached to the serviceable address permanently, including after the lead is converted, so you can revisit it from the account later.
Converting a submission to an account
Once you have confirmed the address is serviceable, the action button changes to Convert to Account. Clicking it opens the account creation modal, pre-filled with the submission’s details and the defaults you set during configuration.
The rest of the flow matches standard account creation. See Creating a New Account.
Hiding and showing submissions
Tower Coverage submissions cannot be deleted from Sonar. Hiding is how you clear completed or junk leads out of your working view without losing the record.
Any submission can be hidden, whether it has been linked, converted, or left untouched. Click Hide in the action column, and the button changes to Show.
To filter by state, apply the Visibility Status filter and select Hidden or Visible. Leaving the filter off displays all submissions.
Troubleshooting
Submissions are not arriving in Sonar. Confirm the Enabled checkbox is ticked, then compare the API key in TowerCoverage against the one in your instance character for character. Confirm the push URL in TowerCoverage matches your instance exactly.
Submissions are not arriving and your network restricts inbound traffic. TowerCoverage pushes from a fixed set of addresses. Allow 162.60.210.0/25 (IPv4) and 2602:fea0::/64 (IPv6). See TowerCoverage’s Billing System not receiving EUS API Push page.
Submissions stopped arriving after working previously. Check whether the API key was regenerated on either side without being updated on the other, and confirm the TowerCoverage subscription is still active and has API calls remaining on its tier.
Submissions arrive but Valid shows No. The prospect left a required field blank, or the address could not be resolved. Convert the lead manually and fill in the missing details.
No coverage images appear on the serviceable address. Coverage data only attaches once the serviceable address is linked. If the address is linked and images are still missing, the submitted address likely falls outside your coverage maps.
A user cannot see the Tower Coverage Submissions tab. The tab only renders when the integration is enabled and the user’s role has the “View all TowerCoverage submissions” permission.
Related Articles
- Network Sites: Management View Overview
- Serviceable Addresses: Overview and Usage
- Creating a New Account
- Lead Intake Form Processing
- User Role Creation & Best Practices
Need a hand?
Our Support Team is here to help
