LinkedIn
Copied!

Table of Contents

Creating an event type in the Event Catalog

Version:

Only available versions of this content are shown in the dropdown

You can create multiple events in the Event Catalog to collect customer data from specific data sources (Data set or Report definition) and store it in the Event Store data set. You can retrieve this data to get information about customer interactions and display them in an events feed that you add to your user interface.

  1. In the header of Dev Studio, click Configure Decisioning Infrastructure Customer Movie Event Catalog .

  2. On the Event catalog tab, click New.

  3. Click Create to start the New Event Type wizard.

  4. Configure the source of the event.

    1. Select the event class which is the class of the source data set or report definition.

    2. Select the source type (Data set or Report definition).

    3. Select an instance of the source rule.

    4. Select an event ID to fetch each of the event details. The event ID values must be unique to avoid overwriting data in the Event Store data set.

    5. Optional:

      Use event time instead of the system time. Event time is stored as the .pxCaptureTime property of the Event Store data set and appears in the customer’s timeline.

    6. Enter a name for the event type.

    7. Optional:

      Click the default icon to select a different one.

    8. Enter a description for the event type.

    9. Click Next.

  5. Configure identity matching details for retrieving customer data.

    1. Select the source of the customer ID to specify where the customer data is:

      • Event class - Select this option if the customer information (customer ID and group ID) is in the event class.

      • Customer class - Select this option if the customer information (customer ID and group ID) is in a class other than the event class.

        • Map properties from the customer class and the event class that will be used to match and retrieve customer data for the event.

    2. Map customer ID. Select the source field that will be mapped to the Customer ID in the Event Store data set.

    3. Optional:

      Store events by customer group also. Use this option when there are groups of customers in the data source, for example, employees of a department, credit card holders.

      • Map group ID. Select the source field that will be mapped to the Group ID in the Event Store data set.

  6. Configure storage and retrieval options.

    1. Specify how long you want to keep events. The default configuration is to keep events for unlimited time.

    2. Select whether you want to store event details. You need to store event details in a new data set when this data comes from an external data set. This way you can query the data set to get event details.

      • Do not store event details

      • Store in a new data set (Decision data store)

        • Provide the name of a data set where you want to store event details.

          When you use this option, you store a copy of the source data in a Decision Data Store data set.
    3. Select how you want to retrieve event details.

      This option is not available if you store event details in a new data set.
      • Retrieve from internal source - Select this option if the event details can be retrieved from the source data set. This option is not available for data sources other than data set.

      • Retrieve from external source - Select this option if the event details cannot be retrieved from the source data set.

        • Save the GetExternalEventDetails activity in the event class and specify the details that you want to populate through the primary page of this activity.
    4. Click Next.

  7. Review the details.

    • Review the details of the event type that you want to create.

    • Select the ruleset and its version where you want to create the event type.

  8. Click Create to submit the Event Catalog configuration.

When you finish creating an event type, an instance of a Data Flow rule ( <event name>CMF ) is generated. The source of this data flow is the event source that you configured in the first step of the New Event Type wizard and the destination is the Event Store data set.

  • Clearing an event type in the Event Catalog

    Use this option to remove unnecessary data from the Event Store data set. Clearing removes customers interactions that are stored in the Event Store data set, but it does not remove event types from the Event Catalog that can be used again.

  • Deleting an event in the Event Catalog

    Delete event types in the Event Catalog that you no longer use or need. Data associated with the deleted event type is deleted from the Event store data set.

  • Adding an events feed to your user interface

    An events feed lists information about customer interactions for specific event types and time ranges. You can add an events feed to your user interface by creating a reusable section that references the default data page (D_pxEvents), which points to the Event Store data set. This information can help you make informed and personalized decisions for each customer.

  • Browsing events for a customer or a group of customers

    Use the Event Browser to browse customer event types that occurred over a period of time and display them on the Customer Movie landing page. Browsing events for an individual customer or for a group of customers provides insight into the history of customer interactions.

  • Accessing the Customer Movie landing page

    Use this landing page to manage event types that you use for decision-making.

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.