Overview

Follow this guide to learn how to Sync Shopify Locations with Meta Location Manager. Before you can continue, ensure that your Point-of-Sale (POS) orders are being sent to Meta. Follow this guide to learn how to send POS Orders to Meta.

Understanding Store Location Syncing:

Syncing your Shopify locations with meta Location manager step connects your in-store data from Shopify to the corresponding business locations within Meta, allowing offline purchases to be correctly attributed in reporting and analytics.

Each Shopify store location has a unique Location ID, which Elevar includes when sending offline (POS) events to Meta through the Conversions API (CAPI). Meta uses these IDs, referred to as Store Codes in its Location Manager, to determine which physical store a purchase came from. If the IDs don’t match between Shopify and Meta, Meta can’t associate those offline purchases with the right location, which means your data may appear incomplete or misattributed.

Why Syncing Locations Is Important:

Proper location syncing ensures that your offline orders contribute meaningful insights in Meta reporting. When configured correctly:

• Each in-store transaction is matched to its corresponding business location.
• Meta can accurately measure offline conversions and match them to ad interactions.
• You gain a unified view of your marketing performance across both online and offline channels.

Without this step, Meta will still receive offline events, but it won’t know which location they belong to, resulting in limited or inaccurate reporting.

How This Fits Into the Offline Event Setup:

Syncing Shopify and Meta locations is Step 2 of your offline event configuration. Once POS orders are being sent through Elevar, this step ensures the data Meta receives can be properly mapped and used for attribution and performance optimization.

Completing this setup creates a direct link between your Shopify and Meta business infrastructures, ensuring your offline conversions are as reliable and actionable as your online ones.

Prerequities:

Before you can sync your Shopify locations with the Meta Location Manager, ensure that:

• Your Meta Pixel (Dataset) and Store Locations are in the same Business Manager.
• You have permission to edit store locations.
• You can access your Shopify Location IDs, which act as your store codes.

How to Add or Update Store Codes in Meta Location Manager

Option 1: Edit Individual Stores

This option works best if you have only a few store locations.

• Begin on your Meta Business Manager homepage and navigate to "Store Locations".
• If a store already exists, select it and click "Edit Store". Otherwise, click "Add Store" and then "Add a Store Manually".
• Under the Store Code field, enter your "Shopify Location ID" (a 64-character alphanumeric value).
• Fill in the remaining details and click "Save".

Option 2: Bulk Edit Multiple Stores

If you have multiple store locations, use the bulk edit feature:

• In Meta Location Manager, select all stores and click Download Stores.
• Open the file in Excel or Google Sheets.
• Add or update the Store Code column with your Shopify Location IDs.
• Go back to Meta, click Add Stores → Upload Multiple Stores.
• Upload your updated file and click Start Upload.

🚧

NOTE: Removing a store from your upload file and re-uploading will also delete that store in Meta. Only remove stores intentionally.

Verification and Testing:

• After syncing, verify that store codes match between Shopify and Meta.
• In Meta Event Manager, confirm that your POS (offline) purchases are appearing under the correct location.
• Once verified, all future offline orders from Elevar will automatically associate with the correct store.

🚧

NOTE: Correctly syncing your locations ensures offline events are properly attributed in Meta, improving match quality and offline conversion accuracy.

Common Blocking Scenarios to Review

Blocking orders in the Filter Transactions step can prevent Meta from receiving your offline (POS) events. Below are some of the most common cases to check and how to address them.

Offline Orders Aren’t Appearing in Meta:

If your in-store or POS purchases aren’t showing up in Meta reporting, it’s likely that these orders are being blocked.
In your Filter Transactions settings, make sure the “pos” channel is allowed. This ensures that in-store transactions can flow to Meta through Elevar.

If your business intentionally excludes certain offline orders (like draft orders or manual imports), review your filter logic to confirm that only those specific order types are blocked — not all POS events.

Test Orders Showing in Reports:

If you see internal or test purchases in your Meta reporting, you can prevent these from being sent by using Customer Tags in Shopify. Tag internal customer accounts (for example, InternalUser) and then add a filter in the Filter Transactions step to block any order placed by a customer with that tag. This keeps your internal testing activity from affecting campaign performance data.

Subscription or Recurring Orders Included:

If you use subscription software, you may notice both first-time and recurring subscription orders being sent to Meta. To exclude recurring subscription purchases, review your Order Tags in Shopify. Many subscription apps add tags like Subscription Recurring Order or First Subscription Order. Add these tags to your filter rules to block the recurring orders and only send the first subscription event if desired.

Custom or Headless Sales Channels:

If you’re using a custom checkout or headless storefront, you might have additional sales channel codes that need to be explicitly included in your filter logic. Make sure your filters don’t unintentionally block these source names. If you’re unsure what source_name your custom checkout uses, you can find it by viewing an order in Shopify and adding .json to the end of the URL.

App-Specific Orders Being Excluded:

If you use third-party apps (like Tapcart or the Facebook Sales Channel), those apps will have unique App IDs associated with each order. If an App ID is blocked in your Filter Transactions setup, any orders created through that app will not be sent to Meta. Double-check your filter rules to confirm whether these IDs should be included or excluded based on your desired reporting scope.

POS Orders Blocked by Mistake:

Sometimes, teams set up filters to only allow “web” orders (for online purchases). While this setup is common, it also blocks POS orders by default. If you want Meta to receive offline data, update your filter to include both “web” and “pos” sales channels. This ensures all in-store orders are transmitted and categorized correctly.