An attribution report assigns credit for a KPI to certain engagements along the customer journey.

There are tens of thousands of actions recorded by HockeyStack for each company. Therefore we have to have a way of filtering to the exact engagements we want to receive credit. Attribution touchpoints are the engagements along the customer journey selected for credit distribution towards a KPI.

To give an example, see the below table for actions that a company has recorded. The red actions are ones that a HockeyStack user might want to filter out. The green actions are ones that a HockeyStack user might want to keep. The action at the end is our KPI.

Looking at the above journey, we need to distribute $100k in total credit into actions along the journey.

If we weren’t filtering out touchpoints, the credit distribution would be:

But it doesn’t make sense for a “scroll down” action to be attributed $12.5k, so we instead want the below distribution:

HockeyStack does this filtering using “breakdowns” in reports.

If the property that is selected as the breakdown is not empty and the action it is tied to has a timestamp that is before the timestamp of the KPI chosen for attribution, then that property is used as an attribution touchpoint.

If your breakdown does not have an associated timestamp, it won’t be usable in attribution. Examples include company properties & user properties. For example, many HockeyStack users try to use Lead Source in their breakdown using an attribution model. This doesn’t make sense because Lead Source is not attached to any timestamp, and does not exist on the customer journey — it’s just a property.

​