Overview

Connect identifies customers using email addresses or the alternate customer id field. This section provides examples of each approach and discusses how Connect handles redundant records.

The scenarios in this section use the following static content.

<html> 
    <body> 
    Dear <%[First Name]|,member]%>,<br/>
    Your order for product has been accepted
    and the product will be delivered in two weeks time.<br> 
    Thanks,<br>
    Administrator 
    </body> 
</html> 

XML

A typical XML message is shown below. The event-triggered campaign in this section does not use an ExternalXML element.

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

<kanaRoot>

<EventRequest CompanyName="default" CampaignName="ETCamp5">

<Customer KeyField="EmailAddress" EmailAddress="[email protected]">

</Customer>

</EventRequest>

</kanaRoot>

Note: The CampaignName attribute is declared in the EventRequest tag. There is no Event tag in the XML.

Result

The email content to John will look like:

From: Administrator [kc.162.104.154@kc.kana.com]
To: [email protected]
CC:
Subject: Receipt for Order
Dear John,
Your order for product has been accepted and the product will be delivered in two weeks time.
Thanks, Administrator