skip to the main content area of this page
EMM Help: Tables Used in EMM

EMM Specific Tables

  • xaEmmAudiences: This table is used internally currently the types of audiences available to an individual using the EMM. There is no interface for editing it.
  • xaEmmCampaigns: This is the primary table used to define all elements of a given campaign. This database is managed using the main Campaigns page in both the pending and completed campaign views.
  • xaEmmClickTracks: This is the table used to track the number of click-throughs to a given URL that is driven by a particular Campaign.
  • xaEmmErrorLog: This is table is used to record exceptions as they occur. Data is currently being collected here however we do not yet have a interface for this data.
  • xaEmmExternalCustomer: This table is used to hold the External Customer data. This allows you to run a secondary store of individuals to mail to. One customer uses this table to track the customers of their real-world store while the Customers table is just for their website customers. Many customers will never use this table.
  • xaEmmMasterUnusbscribeList: This table is to allow larger organizations who might have multiple lists where customers could be on any number of them to maintain their CAN-SPAM compliance. Anytime you add an opt-out using the unsubscribe form an entry will be made here that can be checked against to prevent mailing to specific addresses even if they don't exist in either the Customer or ExternalCustomer tables.

ASPDNSF Tables Used

  • AppConfig: This is where we've stored a number configuration options for EMM. We also utilize some of the AppConfig variables that ASPDNSF depends upon in the configuration of EMM.
  • Customer: This is the table that contains the majority of the user data for campaigns
  • StringResources: Localization text specific to EMM is stored in this table. Currently, we are providing English language (en-US) version of string resources. The entire application is not entire ML at this point as there are still phrases that are hard coded into administrative interface. This will get up resolved over the next few releases.
  • Topic: The content for a few pages and the Double Opt-In email (HTML only) are designed and housed in ASPDNSF Topics.