| title | layout |
|---|---|
|
Push Endpoint Content section
|
xmldelivery
|
Push Endpoint Content section
The Push Message Content section contains the content to be send to every endpoint used in the delivery.
The content should be a string json formatted and should compatible with the destination platform.
In order to allow maximum flexibility, any control is performed about validity of the content if not that is valid json string.
If the Push Endpoint section children are used, they are:
- Positioned within the
<message>section of the XML instructions file - Positioned after the section of the XML instructions file
The Push section includes the following children:
| Child | Type | Description | Use |
|---|---|---|---|
| apn | element | Content to send to apple devices that uses Apple servers | Mandatory if some recipients have APN endpoint |
| gcm | element | Content to send to google and apple devices that uses the Google Cloud Message servers. | Mandatory if some recipients have GCM endpoint |
It is best practice to wrap the json string with a CDATA section in order to avoid XML syntax problem
See Push delivery working example for more about creating an XML instructions file for a Push delivery.
Next page:
Related Pages:
- Push message section
- Common sections and elements
- Newsletter
- Recipients section
- Delivery section
- Message section
- Building a campaign with XMLDelivery
Also see:
- Filtering and added recipients
- Contactlab section
- Using XMLDelivery
- Does XMLDelivery match your needs?
- Setting up XMLDelivery
- Working examples
Other links: