<aside> ❗ Read the below guide on defined properties before proceeding:

Defined Properties

</aside>

Before this step, you organized all information needed for your channel definition like below:

• Website visit where utm_medium = google_paid | | Paid Social — LinkedIn Ads | - Website visit where utm_source = linkedin_paid
• LinkedIn Ads Ad Engagements
• LinkedIn Ads Video Completions | | Organic Social | - Website visit where source is any of linkedin,facebook,reddit,quora,instagram,youtube,t.co | | Organic Search | - Website visit where source is any of google,bing,yahoo,yandex,duckduckgo,ecosia | | Email Marketing | - Integration = Marketo
• Action Name contains one of Open Email,Click Email
• Website visit where utm_medium contains email | | Events | - Salesforce CampaignMember where Status is one of Attended, Responded, Scanned, Booth AND Campaign Name contains EVT- | | Other Referral Traffic | Run through all the other rules, and if it doesn’t match any and Source is not direct and Source is not empty, count that as Referral traffic. |

Now, we will translate this into a defined property called “Unified Channel”, which will have each of the above rows as mappings inside it.

Navigate to Definitions > Properties and click + on the top right.

Paid Search — Google Ads

https://app.arcade.software/share/uOpQymHwY6iqycDyHaZu

The HockeyStack data model is based on "actions" that prospects take along their journey to becoming a customer. "Actions" by definition have a specific timestamp.

Whereas the CRM data model is based on "objects" and "fields" inside those objects. For example, you might have a Lead record, and that Lead record might have a Source field. The Source field does not have a timestamp, so is not convertible to "actions" in HockeyStack.

Things that are convertible:

• Any date field within any field
• Campaign memberships
• Tasks, activities, etc.
• Website data,
• Other integration data like LinkedIn Ads engagements

The commonality between all of the above is that we know what date and time these interactions happened, so we can place them on the account journey.

Read more about the data model here: https://docs.hockeystack.com/hockeystack-academy/101-how-hockeystack-works/the-hockeystack-data-model

Also this is a good resource for how HockeyStack works: https://hockeystack.com/the-flow/episodes/hockeystack-webinar-office-hours-05-09-2024