> 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/channels/bing.md).

# Bing

Bing integration helps connect your Microsoft Advertising dataset with your website through browser pixel tracking. We manage browser event streaming for you, enabling seamless tracking of user interactions and conversions. The integration provides a straightforward setup with simple configuration options to get you started quickly.

### Details

Channel name: bing

NPM package: [@blotoutio/providers-bing-sdk](https://www.npmjs.com/package/@blotoutio/providers-bing-sdk)&#x20;

### Event Flow

Our Bing integration focuses exclusively on browser-side event tracking. When enabled, we automatically inject the Bing browser pixel and handle event transmission from the user's browser to Microsoft Advertising. This integration requires specific conversion events to be set up in your Microsoft Advertising account for proper tracking.

### Useful Links <a href="#useful-links" id="useful-links"></a>

{% embed url="<https://help.ads.microsoft.com/#apex/ads/en/56684/2-500>" %}

{% embed url="<https://help.ads.microsoft.com/#apex/ads/en/56689/2-500>" %}

{% embed url="<https://help.ads.microsoft.com/#apex/ads/en/60178/2-500>" %}

{% embed url="<https://help.ads.microsoft.com/#apex/ads/en/56775/2>" %}


---

# 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/channels/bing.md?ask=<question>&goal=<user_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.
