> For the complete documentation index, see [llms.txt](https://docs.edgetag.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.edgetag.io/changelog/january-2026/14th-jan-outbrain-provider-gcp-v2-provider-updated-meta-integration-to-permanent-token-and-more.md).

# 14th Jan: Outbrain Provider, GCP v2 Provider, Updated Meta Integration to permanent token and more

### :sparkles:New and noteworthy

#### **Introducing: Outbrain Provider**

Say hello to the newest member of the family— **Outbrain**!\
Added server-side support for Outbrain, allowing conversion events to be sent directly from the server instead of relying solely on the browser. This means more reliable tracking, especially in environments where browser tracking is restricted. As a result, you get more consistent and dependable campaign measurement.

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

### :zap:Improvements

* \[Channel] - Meta channel integrations now use manually generated long-lived access tokens for setup instead of OAuth-based authorization flows, resulting in a simpler and more stable integration process.
* \[Channel] - Updated the GCP provider payload to v2 to better support modern Google Cloud setups.
* \[Channel] - Audiohook tracking has been updated to use the recommended GET-based pixel, ensuring correct visitor data (including IP address) is captured.

### :bug: Fixes

* \[Channel] - Google Ads now accepts conversions without click IDs when user-provided data is available, improving conversion coverage and measurement accuracy.

### :book: Details

Release day: 14th January 2026\
Release version: 26-01\
Edge version: 13.137.0\
SDK version: 1.39.0


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.edgetag.io/changelog/january-2026/14th-jan-outbrain-provider-gcp-v2-provider-updated-meta-integration-to-permanent-token-and-more.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.