Why Do I Need To Map Fields When Importing Transactions?

Why Do I Need To Map Fields When Importing Transactions?


We need fields to be mapped in order to:

We try to make the mapping as painless as possible by:
  • Analyzing your data to guess likely mappings
  • Remembering your mappings for future imports
  • Enabling automated imports from connections

To learn more about system vs. imported fields, click here.


    • Related Articles

    • Which Format Do You Support When Importing Transactions?

      We do not have a pre-defined, preferred format. We provide different ways to ingest sales transactions - from CSV files, from CRM and accounting systems (ex: QuickBooks, HubSpot, SalesForce, Stripe, Chargebee, Xero, Dynamics, etc.), from FTP, from ...

    • How Can I Programmatically Import Sales Transactions?

      For non-programmatic import options, click here. Three options are available: You can use a Web Endpoint. Using this model, you deploy a web page, from which we securely pull transaction data. We will query your web page at least every hour. You can ...

    • Why Do I Need To Import Transactions?

      In order to efficiently determine sales performance and calculate incentive rewards, Sales Cookie requires sales transactions to be imported. For each incentive plan you design, you can specify a saved query, which will filter imported transactions ...

    • Do I Need To Install Anything?

      You do not need to install anything because our solution is 100% cloud based. You can create an online account and start working immediately. One situation where you would "install" anything is if you want to automatically sync sales transactions ...

    • How Can I Import Transactions?

      For programmatic import options, click here. You can use the following methods to add transactions: Manually or automatically from CSV files Manually upload CSV files containing sales transactions Automatically by having us fetch CSV files from FTP ...