> 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/february-2026/05th-feb-meta-oauth-migration-to-permanent-access-tokens-stackadapt-pixel-support-and-more.md).
# 05th Feb: Meta OAuth Migration to Permanent Access Tokens, StackAdapt Pixel Support and more
### :sparkles:New and noteworthy
#### **Meta Authentication Migration to Permanent Access Tokens**
We’ve improved the transition from Meta OAuth to permanent access tokens by updating all guidance and recovery flows. Authentication emails now clearly explain how to fix issues using Pixel Access Tokens instead of legacy OAuth steps. We’ve also introduced a dedicated migration page that makes it easy for existing customers to add and manage their Pixel Access Tokens in one place, ensuring a smooth and reliable upgrade.
#### Improved InitiateCheckout Tracking for Shopify Express Checkout
We’ve added a more reliable way to trigger the InitiateCheckout event for Shopify Express Checkout flows, including Shop.app redirects. Instead of relying only on browser pixel behavior, the system now detects checkout actions directly and fires the event instantly using cached cart data. This ensures checkout intent is captured even when customers are redirected offsite, without duplicate events being fired.
#### StackAdapt Pixel – Browser-Side Support
We’ve added browser-side support for the StackAdapt Pixel using a fetch-based implementation. This enables StackAdapt Pixel events to be triggered directly from the client and supports view-through conversion tracking based on IP, in line with StackAdapts Pixel API behavior.
What’s new
* Browser-side firing of StackAdapt Pixel events via `fetch`
* Support for view-through conversions using IP-based attribution
* Continued support for conversion tracking, engagement, and audience building
Impact
* Complements the existing server-side integration.
* Event tracking continues to function as expected.
### :zap:Improvements
* \[Channel] - The `init` response now includes the visitor IP address to support integrations like StackAdapt Pixel.
### :bug: Fixes
* \[App] Authentication error emails will now be also delivered to Blotout Slack channels, ensuring faster visibility and response even when email verification is not present.
### :book: Details
Release day: 05th February 2026\
Release version: 26-03\
Edge version: 13.139.0\
SDK version: 1.41.1
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.edgetag.io/changelog/february-2026/05th-feb-meta-oauth-migration-to-permanent-access-tokens-stackadapt-pixel-support-and-more.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.