> 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/ometria/use-case-how-to.md).
# Use Case how-to
In order to ingest Contacts from your Ometria 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 **Ometria** tile as your data connection
3. Using the table, find the **Static or Dynamic Segment** you want to use and click the **connect** icon
4. 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 Ometria Contact fields.
5. 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 Static Segment and create a submission, Dynamic 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 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://userguide.zappost.com/zap-integrations/zap-post-integrations/ometria/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 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.