User Guides

User Guides
User Import/Export
Resources
API Documentation Support Center

    User Import/Export Guide

    Overview

    This guide explains how to import and export users using CSV files in Tagify. The system provides flexible options for handling user data, including automatic or manual card ID assignment and payment setup.

    CSV Format

    Required Header Line

    The first line of your CSV file MUST contain these exact column headers in this order:

    csv

    Email,First Name,Last Name,Card ID,DOB,Status,Points Balance,Is Paying,Payment Amount,Payment Method

    Required Fields

  • Email - User's email address
  • First Name - User's first name
  • Last Name - User's last name

    • Optional Fields

  • Card ID - Unique card identifier (auto-generated if not provided)
  • DOB - Date of birth in YYYY-MM-DD format
  • Status - User status (see Status Types below)
  • Points Balance - User's points balance (defaults to 0)
  • Is Paying - Whether the user is a paying member (yes/no)
  • Payment Amount - Payment amount for paying members
  • Payment Method - Payment method (Credit Card, Cash, Bank Transfer, etc.)

    • Important CSV Rules

  • The header line is MANDATORY and must match exactly
  • Column order must match the header line
  • Do not include spaces after commas
  • Do not use quotes unless the field contains commas
  • Empty optional fields should be left blank (e.g., value1,,value3)

    • Status Types

  • active - User is active and can use the system
  • inactive - User is temporarily disabled
  • pending - New user awaiting activation (default for non-paying users)
  • pending_payment - User is waiting for payment setup/confirmation (default for paying users)
  • suspended - User access has been suspended

    • Default Status Behavior

  • If no status is specified:

    • - Users with is_paying = yes will default to pending_payment

    - Users with is_paying = no will default to pending

  • When a user completes payment setup:

    • - Status automatically changes from pending_payment to active

  • Invalid status values will be set to:

    • - pending_payment if the user is marked as paying

    - pending if the user is not marked as paying

    Example CSV

    csv

    Email,First Name,Last Name,Card ID,DOB,Status,Points Balance,Is Paying,Payment Amount,Payment Method
    

    [email protected],John,Doe,CARD123,1990-01-01,active,100,yes,29.99,Credit Card
    

    [email protected],Jane,Smith,CARD124,1985-06-15,pending_payment,50,yes,19.99,Bank Transfer
    

    [email protected],Bob,Wilson,CARD125,1988-12-31,pending,0,no,,

    Status Behavior

  • Users marked as pending_payment will:

    • - Be able to log in but have limited access

    - See payment setup prompts

    - Need to complete payment setup to become fully active

    - Automatically change to active once payment is confirmed

  • New paying users are automatically set to pending_payment until payment setup is complete
  • Non-paying users start as pending and can be manually activated

    • Notes

  • Email addresses must be unique in your system
  • Users are marked as paying members if 'Is Paying' is set to 'yes'
  • Card IDs will be auto-generated if not provided
  • Dates should be in YYYY-MM-DD format
  • All optional fields can be left blank
  • Payment setup is required for users with 'Is Paying' set to 'yes'

    • Importing Users

    Step-by-Step Import Process

  • Navigate to Dashboard > Users > Import/Export
  • Click "Download Template" to get the CSV template
  • Fill in your user data following the format above
  • Upload your completed CSV file
  • Review the import summary
  • Confirm the import

    • After Import

  • Users will receive welcome emails with setup instructions
  • Payment setup will be initiated for users marked as paying
  • Card IDs will be generated for users without one
  • Paying users will be set to pending_payment status until payment is confirmed

    • Troubleshooting

    Common Import Errors

  • Invalid Email Format

    • - Ensure email addresses are valid

    - Each email must be unique in your system

  • Invalid Card ID Format

    • - If provided, must match your business format

    - Leave blank for auto-generation

  • Invalid Date Format

    • - Use YYYY-MM-DD format

    - Example: 1990-01-01

  • Payment Information

    • - Monthly Rate must be a valid number

    - Currency must be a supported code (USD, EUR, GBP)

    - Payment Method must be one of the supported options

    - Paying users must have Payment Amount and Method specified

  • Status Issues

    • - Invalid status values will default to 'pending'

    - Paying users without payment info will be set to 'pending_payment'

    - Active status requires completed payment setup for paying users

    Need Help?

    Contact support at [email protected] for assistance with imports or exports.

    Last updated: March 25, 2024