> For the complete documentation index, see [llms.txt](https://doc.batch.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.batch.com/integrations/marketing-platforms.md).

# Marketing Platforms

- [How to integrate Batch on Shopify for web tracking](https://doc.batch.com/integrations/marketing-platforms/how-to-integrate-batch-on-shopify-for-web-tracking.md): This guide explains how to integrate the Batch Web SDK on a Shopify storefront to collect profile data and behavioral events without enabling Web Push.
- [What can you do with our SFMC (Salesforce Marketing Cloud) connector?](https://doc.batch.com/integrations/marketing-platforms/what-can-you-do-with-our-sfmc-salesforce-marketing-cloud-connector.md): With our brand new connector, you can run complex push automation scenarios from the famous Salesforce Journey Builder.
- [How to connect Batch to Voucherify?](https://doc.batch.com/integrations/marketing-platforms/how-to-connect-batch-to-voucherify.md): Include voucher codes from Voucherify in Batch communications
- [How to connect Batch to Poool?](https://doc.batch.com/integrations/marketing-platforms/how-to-connect-batch-to-poool.md): This guide explains how to connect Batch with Poool to track paywall interactions — such as page views, logins, and subscription clicks — directly in Batch.
- [How to connect Batch to Refiner?](https://doc.batch.com/integrations/marketing-platforms/how-to-connect-batch-to-refiner.md): Sync Refiner survey responses and events to Batch Profiles, and send Refiner Email Surveys from your Batch campaigns and automations.


---

# 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://doc.batch.com/integrations/marketing-platforms.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.