Logs

Every action your customers and platform users take gets recorded here. You can track their activity over time across three areas: panel logs, website activity, and session events. 

Panel logs 

This tab shows you what your platform users have been doing. Think of it as a detailed activity journal that records every action taken by people who have access to your marketing platform.

These logs help you track down issues quickly. For example, if someone reports problems with email sending, you can check the logs to see exactly what happened and when.

We’ve organized the log data in a clear table format:

• Log ID – unique identifier for each log entry.
• Created – when the action happened.
• URL – which page or feature was involved.
• Method – how the information was retrieved (POST for adding data, GET for viewing data).
• Status – whether the action succeeded or failed (shown as a code)..
• User email – who performed the action.
• IP address – where the user was connecting from.
• Preview of details – additional context like processing time and user ID.

Log statuses 

Status codes tell you at a glance whether something worked or went wrong:

Website activity 

Here you can see what your customers are doing on your website. To collect this data, you’ll need to set up the Web Tracking channel first.

If you manage multiple websites, you can switch between them using the dropdown menu above the table.

The activity log shows:

• Log ID – unique identifier for each entry.
• Created – when the activity happened.
• Visitor ID – unique number we assign to each customer.
• Session ID – identifier for their browsing session.
• Event type – what they did:
  • VisitOnWebsite – visited any page on your site.
  • VisitOnProductPage – looked at a specific product.
  • VisitOnCartListPage – checked their shopping cart.
  • VisitOnLoginPage – went to the login page.
  • ModifyCart – added or removed items from their cart.
  • VisitOnSalePage – reached the purchase confirmation page.
• Visitor’s email – customer’s email address (if available).
• Active session – whether they’re still browsing.

Click the details button in the last column to see more information about any activity, like session duration, products viewed, or cart value.

Session events log

This tab focuses on key customer behaviors in your online store – things like abandoned carts, browsing patterns, and completed purchases. Like website activity logs, you’ll need Web Tracking configured to see this data.

Here’s what you’ll find:

• Log ID – unique identifier for each event.
• Created – when it happened.
• Visitor ID – customer’s unique identifier.
• Event type – what occurred:
  • AbandonedBrowse – customer stopped looking at products.
  • AbandonedCart – customer left items in their cart without buying.
  • FinalizedTransaction – customer completed a purchase.
• Visitor’s email – customer’s email address.

In the last column there is a button displaying detailed information about the recorded event.

API logs 

All API requests for your business unit are recorded here. This is particularly useful if you’re integrating our platform with other tools or systems.

The log includes:

• Log ID – unique identifier.
• Created – when the request was made.
• URL – what the request was about:
  • /customers – customer data requests.
  • /orders – order-related requests.
  • /scenariocustomevents – custom event requests for automation scenarios.
• Method – what type of action was requested:
  • POST – adding new data.
  • GET – retrieving existing data.
  • PUT – updating data.
  • DELETE – removing data.
• Status – server response code (explained in the next section).
• API key – your unique authorization key.
• IP address – where the request came from.
• Preview of details – additional information like full request ID and processing time.

API log statuses 

Log statuses are displayed in the form of codes indicating the success of a given action or an error: 

SMS logs 

When SMS messages fail to send, the details end up here. This helps you troubleshoot delivery issues:

• ID – log identifier.
• Created – when the error occurred.
• Gateway – which SMS provider was used.
• Sender – sender name configured for that gateway.
• Customer’s telephone number – the number that couldn’t receive the message.
• Error – specific error code and description explaining what went wrong.