ServiceTitan Marketing Pro vs PipelineOn: Tracking

ServiceTitan Marketing Pro and PipelineOn open source are different layers of a contractor’s system. Marketing Pro provides marketing capabilities within the ServiceTitan ecosystem. The open-source software provides an independent source/outcome tracking foundation with optional Meta delivery. Check what the existing ServiceTitan configuration already does before adding a second sender.

The software does not replace dispatch, job management, invoicing, customer communications or the broader Marketing Pro suite. The useful comparison is which system supplies the authoritative business fact, which report applies the attribution rule and which sender owns the destination event.

Disclosure and method: PipelineOn publishes this guide. We reviewed ServiceTitan’s public documentation and the versioned open-source software on October 14, 2026. This is a documented-scope comparison, not a tested native ServiceTitan connector or a performance comparison.

On this page

• Compare scope before monthly prices
• What ServiceTitan documents for the Meta connection
• Verify the reporting features available to your account
• What the open-source software adds and what you must supply
• Give each conversion one server sender
• Test a complete HVAC or plumbing journey
• Choose the smallest useful addition

Compare scope before monthly prices

A free software licence and a field-service marketing package do not include the same work. Compare total setup and operating responsibilities as well as recurring charges. PipelineOn-hosted is planned at around $20/month; final pricing, included usage and availability are still being finalized.

What ServiceTitan documents for the Meta connection

ServiceTitan’s Meta Ads integration guide describes importing campaign costs, mapping campaigns, posting job events as conversions and updating a customer audience. It requires account configuration and DNI for attribution and conversion posting. The guide currently states that Facebook Lead Forms and Meta Instant Forms are not tracked by this integration.

The guide points to the Google integration’s event list for conversion scope. Confirm the exact events, naming, eligibility and destination diagnostics in your account rather than assuming every job or payment stage uses the same mapping.

This documented outbound flow matters: it would be misleading to describe the integration as campaign-cost reporting only. It also means a second CAPI sender can overlap with an existing workflow.

Verify the reporting features available to your account

ServiceTitan’s multi-touch documentation describes first-touch, last-touch and assigned-campaign views, plus assisted metrics. It currently labels the feature Early Access for specific accounts and requires ServiceTitan DNI.

Ask which features your account actually has and how manual campaign overrides affect the report. Availability in documentation is different from activation for your tenant. Do not buy another attribution tool solely because a view is hidden before checking configuration and access.

Use the home-service attribution scorecard when you need an independent report or a different source architecture. Compare definitions before comparing totals.

What the open-source software adds and what you must supply

The free software captures permitted website sources and accepts normalized forms, calls, bookings and payments through authenticated HTTP endpoints. Linked outcomes can appear in supported touch reports; optional Meta delivery has stable IDs, retries and receipts.

It is not a native ServiceTitan marketplace login. A trusted backend, workflow or adapter must obtain the permitted source records, validate their meaning and map them into the software’s contract. API access and source-plan requirements remain separate from the MIT licence.

For a website-linked record, preserve the accepted visitorSessionId. For source identity, preserve a stable source and externalId, the real occurredAt and a trustworthy sourceUpdatedAt. Include explicit status and amount/currency for a completed payment. Do not label a won estimate as collected revenue.

The server-side installation guide shows the generic route. The public release provides inspectable examples and limits.

Give each conversion one server sender

Before enabling software delivery, list the actions the native connector already sends. Name the owner for each action and destination. If ServiceTitan owns a logical conversion, do not send another copy from the software just because a second report needs the same source fact.

The software supports deliveryOwner: "external" to skip its own Meta delivery for an outcome owned elsewhere. It cannot universally discover whether an unrelated sender already submitted an event. For a browser/server pair, coordinate the same event name and stable action ID; retries must keep that identity.

Use the CAPI setup guide to test the event and the Pixel comparison for the browser side. Consent, permitted matching data and accurate action source still apply to either architecture.

Test a complete HVAC or plumbing journey

Use a synthetic inquiry with an approved test destination. Confirm the source campaign, accepted form or tracked call, booking and completed payment. Inspect each system’s record and the configured destination receipt separately.

Then replay the source record, test an unavailable session reference and change a record using a newer source revision. The expected result should be explicit: duplicates do not become new facts, missing linkage stays visible and corrections do not silently manufacture a new conversion.

If Meta already accepted an event, changing the local source record does not revoke that receipt. Handle downstream corrections separately. An accepted event proves provider receipt, not person matching, attribution to an ad or improved campaign performance.

Choose the smallest useful addition

If Marketing Pro already covers the source, report and Meta event you need, configure and verify that route first. If you need an independent open-source foundation and can own the bridge, evaluate the software with the same sample records. Keep the existing field-service system authoritative for its business operations.

For a broader reporting decision, read SearchLight versus PipelineOn. For campaign improvements, follow the Facebook Ads guide and nine-tool shortlist. A new tracking layer should solve a named gap rather than create duplicate conversions.