Sending Orders via the API Resource Generate event

Order data is transmitted to our system via the Add orders resource that has the following limitations:

• Fixed fields that are determined by the specification;
• Impossible to add custom fields;
• Order parameters cannot be used to build segments.

You can overcome them with the resource Generate event that can be used to replace or complement Add orders. By using it, you’ll be able to:

• Transmit more data with additional fields;
• Use segmentation by events and their parameters, for example, sort out contacts who bought a particular item within a week;
• Expand/receive RFM segmentation by order without additional usage of Add orders.

Important To save orders in the system, you need to set up segmentation by events as the event contains a contact identifier. It can be determined based on the default or conditional parameters.

How to Use Generate event to Send Orders

For example, you can set up identification by unique token. The order will not be saved until these parameters are transmitted to the system. If you don’t set your own parameters, the system will search the identifier based on default parameters (email, phone, etc.).

You can send Generate event only for the existing contact. To send the order for a new contact, first import this contact into the system via:

• Add/update a contact;
• Add orders.

To send an order, you need to specify the event type. Choose the type from the below table based on the order status.

orderCreated

To create an order, name the parameters as indicated in the documentation and fill in the required parameters. If any of the required parameters isn’t filled, the event is ignored and the order will not be sent.

• ${eventKey} - event unique key transferred in externalOrderId. Used as an order identifier;
• ${orderId} - event ID in our system. Required to assign the event to a workflow.

The contact ID must be one of the following:

• ${externalCustomerId} - external contact ID;
• ${email} - contact’s email address;
• ${phone} - contact’s phone number.

To substitute parameter values in messages, send the fields with event parameters as an array.

• Required parameters for the order array: externalOrderId, totalCost, status, date, externalCustomerId / email / phone.
• Required parameters for the items array: externalItemId, name, quantity, cost, url, imageUrl.

Example:

{
	"eventTypeKey": "orderCreated",
	"keyValue": "380501234567",
	"params": [{
		"name": "phone",
		"value": "380501234567"
	}, {
		"name": "externalOrderId",
		"value": "12345679"
	}, {
		"name": "externalCustomerId",
		"value": "AV13760"
	}, {
		"name": "totalCost",
		"value": "258.0"
	}, {
		"name": "status",
		"value": "INITIALIZED"
	}, {
		"name": "date",
		"value": "2020-05-14T10:11:00"
	}, {
		"name": "currency",
		"value": "UAH"
	}, {
		"name": "items",
		"value": [{
			"externalItemId": "200600",
			"name": "Super Device",
			"category": "devices",
			"quantity": 1,
			"cost": 990,
			"url": "http://example.com/item/200600",
			"imageUrl": "http://example.com/item/200600/image.png",
			"description": "High quality"
		}]
	}]
}

orderUpdated

• Updates the order that has the parameter externalOrderId filled.
• If the transmitted order doesn’t exist in the system, it’s created anyway.
• The parameters must be named as indicated in the documentation. If the order is to be created, the orderCreated requirements apply.

orderDelivered

• Changes the order status to DELIVERED.
• If the order does not exist, it is ignored.

orderCancelled

• Changes the order status to CANCELLED.
• If the order does not exist, it is ignored.