Description
Allocate one touch's conversion credit under a supplied rule.
Business accounting and analytics distinguish gross, net, allocated, recognized and forecast amounts. Currency, period, eligibility and interaction-allocation conventions determine a reported contribution; reconciling one term does not verify revenue, payment rights or future commercial outcomes.
Allocate one touch's conversion credit under a supplied rule.
When to use this tool
Use Conversion Path One Touch Credit Rule when reconciling the stated business amount, share, bridge or forecast convention.
How to use the tool and how it works
- Enter touches, targetIndex, value, rule. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read credit, weight. Use the output convention below.
Allocate one touch's conversion credit under a supplied rule. Require valid targetIndex in nonempty touches and first/last/equal rule; weight is one for the chosen endpoint, 1/count for equal or zero otherwise; credit = value*weight.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| touches | Touches | Required. Array of text; maximum UTF-16 length 8192; maximum items 256. |
| targetIndex | Target Index | Required. Safe integer; minimum 0. |
| value | Value | Required. Finite number. |
| rule | Rule | Required. Text; one of "first", "last", "equal"; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| credit | Credit | Required. Finite number. |
| weight | Caller-supplied weight on the stated observation, model or allocation basis. | Required. Finite number. |
{
"input": {
"touches": [
"A",
"B",
"A"
],
"targetIndex": 1,
"value": 90,
"rule": "equal"
},
"output": {
"credit": 30,
"weight": 0.3333333333333333
}
}Limitations and assumptions
- Input order defines first/last and value may be signed; this is attribution bookkeeping rather than causal impact or inferred channel effectiveness.
- 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.
- Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.
Alternative or Complementary methods
Use complete verified accounts and governing commercial terms, and apply the appropriate accounting and financial judgment for actual reporting, payment or investment decisions.
References
Similar or alternative tools
- Sales Territory Transfer Credit Split
Split sales value into three supplied credit fractions.
- Subscription Revenue Reactivation Tag
Identify reactivation under explicit previous-subscription and adjacent-period activity flags without confusing it with a first subscription.