User Guide
  • Intro
    • Welcome
      • About DotApparel
      • What is DotApparel?
      • Where is it hosted?
      • What platform(s) do we support?
      • How does syncing work?
      • Solution architecture
      • Definition of “Instance”
      • Security Overview
    • Implementation
      • Google Cloud and Firebase
  • Quick Links
  • Core
    • Overview
    • Dashboard
    • Orders
      • Mappings
      • Integrations
    • Returns
      • Mappings
    • Products
      • Mappings
        • Default mapping rules
      • Translations
      • Markets
      • Publishing products
    • Inventory
      • Mappings
        • Examples
          • Ignore Sync
          • Inventory Buffer
          • Keep Items Sold Out
          • Unlimited Inventory
    • Customers
    • Rewards
    • System Alerts
    • Settings
      • Shopify Locations, DotApparel Locations and Inventory Buffers
      • ERP credentials
      • Product images
      • Fulfillments
      • Payment gateways
      • Gift cards
      • Refunds
      • Notifications
      • Harmony Integration with DotApparel
    • Modules
      • Ship From Store
      • Local Pickup/Click & Collect
      • Shopify Markets
      • Returns
        • Australia Post (AusPost)
        • Loop Returns
      • Auto-Refunds
        • Refunding Shopify Orders from POS (In-Store)
      • Integrate with Brauz (app)
      • Integrate with The Wishlist (app)
    • Release Notes
    • Troubleshooting
      • FAQs
      • How to raise a support ticket for an issue
      • Good and bad examples of a problem ticket
      • Want to enable a new omnichannel feature?
      • Want to integrate a marketplace using DotApparel?
  • Customers
    • Overview
      • Email Examples
    • Getting Started
      • Understanding Customer Setup in your ERP
      • Data Sync
      • Configuration
      • Testing
    • Data Export Approaches
      • Option A: Consultant
      • Option B: In-House
    • Apparel21 Export Templates
    • Apparel21 Export Changelog
    • Dashboard
    • Customers
    • Orders
    • Translations
    • Mappings
    • Settings
    • Support
  • Loyalty
    • Overview
    • Getting Started
      • Terminology
    • Data Sync
      • Workflows
    • Front-End Implementation
    • Rewards Redemption
    • Rewards Emails
    • Things To Know
Powered by GitBook
On this page
  • Multiple Klaviyo Connections
  • Initial Setup Instructions
  • Configure Settings
  • Orders

Was this helpful?

Export as PDF
  1. Customers
  2. Getting Started

Configuration

Steps we take to configure your instance

PreviousData SyncNextTesting

Last updated 1 year ago

Was this helpful?

Once DotApparel Customers is installed, we will provide the SFTP server information to the merchant, including host, username, password, and port number.

All the CSV files need to be uploaded to the pending and bulk folders.

  • /test: Files saved here are for testing, we will review these during setup.

  • /pending: New files that are waiting for processing.

  • /processed: Files that have been processed.

  • /bulk: Files saved here will not undergo automatic processing. Instead, it will exclusively generate new customer profiles in Klaviyo without performing updates to the marketing preference.

Multiple Klaviyo Connections

This feature allows users to establish and manage connections to multiple Klaviyo accounts from within the app. Each connection is uniquely identified by a user-defined name, Klaviyo private key, and corresponding file directory.

Initial Setup Instructions

  1. Navigate to the app's settings page.

  2. Click on the "Add new connection" button to create a new configuration.

  3. Give the connection a meaningful name that reflects the Klaviyo account it represents. For example, "Klaviyo AU" or "Klaviyo NZ."

  4. Obtain the private API key for the corresponding Klaviyo account. Enter this key in the provided field to enable data synchronization with Klaviyo.

  5. Define the file directory that corresponds to the specific Klaviyo connection. For example, you can set '/pending/au' to connect to your Klaviyo AU store and '/pending/nz' for the Klaviyo NZ store.

  6. Click the "Add new Klaviyo connection" button to save the configuration.

Configure Settings

Customers

  1. Primary Key* The primary key is a unique identifier for each customer in your CSV file. It could be any value that is unique for each customer, such as a customer ID. During the configuration process, you will be prompted to specify the name of the primary key column in your CSV file.

  2. Email Column* The email column represents the column in your CSV file that contains the email addresses of your customers. It is used to map the email field in Klaviyo.

  3. Phone Column The phone column represents the column in your CSV file that contains the phone numbers of your customers. It is used to map the phone number field in Klaviyo.

  4. First Name Column* The first name column represents the column in your CSV file that contains the first names of your customers. It is used to map the first name field in Klaviyo.

  5. Last Name Column* The last name column represents the column in your CSV file that contains the last names of your customers. It is used to map the last name field in Klaviyo.

Please note that these column names should match the actual column names in your CSV file. Make sure to provide accurate column names during the configuration process to ensure proper mapping between your CSV fields and Klaviyo API fields.

Orders

  1. Primary Key* The primary key for orders is a unique identifier for each order in your CSV file. It can be any value that is unique for each order, such as an order ID or transaction ID. During the configuration process, you will be prompted to specify the name of the primary key column in your CSV file.

  2. Customer Reference Key* The customer reference key is the customer identifier that you have configured in the customer CSV configuration. It allows you to link the order data with the respective customer data. For example, if you have used "customer ID" as the primary key in the customer CSV configuration, you would enter the name of the column that references the"customer ID" in the order CSV configuration.

  3. Order Number Column* The order number column represents the column in your CSV file that contains the order numbers. It is used to uniquely identify each order.

  4. Unique Order Item Identifier The unique order item identifier represents the column in your CSV file that contains the order items. It is used to uniquely identify each item within an order. This identifier is helpful when dealing with orders that have multiple items.

Ensure that the column names provided during the configuration process match the actual column names in your CSV file. This will ensure accurate mapping between your CSV fields and Klaviyo API fields for order data.

Once the checklist is complete, we will need to test the integration which will consist of uploading the example files to the SFTP server.