Data and storage

Data model (md)

SDK internally exposes a structured model used by filters/macros:

• data: user properties set via setuserproperties / identify
• var: transient variables (setVar)
• event: last event name
• partner: retargeting/link partner data
• session: session data (e.g., visitor id)
• utm: utm_campaign, utm_source, utm_medium, utm_term, utm_content, utm_click, utm_ht, utm_at
• url, referrer: parsed URL parts + query
• cookie: parsed cookies

Access via macros, e.g. {{data.user_id}}, {{url.host}}.

Browser info (BW_INFO)

Collected at runtime and enriched when available (navigator.userAgentData). Useful fields:

• n (browser), v (version), t (device: mobile/desktop)
• https (1/0), z (timezone offset), ls (localStorage available)
• wv (webview), uab/uam/uap (UA brands/mobile/platform), uapv (platform version)
• ul (user language if set), pe (push enabled support flag)

Use in filters: {{window.BW_INFO.t}}, {{window.BW_INFO.ul}}.

Storage keys

Storage is namespaced under a JSON blob in _opc (local/session).

• Local:

  • user_data with { id, expiry } (1‑year expiry)
  • userConsent JSON
  • UTM keys
  • Modal limits: modal_<modalId>_views
  • Push: webpush_dismissals, push or psh<hash>

• Session:

  • userID as <timestamp>.<rand>.<count>

Privacy gate

Analytics payloads are sent only when consent (analytics) is true and browser allows storage.