Maqetin takes events from your code today, with connections to other tools planned.
Pick a kind of tool to see how its events reach Maqetin today and what is planned.
6 kinds
- Your own codeSend events with the JavaScript SDK or the REST API
- PaymentsPlannedSend payment events from your own code until the connection exists
- CommercePlannedSend cart and order events from your own code until the connection exists
- Product analyticsPlannedSend the same events to Maqetin with track() until the connection exists
- Data warehousesPlannedSend events in batches from your own code until the connection exists
- Support desksPlannedSend ticket events from your own code until the connection exists
Send the events yourself today.
- Payments
- Call track() with payment.failed when your server learns that a payment did not go through, and a journey can send the failed-payment email.
- Commerce
- Call track() with cart.updated as a cart changes and with order.placed when an order is placed.
- Product analytics
- Call track() with the same event names beside the calls you already make.
- Data warehouses
- Send 1 to 100 identify or track items in one batch request.
- Support desks
- Name the event yourself, as object.action in lower case, such as ticket.opened.
Every event name is on the events page of the docs.