> For the complete documentation index, see [llms.txt](https://help.littledata.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.littledata.io/sources/shopify-markets/markets-faq.md).

# Shopify Markets FAQ

Answers to common questions about how Littledata works with Shopify Markets.

Answers to common questions about Littledata's Markets module, how markets are synced from Shopify, and the special Unassigned markets market.

### Settings

<details>

<summary>What happens when the Markets module is enabled?</summary>

Littledata fetches all active Shopify markets and turns on per-market configuration for market-aware destinations (such as GA4 and Meta). Each active market gets its own settings for each destination. At the same time, Littledata creates a special internal market called **Unassigned markets**.

</details>

<details>

<summary>What happens when the Markets module is disabled?</summary>

Per-market settings stop being used. Each destination goes back to using its own destination-level settings. Littledata keeps your per-market settings stored, but doesn't apply them while Markets is off. This includes the settings for **Unassigned markets**.

</details>

<details>

<summary>What happens when Markets is re-enabled?</summary>

Destinations switch back to per-market configuration. Markets you had customized before get their previous per-market settings back. Markets that are new since you last used the module start with default settings.

</details>

<details>

<summary>Are per-market settings copied from my destination's settings?</summary>

Partly. A new market starts from the destination's current settings, but some options are reset to defaults. For example, all events are turned on, and order and product identifiers go back to their defaults. You can then change the settings for each market.

</details>

<details>

<summary>Can I change the market_handle?</summary>

Not in Littledata. Littledata always takes `market_handle` from Shopify. To change it, edit the market's handle in Shopify.

</details>

### How Markets work

<details>

<summary>Where does Littledata get market information from?</summary>

Littledata reads market data directly from Shopify using the Shopify Admin API and Shopify webhooks. Shopify remains the source of truth for which markets exist and whether each market is active, draft or deleted.

</details>

<details>

<summary>Does Littledata create or manage Shopify markets?</summary>

No. Littledata only reads market data from Shopify. It never creates, edits or deletes Shopify markets.

The one exception is **Unassigned markets**, a special market that exists only in Littledata. It doesn't appear in your Shopify markets list.

</details>

<details>

<summary>How are new markets handled?</summary>

When a new active market appears in Shopify, Littledata detects it automatically and sets it up with default settings for each destination. Draft markets are stored but not shown, because only active markets appear in Littledata.

</details>

<details>

<summary>What if the tracking script can't work out the market?</summary>

Events are sent with the **Unassigned markets** values instead. This prevents event loss during temporary failures. This is unlikely to happen.

</details>

<details>

<summary>Why does Littledata send both market_handle and market_id?</summary>

`market_handle` is human-readable and useful for reporting and filtering. `market_id` is the Shopify identifier and stays the same over time. They do different jobs, so Littledata sends them together.

</details>

### Unassigned markets

<details>

<summary>What is Unassigned markets?</summary>

**Unassigned markets** is an internal, Littledata-only market. It is used when a Shopify market can't be found for an event. It doesn't exist in Shopify. It appears under every market-aware destination and has its own settings, like any other market.

</details>

<details>

<summary>Why does Unassigned markets exist?</summary>

It prevents data loss when an event can't be linked to a market. It also gives you clear settings for events where the market is unknown.

</details>

<details>

<summary>When do events become unassigned?</summary>

Events become unassigned whenever Littledata can't find a Shopify market for them. Common examples are draft orders, POS orders, orders created in the Shopify admin, third-party channel orders (such as Amazon), imported data, tracking script failures, or cases where Shopify context is missing.

</details>

<details>

<summary>What happens to unassigned events?</summary>

They are sent to destinations using the **Unassigned markets** settings. They are not dropped, and they are not quietly given another market.

</details>

<details>

<summary>Does Unassigned markets follow the same lifecycle as other markets?</summary>

Yes. It is created when Markets is enabled and used again when Markets is re-enabled.

</details>

<details>

<summary>What values are used for Unassigned markets?</summary>

Littledata uses fixed values: `market_id = 0` and `market_handle = unassigned_market`.

</details>

<details>

<summary>Can unassigned events be turned off separately?</summary>

Yes. **Unassigned markets** has its own settings for each destination, so you can turn its events off for one destination without affecting other markets.

</details>

<details>

<summary>Can Unassigned markets be removed?</summary>

No. It is set by the system and is always there when Markets is enabled.

</details>

### Related articles

* [Setup and sync flow for Shopify Markets](https://help.littledata.io/sources/shopify-markets/setup-and-sync)
* [Markets settings](https://help.littledata.io/sources/shopify-markets/markets-settings)
* [How markets are detected](https://help.littledata.io/sources/shopify-markets/how-markets-are-detected)
* [Unassigned markets](https://help.littledata.io/sources/shopify-markets/unnasigned-markets)