> For the complete documentation index, see [llms.txt](https://userguide.zappost.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://userguide.zappost.com/zap-integrations/zap-post-integrations/shopify-1/use-case-how-to.md).
# Use Case how-to
In order to ingest Contacts from your Shopify Customer Segments, you need to ensure you have a campaign created and a design published, see our [ZAP\~POST User Guide](https://userguide.zappost.com/) for a detailed walk through.
1. From the Campaign Management screen, click the data upload option and then select **New Data Connection**
2. Select the **Shopify** tile as your data connection
3. Using the table, find the **Customer Segment** you want to use and click the **connect** icon
4. Select if you only want a single ingestion or if you'd like ZAP-POST to query on a regular basis for any new contacts added to the segment
5. Confirm your field mapping, on the left you'll see the ZAP-POST campaign fields, using the drop down you can map them to your Shopify metafields configured in your store.
6. Once confirmed, you'll see a confirmation that the Segment has been connected
{% hint style="info" %}
Note
ZAP-POST will immediately ingest all records once for a one-off Segment and create a submission, Regular Segments are ingested at 9pm every day, this can be changed in the integrations settings.
{% endhint %}
---
# 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://userguide.zappost.com/zap-integrations/zap-post-integrations/shopify-1/use-case-how-to.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.
