> 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/crm-connections/shopify.md).

# Shopify

A CRM connection is crucial for maintaining the quality and delivery of signals. It serves two main purposes:\
\
1\. **Customer Activity Tracking**: We analyze past orders to determine whether a customer is a first-time buyer or a repeat customer.\
&#x20;  \
2\. **Backup Mechanism**: In case of a failure in the browser, we can directly retrieve purchase data from Shopify, allowing us to link attribution to EdgeTag data effectively.

{% hint style="warning" %}
For the NC/RC feature to work, this step is necessary.
{% endhint %}

### How does it work?

We check for  orders every 15 minutes. When you first add a channel, we will review the last 15 minutes for any orders. After the first successful synchronization, we will store the timestamp of the last synced order in the database. \
\
During subsequent checks, we will look for orders between the timestamp of the last synced order and the current time. If there are any new orders, we will update the database with the timestamp of the latest synced order. \
\
This process will be repeated every 15 minutes to ensure that no orders are missed.


---

# 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.edgetag.io/crm-connections/shopify.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.
