Working with events

An event is a signal about something a customer did. It comes from your website, app, or another system. Examples: a site visit, adding a product to the cart, an abandoned cart, or opening an email or a messenger message.

The Events section is available on the Expert plan and above. One cabinet can have at most 10 events.

Accepted events appear on the customer card. Use that history to confirm the signal reached the right person. A segment collects the group, and a trigger runs the action.

Create an event

1. Open Events and click Create event.
2. Enter a key. This is the event name for the API, for example cart_abandoned.
3. Add a comment if you want the cabinet to show what the event means.
4. Save the event.

The key must be unique in the cabinet, start with a Latin letter, and contain only Latin letters, digits, and _. Spaces are not allowed. After the event is created, the key cannot be changed. The comment can be edited later.

Send an event

An event is accepted only after its key exists in the cabinet. Send a POST request to https://core.passquare.com/api/v2/crm/event/send.

The request body includes:

• app_key — the private key from Settings → API;
• exactly one customer identifier: phone, card, or remoteId;
• event — the event key;
• value — an optional string of up to 100 characters, such as a step or a product name.

{
  "app_key": "private key",
  "phone": "+420000000001",
  "event": "cart_abandoned",
  "value": "checkout"
}

Instead of a phone number, you can send the card number in card or the CRM customer id in remoteId. Send only one identifier in a request.

You can test an event without your own integration. In the event list, open the test, enter a phone number, card number, or remoteId, and a value if you need one. A successful send is added to the customer history.

Requests follow the cabinet API limits. You can see them in Settings → API.

Where to see the result

Open the customer card and the event history tab. The table shows the key, value, source, and date. Events sent from the cabinet and events sent through the API appear in the same history.