Kommo

Kommo knows what happened to a lead after the click: every conversation, every stage, and the number on the deal when it closes. What it cannot tell you is where that person came from, and what your ad platforms never learn is which leads turned into money. Connecting Kommo to Zappush closes both halves of that loop.

What you get

Closed revenue reaches your ad platforms. When a lead moves to Won, Zappush sends it to Meta and Google as a conversion carrying the actual deal value, not a flat estimate. Bidding starts optimising for revenue instead of lead volume.

Your leads gain their source. Kommo ships fields for the click and campaign that brought someone in, and leaves them empty. Zappush fills them, so your existing Kommo views, filters and reports start showing where each lead came from. Nothing to learn and nothing to set up.

A note on the lead card. A salesperson opening a lead sees the channel and campaign that produced it before they pick up the phone.

Connecting

Open Connections → Sources. Kommo sits under CRM sources, alongside your store's platform source rather than in place of it: a Shopify store keeps Shopify connected and runs Kommo as well, without giving up anything Shopify already sends.

Choose Kommo and authorise. Kommo asks which account to connect and returns you to Zappush. Nothing else is required.

An account can be connected to one workspace. If you try to connect an account another workspace already uses, Zappush refuses rather than moving it.

Stages

Won and Lost work immediately with no configuration, because Kommo uses the same two stage identifiers on every account. Everything between them is named by you, so Zappush makes no assumptions about the middle of your pipeline.

Lost deals

When a deal is lost, Zappush records it with the reason from your account and stops including that person in what it sends onward. Ad platforms accept conversions; there is no way to tell one that a lead turned out badly. Not spending to reach that person again is the useful response.

By default a lost deal excludes someone indefinitely, which is the safer choice. If your sales cycle means a prospect who went quiet a year ago is worth approaching again, set a recycling window on your Kommo connection yourself: losses older than it stop counting. Leave it unset and the exclusion never expires.

Winning a deal that was previously lost clears the exclusion.

Pipeline timing

Zappush records every stage a lead moves through, so how long deals sit at each step and how long they take to close becomes answerable. Kommo keeps only the current stage, so this is history that would otherwise not exist.

Open Connections → Sources → Kommo, then the Pipeline tab, for the report: how long deals sit at each stage and how many are still waiting there, plus how long deals take to close, reported separately for deals you won and deals you lost. It covers one pipeline at a time, your main one by default.

The Pipeline tab is available on a higher plan. A locked tab means an upgrade unlocks it, not that something is broken.

Merges

When someone merges two duplicate contacts in Kommo, Zappush follows the same merge on its next sync, for anyone it has already seen on a deal that reached Won, Lost, or a stage you've set up in Zappush. A contact it has never seen on a deal like that carries nothing to follow, so nothing changes for them. Where it applies, the record you kept is the record Zappush keeps.