Britixo CRMBritixo CRMEnterprise Help Centre
Ctrl K
Public endpoints and data flow

Understand event storage

Supported event payloads are recorded against the visitor session. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.

Audience: CRM administrators, authorised service and sales staff, privacy teams and website implementersPermission: Technical administratorModule v1.4.0
Jump to steps
Where to goPublic collection endpoint
Before you start
  • Verify the module is active and use the exact navigation shown above.
  • Use an account with the stated module and core CRM permissions.
  • Use known test records when changing statuses, visibility, saved filters or global navigation.

What you’ll accomplish

Supported event payloads are recorded against the visitor session. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.

Follow these steps

  1. Go to Public collection endpoint.
  2. Select the record or action required for understand event storage.
  3. Complete the displayed fields and choices described in this guide.
  4. Save, submit, approve or confirm the action as shown on screen.
  5. Refresh the relevant list, record or report and verify the expected result.

Fields and options to review

WorkspacePublic collection endpoint
ActionSupported event payloads are recorded against the visitor session.

Rules the system enforces

  • Only controls rendered by the supplied module are documented; hidden AJAX helpers are mapped to their visible parent workflow.
  • Core CRM record permissions and module permissions are both enforced where the code checks them.

How to confirm it worked

  • The understand event storage action completes without a validation or permission error.
  • The affected record, stock balance, response, session or style reflects the saved state.
  • Audit, notification, report or portal evidence appears only where the module code creates it.

Security, privacy and operational checks

  • Use a controlled test record before applying changes to live inventory, recipients, visitor tracking or global styling.
  • Grant only the minimum module and core CRM capabilities needed for the task.
Understand session creation and updateUnderstand page-view storagePublic endpoints and data flowBrowse all Visitor Intelligence & Live Engagement guidesLeads and pipelineCustomers and contactsCommunicationsData, privacy and securityEnterprise integrationsAdvanced Task Filters