# 06th Jan: Vibe.co Provider, Updated Meta Graph API, CAPI and more

### :sparkles:New and noteworthy

#### **Introducing: Vibe.co Provider**

Say hello to the newest member of the family—**Vibe**!\
Added support for tracking via browser-side implementation, enabling event tracking using the Vibe Pixel as per official documentation.

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

### :zap:Improvements

* \[Channel] - Upgraded Facebook Graph API to version 24 to ensure compatibility with the latest platform updates and API standards.
* \[Channel] - Improved Facebook Conversions API implementation by adding missing `user_data` parameters, ensuring more complete and accurate payloads aligned with Facebook’s latest documentation.

### :bug: Fixes

* \[App] - Fixed an issue where activity log data in the Configurator was not displaying correctly.
* \[App] - Resolved an issue where RC Purchases were still being tracked despite rules configured to skip them.

### :book: Details

Release day: 06th January 2026\
Release version: 25-45\
Edge version: 13.136.0\
SDK version: 1.38.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/january-2026/06th-jan-vibe.co-provider-updated-meta-graph-api-capi-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.