# Touchpoints — Property Guide > 67 properties documented · 65 fully reviewed · 30 pending documentation. ## Downloads Information ### Single text line *Type: **Single-line text*** 4flow definition of business line --- ### 4f_Touchpoint-name *Type: **Single-line text** · Owner: Marketing Ops* Standard single-line text field with name of touchpoint. Is always overwritten by _dd variant. **How to use it:** Can be fused for filtering if the single line filtering is required. Also, can be modified manually to find specific touchpoints. --- ### 4f_Activity status *Type: **Dropdown** · Owner: Marketing Ops* This property works in conjunction with the property 4F_activity_type. It further explains the actual action that happened and is used to e.g. distinguish between registrations for and attendances of a webinar. **How to use it:** The property is set by the admin team and in workflows with every conversion. It can be used to filter for specific actions (e.g. people who registered but did not attend or vice versa). **Options:** Registered, Attended, Cancelled, No-show, Pre-scheduled meeting, Booth discussion, Speaker, Downloaded, Inbound --- ### 4f_associated company ID *Type: **Number** · Owner: Marketing Ops* stores the ID of the associated Company **How to use it:** used for tracking purposes mainly, only updated via workflows on change of associations --- ### 4f_Business line *Type: **Checkboxes** · Owner: Marketing Ops* This property reflects the 4flow business lines and is used whenever a clear association with one of our business lines/services is possible. Also used at events in booth protocols, etc. **Options:** 4fs, 4fc, 4fm, 4fc-SAP, 4fc-Kinaxis, 4flow, 4fs-Platform --- ### 4f_campaign-ID_freetext *Type: **Single-line text** · Owner: Marketing Ops* is used to store the campaign-ID of Google and LinkedIn campaigns. It is derived from conversion URLs through these paid channels and used to find the correct campaign to pull the cost via API from LinkedIn and Google. **How to use it:** is used and set only via workflows but can be used to filter on specific LinkedIn and Google campaigns --- ### 4f_campaign owner *Type: **Checkboxes** · Owner: Marketing Ops* Depreciated property was used to identify internal campaign stakeholders (business line representatives who requested/are responsible for a campaign). **How to use it:** Do not use anymore. --- ### 4f_campaign-spend_last_skip_reason *Type: **Single-line text*** Property is filled in case of an error when trying to pull LinkedIn and Google campaign spend. Work in conjunction with the 4f_last campaign_spend property. **How to use it:** Bug fixing only --- ### 4f_campaign_spend_last_updated *Type: **Date** · Owner: Patrick G* This represents the date of the last update of campaign spend. It is set by the Google and LinkedIn workflows when pulling campaign spend data. **How to use it:** is filled by workflows only. helps admins understand when the campaign spend was pulled so works in conjunction with 4F_Last campaign spend --- ### 4f_company customer industry *Type: **Dropdown*** sync the company's customer industry to the touchpoint for reporting purposes on industry penetration **Options:** Automotive supplier, Aviation, Basic materials industry, Chemical, Energy, FMCG/CPG, High-tech and telecommunication, Industrial/manufacturing, IT service provider, Logistics Services Provider, Medical technology, Packaging, Pharmaceutical, Recycling, Retail, e-commerce & wholesale, Vehicle manufacturer, Consulting, Other - relevant, Other - irrelevant, Defense, Multi-industry --- ### 4f_current_campaign_spend *Type: **Number** · Owner: Patrick G.* This property stores the campaign cost of a campaign that enabled the conversion. It is filled static with 3rd party media cost (e.g. for mailing) and dynamically by pulling campaign spend at the moment of conversion from LinkedIn and Google. The spend serves as basis to calculate cost per conversion/lead etc. **How to use it:** filled in by admins only. frontload with 3rd party cost --- ### 4f_Date of conversion *Type: **Date** · Owner: Patrick G.* This property is used instead of the create date. It is especially relevant when we are adding older conversions to the system, e.g., from an Excel sheet. It represents the actual date of conversion, not the create date of the touchpoint. **How to use it:** use this date to filter for touchpoints/conversions in a given timeframe. fill this date when backdating conversions. if it stays empty, it gets auto-populated with the create date of the touchpoint --- ### 4f_deal-id for TP-influece *Type: **Single-line text** · Owner: Marketing Ops* helper property used to track associated deal deals... purpose is tracking/association of touchpoints to existing deals **How to use it:** used and set in Workflow only --- ### 4f_End date *Type: **Date** · Owner: Marketing Ops* End date - e.g. of events or webinars. --- ### 4f_event_additonal comments *Type: **Multi-line text*** freetext field to fill in additional comments at events. used to build the booth protocol --- ### 4f_event_discussed topics_dd *Type: **Checkboxes*** Add field to fill in discussed topics at events. Used for reporting mainly. **Options:** SAP Digital Supply Chain, 4flow software solutions, Warehousing and intralogistics, General interest in 4flow, Network design & transportation optimization, Data-driven supply chain & AI, Supply Chain Orchestration & 4PL, End-to-end-optimization --- ### 4f_event_Quality of contact *Type: **Checkboxes** · Owner: Patrick G.* This property is used as the selector for event booth staff. By selecting the right measures, we determine if a conversion (of the contact) is an MQL and create a lead. **How to use it:** tbd **Options:** Sales potential, Sales potential unclear, Contact maintenance (e.g. known contacts drop by to discuss current projects), Vendor, Competitor, Other (doesn't fit categories above, e.g. press inquiries), Partner --- ### 4f_event_What was discussed *Type: **Multi-line text*** freetext field to fill in discussed topics at events. used to build the booth protocol --- ### 4f_Focus topic *Type: **Checkboxes** · Owner: Marketing Ops* defined focus topics assets. used to cluster different assets (touchpoint names) and identify topics of interest. used in conjunction with the funnel stages to identify correct nurturing workflows. **How to use it:** Labels are pre-defined during asset creation and stored in HubDB. Workflow writes these values to the touchpoint after conversion. **Options:** Network Design, Transport optimization, Technology Implementation - General & AI, Data solutions, Transport management, Supply Chain Orchestration, Technology Implementation - SAP, Technology Implementation - Kinaxis, Inventory & Warehouse, Cost optimization, Sustainability, Resilience, S&OP, Change management & resilience, Software platform --- ### 4f_Impact tracking *Type: **Checkboxes*** reflects the lead and deal association labels and is used for reporting (MQL, SQL, etc.) **Options:** Created lead, Influenced lead, Re-opened lead, Created deal, Influenced deal, Qualified --- ### 4f_Lifecycle stage at touchpoint *Type: **Single-line text** · Owner: Marketing Ops* Tracks the contact's lifecycle stage at conversion and thus gives a snapshot of that information. **How to use it:** Set by workflows only, --- ### 4f_Paid campaign account *Type: **Single-line text** · Owner: Marketing Ops* is used to store the campaign account-ID of Google and LinkedIn campaigns. It is derived from conversion URLs through these paid channels and used to find the correct campaign account to pull the cost via API from LinkedIn and Google. **How to use it:** can be used for filtering in reports to refine and rebuild the report structure to LinkedIn and Google logic --- ### 4f_Paid campaign account name *Type: **Single-line text** · Owner: Marketing Ops* is used to store the campaign account name (directly linked to the 4f_Paid campaign account-ID) of Google and LinkedIn campaigns. It is derived from conversion URLs through these paid channels and used to find the correct campaign account to pull the cost via API from LinkedIn and Google. **How to use it:** can be used for filtering in reports to refine and rebuild the report structure to LinkedIn and Google logic --- ### 4f_Paid_campaign group *Type: **Single-line text** · Owner: Marketing Ops* is used to store the campaign group of Google and LinkedIn campaigns. It is derived from conversion URLs through these paid channels and used to find the correct campaign account to pull the cost via API from LinkedIn and Google. **How to use it:** can be used for filtering in reports to refine and rebuild the report structure to LinkedIn and Google logic --- ### 4f_Paid_campaign group ID *Type: **Single-line text** · Owner: Marketing Ops* is used to store the campaign group ID of Google and LinkedIn campaigns. It is derived from conversion URLs through these paid channels and used to find the correct campaign account to pull the cost via API from LinkedIn and Google. **How to use it:** can be used for filtering in reports to refine and rebuild the report structure to LinkedIn and Google logic --- ### 4f_Paid_campaign name *Type: **Single-line text** · Owner: Marketing Ops* is used to store the campaign name of Google and LinkedIn campaigns. It is derived from conversion URLs through these paid channels and used to find the correct campaign account to pull the cost via API from LinkedIn and Google. **How to use it:** can be used for filtering in reports to refine and rebuild the report structure to LinkedIn and Google logic --- ### 4f_Partner Involved *Type: **Dropdown*** Partner name in case a partner is part of the deal **Options:** Alpega, Kinaxis, Shippeo --- ### 4f_protocol_id *Type: **Number*** helperfield used to match the LeadScanner protocol id --- ### 4f_Start date *Type: **Date** · Owner: Marketing Ops* Start date - e.g. of events or webinars. --- ### 4f_Touchpoint conversion source 1_clean name *Type: **Dropdown** · Owner: Marketing Ops* Drill down level 1 of paid campaigns with 3rd party media, Google, LinkedIn, Bing, etc. Also used to mark specific web forms. **How to use it:** Select the correct media outlet or platform to track conversion. --- ### 4f_touchpoint_document *Type: **File** · Owner: Marketing Ops* document field, used if an attachment is stored - e.g. in inbound message. advantage: document is tied to the touchpoint (unique) and not overwritten like the document field on contact level --- ### 4f_Touchpoint Funnel Stage *Type: **Dropdown** · Owner: Marketing Ops* This property is used to qualify the marketing funnel stage the content piece serves and to indicate if a contact showed a broad or very specific interest. It is used for routing to the correct nurturing workflows and to identify gaps and overloads in content. **How to use it:** It is defined with creating the asset, documented in HubDB and filled to the touchpoints using workflows. **Values:** | Option | Meaning | When to use | |---|---|---| | **Middle of the Funnel** | [object Object] | Specific topic interest but no clear solution indication yet. | | **Top of the Funnel** | [object Object] | Broad, generic interest | --- ### 4f_Touchpoint name_dd *Type: **Dropdown** · Owner: Marketing Ops* 4flow specific dropdown select of touchpoint names such as webinar names, content pieces, event names, etc. It replaces the free text field and makes sure touchpoints can be selected easily and naming is consistent. Used in filters, in reports, etc. It also overwrites the standard touchpoint name field to make sure all touchpoint names are consistent and groupable. **How to use it:** Is updated by Marketing for each new asset and also mirrored to contact_source_level 2, lead_source_level 2, and deal_source_level 2 for consistent tracking and attribution. --- ### 4f_Touchpoint type *Type: **Dropdown** · Owner: Marketing Ops* 4flow specific dropdown select of touchpoint types. Works in conjunction with 4f_Touchpoint name_dd and 4f_activity type. **How to use it:** Is updated by Marketing for each new asset and also mirrored to contact_source_level 1, lead_source_level 1, and deal_source_level 1 for consistent tracking and attribution. **Options:** Content download, Webinar, 4flow event, Event booth meeting, Event session, Externally hosted Webinar, Marketing assessment, Inbound request, Networking event --- ### 4f_TP_Event_follow-up meeting *Type: **Radio select*** used to indicate at events if a follow-up meeting was scheduled on-site **Options:** yes, no --- ### 4f_TP_Event_Onsite 4flower *Type: **Dropdown*** Indicates whether the event is part of the 4Flower program, helping to categorize and track event participation. --- ### 4f_TP_Event_Pre-schedulded meeting *Type: **Radio select*** Indicates whether a meeting was pre-scheduled during an event. **Options:** yes, no --- ### All teams *Type: **Checkboxes*** The team IDs, including the team hierarchy, of all default and custom owner properties for this record. --- ### Business units *Type: **Checkboxes*** The business units this record is assigned to. --- ### All owner IDs *Type: **Checkboxes*** Values of all default and custom owner properties for this record. --- ### All team IDs *Type: **Checkboxes*** The team IDs of all default and custom owner properties for this record. --- ### Created by user ID *Type: **Number*** The user who created this record. This value is set automatically by HubSpot. --- ### Object create date/time *Type: **Date*** The date and time at which this object was created. This value is automatically set by HubSpot and may not be modified. --- ### Object last modified date/time *Type: **Date*** Most recent timestamp of any property update for this object. This includes HubSpot internal properties, which can be visible or hidden. This property is updated automatically. --- ### Merged record IDs *Type: **Checkboxes*** The list of record IDs that have been merged into this record. This value is set automatically by HubSpot. --- ### Record ID *Type: **Number*** The unique ID for this record. This value is set automatically by HubSpot. --- ### Record creation source *Type: **Single-line text*** Raw internal PropertySource present in the RequestMeta when this record was created. --- ### Record source detail 1 *Type: **Single-line text*** First level of detail on how this record was created. --- ### Record source detail 2 *Type: **Single-line text*** Second level of detail on how this record was created. --- ### Record source detail 3 *Type: **Single-line text*** Third level of detail on how this record was created. --- ### Record creation source ID *Type: **Single-line text*** Raw internal sourceId present in the RequestMeta when this record was created. --- ### Record source *Type: **Dropdown*** How this record was created. --- ### Record creation source user ID *Type: **Number*** Raw internal userId present in the RequestMeta when this record was created. --- ### Owning Teams *Type: **Checkboxes*** The direct teams associated to this record's owner. --- ### Pinned Engagement ID *Type: **Number*** The object ID of the current pinned engagement. This will only be shown in the app if there is already an association to the engagement. --- ### Read only object *Type: **Yes / No*** Determines whether a record can be edited by a user. **Options:** True, False --- ### Shared teams *Type: **Checkboxes*** Additional teams whose users can access the record based on their permissions. This can be set manually or through Workflows or APIs. --- ### Shared users *Type: **Checkboxes*** Additional users that can access the record based on their permissions. This can be set manually or through Workflows and APIs. --- ### Unique creation key *Type: **Single-line text*** Unique property used for idempotent creates --- ### Updated by user ID *Type: **Number*** The user who last updated this record. This value is set automatically by HubSpot. --- ### User IDs of all notification followers *Type: **Checkboxes*** The user IDs of all users that have clicked follow within the object to opt-in to getting follow notifications --- ### User IDs of all notification unfollowers *Type: **Checkboxes*** The user IDs of all object owners that have clicked unfollow within the object to opt-out of getting follow notifications --- ### User IDs of all owners *Type: **Checkboxes*** The user IDs of all owners of this record. --- ### Performed in an import *Type: **Yes / No*** Object is part of an import **Options:** True, False --- ### Owner assigned date *Type: **Date*** The most recent timestamp of when an owner was assigned to this record. This value is set automatically by HubSpot. --- ### Owner *Type: **Dropdown*** The owner of the object. --- ### Owner's main team *Type: **Dropdown*** The main team of the record owner. This value is set automatically by HubSpot. ---