Overview

In this case we show how a single event record can result in messages to multiple customers. When the Event Listener processes the event record in this scenario, it updates the master data and attributes for each customer, subscribes each customers to the conversation, and sends an email to each customer. This scenario assumes the customers already exist in Connect.

XML

<?xml version="1.0" encoding="UTF-8"?>

<kanaRoot>

<EventRequest Id="" CompanyName="default" CampaignName="camp1">

<Customer EmailAddress="[email protected]" First_Name="Jane" Last_Name="Doe"

City="Menlo Park" State="CA">

<CustomerAttribute name="Favorite Color">blue</CustomerAttribute>

<CustomerAttribute name="Occupation">chef</CustomerAttribute>

</Customer>

<Customer EmailAddress="[email protected]" First_Name="Jane" Last_Name="Madison"

City="Menlo Park" State="CA">

<CustomerAttribute name="Favorite Color">red</CustomerAttribute>

<CustomerAttribute name="Occupation">pilot</CustomerAttribute>

</Customer>

</EventRequest>

</kanaRoot>

Result

The KCXML contains one <Event> element and multiple <Customer> elements. This means that one event applies to all customers in the event request.