The following table provides an overview of all valid tags of an Inxmail Commerce event XML.
|
XML |
Description |
|
|---|---|---|
|
<event> |
|
|
|
|
<eventtype> |
Basic information on the type of event |
|
<id> |
Key for mapping incoming data to the correct <eventtype>, <phgroup>, <phlist> or <placeholder> |
|
|
<translation> |
<translation> elements must exist in all child nodes; they contain a translation of the respective field in a default language (language=“de“) and further optional languages. |
|
|
<customeremail> |
This XML tag describes which event data contains the customer’s email address. |
|
|
<customermapping> |
This XML tag describes which event data contains the customer number (optional). |
|
|
<phgroup> |
Event data group. Every event data group must have an <id> and a <translation>. |
|
|
<phlist> |
This XML tag contains a list of placeholders that can be used as a list element, for example, the ordered articles to be displayed in a table in the email. Every list of placeholders must have an <id> and a <translation>. |
|
|
<placeholder> |
Element for the definition of the incoming event data. Every <placeholder> must have an <id>, a <translation> and a <datatype>. |
|
|
<datatype> |
The following generic data types are permissible for the placeholder fields, and are specified as a value in the <datatype> element:
|
|
