# 4th Sep: Bloomreach, LiveIntent, Webhook validation and more

### :sparkles:New and noteworthy

#### Added support for Bloomreach

Bloomreach is an AI-powered e-commerce platform unifying customer & product data for personalized shopping. Combines marketing automation, search & content management to help retailers boost conversions, revenue & loyalty through real-time personalization across email, web & mobile. Used by 850+ brands globally. We implemented their server-side APIs to leverage our powered data and achieve even better results.

#### Migrate LiveIntent to the new CAPI endpoint

LiveIntent has introduced a more powerful, descriptive API. This enables our data stream to excel and deliver better results. We analyzed the new API and now send higher-quality data to LiveIntent. To start using the new API, go to our app and add an access token and a pixel ID, as shown in our [onboarding guide](/channels/liveintent/onboarding.md).

#### Add header validations to Webhooks

We understand that protecting your data is essential. This means we need to ensure that we only accept data that genuinely comes from you, rather than from malicious actors attempting to disrupt your attribution models. To address this, we have added header validation to Webhooks. \
\
Now, when you access the Webhook editor, you'll see a checkbox labeled "Require authorization header." If you enable this option, we will provide you with an access token that will secure your Webhook. You will need to include this token in the Authorization Bearer header when sending events to the webhook.

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

### :zap:Improvements

\[Channel] - Allow custom keys in the Validation channel

\[Channel] - Add custom data for Blotout Cloud

\[Shopify] - Add period checks for consent changes

\[Channel] - Allow phone-only contacts for Omnisend

\[Plugin] - Do not remove all utm parameters for HIPAA

### :book: Details

Release day: 4th September 2025\
Release version: 25-32\
Edge version: 13.122.0\
SDK version: 1.28.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/september-2025/4th-sep-bloomreach-liveintent-webhook-validation-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.