Column Settings
Column settings let you configure column formatting, some of which can be conditional.
embed |
---|
|
This video demonstrates the functionality using Adobe Analytics. However, the functionality is similarly available in Customer Journey Analytics. Be aware of the following differences in terminlogy.
table 0-row-2 1-row-2 2-row-2 3-row-2 4-row-2 1-align-center 2-align-center 4-align-center 5-align-center 7-align-center 8-align-center 10-align-center 11-align-center 13-align-center 14-align-center | |
---|---|
Adobe Analytics | Customer Journey Analytics |
Segments | Filters |
Visitor | Person |
Visit | Session |
Hit | Event |
To access Column settings, select in the column heading.
You can edit settings for multiple columns at once. Select multiple columns and select in any one of the selected columns. Any change that you make applies to all columns with cells selected in them.
Conditional formatting conditional-formatting
Conditional formatting applies formatting to upper, midpoint, and lower limits that you can define. Applying conditional formatting within Freeform tables is also automatically enabled on breakdowns, unless Custom limits are selected.
Replacing a dimension in the table resets the conditional formatting limits. Replacing a metric recalculates the limits for that column (where a metric is on the X axis and a dimension is on the Y axis).
Use non-default attribution model use-non-default-attribution-model
You can override the default attribution model that is configured in Data views.
-
When using the component in a report with a single dimension: The component’s attribution ignores the allocation model when a non-default attribution model is used.
-
When using the component in a report with multiple dimensions: The component’s attribution retains the allocation model when a non-default attribution model is used.
To use a non-default attribution model for a metric in an Analysis Workspace:
-
Select Use non-default attribution model. When already selected, use Edit to edit the attribution model. Or unselect to return to the default attribution model.
-
In Column attribution model, select a Model and a Lookback window. The lookback window determines the window of data attribution that is applied for each conversion.
Attribution models
An attribution model determines which dimension items get credit for a metric when multiple values are seen within a metric’s lookback window. Attribution models only apply when there are multiple dimension items set within the lookback window. If only a single dimension item is set, that dimension item gets 100% credit regardless of attribution model used.
2^(-t/halflife)
, where t
is the amount of time between a touch point and a conversion. All touch points are then normalized to 100%. Ideal for scenarios where you want to measure attribution against a specific and significant event. The longer a conversion happens after this event, the less credit is given.At a high level, attribution is calculated as a coalition of players to which a surplus must be equitably distributed. Each coalition’s surplus distribution is determined according to the surplus that was previously created by each subcoalition (or previously participating dimension items) recursively. For more details, see John Harsanyi’s and Lloyd Shapley’s original papers:
Shapley, Lloyd S. (1953). A value for n-person games. Contributions to the Theory of Games, 2(28), 307-317.
Harsanyi, John C. (1963). A simplified bargaining model for the n-person cooperative game. International Economic Review 4(2), 194-220.
Lookback window
A lookback window is the amount of time a conversion should look back to include touch points. If a dimension item is set outside of the lookback window, the value is not included in any attribution calculations.
- 14 Days: Looks back up to 14 days from when the conversion happened.
- 30 Days: Looks back up to 30 days from when the conversion happened.
- 60 Days: Looks back up to 60 days from when the conversion happened.
- 90 Days: Looks back up to 90 days from when the conversion happened.
- Session: Looks back up to the beginning of the session where a conversion happened. Session lookback windows respect the modified Session timeout in a data view.
- Person (Reporting Window): Looks at all visits back up to the first of the month of the current date range. For example, if the report date range is September 15 - September 30, the person lookback date range includes September 1 - September 30. If you use this lookback window, you can occasionally see that dimension items are attributed to dates outside of your reporting window.
- Custom Time: Allows you to set a custom lookback window from when a conversion happened. You can specify the number of minutes, hours, days, weeks, months, or quarters. For example, if a conversion happened on February 20, a lookback window of five days would evaluate all dimension touchpoints from February 15 to February 20 in the attribution model.