Increase Effectiveness With A Common ID

Organizations integrate multiple separate silos of information for a variety of reasons.  Today, I will discuss how generating a Common ID on your same or related company and contact records that are represented multiple times and located in disparate data systems can increase sales, marketing, and data management effectiveness with a Common ID.

With a Common ID on records from the same organization regardless of the data source, queries and other reports can be generated using data from multiple data sources and/or multiple tables within a single data source in order to generate reports for better decision making and for executing strategies such as:

• Marketing can produce queries and generate lists such as who bought product “A” and not product “B” based on information in multiple databases/multiple tables.
• Business Intelligence/Dashboard Reporting tools can be utilized to analyze data from multiple data sources/tables and not just on data “silos”.

Reports are more accurate since multiple records that are part of the same organization can be given a Common ID and therefore counted as one organization.  For example, marketing can count multiple records for the same organization as one “opportunity”.

By having a single customer view by matching and linking records from the same organization by a Common ID, employees can now make better decisions based on information contained in multiple data sources and/or multiple records for the same Entity/Contact within a single database.  For example,  a sales person can see all the authorized information for an organization in their sales database, the external marketing file (firmographics, public records, etc.), the accounting system, the customer service system, and other data sources in a single view in order to help to prioritize who they should target, what they can cross-sell and up-sell, and overall better management of their accounts.

A new database can be built in a more compete manner utilizing Common Entity and Contact IDs.   For example, If a company merges with a former competitor, there are going to be overlapping entities and contacts within the two former organizations’ legacy systems.  You can now build a new database that identifies and merge/purges duplicates and the new database can be organized so that there is a primary record for each location and the contacts that are associated with the location can be linked to that primary location record as well as all location records for the organization.

A single database can be re-organized utilizing Common Entity and Contact IDs.  Some examples include duplicates records within a single database can be identified and merge/purged.  The multiple records that are part of same organization that are not duplicates can be linked to the primary organization record within the database.

Organizations integrate multiple separate silos of information for a variety of reasons.  Today, I will discuss how generating a Common ID on your same or related company and contact records that are represented multiple times and located in disparate data systems can increase sales, marketing, and data management effectiveness with a Common ID.

With a Common ID on records from the same organization regardless of the data source, queries and other reports can be generated using data from multiple data sources and/or multiple tables within a single data source in order to generate reports for better decision making and for executing strategies such as:

• Marketing can produce queries and generate lists such as who bought product “A” and not product “B” based on information in multiple databases/multiple tables.
• Business Intelligence/Dashboard Reporting tools can be utilized to analyze data from multiple data sources/tables and not just on data “silos”.

Reports are more accurate since multiple records that are part of the same organization can be given a Common ID and therefore counted as one organization.  For example, marketing can count multiple records for the same organization as one “opportunity”.

By having a single customer view by matching and linking records from the same organization by a Common ID, employees can now make better decisions based on information contained in multiple data sources and/or multiple records for the same Entity/Contact within a single database.  For example,  a sales person can see all the authorized information for an organization in their sales database, the external marketing file (firmographics, public records, etc.), the accounting system, the customer service system, and other data sources in a single view in order to help to prioritize who they should target, what they can cross-sell and up-sell, and overall better management of their accounts.

A new database can be built in a more compete manner utilizing Common Entity and Contact IDs.   For example, If a company merges with a former competitor, there are going to be overlapping entities and contacts within the two former organizations’ legacy systems.  You can now build a new database that identifies and merge/purges duplicates and the new database can be organized so that there is a primary record for each location and the contacts that are associated with the location can be linked to that primary location record as well as all location records for the organization.

A single database can be re-organized utilizing Common Entity and Contact IDs.  Some examples include duplicates records within a single database can be identified and merge/purged.  The multiple records that are part of same organization that are not duplicates can be linked to the primary organization record within the database.