Google Analytics 4 (GA4)

The official GA4 node gives you a browser-friendly way to load the Google tag and send events without rebuilding the setup from scratch in every flow.

It is a good fit when:

• your site uses GA4 as a primary analytics destination
• you want a reusable way to install GA4 and send events
• you want event parameters to come from Fluxyn expressions and page state

When to Use It

Typical use cases include:

• ecommerce events such as add_to_cart and purchase
• lead generation or signup flows
• page and route tracking in single-page applications
• sending the same event to more than one measurement id

How to Configure

The node currently supports two main actions:

• Load & Start GA4 to load the Google tag and configure a measurement id
• Send Event to send an event and optional parameters

Recommended setup:

1. Add one Load & Start GA4 node in the part of the app where GA4 should initialize.
2. Set the measurement id, optional additional ids, and any config parameters you need.
3. send_page_view is enabled by default. Turn it off only when you want to opt out of the load-triggered page_view.
4. Use page_view_params when the load step should send a page_view event with event-scoped properties such as app_name.
5. Use the node's Send Event action downstream wherever you want to send a GA4 event, including manual page_view events.
6. Map event parameters from $., $eventData, or $input.

config_params remains config-scoped and is passed to gtag('config'). page_view_params is only for the page_view event sent by Load & Start GA4.

If page_view_params is provided and send_page_view is enabled, the node disables the automatic page_view and sends one explicit page_view event with those parameters so they do not leak into later GA4 events.

Flow Preview

Best Practices

• Initialize the tag once in a predictable place and avoid scattering load steps throughout unrelated flows.
• Keep event names and parameter naming consistent with your measurement plan.
• Use the debugger or GA4 DebugView when validating new events.
• If many flows share the same measurement id, store or standardize it in a way that avoids copy-paste mistakes.