What Is the All Customer Metafields Report?
The All Customer Metafields report brings the extra details stored on Shopify customer profiles into one export. Review customer names and emails alongside metafield namespaces, keys and values, such as preferred size, birthday, wholesale account number or loyalty level, where your store saves these details.
Use it to organize customer information for segmentation, check how consistently details are recorded and prepare a file for your team. It describes saved customer attributes; the report fields do not include orders, spending or marketing consent.
A customer may have several metafields and therefore appear more than once. Confirm the premade report’s row structure and whether customers without metafields are included before treating it as a complete customer list.
Report Overview
- Report type
- Customer.
- Reporting basis
- Saved customer metafield data at report generation; no sales date range is specified.
- Data included
- Customer name, email, metafield namespace, key and value; exact field labels need confirmation.
- Best for
- Reviewing custom profile details and preparing customer segments.
- Delivery
- Excel, CSV or PDF, with daily, weekly or monthly email scheduling.
What Can You Learn from Customer Metafields?
1. Which saved preferences can support customer segments
Review values for one relevant namespace and key to group customers with the same recorded preference. These segments reflect information your store has saved.
Example: For example, customers with preferred_size set to M form a size-based group.
What you can do: Export the selected group and check consent separately before using it for marketing.
2. Where recorded values need consistent formatting
Different spellings or formats can split what should be one group. Sorting a single key’s values helps reveal variations.
Example: For example, wholesale, wholesale and WHOLESALE all describe the same account type.
What you can do: Agree on one format and correct the source records or collection form.
3. Which account details are ready for a team handoff
Customer names and emails provide context for custom account attributes, such as an account number or assigned representative.
Example: For example, a wholesale account key contains account numbers needed for a CRM review.
What you can do: Select the required keys and match records against the destination system before importing.
What Should You Check First in This Report?
Check these details before counting, sharing or importing the export.
- Namespace and key: Use both to identify an attribute; matching key names can belong to different namespaces.
- Customer identity: Repeated customer rows are not necessarily duplicates. Request a customer ID field if you need reliable unique-customer counts.
- Value format: Check dates, leading zeros in account numbers, list values and referenced records before importing.
- Coverage: An absent metafield may produce no row. Compare against a complete customer list before concluding that no customers are missing a detail.
When Should You Use This Report?
| When to Use It | How It Helps |
|---|---|
| Preparing preference-based segments | Collects saved size, skin type or other preference values alongside customer emails. |
| Reviewing loyalty classifications | Shows recorded loyalty levels so you can check labels and prepare a review list. |
| Preparing a wholesale account handoff | Brings custom account numbers or account attributes into a file for matching. |
| Checking data after a form or quiz change | Lets you inspect recorded values for unexpected formats or inconsistent answers. |
| Auditing missing customer details | Provides metafield records to compare with a complete customer list; missing-row behavior must be checked first. |
How to Create This Report in Data Export
Start with the All Customer Metafields premade report.
- Open Data Export and go to Prebuilt Reports.
- Find All Customer Metafields and review its available columns and sample rows.
- Keep the customer details and metafields you need. Use the available filters to narrow the output; confirm customer-tag and metafield filtering options in your store.
- Save the report and generate a sample export. Check repeated customer rows, value formatting and customer coverage.
- Choose the export format and, if needed, schedule daily, weekly or monthly email delivery to the appropriate recipients.
Make the Most of This Report
Use these checks to keep the exported customer details useful.
01 / GROUP PRECISELY
Keep namespaces with keys when sorting. This avoids combining different attributes that happen to share a key name.
02 / COUNT CAREFULLY
Count unique customers after selecting one attribute. Several metafield rows can belong to the same customer.
03 / PRESERVE FORMATS
Treat account numbers as text and review birthday formats. Spreadsheet conversion can remove leading zeros or reinterpret dates.
04 / SHARE SELECTIVELY
Keep only the fields needed for the task. Check recipients before scheduling files containing personal customer details.
Frequently Asked Questions
What is the difference between a namespace, key and value?
The namespace groups metafields, the key identifies a detail, and the value holds its saved content. Together, the namespace and key identify the attribute you are reviewing.
Does every customer appear only once?
Do not assume so. A customer with several metafields may appear on multiple rows. Confirm the output layout before counting customers or importing the file.
Can I use this report to find customers missing a metafield?
First check whether missing metafields appear as blank values or are omitted. If they are omitted, compare the report with a complete customer list or ask support for a view designed to find missing details.
Can I chart customer metafield values in Excel or Google Sheets?
Yes. Export the data, select one namespace and key, then summarize the values in a pivot table and chart. Use unique customer counts where possible so repeated rows do not inflate the totals.
Can I schedule the report or request a different layout?
You can schedule daily, weekly and monthly email delivery. For one column per metafield or a view combined with order history, ask Data Export support to configure the layout you need.