People looking up Amplitude attribution usually run a software product or client portal alongside a sales team, and want to know which marketing channels bring users who go on to use the product properly. A product analytics tool sees behaviour inside the product. Your CRM sees the commercial outcome: the meeting, the proposal, the contract. This article answers a specific question. Which system should own attribution, and how do you connect product signals to the levelpartner.ai platform so sales and marketing act on them?
Two systems, two different jobs
Product analytics answers questions such as which onboarding step users abandon and which feature predicts retention. Its attribution view is built around sessions and events. That is valuable for product decisions.
Revenue attribution in a company that sells through people is a different question: which channel produced the contract, and what did that contract cost to win? That answer belongs in the CRM, because the CRM holds the opportunity, its value and its outcome. The mistake is trying to make one system answer both. Keep product attribution in the product tool, keep revenue attribution in the CRM, and pass a small number of signals between them.
What to check in a product analytics tool
We do not describe other vendors' products, so assess yours against these questions:
- Can it send a defined event, such as a user reaching activation, to an external webhook or through an integration?
- Does it identify users by email or an account ID that you also hold on the CRM contact?
- Can it pass the campaign data it captured at sign-up along with that event?
- Does your product's privacy notice cover sharing usage signals with your sales system?
Before you start
- A clear definition of an activated user, agreed by product and sales.
- Custom contact fields on the platform for activation date, plan or tier, and product sign-up source.
- A pipeline stage or tag that represents a product-qualified lead.
- Developer time to send one or two events out of the product analytics tool.
Setting up the product signal
- Agree in writing which product event marks activation and sales readiness.
- Go to Settings, then Custom Fields, select Contacts and stay on Fields.
- Select Create field, choose the Field type and enter a Field name.
- Click Create custom field for activation date, tier and sign-up source.
- Go to Automation, then Workflows, and click + Create Workflow.
- Choose Start from Scratch, click + Add New Trigger and pick Inbound Webhook.
- Copy the webhook URL and give it to your developer.
- Have the product tool POST the activation event to it as JSON.
- Send a test request, map the incoming data, then click Save Trigger.
- Add an If/Else branch for accounts that meet your sales threshold.
- On that branch, add the Create/Update Opportunity action, then click Save Action.
- Toggle the workflow from Draft to Publish.
- Each month, compare won deals by sign-up source with the product tool's report.
Why it matters for a firm with flat revenue
Product-led companies with a sales team often stall in a specific way. Sign-ups rise, marketing celebrates, and revenue stays flat because sales chase every sign-up equally. Passing activation into the CRM changes the queue. Sales call the users who have shown intent, and marketing can see which channels produce activated users rather than empty accounts.
It replaces a weekly export of active users that someone pastes into a spreadsheet for the sales team. For how the wider journey looks once these signals arrive, read mapping customer journey stages.
Imagine 1,200 trial sign-ups a quarter, with sales calling every one. If activation is passed to the CRM and only 260 users meet the definition, sales would call 260 people instead of 1,200, and those calls should convert at a far higher rate. The channel report might then show partner referrals producing the most activated users, while a paid social campaign produces plenty of sign-ups and almost no activation. These numbers are for illustration only.
Weekly time
The platform side takes two to three hours to build. Developer time depends on your product. After launch, the sales lead should check weekly that activated users are arriving with a source and an owner, which takes fifteen minutes. Product and marketing should compare channel reports once a month.
Teams sync every product event to the CRM so salespeople can see everything. Salespeople then see nothing, because the timeline is flooded. Send two or three meaningful events and leave the rest in the product tool.
When not to do this
If you do not sell through people, and every customer self-serves to payment, the product analytics tool is probably the right home for attribution and a CRM link adds little. Equally, if activation is not yet defined, define it first. Syncing an undefined signal only moves confusion into another system. The customer journey analysis guide helps with that definition work.
Troubleshooting
Activated users arrive with no source. The sign-up form inside the product does not capture campaign parameters. Add them at sign-up, or capture source on your marketing site before the product login.
Contacts duplicate. Users sign up to the product with a different email from the one they used on your enquiry form. Store the product account ID on the contact and match on it as well as email.
Sales and product disagree on channel performance. They are measuring different outcomes. Agree that product reports activation by channel and the CRM reports revenue by channel, and present both together.
Frequently asked questions
Should the CRM or the product tool be the source of truth for attribution?
For revenue, the CRM. For product behaviour, the product tool. Store the original sign-up source in both so the two reports start from the same first touch.
Can I score leads on product usage?
Yes. Write usage signals into contact fields and use them in workflow conditions or a scoring field. Keep the score simple: a handful of meaningful behaviours beats a complex formula nobody trusts.
Do I need Amplitude to do this?
No. Any product analytics tool that can send an event with an identifier will work. The design matters more than the tool. For the reporting view, see building a marketing analytics dashboard.