Add Properties to Your Task

Types of Properties

There are three types of properties available for a task:

  • Standard properties, such as the task name and description.
  • Custom properties are specifically applicable to your goal or organization and must be added by your administrator.
  • Planning properties display planning information, such as which currency type is associated with the task.

Accessing Standard and Custom Properties

You can access a task's standard or custom properties in one of these ways:

  • If the task has a Properties tab, click it.
  • For all other task types, hover over the Properties section and click Edit.

Custom properties enable you to supplement the standard properties of an item (such as name, description, and type) with more properties that are specifically applicable to your goal or organization. Custom properties are defined by users with administrator access and can be used for a variety of purposes such as storing item-specific information and personalizing messages and creatives.

For more information, see Custom Properties.

Using the Code Setting

The code setting is a standard property that can be used to identify or track the task. For example, it can be used for auditing or reporting purposes.

When an item is imported or migrated to SAS Customer Intelligence 360, the existing code value for the item is retained. As a result, the code can be used to integrate with external systems. Valid characters for codes are alphanumeric characters, multi-byte characters, numerals, underscores, hyphens, and periods. Blank spaces are not allowed in code formats. This value does not need to be unique.

Note: Depending on the settings for your environment, you might be able to edit this value. Editing this value can be useful if you want to match the code for this task with another item.

For example, the Code field enables marketers to use a segment map to target customers based on their internal attributes (account type, balance, and so on) and their previous interactions. These codes are used to communicate information about the targeted customers to vendors or downstream systems. Using codes can minimize errors in text and punctuation that might occur when using an item name that is typically lengthy.

The information in the Code field can also be used for operational reporting. The information can be used to select or suppress customers for targeting messages (for example, a marketing message might target or exclude all customers who responded to direct marketing task 12345).

Generating Default Contact Events

The default contact event is a standard property. It is triggered by the impression event that corresponds with your task type. By default, the option to generate contact events is not selected when you create a task. For example, when you create an email task, the email send event does not trigger the creation of a contact event unless you select the Generate contact events based on the email send event option.

Note: This option is selected by default for any task that was created before the April 2020 (20.04) release. For tasks that are created after April 2020, this option is not selected by default.

The type of contact event that is created corresponds with the type of task that is being used.

  • Impression viewable events are created for web, mobile spot, and in-app message tasks. For example, a contact event is created when at least 50% of a creative is viewable on a web page or when a creative is sent to a mobile application.
  • Contact events are created for direct marketing tasks each time that a customer is included in the task.

    When you select the Generate contact events for this task option, the contact events are sent to SAS Customer Intelligence 360 only if the generation of export content and any post-processing of the task are successful. If the export is successfully generated, but the post-processing fails, then no contact events are sent to SAS Customer Intelligence 360 for that task.

    Note: A unique occurrence ID is generated for a contact event each time that the direct marketing task is executed.
  • Outgoing events are created for external tasks each time that an outbound event is created.
  • Notification send events are created for mobile push notification tasks each time that a notification is sent.
  • Email send events are created for email tasks each time that an email is sent.
TipYou can continue to classify the events that you add as primary or secondary metrics as contact or response events.

Properties for Associating Items with Plans

You can add planning properties to items such as tasks and activities. You can associate a task or an activity with an existing planning item and include the item in your marketing plan. For more information, see Switch between Planning Mode and Design Mode.

After you create and save a task, switch to the planning view in one of these ways:

  • If the task has tabs, click Plan Mode.
  • For all other tasks, click Go tothen select Plan.

The planning view contains standard and custom properties fields that provide information for planning purposes. To associate the item with an existing planning item such as a campaign, specify the values for the required fields in the standard and custom properties.

After you specify the planning start and end dates, in the Parent planning item field, click Select parent planning item and select a planning item from the filtered list of items that are based on the currency settings and your specified date range. In the Select Parent Planning Item window, use the search box or the drop-down list of options to further filter the list. The planning item that you select is designated as the parent object of the task or activity in the marketing hierarchy.

After you select the planning item, the Parent level field displays the marketing hierarchy level of the selected parent planning item.

Last updated: August 11, 2026