> For the complete documentation index, see [llms.txt](https://docs.bloomanalytics.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bloomanalytics.io/~/revisions/XMbKSjK2DLqHwsienmXB/data-synchronization.md).

# Data Synchronization

Bloom's automated data sync process makes it easy for Bloom and Shopify to share important data, helping merchants get accurate reports and insights. Here's what happens when Bloom connects with Shopify:

#### :point\_right: **Initiation**&#x20;

As soon as Bloom is installed, it starts pulling the required information from the Shopify store's records.

#### :point\_right: **Data Fetch**

Bloom gathers details like orders, products, customers, transactions, and payouts from the Shopify store. This step is crucial for creating detailed reports.

#### :point\_right: **Frequency**

Right after setup, Bloom gets data from the last seven days to start off the reporting. The historical data is then collected in monthly batches.

#### :point\_right: **Automated and Manual Sync**

To keep information current, Bloom automatically updates data every 24 hours. Store owners can also choose to update data manually anytime via the app settings.

### :arrow\_down: Data Points Synced

Bloom collects the following vital information for accurate reporting and insights.

* **Orders**
* **Products**
* **Customers**
* **Transactions**
* **Payouts**

### :rotating\_light: **Protocols and APIs**

Bloom uses Shopify's APIs for a smooth and secure data exchange, adhering to Shopify’s rules for app integration.

### :arrows\_clockwise: **Factors Affecting Sync Time**

Your sync times are impacted by:

* **Data Volume:** Larger data volumes take longer to sync
* **API Call Limit:** Your chosen Shopify plan determines how frequently and quickly data is synced

### :mountain: **Handling Large Data Sets**

Bloom is programmed to prioritize critical data points of a Shopify store and process them in parallel. This technique saves valuable time when handling large data volumes, improving sync efficiency and accuracy.&#x20;

### :wrench: **Troubleshooting Sync Issues**

To fix these issues, check the app for error messages and follow the troubleshooting procedure provided, or [contact](mailto:support@bloomanalytics.io) Bloom's support team.

### :closed\_lock\_with\_key: Data Security and Integrity

Bloom takes the following steps to ensure data security, privacy, and integrity during sync:

* Encrypting data transfers using latest industry-standard protocols
* Using secure methods to check user identity
* Conducting meticulous data validation for consistency and accuracy

### :calling: **Integrated App Data Sync**

Bloom syncs with third-party integrated apps like it does with Shopify, offering the same efficiency, accuracy, and data protection features. By concurrently synchronizing with these platforms, Bloom always maintains data consistency and compatibility. Merchants can look forward to actionable insights about their ad platforms, shipping platform, etc. derived from accurate, timely data.

<br>


---

# 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.bloomanalytics.io/~/revisions/XMbKSjK2DLqHwsienmXB/data-synchronization.md?ask=<question>&goal=<endgoal>
```

`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.
