You know things about your customers that Shopify does not. Which account manager looks after them. What they said in the onboarding survey. Which tier they negotiated. What their reference number is in the system you used before this one.
That knowledge lives in a spreadsheet, and getting it into Shopify means opening each customer and typing. For a few dozen that is an afternoon. For a few thousand it never happens, and the data stays in the spreadsheet where no theme, flow or segment can reach it.
This sheet works backwards from the others
Every other SheetSync sheet is a mirror of your store: you export what is there, change it, push it back. The customer sheet starts empty, with only the columns you chose. You paste your own data in, and the store is the destination rather than the source.
That difference is worth stating because it changes what a blank means and what the sheet is for. You are not editing Shopify's view of your customers; you are adding to it.
Matching by email, and the privacy reason behind it
Rows are matched on email, and there is a specific reason that is the only option.
Shopify's protected customer data rules draw a line that looks odd until you see what it is for: an app approved at Level 1 cannot read the email field, but it can search by it. So you supply the address, SheetSync finds the customer, and writes. The email is never read back and never stored.
What gets kept in SheetSync's own records is the customer ID and a masked address — ti***@example.com — with a fixed number of stars rather than one per hidden character, because padding to the real length would leak how long the address was. Enough to recognise the row later; not a copy of your customer list sitting in someone else's database as a side effect of an import.
A Shopify customer ID is not offered as an alternative because nobody has one in the spreadsheet they are importing from. It would be a column no one could fill.
Tags or metafields
Each column you add is written as either a tag or a metafield, and the choice is about what the data is for.
Tags are for membership — something a customer is. They drive segments, discounts, flows and, if you use tag-based wholesale, pricing. They are a flat list with no values attached, and Shopify caps them at 250 per customer.
Metafields are for values — something a customer has. An account manager's name, a survey answer, a reference number. They can be read by your theme and by Flow, and they hold the actual text rather than just its presence.
One detail that catches people: customer metafields here are written as multi-line text. Shopify rejects a single-line field whose value contains a newline, and a free-text survey answer is exactly the thing that contains one. Multi-line accepts both, so a column of one-word answers and a column of paragraphs can sit in the same sheet without you having to care about the difference.
Customer tags add; they do not replace
This is the opposite of product tags, and getting it the wrong way round in your head is the one genuinely dangerous assumption here.
On a product, the tags cell is the complete list — whatever is in it becomes the product's entire tag set. On a customer, importing tags adds them to whatever is already there. Nothing is removed by an import.
In practice that is the right default: your spreadsheet knows about tiers, and Shopify already knows about things like newsletter subscriptions that your sheet has never heard of. But it does mean an import cannot be used to clean up tags, and a tag imported by mistake has to be removed deliberately.
Step by step
- Open the Customer Data page in SheetSync and connect your Google account on the Setup page first if you have not.
- Define your columns: a name for each, and whether it becomes a tag or a metafield.
- SheetSync creates the sheet with an Email column and your chosen columns, and nothing else.
- Paste your data in. Email is the key; every other column is yours.
- Run the plan. You see which emails matched a customer and which did not.
- Review and approve.
Practical notes
- The unmatched list is the real output. Addresses that match no customer are usually typos, people who never completed checkout, or a second address for someone you already have. It is worth reading rather than ignoring.
- Normalise your emails first. Trailing spaces and mixed case are the usual causes of an avoidable miss.
- Think before tagging at scale. Tags are visible to anyone with admin access and are easy to create and hard to clean. A tier tag is good; a tag recording something sensitive about a person is a decision to make deliberately.
- Metafields need a theme or Flow to do anything. Writing them is step one; something has to read them before they change a customer's experience.
- Start with a dozen rows. Import a small batch, open those customers in admin, confirm it looks the way you expected, then run the rest.
Who this is for
Stores migrating from another platform or CRM with customer attributes worth keeping, B2B sellers tracking account managers and tiers, and anyone running surveys whose answers currently live only in a response spreadsheet.
If you are tagging customers to give them wholesale prices, that is the other half of the job — see wholesale pricing by customer tag.
Get your customer data into Shopify
Paste your own columns into a sheet, match by email, and write tags or metafields in one sync.
Try SheetSync today