> For the complete documentation index, see [llms.txt](https://docs.chord.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chord.co/activate/event-streaming/destinations/email-and-marketing/insider.md). # Insider Insider One is a cross-channel marketing automation platform for personalizing user experiences and triggering journeys across web, mobile and messaging channels. Chord sends events to Insider One from the browser and from the server. ## What each version does * [**Insider Pixel**](/activate/event-streaming/destinations/email-and-marketing/insider/insider-pixel.md) loads the Insider One Web SDK (`ins.js`) in the shopper's browser and sends page views, ecommerce events and user profile updates from there. It captures richer client-side context, such as session data and browser fingerprinting. In Chord, you add it as **Insider Pixel**. * [**Insider One**](/activate/event-streaming/destinations/email-and-marketing/insider/insider-one.md) sends events to Insider One's server-side Upsert API from Chord's servers, so it is not affected by ad blockers or browser restrictions. In Chord, you add it as **Insider One**. ## Why use both The browser version catches on-page behavior and browser-native session context. The server version survives ad blockers and closed tabs, and captures events that occur outside the browser. Using both gives you the most coverage. ## Set up * [Insider Pixel](/activate/event-streaming/destinations/email-and-marketing/insider/insider-pixel.md) * [Insider One](/activate/event-streaming/destinations/email-and-marketing/insider/insider-one.md) --- # 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.chord.co/activate/event-streaming/destinations/email-and-marketing/insider.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.