Shared CRM data's lead count or individual leads cannot be split among properties and will need to rely on cross-family attribution. This means that one property will have the lead counts (the property that we map the shared leads to), while other properties show no physical lead counts but in click_trails will have leads.

We are only able to split CRM data if they have a property column that clearly and consistently defines which property the lead belongs too.

We are unable to filter and split CRM data by the stock numbers as we can only map specific full property names. Normally only a few numbers and letters will be the identifier while the rest is different. Our system have to have a consistant alias through out. It will also cause a lot of errors since many of the cells may be blank and unable to match to a property.

If a property shares a CRM store with another property it is not an issue since they will still have cross family attribution. Some of those properties may not show a lead count but within Click_Trails they will still have attribution as long as they have a separate DMS report.

We can do the following:

• Map the shared CRM data to a parent property
• OR Map the sahred CRM data to one of the properties that shares the CRM data
  e.g.: If a CRM contains a Jaguar Land Rover store, but we have separate properties for Jaguar and Land Rover, we can map the data to the Jaguar property.  The Jaguar Property will show lead counts, while the Land Rover Property will not show lead counts.  As long as both properties have separate DMS data, they will each receive cross-family attribution from those leads.