Turn the Segment events you already send into revenue attribution.

Spectacle connects to Segment in about 10 minutes as a destination function, and every track, identify, page, and group call you already send becomes a touchpoint, an identity, or a milestone on a Spectacle customer journey. No new snippet on the site, no second tracking plan. Segment routes the events. Spectacle joins them to ad spend and revenue, and attributes the outcome to the campaigns that caused it.

At a glance

• Category: CDP
• Setup time: About 10 minutes
• Authentication: Spectacle workspace id, pasted into the destination function
• Segment plan: Any plan with Functions enabled
• Spectacle plan: All Spectacle plans (Essential, Scale, Enterprise); company-level attribution on Scale and Enterprise
• Direction: Segment → Spectacle. Nothing is written back to Segment
• Objects: track, identify, page, group (screen, alias, and delete are not supported)
• Sync: Near real time, per event, with retries on 5xx and 429
• Docs: /docs/segment
• Marketplace: Segment catalog

The gap in Segment's own reporting

Segment is a router. It collects every event from web, backend, and mobile, cleans it, and delivers it to 300+ destinations. What it does not do is attribute. Segment has 0 attribution models, no ad spend import, and no revenue join: it can tell you that user 4821 fired Plan Upgraded, and it cannot tell you that user 4821 first arrived from a LinkedIn campaign in March, came back through a branded search, and is now worth $4,800 a year against $212 of ad spend.

The usual fix is to send Segment events to a warehouse and build attribution in SQL, or to install a second tracking tool next to Segment and maintain 2 tracking plans. Both take months and both drift.

Spectacle takes the third route: it receives the events Segment already has, adds the first-party visit history, the click ids, the ad cost, and the revenue, and runs first-touch, last-touch, linear, and U-shaped models on top.

What syncs

• Segment call: What Spectacle does with it
• page: A touchpoint on the visitor's journey, with UTM, referrer, and click ids resolved to a channel and campaign
• track: A journey event; revenue, transactionId, currency, mrr, arr, and plan properties are read as revenue
• identify: Stitches the anonymous visits to a known person; email is the trait that makes Stripe and CRM matching work
• group: Associates the person with a company, so B2B journeys roll up to the account (Scale and Enterprise plans)
• Retries: 5xx and 429 responses are retried by the function, so a Spectacle-side blip does not drop events

screen, alias, and delete are not forwarded. The function code and the field mapping live in the Segment docs. This page summarizes; Docs is the source of truth.

What you get

• Attribution without a second tracking plan. The Signup Completed and Plan Upgraded events your product already sends are the milestones Spectacle attributes. Nothing to re-instrument.
• A cut-off event you already have. Pick any track event as the end of the journey (trial started, demo booked, deal created) and revenue after it is credited to the touchpoints before it.
• Ad spend joined to product events. Google, Meta, LinkedIn, and Microsoft Advertising cost next to the Segment events they produced, so cost per activated account by channel is 1 report.
• Company-level journeys from group. Every user at the same account on 1 timeline, so the campaign that reached the first stakeholder gets credit for the deal the fourth one signed.
• Server-side events on the journey. Backend track calls routed through Segment land on the same journey as the browser visits, which a pixel-only setup never sees.

Pairs with

Segment + Stripe (revenue on the same journey) · Segment + HubSpot or Salesforce · Segment + Google Ads and LinkedIn Ads for cost · Alternative installation: TAGGRS server-side GTM

An agency running attribution for a client with a busy event stream had been quoted months for a Tealium-based build. With Segment already in place, Spectacle went live as a destination in about 25 minutes, and the client's 498 leads that quarter carried a 99% tracking score across every channel: each lead matched to a journey with a known source, using the events the product team had already written. (Anonymized.)