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 deal 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.

Every pipeline is a board in Leads. Each Kommo pipeline appears in Leads with Kommo's stages, so you can see deals, drag a stage that is behind, and count each person once alongside your Website leads. Work your team does in Kommo also counts as contact there, so a lead your team is already working stops reading as not contacted.

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

Stage settings now live in Leads, next to the board they describe. Open Leads, pick the Kommo pipeline in the switcher and click Configure stages. The Connections → Sources → Kommo page lists your pipelines and links each one straight to its stage settings, on plans that include CRM leads. A pipeline you removed in Kommo shows as Archived, with no link. For each stage you choose two things:

• Outcome: Open, Qualified, Won or Lost. Kommo only marks its own Won and Lost stages, so tag any other stage that means a sale as Won.
• Send to Meta as: the event Meta hears when a deal enters the stage. A stage follows its outcome by default, or you can pick a standard event like Contact or Schedule, a name of your own, or Don't send to Meta. The first time a deal reaches a stage, Zappush sends its event once; moving the deal out and back does not send it again.

Kommo's Won and Lost already work with no configuration. Won sends one purchase carrying the deal's price as its value, a short wait after the deal is won so a price entered a moment later is not missed. Every other stage sends nothing until you choose an event for it. Lost sends nothing by default, because ad platforms accept conversions and offer no way to tell one that a lead turned out badly.

Settings you made on the old Kommo stage mapping carried over and are tagged Kept from Kommo settings, so the same events keep going out. Until you save a pipeline's stages once, its board asks which of its stages mean the customer paid.

A stage you tag Won counts its deals as revenue and sends a purchase, and a deal reports at most one purchase, however many stages it passes through. Tell Meta a sale happened only at a stage that means one, since Meta counts every deal that reaches it as a sale. If your team closes deals in a mid-pipeline stage rather than Kommo's own Won, tag that stage Won and Meta gets a real purchase instead of a generic signup.

Stage names, colors and order always come from Kommo. When a deal changes stage in Kommo, its card moves in Leads. You can drag a card to fix a stage that is behind, and Zappush never changes anything in Kommo. A later move in Kommo wins over your move.

Lost deals

Whatever a Lost stage is set to send, or if it sends nothing, Zappush also records the loss with the reason from your account and stops including that person in what it sends onward for every other stage.

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 Funnel progression table has one row per stage, in pipeline order:

• Entered is how many deals reached the stage.
• Median time in stage is how long deals typically stayed before moving on.
• Still here is how many deals are waiting in the stage now, and Oldest still here is how long the longest-waiting one has been there.
• Funnel progression is the share of deals that entered the stage and later reached any stage after it, with the counts beside it.

Funnel progression is not a stage-to-stage conversion rate. Kommo pipelines can run backwards and deals can skip stages, and Zappush counts both as they happened. A stage no deal has left yet reads "No deals have left this stage yet".

Click a column title to sort the table. When a pipeline has more stages than fit, View all opens the full table in a full-screen view, where you can also search by stage name.

The Pipeline tab shows on plans that include pipeline reporting. On other plans the Kommo page shows the Connection tab alone, and a saved link to the report explains that it is not on your plan.

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.