SearchLight vs PipelineOn for Home Service Attribution

SearchLight and PipelineOn open source offer different ways to connect marketing evidence with home-service outcomes. SearchLight documents a packaged reporting layer with native lead, field-service and ad connections. PipelineOn’s open-source software is a self-hosted foundation for source capture, normalized outcomes, linked touch reports and optional Meta delivery.

Choose based on the work your team can own. A supported packaged integration can reduce custom implementation. Free source code gives a technical owner control, while leaving infrastructure and the source bridge with that owner.

Disclosure and method: PipelineOn publishes this comparison. We reviewed the linked public documentation on October 14, 2026; this is not a hands-on parity test. PipelineOn’s paid homeowner identification is separate from the open-source software. Confirm commercial scope directly with each provider.

On this page

• Compare the attribution responsibilities
• Where SearchLight fits
• Where the free PipelineOn software fits
• Why different reports can credit different channels
• Verify Meta delivery as a separate requirement
• Choose with the same inquiry-to-payment test

Compare the attribution responsibilities

Neither a website tag nor an attractive report proves the entire inquiry-to-payment path. The meaningful comparison is whether your actual records survive the connections and use the definitions the business expects.

Where SearchLight fits

SearchLight’s integration guide lists ServiceTitan, Housecall Pro, FieldEdge and other business systems, alongside call and lead sources. It describes Facebook campaign data and lead campaigns as part of the ad connection. Verify the required account permissions, data history and supported record types for your configuration.

Its attribution documentation describes a hierarchy of evidence for lead classification. It also documents a 90-day first-touch basis for standard dashboards. That is useful context when another report uses a different window or touch rule.

Ask the demonstration owner to explain an unmatched lead and a payment whose reporting date differs from its originating inquiry. A supported integration should be evaluated with those awkward records as well as the clean example.

Where the free PipelineOn software fits

The public open-source software gives a developer an inspectable source and outcome path. The versioned release includes the runtime, documentation, examples and tests. It runs without a PipelineOn account or paid identity provider.

Your website obtains an accepted visitorSessionId; your backend or mapped CRM workflow preserves it and imports the later outcome. That reference links the record to observed visits. A contact ID, phone number or similar timestamp alone does not establish that browser link in the software.

The first release supports one site, one process and persistent SQLite storage. It supplies read-only reports and a tracking doctor, but not native CRM logins, call-number rental or cross-device identity resolution. See the open-source overview and installation walkthrough for the operating responsibilities.

Why different reports can credit different channels

Consider an illustrative homeowner who first visits from Google, later returns through Facebook and then submits a form. The business subsequently records a booking and completed payment. A report based on the first observed visit and one based on the last eligible visit can assign different credit without either representing a second payment.

Do not try to reconcile them by silently changing campaign fields until the totals match. Record the reporting range, window, touch rule and revenue definition first. Then inspect the linked source records and any missing history.

The software’s first-touch report should not be assumed identical to SearchLight’s first lead within its documented window. Similar model names do not establish identical evidence or implementation. Our first-party data guide explains why original source and later interactions should remain available.

Verify Meta delivery as a separate requirement

An integration that imports ad spend is not, by itself, proof of outbound CAPI delivery. SearchLight’s integration listing does not settle every possible outbound configuration. Ask for the exact supported conversion, event identity, source record and destination evidence rather than interpreting an omission as proof of no capability.

The software’s optional Meta sender supports explicitly mapped eligible outcomes. It retains a delivery receipt after provider acceptance. Your bridge supplies permissioned matching data, actual time and source context. One server sender should own each logical conversion; browser/server copies need coordinated event names and IDs.

Use the CAPI guide and offline-events workflow for the checks. A provider receipt is separate from matching, attribution and campaign improvement.

Choose with the same inquiry-to-payment test

Bring a serviceable inquiry, a later booking, a completed payment, a duplicate source notification and a corrected record. Ask both implementations to show source evidence, linkage, reporting and any destination delivery. Identify what the team must handle when a record cannot be linked.

For a packaged home-service reporting need, evaluate SearchLight’s supported connections and proposal. For technical teams wanting an open-source foundation they can operate, evaluate the software’s contracts and limits. PipelineOn-hosted is planned at around $20/month, with final price, usage and availability to be confirmed; the paid visitor identification product remains a separate purchase.

Use SearchLight, MNTN and Scorpion when the broader choice is reporting versus advertising or agency execution. Compare the attribution software shortlist and Facebook Ads tools before adding overlapping systems.