|
||
The following database tables are used to store contact management and scoring data:
•OM_Contact - contains records representing contacts and their settings.
•OM_ContactStatus - contains records representing possible contact statuses.
•OM_ContactRole - stores the possible roles that contacts can have within accounts.
•OM_Membership - this table is used to bind users, subscribers and customers to contacts. Each entry has a member type, which determines whether the related object is a user, subscriber or customer. The given object is then connected through its ID (RelatedID). Please note that the relationships with the CMS_User, Newsletter_Subscriber and COM_Customer tables are not indicated in the diagram below.
•OM_IP - used to store the IP addresses associated with contacts.
•OM_UserAgent - stores the browser user agents of contacts.
•OM_Account - contains records representing accounts and their settings.
•OM_AccountContact - stores relationships between contacts and accounts. Each record indicates that a contact belongs to a specific account. If the contact has a certain role within the account, the information is also stored in this relationship.
•OM_AccountStatus - contains records representing possible account statuses.
•OM_ContactGroup - contains records representing contact groups.
•OM_ContactGroupMember - this table is used to bind contacts and accounts to contact groups. Each entry has a member type, which determines whether the related object is a contact or account. The given object is then connected through its ID (ContactGroupMemberRelatedID). Please note that the relationships with the OM_Contact and OM_Account tables are not indicated in the diagram below.
•OM_Activity - contains records representing the logged activities.
•OM_ActivityType - contains records of all possible activity types.
•OM_PageVisit - used to store the additional details, which are logged along with Page visit activities.
•OM_Search - used to store additional details for Search activities.
•OM_Score - contains records representing and their configuration.
•OM_Rule - contains records representing scoring rules.
•OM_ScoreContactRule - contains relationships between contacts, scores and rules. Each record stores the value that a specific contact has according to a certain scoring rule. The total score points of a contact are calculated as the sum of all values for the rules that belong to the given score.
The diagram below shows the relationships between these tables. For a full‑size diagram including table columns, please click here.