Data

Merging duplicate deals

Automatically merge duplicate deals without data loss

Features

Selecting a merging algorithm
Works between different funnels
Saving transaction history
Association Analytics
Possibility of cancellation

Installation and setup guide

Detailed guide for working with widget "Merging duplicate deals"

CONTENTS

  1. Initial setup
  2. Merge Options
  3. Additional settings
  4. Starting and managing a federation
  5. Merger example
  6. Do not glue inside the block
  7. Analytics and statistics

Initial setup

After installation:

  1. Go to NSettings → Integrations → Widget.
  2. Fill out the form (Name, Number).
  3. Click Activate.

Merge Options

By what entity to combine

  • Primary contact (default)
  • Any contact in the transaction
  • Company
  • Main contact + Company

This widget only combines transactions for one contact/company.

One contact/company is a contact/company with one ID

ID can be viewed in the address bar when going to the contact/company

Which way to combine?

  • Towards a senior transaction - everything is combined into a senior transaction.
  • Priority by order in the block - deals are combined into the one that is lower in the list of selected stages/funnels.

Merge blocks

  • The combination is configuredwithin the selected block (stages and funnels).
  • Deals are not merged between blocks.
  • In the “Unparsed” stage, merging is not performed.

Additional settings

  • Checkbox “Do not glue within a block” - if you need to combine transactions between stages, but not within one stage.
  • Field settings - select which fields to leave or replace when merging.
  • Creating a task after merging - you can set the task type and text.
  • Additional field matching check - merging will only occur if the selected fields match (or if one of them is empty).
  • Save the creation date of the oldest transaction - to see the complete history of correspondence from the first transaction.
  • notmerge tag - allows you to exclude individual transactions from the merge.

Starting and managing a federation

  • Save – saves the settings.
  • Enable database processing first - starts merging old takes. Further, the merger is performed automatically for new transactions.
  • You can stop merging at any time.

Merger example

  • There are three deals in the funnel with one contact
  • According to the settings made, merging occurs, a new deal is merged, but deals from the Paid stage are not merged, since in the settings we indicated that there is no need to merge duplicates at the Paid stage

Do not glue inside the block

  • If you need to combine transactions between stages, but not within one stage, then in the block settings you need to enablethe checkbox “Do not glue within a block”

How does this work?

  • There are three deals in the funnel with one contact
  • According to the settings after the merger, the deal from the NEGOTIATIONS stage was merged with the senior deal in the PAID stage
  • Transactions at the PAID stage were not merged

Analytics and statistics

  • Go to the Analytics → Event List section.
  • In the filter, select Event type → merged
  • Select entity - Transactions
  • The system will show all joins
  • When you click on Apply, all transactions with this filter will be displayed

https://xxxxxx.kommo.ru/events/list/?with_filter=y#filter_date_switch=created&filter%5Bevent_type%5D%5B%5D=92&filter%5Bentity%5D%5B%5D=2&useFilter=y -where instead of xxxxxx is your subdomain

  • You can also copy and paste the link into the address bar of your browser: