On-line Marketing

Enable on-line marketing

Indicates if on-line marketing should be enabled. This includes the following functionality:

•Tracking of users on the live site as contacts. If the setting is disabled, existing contacts may still be worked with in the administration interface.

•Logging of on-line marketing activities.

•Newsletter marketing features, i.e. e-mail tracking and bounced mail monitoring.

Optimization

Enable A/B testing

Indicates if A/B testing should be allowed for pages (documents). When an A/B test is defined for a page, new visitors who access it will be randomly assigned to one of the defined page variants and their activity from that point will be logged accordingly. For detailed information, please see the Modules -> Website optimization -> A/B testing chapter in the Developer's Guide.

In order to work correctly, A/B testing additionally requires the Enable web analytics and Track conversions settings to be enabled in Site Manager -> Settings -> On-line marketing -> Web analytics.

Enable multivariate testing

Indicates if multivariate testing (MVT) should be enabled. This allows you to define MVT tests for pages and create different variants of their content. Once the test is running, visitors who access the page on the live site will be shown one of the possible content combinations and their activity on the website from that point will be logged accordingly. To learn more, please refer to the Modules -> Website optimization -> Multivariate testing chapter in the Developer's Guide.

In order to work correctly, multivariate testing additionally requires the Enable web analytics and Track conversions settings to be enabled in Site Manager -> Settings -> On-line marketing -> Web analytics.

Content personalization

Enable content personalization

Indicates if content personalization should be enabled. This allows page designers (and content editors) to create different variants of web parts, entire web part zones or editor widgets that are displayed on the live site according to a dynamically resolved macro condition.

Additional information can be found in Developer's Guide -> Modules -> Content personalization.

Contact management

Notes stamp format

Allows to define a customizable stamp which will be used in accounts or contact notes.

Log IP addresses

Indicates if logging of IP addresses should be allowed.

Remember contacts permanently

Indicates how long contacts should be remembered. If checked, a contact is kept until cookies are deleted or another contact is determined. If unchecked, a contact is kept until the current session expires.

Automatically recognize visitors by user agent

Indicates if visitor's browser user agent information should be used to determine what contact should be assigned to the current anonymous visitor.

Automatically recognize visitors by IP address

Indicates if visitor's IP address should be used to determine what contact should be assigned to the current anonymous visitor.

Global data

Allow global contacts

Indicates if global contacts should be allowed on the website.

Automatically create global contact for user on multiple sites

If a user is present on multiple sites, a global contact will be created for all site contacts related to the given user.

Allow global accounts

Indicates if global accounts should be allowed on the website.

Allow global contact groups

Indicates if global contact groups should be allowed on the website.

Allow global configuration

Indicates if global configuration should be allowed on the website.

Automatic merging of contacts

Merge contacts for identical E-commerce customers

Automatic contact merging will occur if multiple contacts exist for an e-commerce customer.

Merge contacts for identical Newsletter subscribers

Automatic contact merging will occur if multiple contacts exist for a newsletter subscriber.

When a visitor has more contacts, use

Indicates which contact should be used as parent contact if a site visitor has multiple contacts assigned.

•Last logged contact - a contact which has the last logged activity will be selected.

•Most active contact - a contact which has the highest number of logged activities will be selected.

•Create a new contact - a new contact will be created.

Delete inactive contacts (only available if hotfix 6.0.7 or newer is applied)

Delete inactive contacts

Determines whether the contacts associated with the given site should be affected when the Delete inactive contacts scheduled task is executed. This task is used to periodically clear out contacts (and the activities logged for these contacts) according to certain conditions. If disabled, the site's contacts will only be removed if they are deleted manually.

The remaining settings in this category are used to set the conditions that specify which contacts should be deleted. At least one condition must be entered in order for any contacts to be deleted.

If multiple conditions are set, only those contacts that fulfill all of them will be removed.

Last activity older than (days)

Can be used to delete contacts that do not have any recent activities logged. Contacts whose latest activity is older than the specified number of days will be removed.

For example, entering 14 would mean that contacts which do not have any activities logged within the last two weeks would be removed.

Contact created before (days)

Can be used to clear out old contacts. All contacts that are older than the specified number of days will be removed.

For example, setting the value to 365 would mean that all contacts created more than a year ago would be removed.

Contact last logon before (days)

This condition is only applied to contacts that are not anonymous (i.e. only those that are associated with a specific user account). It can be used to delete contacts who have not logged into the website recently.

For example, entering 31 would mean that all contacts who have not logged in within the last month would be removed.

Contact last modified before (days)

Can be used to remove contacts that were not edited recently (e.g. had their contact address changed). Contacts whose latest modification is older than the specified number of days will be deleted.

For example, entering 31 would mean that all contacts which were not modified within the last month would be removed.

Contact merged before (days)

Can be used to delete contacts that were merged into another contact a certain number of days ago.

A merged contact is one that was combined into another contact, not the contact which is the actual result of a merge operation.

For example, entering 7 would mean that all contacts which were merged more than one week ago would be removed.

Merged into site contact

Determines whether the task should delete all contacts that were merged into another contact associated with the given site.

A merged contact is one that was combined into another contact, not the contact which is the actual result of a merge operation.

Merged into global contact

Determines whether the task should delete all contacts that were merged into a global contact.

A merged contact is one that was combined into another contact, not the contact which is the actual result of a merge operation.

Contact is anonymous

Can be used to choose whether the task should remove all contacts that are anonymous, or the opposite (those that are related to a specific user account).

Please note: Contacts that are only related to a customer or subscriber are still considered as anonymous.

The Doesn't matter option is the equivalent of an empty value in this condition. (i.e. if selected, the task will not delete any contacts unless at least one other condition is specified).