<test_recipient> element is where you add up to 30 test recipients directly to the XML file, if you have decided to use this option.
<test_recipient> element is:
A child of the Test_recipients section
You can use
<test_recipient>or a CSV_file to add new recipients.
Positioned within the
<test_recipients>section of the XML instructions file
Use the following format to add test recipients directly to the XML:
<test_recipients> <test_recipient> <field1>field1 content</field1> <field2>field2 content</field2> </test_recipient> <test_recipient> ... </test_recipient> </test_recipients>
<test_recipient> element for each recipient.
While only one field is required to identify an email or SMS test recipient, three fields are needed to define a test recipient of a Push campaign. See the Example: below and Push delivery working example for more details.
<field> tags in the above example represent the actual field names, which must be selected from and match those used in the database. However, field name matching is not case sensitive, for example, you can use Name or name.
<test_recipient> <email>field1A</email> <firstname>field2A</firstname> ... </test_recipient>
<test_recipient> <phone>field1A</phone> </test_recipient>
<test_recipient> <PUSH>Device_ID_Token</PUSH> <PUSH_ENDPOINT>Endpoint_Type</PUSH_ENDPOINT> <CLAB_15_NAME>Application_Identifier<CLAB_15_NAME> </test_recipient>
See Filtering and added recipients for more about how the user database is filtered to match new recipients.
- Common sections and elements
- Recipients section
- Delivery section
- Notes section
- Message section
- Building a campaign with XMLDelivery
- Filtering and added recipients
- Contactlab section
- Using XMLDelivery
- Does XMLDelivery match your needs?
- Setting up XMLDelivery
- Working examples