Define the dataset you actually need.
An online shopper audience is not the same as a customer list for your store. E-commerce requests can involve general consumer data, a documented product-category audience, or past campaign inquiries. Each has a different meaning, so specify which information your project needs.
Define the audience and category
Name the product category, U.S. geography, and contact fields relevant to your project. If a category-interest field is requested, ask how that attribute is defined and whether its source is available. Avoid treating broad audience labels as proof of a purchase.
Distinguish customers from prospects
A prospect record should not be described as a past customer of your business. If you are working with your own customer file instead, describe whether the task is cleansing, deduplication, or enrichment of existing records.
Plan the file structure
Agree on a stable record ID, field names, and the handling of blank values. Ask for counts of unique contacts and usable emails separately when email is essential. Choose a delivery format that fits your existing workflow.
A useful project brief
U.S. consumer audience for a defined retail category, focused on specified states. Request available email and location fields, a definition of the category attribute, and a unique-contact count.
Does an online shopper record prove purchase intent?
No. Audience membership alone does not confirm interest in your products. Any purchase or inquiry attribute must be defined and supported separately.
How your request is reviewed
Share your requirements through Request Data. Our team reviews availability, field coverage, and project fit before responding with the options and next steps. Submitting a request does not create an order or start a payment.
