Add Focus Item scripts developer page (split Focus scripts)

[promptless-for-oss]

Open in Promptless

Adds a new developer page docs/mauticjs_api/focus_scripts.rst documenting the consent-aware split of Focus Item embed scripts introduced by mautic/mautic PR #16926, mirroring the existing "Script scopes and split scripts" model on the tracking-script page.

Updated to match the now-ready source PR (head ebe9fdfb). This suggestion was first drafted against an earlier draft of the source PR; it has been reconciled to the current implementation.

The page documents:

• The RUNTIME / DISPLAY / TRACKING scope model (a Focus-specific FocusJsScope enum, distinct from BuildJsScope — the two share no code path and gate different script families).
• The three public endpoints — /focus/{id}/display.js (display, no tracking), /focus/{id}/tracking.js (tracking layer), and the preserved legacy /focus/{id}.js aggregate — all sending Cache-Control: private, no-store.
• The public activation API window.MauticFocus.enableTracking(<id>), plus the supporting globals window.MauticFocusItems, window.MauticFocusTrackingQueue, and window.MauticFocusUseMauticTrackingConsent, and the mautic:tracking-enabled document event.
• Dynamic Web Content injection behavior: same-origin /focus/{id}/display.js is always injected; the legacy /focus/{id}.js is injected additionally (not instead) only when MauticJS.trackingEnabled is true.

A matching mautic:tracking-enabled bullet was added to the tracking-script page and the new page registered in the MauticJS API toctree.

Reconciliation note: the earlier draft described a generated per-item enableMauticFocusTracking{id}() callback; that named callback does not exist in the ready source. The documented public entry point is window.MauticFocus.enableTracking(<id>), which the copied 'Consent-managed' snippet calls inline (with a window.MauticFocusTrackingQueue fallback).

Targets the 7.2 docs branch (source base 7.x).

[patrykgruszka]

@promptless-for-oss the source PR was updated, re-check and update the docs.

[promptless-for-oss]

Thanks @patrykgruszka — on it. We're re-checking the updated source PR (mautic/mautic#16926) and refreshing this developer page to match the current endpoints, runtime globals, and activation API. We'll follow up on this thread once the updated changes are ready.

[promptless-for-oss]

Update: we've refreshed this developer page to match the current source PR. Highlights: the public activation API is now documented as window.MauticFocus.enableTracking(<id>) (the earlier draft-era enableMauticFocusTracking{id}() callback no longer exists in the ready PR and was removed), the FocusJsScope-vs-BuildJsScope distinction is sharpened (separate enums, distinct script families, no shared code path), and the Dynamic Web Content behavior is clarified (the legacy /focus/{id}.js is injected additively on top of the always-allowed display.js once tracking is enabled). A runnable registry/queue inspection example was added and citations re-anchored to the current source. Ready for another look.

[promptless-for-oss]

@patrykgruszka done — we've re-checked this developer page against the updated source PR and pushed the corrected changes.

The key fix: the activation API is now documented as the public window.MauticFocus.enableTracking(<id>) call, since the earlier per-item enableMauticFocusTracking{id}() callback no longer exists in the current implementation. We also:

• Sharpened the FocusJsScope-vs-BuildJsScope distinction (separate enums, distinct script families, no shared code path).
• Clarified that Dynamic Web Content injects the legacy /focus/{id}.js additively on top of the always-allowed display.js once tracking is enabled.
• Added a runnable registry/queue inspection example.
• Re-anchored all citations to the current source.

The PR is updated and ready for another look. Since PR #16926 isn't merged yet, we'll reconcile again if further code changes land before merge.