Organic Paid Traffic Projection

Compare an assumed compounding organic traffic stream with paid traffic ending at a chosen month.

Description

Traffic scenarios can combine compounding organic visits with paid visits that stop after a selected duration.

Traffic scenarios can combine compounding organic visits with paid visits that stop after a selected duration. The result follows assumptions rather than forecasting demand.

Compare an assumed compounding organic traffic stream with paid traffic ending at a chosen month.

When to use Organic Paid Traffic Projection

Use this for the following task: Compare an assumed compounding organic traffic stream with paid traffic ending at a chosen month.

Prepare the scenario values in one currency and consistent time periods. Use fractions for fraction fields and percentage points for percent fields.

How to use Organic Paid Traffic Projection and understand its results

Prepare the scenario values in one currency and consistent time periods. Use fractions for fraction fields and percentage points for percent fields.
Enter initialOrganicVisits, monthlyOrganicGrowth, paidMonthlyVisits, paidStopMonth, months using the field table, then run the tool.
Read organicVisits, paidVisits, totalVisits. Interpret flags, units, ordering and placeholder values using the rules below.
Review any reported issue or failed check, correct the supplied values when appropriate, and verify the result in its intended context.

Input field	Meaning	Value type and bounds	Requirement
initialOrganicVisits	Initial organic visits	number	Required
monthlyOrganicGrowth	Monthly organic growth	number	Required
paidMonthlyVisits	Paid monthly visits	number	Required
paidStopMonth	Paid stop month	integer	Required
months	Months	integer	Required

Use nonnegative initial/paid visits, growth in [0,1] and a positive month count no greater than 1200. Index months from zero and add both streams.^[1]

organic[i]=initial(1+growth)^i; paid[i]=paidMonthly if i<paidStopMonth else 0

This summarizes the declared operation. Units, indexing, inclusivity and exceptional cases are explained in the surrounding text.

Output field	Meaning	Value type
organicVisits	Organic visits	list of number
paidVisits	Paid visits	list of number
totalVisits	Total visits	list of number

json

{
  "input": {
    "initialOrganicVisits": 100,
    "monthlyOrganicGrowth": 0.1,
    "paidMonthlyVisits": 200,
    "paidStopMonth": 2,
    "months": 3
  },
  "output": {
    "organicVisits": [
      100,
      110.00000000000001,
      121.00000000000001
    ],
    "paidVisits": [
      200,
      200,
      0
    ],
    "totalVisits": [
      300,
      310,
      121.00000000000001
    ]
  }
}

Limitations and assumptions

Month zero uses the initial organic value. No campaign decay, seasonality or attribution is modeled.

These outputs describe the supplied scenario; accounting definitions, capitalization terms and time periods must match the intended use. Malformed requests produce input errors. A successfully evaluated request can still contain false flags, empty result lists or a result outside the supplied threshold; those outcomes have the meanings stated above.

Alternative or Complementary methods

Choose Monthly Growth Comparison for this operation: Compare arithmetic mean monthly growth with compounded average growth. For a complementary task, use Cohort Retention Matrix for this operation: Generate age-aligned customer retention percentages for multiple cohorts.

The implementation reference documents the exact calculation, supported input shapes and returned fields.

References

Organic Paid Traffic Projection — tool.io

Similar or alternative tools

Monthly Growth Comparison
Compare arithmetic mean monthly growth with compounded average growth.
Cohort Retention Matrix
Generate age-aligned customer retention percentages for multiple cohorts.