> 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/mcp/skills/edgetag.md). # EdgeTag The EdgeTag skill is the comprehensive implementation skill covering everything you need to build, configure, and debug your EdgeTag setup. ### What it covers * **JavaScript SDK** - Initialization, event tracking, user identification, consent management, and configuration for both browser and headless implementations * **Platform deployments** - Step-by-step guidance for Shopify, WooCommerce, WordPress, Wix, React, Next.js, and more * **Channel integrations** - Setting up and configuring 50+ channels including Meta CAPI, Google Ads, TikTok, Klaviyo, and others * **HTTP API** - Server-side event tracking via the EdgeTag REST API * **Identity graph** - Cross-domain identity stitching, user data management, and cookie handling * **Webhook ingestion** - Receiving events from external systems like Shopify, Salesforce, and HubSpot * **Audience uploads** - Building and uploading audiences to ad platforms * **Debugging** - Common issues, error interpretation, and troubleshooting workflows ### When it triggers The skill activates automatically when you mention: * EdgeTag, Blotout, or `@blotoutio` * Server-side tagging or first-party data infrastructure * CAPI, conversion API, or event match quality * Identity stitching, `tag_user_id`, or `et_uid` * EdgeTag SDK, `edgetag-sdk-js` * Any EdgeTag implementation or configuration task ### Example prompts * "How do I install EdgeTag on my Shopify store?" * "Add a Purchase event with order value to my checkout page" * "Set up the Meta CAPI channel for my domain" * "Debug why my events aren't reaching Klaviyo" * "Implement cross-domain tracking between my main site and checkout" --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.edgetag.io/mcp/skills/edgetag.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.