Attribution

Iron’s attribution app (apps/attribution) is a lean in-house attribution engine: it ties an ad click to a lead, the lead to a booking, and the booking to revenue — then sends conversions back to the ad platform (CAPI). It lives in its own hyros schema and is served at your-domain.example.

The attribution chain

Ad click  →  Lead (funnel)  →  Booked (appointment)  →  Revenue (Stripe / connector)

Each hop is matched via an identity-match waterfall (click id, email, phone). The result credits the originating ad, and a server-side conversion event is sent back to the ad platform so the platform can optimize.

Where attribution touches the CRM

• Lead capture — funnel leads land via POST /webhooks/funnel-lead, carrying UTM / click identifiers that seed the attribution join.
• Ads launcher — the CRM’s ads launcher stamps UTM parameters on launched campaigns so the attribution join can later credit the ad. The launcher does not do reporting itself.
• Identity lookup — GET /integrations/contacts/by-identity resolves a contact by an external identity for bridging.
• Revenue — connector revenue (Jobber, QuickBooks) and the Stripe mirror feed the revenue end of the chain.

Channel attribution and unit economics

Per-channel unit economics roll up in the analytics app. The first-touch acquisition channel of a customer feeds the cost-per-acquisition and ROAS math used by the operator reporting and the ROI calculator.

Draft

This guide summarizes how attribution connects to the CRM. The attribution app’s internal data model (identity waterfall, CAPI payloads, per-tenant config) is documented in the attribution app’s own context.