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

# StackAdapt

StackAdapt integration helps connect your StackAdapt pixel with your website. We handle both browser pixel events and server-side conversion postbacks. You can also pass custom event arguments through stackAdaptArgs (or args) on your event payloads.

### Details

Channel name: stackAdapt

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

Browser pixel endpoint: <https://tags.srv.stackadapt.com/saq\\_pxl>

Server postback endpoint: <https://srv.stackadapt.com/postback/conv>

### Event Flow

Our StackAdapt integration supports both browser and server events:

Browser events: We send GET requests to the StackAdapt pixel endpoint using your pixel ID, user agent, page URL/title, IP, and a JSON args payload.

* action defaults to the event name
* revenue maps to value
* order\_ID maps to orderId

Server events: We capture ref\_id from the landing-page query string and send a server postback with:

* event = event name (snake\_case)
* postback\_id = captured ref\_id
* optional sa\_conv\_data\_revenue and sa\_conv\_data\_order\_id when value and orderId are present


---

# 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/stackadapt.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.
