Custom Objects are a special type of table in the EDP database, designed to extend the customer profile with object types specific to the user’s business. These objects contain their own set of Attributes, and can be used for segmentation, personalization, and analytics.
Custom Object tables join to the Person table using a one-to-many relationship, meaning that a single consumer can have one or more Custom Objects associated with them. For example, a single consumer could make multiple hotel reservations, or purchase multiple flights, or hold multiple subscriptions. A Custom Object record can't exist by itself; it must be joined to a record on the Person table.
The intented use of Custom Objects is to store information that doesn't otherwise fit into other EDP concepts like Orders, Activities, or Lookups.
A Custom Object record can have Activity associated with it. For example, let's say you're using Custom Objects to store hotel reservations. The action take by the consumer (making the reservation) is captured as an Activity, but the information about the reservation itself (date, price, status, special requests, and so forth) is stored on the Custom Object table. Activities don't provide the necessary functionality to adequately capture this information, because Activities are intended to provide a historical log of consumer actions, not to track ongoing, changeable details, like "status."
Custom Objects differ from Lookup tables in that a Custom Object is joined to a consumer, and is part of the consumer's overall profile. Lookup tables are best suited for non-person related data, like store locations, products, etc.
The platform allows you to create a hierarchy of Custom Objects. Every Custom Object table in the hierarchy must have its own primary key that uniquely identifies a record on that table. Continuing the above example for hotel reservations, you could use a nested Custom Object table to store special requests. A single reservation (joined up to the Person table) could have one or more special requests associated with it.
To access the Custom Objects screen, select Definitions from the Main Navigation Menu, then select Custom Objects from the Sub-Category menu.
The Custom Objects screen provides the following features:
SearchThe search feature allows you to search for a specified text string within the following Custom Object fields: Display Name, Internal Name, Type, Source, Tag, Category label, or Category name
SortThe "Sort" drop-down menu allows you to sort the Custom Objects on a variety of different fields. To sort the list of Custom Objects, select the desired sort option from this menu.
NavigationOnce you've found the desired Custom Object, you can navigate to the following other screens:
|
To create a new Custom Object:
Note: The other options listed in this menu -- Streaming and Synthesized -- are not yet supported.
|
To view or edit the details of a Custom Object:
|
After you've created a Custom Object, you must deploy the Custom Object metadata. If you have modified Custom Objects in your account that haven't yet been deployed, a warning message is displayed at the top of the Custom Objects screen. When you deploy the metadata to the server, the process automatically deploys the metadata for ALL modified Custom Objects.
Note: You can deploy metadata immediately, but the best practice is to validate the Custom Object logic before deploying metadata to ensure no incorrect code gets deployed to the server that could cause issues.
|
To see the details of what Custom Objects metadata has been deployed:
|
Last Updated: April 2022