中文 | English | 日本語 | 한국어 | Русский | Español | العربية | Français | Bahasa Indonesia | Tiếng Việt | Türkçe
Back to Home

New Customer Repurchase Analysis

Analyze new customers' repurchase behavior within 7 and 30 days after registration

Please upload an Excel or CSV (UTF-8) file

User ID Column
Each row represents an order. Please specify a column that uniquely identifies users (e.g., member ID, phone number)
Order Date Column
Date when the order occurred, format: 2025-01-01 or 2025/1/1
Registration Date Column
User registration date (used to determine if new customer and calculate repurchase window)

🔍Data Filter (Optional)

After setting filter conditions, only data matching the conditions will be analyzed
正在分析数据,请稍候...
正在处理数据,可能需要几秒钟时间
About This Tool

I. Calculator Introduction

The New Customer Repurchase Analysis Calculator is a specialized tool for analyzing repurchase behavior of newly registered users after registration. By calculating 7-day and 30-day repurchase rates, this tool helps you gain deep insights into new customers' loyalty and repurchase potential, providing data support for developing new customer operation strategies.

Core Features

Application Scenarios

Target Customers

This calculator is suitable for all industries and scenarios that need to analyze new customer repurchase behavior, especially the following types of customers:

Prerequisites: Your business needs to be able to provide data with user ID, order date, and registration date, and new customers typically have orders on the registration day.


II. Algorithm Introduction

2.1 Core Concepts

Repurchase Definition

Repurchase: Users have multiple different order dates within a specified time window (count(distinct order_date) > 1).

For example:

Time Window Definition

2.2 Calculation Logic

Step 1: Data Filtering

The system filters users who meet the following conditions:

  1. Registration date must be provided: Users must have a valid registration date field
  2. Must have order on registration day: Only users who placed orders on the registration day are counted; users without orders on registration day are excluded

Step 2: User Repurchase Judgment

For each qualified user:

  1. Get all order dates (deduplicated) of the user within the specified time window after registration
  2. Judge whether the number of order dates is greater than 1
    • If count(distinct order_date) > 1 → The user has repurchase
    • If count(distinct order_date) = 1 → The user has no repurchase

Step 3: Repurchase Rate Calculation

Overall repurchase rate:

Repurchase Rate = Number of users with repurchase / Total number of qualified users

Repurchase rate grouped by registration date:

Repurchase rate on a specific day = Number of users registered on that day with repurchase / Total number of users registered on that day

Step 4: Result Display

  1. Overall Metrics:
    • 7-day repurchase rate: Repurchase rate of all new customers within 7 days after registration
    • 30-day repurchase rate: Repurchase rate of all new customers within 30 days after registration
  2. Trend Charts:
    • 7-Day Repurchase Rate Daily Trend: Displays daily 7-day repurchase rates by registration date
    • 7-Day Repurchase Rate 30-Day Trend: Displays daily 30-day repurchase rates by registration date (Note: This chart shows the repurchase rate within 30 days after registration, not within 7 days)
  3. Grouped Statistics Table:
    • Grouped by registration month
    • Displays new customer count, 7-day repurchase count, 30-day repurchase count, 7-day repurchase rate, and 30-day repurchase rate for each month

2.3 Data Filtering Rules


III. Usage Instructions and Notes

3.1 Data Preparation

Required Fields

Before importing data, please ensure your data file contains the following three fields:

  1. User ID (user_id)
    • Description: Field that uniquely identifies users (user ID or phone number)
    • Format requirements: Text or numbers are acceptable
    • Examples: U001, 12345, 13800138000
  2. Order Date (order_date)
    • Description: Date when the user placed the order
    • Format requirements: Supports multiple date formats (such as YYYY-MM-DD, YYYY/MM/DD, MM/DD/YYYY, etc.)
    • Notes: The system automatically recognizes common date formats; it is recommended to use standard date formats to ensure accurate parsing
  3. Registration Date (first_order_date)
    • Description: User's registration date (used as label day)
    • Format requirements: Same as order date format
    • Important: This field must be provided; users missing this field will be excluded from the analysis

Data Format Requirements

3.2 Field Mapping

After uploading data, the system will ask you to map columns in your data file to the following fields:

3.3 Data Filtering (Optional)

The system supports filtering order dates and registration dates:

3.4 Result Interpretation

Metric Description

Trend Analysis

3.5 Notes

⚠️ Important Limitations

  1. Must have order on registration day:
    • The system only counts users who placed orders on the registration day
    • If a user did not place an order on the registration day, even if they have repurchase later, they will not be included in the analysis
    • Recommendation: Ensure the "registration date" field accurately reflects the user's registration date
  2. Registration date must be provided:
    • If a user lacks a registration date field, that user will be automatically excluded
    • Recommendation: During data preparation, ensure all users have valid registration dates
  3. Time Window Calculation:
    • 7-day window = Registration day + 6 days (7 days total, including registration day)
    • 30-day window = Registration day + 29 days (30 days total, including registration day)
    • Calculation is based on calendar days, time zone differences are not considered
  4. Data Timeliness:
    • Charts and tables only display data from the last 2 years
    • If you need to analyze earlier data, please analyze by time period

💡 Usage Recommendations

  1. Data Quality Check:
    • Check data completeness before uploading, ensure key fields are not missing
    • Verify date formats are correct to avoid date parsing errors
  2. Analysis Time Range:
    • It is recommended to analyze the last 3-6 months of data first to observe short-term trends
    • Then extend to 1-2 years of data to observe long-term trends
  3. Result Validation:
    • Compare repurchase rates across different periods to identify abnormal fluctuations
    • Combine with business activity times to analyze reasons for repurchase rate changes
  4. Strategy Optimization:
    • If the 7-day repurchase rate is low, it is recommended to strengthen user outreach 3-7 days after registration
    • If the 30-day repurchase rate is low, it is recommended to optimize new customer retention strategies to extend user lifecycle

3.6 Frequently Asked Questions

Q1: Why are some users in my data not counted?

A: Possible reasons include:

Q2: Does repurchase rate calculation include orders on the registration day?

A: Yes. Repurchase judgment is based on "the number of different order dates." If a user placed an order on the registration day and has orders on other dates later, it counts as repurchase.

Q3: If a user places multiple orders on the same day, does it count as repurchase?

A: No. The definition of repurchase is "multiple different order dates." Multiple orders on the same day only count as 1 order date, so it does not count as repurchase.

Q4: What does "7-Day Repurchase Rate 30-Day Trend" in the chart mean?

A: This chart shows: For each registration date, the repurchase rate of users registered on that day within 30 days after registration. Note: The time window here is 30 days, not 7 days.

Q5: How to improve new customer repurchase rate?

A: It is recommended to start from the following aspects:


IV. Summary

The New Customer Repurchase Analysis Calculator helps you fully understand new customers' repurchase behavior through scientific algorithms and intuitive visualizations. Proper use of this tool can:

If you have any questions or need technical support, please contact the system administrator.