1) The ADOR or Content object is the item (or tag) that is placed into a print/email/web/sms/video dynamic document (template) to change text/graphic/style/visibility or other attributes dynamically. The ADOR/CO can uses a data field's value from a database or a value calculated by using logic or business rules.

2) ADOR stands for Automatic Dynamic Object Replacement, the XMPie technology for personalizing and calculating the value for objects to synchronize, customize and track content across various media within a campaign.

This refers to a collection of campaign assets - for example: images and formatted text files - and their location.

• For desktop production, define a single folder with files or a single folder with files organized within subfolders (i.e. one source for the campaign). 
• For server production, you can define one or more asset sources for a single campaign.  Sources can be local or remote server shared files. 
• Templates with uImage, have specific steps for organizing these generated assets for access via their asset source.

Files that are fetched (or called) to place into a template during variable data output generation. XMPie software has use two types of assets, either images (PDF, JPG, EPS, and more) or text files (TXT, RTF, DOC, XNIP). 

Static Files placed into a design are referred to as Resources.

When a marketing campaign uses multiple and different media types to communicate with recipients, it can be called an omnichannel, transmedia or cross media (xm) campaign.

In terms of XMPie software, our XM solution/product provides the creation and management of a multichannel campaign and its production for print, email, webpages, video and SMS media types, where the campaign synchronizes the content using the same logic, data and other resources.

1) The generated output from an InDesign or XLIM template that has been merged with data either using the desktop software (uCreate) or the XMPie production server system (uProduce).

2) Any document that requires information or images to change (including backgrounds) based on data or user input.

3) aka VDP Output.

A plan file stores data references and implemented business rules for print and cross media campaigns.

A proofset file contains a set of values for content objects based on a particular plan file and data set. A proofset is a snapshot in time, if the plan or data changes the proofset would need to be regenerated.

Both the plan file and its associated proofsets are XML-encoded files. 

XMPie proprietary scripting language with functions and expressions for writing business rules to calculate values for Content Objects.

QLingo rules are created with uCreate, uPlan and Circle products.

A recipient is typically a person who receives an individual instance of the document. If the document is static, all recipients receive identical copies; if the document is dynamic, each recipient receives a unique document instance, which has been personalized based on this recipient’s specific data.

Alternatively, recipients can be a group of people (for example, a company), an event (for example, a company picnic), a place (for example, company branch, or a specific location) or a thing (for example, a product). Often documents of this nature are referred to as versioned/customized rather than personalized.

Static (not data driven) graphics and other elements placed into the template. 

XMPie proprietary document composition engine and document format. XLIM was built for speed (production speed). Templates are setup in InDesign with uCreate then configured to work with XLIM composition. XLIM templates can also be used with uEdit.

The engine is available in all PersonalEffect Turn-Key solutions and Enterprise configurations.