Understand the public ping endpoint
Maintains active session state.
Exact navigationPublic endpoint → visitor_intelligence/visitor_collect/ping
Before you begin
- Confirm 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 this guide covers
Maintains active session state. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.
Exact step-by-step process
- Open Public endpoint → visitor_intelligence/visitor_collect/ping.
- Select the record or action required for understand the public ping endpoint.
- Complete the displayed fields and choices described in this guide.
- Save, submit, approve or confirm the action as shown on screen.
- Refresh the relevant list, record or report and verify the expected result.
Fields, choices and supported possibilities
WorkspacePublic endpoint → visitor_intelligence/visitor_collect/ping
ActionMaintains active session state.
Code-backed validations and workflow rules
- 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.
Expected result and verification
- The understand the public ping endpoint 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.