Skip to content

Main content

Product Trial To Repeat Gap

Count Gregorian calendar days between an explicitly recorded product trial and repeat purchase.

Loading tool…

Description

Measure nonnegative calendar days between a supplied product trial and repeat purchase.

Consumer records distinguish events, choices, prices, quantities and supplied survey scales. A unit-price comparison requires comparable goods and quantity units, while a reversed score retains the original scale bounds. An observed time gap or selected option does not establish motivation, causation, consent or the fairness of a commercial practice.

Measure nonnegative calendar days between a supplied product trial and repeat purchase.

When to use this tool

Use Product Trial To Repeat Gap when you already have trialDate, repeatPurchaseDate and need to measure nonnegative calendar days between a supplied product trial and repeat purchase.

How to use the tool and how it works

  1. Enter trialDate, repeatPurchaseDate. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read gapDays. Use the output convention below.

Parse real UTC dates, require repeat>=trial, and return repeat-trial days.1

Input fieldMeaning and unitsAccepted input
trialDateTrial DateRequired. Text; maximum UTF-16 length 8192. Real proleptic Gregorian YYYY-MM-DD; four-digit years 0000-9999 accepted.
repeatPurchaseDateRepeat Purchase DateRequired. Text; maximum UTF-16 length 8192. Real proleptic Gregorian YYYY-MM-DD; four-digit years 0000-9999 accepted.
Output fieldInterpretationReturned shape
gapDaysGap DaysRequired. Safe integer.
json
{
  "input": {
    "trialDate": "2026-10-01",
    "repeatPurchaseDate": "2026-11-01"
  },
  "output": {
    "gapDays": 31
  }
}

Limitations and assumptions

  • The same date gives zero. No purchase, customer identity, retention, repeat behavior or causal product effect is established.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.

Alternative or Complementary methods

Review the original transaction, interface, survey and event records for a behavioral conclusion. Use the complete study design and applicable commercial terms when interpreting comparisons; local flags and ratios do not estimate demand or verify an actual customer experience.

References

  1. Calculation and input contract: consumer-behavior/product-trial-to-repeat-gap — tool.io

Similar or alternative tools