---
schema_version: "1"
id: 9d409ec5ce988ffc0af604dd5ddd9e2d53d3706d1d6c1427bdc39e25c3bd493c
title: Evaluate Account Matching in Query Editor
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/data/264-0-0/c360_a_identity_resolution_evaluate_account_matching.md
canonical_url: https://help.salesforce.com/s/articleView?id=data.c360_a_identity_resolution_evaluate_account_matching.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: ad519de26907c9b75df908c42d2834436b905c63dc038f383c154c2f43216974
description: Check the effectiveness of your account unification match rules by reviewing Unified Account profiles with Query Editor.
products:
  - Data 360
release: "264"
---
# Evaluate Account Matching in Query Editor

Check the effectiveness of your account unification match rules by reviewing Unified Account profiles with Query Editor.

The following query compares the output from a ruleset with the ruleset ID `001` with the output from a ruleset with ruleset ID `002`. The query compares how profiles linked to the phone number 555-234-5678 were unified by each ruleset.

To run this query in Query Editor in your org, customize the query for your org’s data.

1. Replace the account IDs in the specified UnifiedLinkssotAccount objects with ruleset IDs that are valid for your org. For example, to compare rulesets with IDs `ABC` and `XYZ`, replace `UnifiedLinkssotAccount001__dlm` and `UnifiedLinkssotAccount002__dlm` with `UnifiedLinkssotAccountABC__dlm` and `UnifiedLinkssotAccountXYZ__dlm.`
2. Replace the sample phone number, `(555) 234-5678`, with the phone number of specific record you want to review. Or, update the `WHERE` clause with different criteria.

![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-data-data_cloud-264-0-0-production-enus/f3569962-3c9b-4f83-9d0c-b6a574e785da/images/icon_important.png)

Important Don’t remove the LIMIT clause from your query. An unlimited query response can return too many records to be useful.

After running the query, review the output to determine if the matches created by your match rules fulfill your business requirements. If not, tweak your match criteria and match methods to optimize your matching.

```
SELECT
	"ssot__Account__dlm"."ssot__Id__c",
	"UnifiedLinkssotAccount001__dlm"."UnifiedRecordId__c" as Med_UUID,
	"UnifiedLinkssotAccount002__dlm"."UnifiedRecordId__c" as LOW_UUID,
	"ssot__Account__dlm"."ssot__Name__c",
	"ssot__ContactPointAddress__dlm"."ssot__AddressLine1__c",
	"ssot__ContactPointAddress__dlm"."ssot__AddressLine2__c",	
	"ssot__ContactPointAddress__dlm"."ssot__CityId__c",
	"ssot__ContactPointAddress__dlm"."ssot__CountryId__c",
	"ssot__PartyIdentification__dlm"."ssot__PartyIdentificationTypeId__c",
	"ssot__PartyIdentification__dlm"."ssot__Name__c" AS "Party_Name",
	"ssot__PartyIdentification__dlm"."ssot__IdentificationNumber__c",
	"ssot__ContactPointPhone__dlm"."ssot__FormattedE164PhoneNumber__c"	
FROM "ssot__Account__dlm" 
	LEFT JOIN "UnifiedLinkssotAccount001__dlm" ON "UnifiedLinkssotAccount001__dlm"."SourceRecordId__c" = "ssot__Account__dlm"."ssot__Id__c"
	LEFT JOIN "UnifiedLinkssotAccount002__dlm" ON "UnifiedLinkssotAccount002__dlm"."SourceRecordId__c" = "ssot__Account__dlm"."ssot__Id__c"
	LEFT JOIN "ssot__ContactPointAddress__dlm" ON "ssot__ContactPointAddress__dlm"."ssot__PartyId__c" = "ssot__Account__dlm"."ssot__Id__c"
	LEFT JOIN "ssot__PartyIdentification__dlm" ON "ssot__PartyIdentification__dlm"."ssot__PartyId__c" = "ssot__Account__dlm"."ssot__Id__c"
	LEFT JOIN "ssot__ContactPointPhone__dlm" ON "ssot__ContactPointPhone__dlm"."ssot__PartyId__c" = "ssot__Account__dlm"."ssot__Id__c"
WHERE "ssot__ContactPointPhone__dlm"."ssot__FormattedE164PhoneNumber__c" = '(555) 234-5678'
ORDER BY 
	"ssot__ContactPointPhone__dlm"."ssot__FormattedE164PhoneNumber__c",
	"ssot__Account__dlm"."ssot__Id__c"
LIMIT 100
```