Ale Cabrera
SHIPPED · ZAPIER
Revenue Partner Share Attribution
Built partner revenue attribution from scratch, becoming the base model for a later multi-touch attribution system.
- ↑ability to identify high-performing partners
- →became the base model for a later multi-touch attribution system
- POCshipped and validated against expectations, with edge cases confirmed through audit
Timeline
- Phase 0Kickoff: partner contributions unrecognized, no attribution path
- Phase 1Discovery: interviewed business owners, translated rules into specs
- Phase 2Ship v1: POC shipped, validated against expectations
- Phase 2Feedback: audit surfaced edge cases and exceptions
- NextBecame the base model for multi-touch attribution
From invisible to attributed
- Partner contributions invisible
- Interviews + spec
- POC + audit
- Base model
for multi-touch
The risk, and what happened
| Risk | How it was handled | Result |
|---|---|---|
| Business viability. Partners driving signups and upgrades had no way to be recognized or incentivized, risking lower partner engagement over time. | Started from interviews with business owners, PMs, and POs rather than assuming which rules mattered. Shipped a POC and tested use cases through audit. | Marketing improved its ability to identify high-performing partners, focusing effort where it mattered. |
My role. Owned the business rule translation into specs, the technical spec definition, and the ETL modeling and audit.
The tradeoff. Traded a broader attribution model upfront for a single-touch model that could be validated and extended later.
Product leader with a data scientist past · Zapier, Clearbit, HubSpot
Product doc: ale-cabrera.com/portfolio/revenue-partner-share-attribution