BuyerGenomics

Your BuyerGenomics (“BG”) database will generate actionable customer intelligence and help your organization methodically grow sales and profitability. 

All we need from you is the record of:

• Who Bought
• What Product
• For How Much
• When
• Through What Channel

This document is for you to reap the benefit of BG as soon as possible.

Implementation Process

Roles

Setting up BuyerGenomics is a straightforward process, generally measured in days, not months. For smooth implementation of BG, we recommend you to identify an executive sponsor and a data manager, requiring modest time from each.

• The executive sponsor will play an important role of providing marketing strategy and directions in the use of BG, ensuring seamless transition to best practices of intelligent marketing operation.
• The data manager will be responsible for delivery of new and historical data from various systems on the client side. The key responsibility of this role is to ensure proper alignment of data, while most of the heavy lifting will happen on the BG side.

A dedicated account manager on the BuyerGenomics side will be working closely with your team, answering day-to-day questions regarding data transfer and providing guidance in everyday usage of the toolset.

Implementation Process

Initial BuyerGenomics implementations are completed in less than 2 weeks from the kickoff date with all involved parties, granted that we receive usable transaction history files in a timely fashion.

The following are the key steps of typical BG implementation process: 

• Kickoff meeting with executive sponsor, data manager, and BG Account Manager
  • Data requirement review and QA session
  • Finalize data transfer method
  • Discussion regarding ongoing data feed from the client
  • Review of custom fields such as various item details and descriptions
• Initial “historical” data transfer via mutually agreed upon method
  • Data quality assurance (by BG)        
  • Initial data audit report (shared if necessary)
  • Follow up meeting if there are any issue with data
• Data load (by BG)
  • BuyerGenomics launch
  • Q&A session
  • Initial review and training with active and potential users
  • Continuous data feed and BG update

Input File Format

Our goal is to minimize your involvement in file conversion and transfer. Please let us know if you have any question regarding file or data formats.

• Plain text files are preferred, but please let us know if other formats should be considered for your convenience. The following formats are preferred:
  • Tab or pipe delimited ASCII 
  • Comma (with “ ”) delimited ASCII
  • Fixed fielded ASCII text file (separate data layout including field position and length required)
• Please name the data file as MyCompany_YYYY-MM-DD_YYYY-MM-DD, containing the client’s name and the period covering the transactions submitted in the file. 
  • For example, a tab-delimited file with transactions ranging from Jan 15, 2016 to Feb 15, 2017 would be: MyCompany_2016-01-15_2017-02-15.txt.
  • Provide header row with variable descriptions, or separate data layout including field descriptions.

Data Requirements

In order to provide a 360 degree customer view based on their behavior, BG requires personally identifiable information and transaction data. Please note:

• Customer, transaction and item details can be shared in 3 separate tables in a relational structure, or pre-merged (or denormalized) format on an item level. Required elements are:
  • Customer information: Name, address, email, phone number, and if available, customer ID
  • Transaction information: Unique transaction ID, transaction date, transaction amount
  • Item information: SKU number, item descriptions, product categories (up to 3 levels), plus user specific item feature fields (up to 6 fields) 

Important: The date range must be set using the Transaction Date in the Transaction Table, and only corresponding Customer and Item records should be selected based on it.

• Returns are considered unique transactions. Please let us know if the transaction IDs are reassigned or re-used for return transactions.
• Please include field names in the header rows as outlined in the detailed data specifications below..

Important Notice Regarding Data Originating EU Countries and U.K.

Starting May 25, 2018, GDPR (General Data Protection Regulation) goes in effect in the EU and the U.K., providing data subjects control of their personal data and imposing strict rules on those hosting and processing such data anywhere in the world.

All merchants who operate in the EU and the U.K. must comply by communicating their clear intention and purpose for data storage and usage in no obscure terms, and must purge records upon request. 

Provided with explicit “opt-in” tag (see the attached input data layout below) for each customer from the EU and the U.K., BG will store customer information and their transaction data.  

Records came in only with email address without valid address or country of origin, BG will examine the domain name of the email address (e.g., xxxx.co.fr from France), phone number (with country and area code), and IP address (if provided) to identify the origin to best of our ability.

Records without opt-in tag from the EU and the U.K. will be isolated from BG, and may be purged depending on the client’s data privacy policy regarding GDPR.  Records from unknown origin will be determined during the onboarding process, as each client’s footprint differ greatly.

Please let us know if you have any questions regarding GDPR and data storage in BG.

The following includes specific data elements that are required.

Customer Data

Transaction Data

Product Data