# 18th Nov: Audiohook Support, Introducing Configurator Rules, and more

### :sparkles:New and noteworthy

#### **Introducing: Audiohook Provider**

Say hello to the newest member of the family—**Audiohook**!\
Your audio campaigns just got a major uplift with first-class provider support.\
Plug it in, sync your events, and let your sonic marketing strategy evolve. 🔊✨

<figure><img src="/files/74xZyu5ceHbSvAy5FoAR" alt=""><figcaption></figcaption></figure>

#### **Introducing the Configurator Rules Engine**

We’ve unlocked a whole new level of intelligence in how your events behave! 🎉\
Now, every incoming event runs through a powerful rule-checking engine that can reshape payloads, create new events, skip unwanted triggers, and even selectively block providers — all before anything fires.\
Whether it’s browser-side or server-side, the system smartly decides where rules should execute, ensuring zero duplication and maximum efficiency.\
Think of it as giving your events a brain… and you’re the one programming it. 🧠⚡

<figure><img src="/files/W48cxc9COmPxfmoMIsUL" alt=""><figcaption></figcaption></figure>

#### **\[SDK]** Resolved issue where consent was not applied to events triggered prior to initialization.

We’ve updated the initialization flow so that all consent checks run *before* any tracking events. Now, events like `PageView` fire only after the default consent settings are applied. This ensures proper behavior in regions where consent is required and prevents events from triggering prematurely — leading to smoother tracking, cleaner data, and no unexpected behavior. 🎯

### :bug: Fixes

* \[WordPress] - Fixed `Cannot modify header information – headers already sent` warning in header processing.
* \[WordPress] - Resolved a Woo-commerce checkout crash caused by `merge()` mishandling shipping & billing address structures.

### :book: Details

Release day: 18th November 2025\
Release version: 25-41\
Edge version: 13.132.0\
SDK version: 1.36.0


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.edgetag.io/changelog/november-2025/18th-nov-audiohook-support-introducing-configurator-rules-and-more.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.