Actions¶

Actions define what happens when a rule matches. They are the executable component of Dxtra Tag Manager's rule engine.

How Actions Work¶

When a rule's event fires and its conditions pass, the rule's actions execute sequentially within their action group. Each action performs a specific task -- firing a pixel, loading a script, tracking an event, or injecting content.

Rule Matches → Action Group Selected → Actions Execute (in order)

Actions run serially within a group. Earlier actions can set up data that later actions depend on.

Built-in Action Types¶

Dxtra Tag Manager provides 11 built-in action types:

Configuring Actions¶

Actions are created within rule configurations in the Tag Manager dashboard.

Creating an Action¶

1. Open a rule in the Tag Manager dashboard
2. In the Actions section, click Add Action
3. Select the action type from the dropdown
4. Configure the action parameters
5. Set the execution order within the action group

Action Parameters¶

Each action type has its own configuration fields. Common parameters include:

Track Event¶

Sends an event to Dxtra's built-in analytics (ClickHouse backend):

Inject Script / Load JS Direct¶

Executes custom JavaScript code. Use this for custom logic or third-party integrations:

Fire Pixel¶

Sends an HTTP request to a tracking pixel URL:

Load HTML¶

Injects HTML content into the page, useful for embedding widgets or banners:

Set / Increment App State Variable¶

Manages application state that persists across rule evaluations:

Using Variables in Actions¶

Actions can reference dynamic values using the {{variable}} syntax:

{{Page URL}}           - Current page URL
{{Page Title}}         - Current page title
{{Referrer}}           - Referring URL
{{Environment.NAME}}   - Environment variable
{{CMP.analytics}}      - Consent status

Variables are resolved at execution time, so they reflect the current state when the action runs.

Action Execution Order¶

Actions within a group execute in the order defined by their position. This matters when:

• An earlier action sets a state variable that a later action reads
• You need scripts loaded before configuration code runs
• A consent check must happen before firing tracking pixels

Error Handling¶

If an action fails (e.g., a script throws an error or a pixel URL is unreachable), the Tag Manager logs the error. Other actions in the group continue executing unless the failure is critical.

Use the debug overlay (#dxtra-debug) to monitor action execution and identify failures in real time.

Best Practices¶

• Name actions clearly so their purpose is obvious in the dashboard
• Order actions logically -- load scripts before running code that depends on them
• Use Track Event for Dxtra analytics rather than custom JavaScript
• Check consent in rule conditions before firing third-party tracking actions
• Test in development using the debug overlay before publishing to production
• Keep custom scripts minimal -- complex logic is harder to debug and maintain

Continue to Action Groups to learn how actions are organized and executed together.