Customer work, connected.

Help & supportMyAccount
Tracking snippet, identities and events

Use explicit granted consent

Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.

Follow this guide to set data-consent="granted" only where the site’s consent process authorises collection.

Audience: CRM administrators, authorised service and sales staff, privacy teams and website implementersPermission: Visitor Intelligence: Manage SettingsModule v1.4.0
Jump to steps
Where to goAdmin Area → Visitor Intelligence → Tracking Snippet
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 this guide helps you do

Set data-consent="granted" only where the site’s consent process authorises collection. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.

Follow these steps

  1. Go to Admin Area → Visitor Intelligence → Tracking Snippet.
  2. Select the record or action required for use explicit granted consent.
  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

WorkspaceAdmin Area → Visitor Intelligence → Tracking Snippet
ActionSet data-consent="granted" only where the site’s consent process authorises collection.

Rules and limits

  • 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.

Check it worked

  • The use explicit granted consent 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.

Search the platform, integrations and practical Help Centre guides.

Press Esc to close.Browse every page