SMART Profile - Match and Merge Rules

Prerequisites for Smart Profiles - Match and Merge Rules
This screen defines how incoming profiles are matched and merged in OPERA Cloud Central after passing initial internal validation and region configuration checks.

Internal Match Criteria

Before the merge rules can evaluate a profile, it must first meet the internal match criteria. The configuration of Cloud Hub determines how profiles are validated before the matching and merging process. These original internal match criteria must be satisfied and are validated within OPERA Cloud Central, which cannot be directly configured through the SMART Profile UI. Additionally, integration rules within Cloud Hub may influence which data is sent and how it is validated.

Important:

These notes apply to how OPERA PMS profile changes are handled and communicated to OPERA Cloud and external systems.
  • Each profile must contain only one primary address.
  • When a phone number or address is removed in OPERA PMS, it is marked as inactive rather than deleted.
  • Inactive records are automatically purged after 30 days, unless reactivated.
  • When such deletions occur in OPERA PMS, the OPERA Cloud Interface transmits the record as inactive to external systems.
  • Profile merging operates on a one to one basis only.

The following fields are used as part of pre-merge validation to determine if a profile qualifies to enter the merge rule evaluation process. The profile will only advance to rule-based matching if these fields are sufficiently aligned.

  • Name ID
  • Property ID
  • Resort (Subscription) ID
  • Name Code

Merge Rule Overview

Once a profile passes the internal match checks, it proceeds to rule-based matching using configurable weighing points. Merge rules and weighing logic are defined per profile type and region. The matching process is influenced by:

  • Profile type (Individual, Company, Group, etc.)
  • Region configuration (set up through Profile Regions)
  • Data quality and structure are sent from external systems through the OPERA Cloud Interface.

Merge rules utilize weighing points to determine whether a profile should be merged, created as a new one, or staged for manual review.

Key Thresholds:

  • Lower Threshold: If the total score is below, a new profile is created.
  • Upper Threshold: If the score exceeds this threshold, the profile is automatically merged.
  • Matches Found: Scores between thresholds require manual review.

Address Matching: An address does not need to match exactly. Only the number of characters defined in the COMPARE ADDRESS LENGTH parameter must match.

Multiple Match Handling

When the Multiple Matches OPERA Control is active and more than one profile exceeds the MULTIPLE_THRESHOLD score (but none surpass the Upper Threshold), the best match cannot be determined. In this situation, the profile is suspended with a Matches Found status, allowing you to manually identify the correct match among the various results in OPERA Cloud Central. If the Multiple Matches OPERA control is inactive, the Multiple Match threshold does not appear on the Match and Merge screen. In this case, when evaluating matches, OPERA Cloud only considers the first match found for validation purposes.

Example Scenario (Multiple Threshold):

When Enabled

A match is found on Property ID <<PROP ID>>

Further search finds multiple potential matches based on the Merge Rule configuration:

  • Profile A - Name: NAME, email: <<NAME@example.com>>
  • Profile B - Name: name, email: <<name@sample.com>>
  • Profile C - Name: Name, email: <<Name@demo.com>>

When Disabled

A match is found directly on Profile ID XXXXX.

Any further search is skipped only the 1st profile found for match processing is considered.

Profile ID XXXXX matched.

Parent topic: Profile Management