# 16th July: Backup Meta token, Consent categories, Event Filtering, and more

### :sparkles:New and noteworthy <a href="#new-and-noteworthy" id="new-and-noteworthy"></a>

#### Backup Meta token

Lately, we have noticed that many customers are receiving Meta authorization errors. This usually occurs when the user who authenticated the Meta channel changes their password, logs in on an unknown device, or accesses the account from a different country. As a result, there may be a disruption in server events being sent to Meta until the user authenticates again in our app. To solve this, we added a backup Meta token, which is used when authentication fails.  You can follow our guide on how to generate a backup token.

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

#### Consent categories

Before this release, we relied on the developer to define consent based on channels, and they could optionally provide categories as well, though we didn't utilize it. With this release, we have introduced an option that allows you to focus solely on categories, eliminating the need to set channel configurations. We will handle the heavy lifting for you. Once you define your categories, when a new channel is added, we will automatically manage consent for that channel on your behalf.

**The old way of defining consent:**

{% code title="Defining channels and categories" %}

```javascript
edgetag(
  'consent', 
  { all: false, facebook: true, "googleAnaltyics4": false }, 
  { marketing: true, analytics: false }
)
```

{% endcode %}

{% code title="Defining only channels" %}

```javascript
edgetag(
  'consent', 
  { all: false, facebook: true, "googleAnaltyics4": false }
)
```

{% endcode %}

New possibility:

{% code title="Defining only categories" %}

```javascript
edgetag(
  'consent', 
  null, 
  { marketing: true, analytics: false }
)
```

{% endcode %}

#### Event Filter plugin

One key aspect of zero-code solutions is that they empower users to modify data flows without needing to write any code. In some instances, you may want to skip certain events that are automatically generated by our system or the apps you've added. Now, you can! You can specify which events to allow and which ones to skip. Let’s see how it works in action.

{% embed url="<https://www.loom.com/share/76b37995a6a84462b90fbe5f54369cdb?sid=47f8d760-b963-49fe-a8ca-107950bf19e1>" %}

#### StackAdapt

We have added support for [StackAdapt](https://www.stackadapt.com/) in response to customer requests. This feature enables you to send events to the StackAdapt platform server-side when we detect the referrer link used.

### :zap:Improvements

\[Shopify] - Allow installation when the domain is not set up\
\[Channel] - Capture TradeDesk click ID more reliably

### :bug: Fixes

\[Plugin] - Do not show already used events for Custom event names\
\[Channel] - The NC/RC flag is not determined correctly in some cases\
\[Channel] - Deleting the Emotive app doesn't remove it from the cloud correctly

### :book: Details

Release day: 16th July 2025\
Release version: 25-25\
Edge version: 13.115.0\
SDK version: 1.21.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/july-2025/16th-july-backup-meta-token-consent-categories-event-filtering-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.