Skip to main content

Browser Source Commands

The browser source provides an enhanced elb function that supports browser-specific features like DOM interaction, elbLayer communication, and automatic initialization. These commands are processed by the browser source translation layer before being passed to the collector.

elb

The browser source provides an enhanced elb function that supports flexible argument patterns and browser-specific features.

Loading...

Usage options:

Loading...

config

Configure the browser source during initialization through startFlow. These settings control browser-specific behavior:

Loading...
note

Browser source configuration must be done during initialization. Settings like prefix and elbLayer cannot be changed after the source is created.

run

A run initializes the browser source and triggers automatic DOM scanning and event setup. It will:

  • Initialize DOM event listeners
  • Scan for data-elb attributes
  • Trigger a page view event by default
  • Process the elbLayer stack
Loading...

A run accepts a partial state parameter:

Loading...

init

Re-initializes event listeners on one or multiple target elements. Useful for dynamically loaded content like newly added products or wizard steps.

Loading...

This command is essential for Single Page Applications (SPAs) where content is added dynamically after the initial page load.

tip

Use walker init after adding new DOM elements with data-elb attributes to ensure they are tracked properly.

Integration with Collector

Browser source commands work in conjunction with collector commands. The browser source handles DOM-specific functionality while the collector manages destinations, consent, and user data.

Common workflow:

  1. Configure browser source in startFlow
  2. Browser source automatically initializes (or use walker run for manual control)
  3. Use walker init for dynamic content
💡 Need Professional Support?
Need professional support with your walkerOS implementation? Check out our services.