# HubSpot Data Integration # Tables integrated: - deals: All information about user deals **(We need to deal with timestamps figuring out which id represents which stage on the lifecycle)** - id: - archived: irrelevant - contacts: - companies: - createdAt: - updatedAt: - line_items: unused for now, but will be used to show what services they originally signed up for - properties: - hubspot_owner_id: owner in Superhog responsible for one or multiple deal_ids, the one that brought the account in - dedicated_am: account manager’s name in Superhog - createdate: date that the account was created in HubSpot - contract_signed_date: date in which the contract was signed - live_date: date in which the account went live - cancellation_date: date in which an account that was being used was cancelled - dealname: name of the deal - sales_stage: stage on the lifecycle of the sales team - dealstage: id stage related to the lifecycle of sales - deal_source: general source of where did the deal/opportunity came from - lead_source: Inbound/Outbound - amount_of_properties: amount of properties the owner told us they manage - demo_scheduled: boolean - sales_demo_scheduled: date at which the demo is scheduled for - demo_completed: boolean - meeting_status__hubspot_: detail of what happen during demo - cancellation_category: categorization as to why they cancelled the account - cancellation_details: free text explaining why they cancelled the account - last_nps_survey_date: date when the response of the form is sent - last_nps_survey_rating: rating if the survey form - last_nps_survey_comment: free text of the survey response - customer_nps_sentiment: 9-10: promoter - 6-8: passive - <6: detractor - notes_last_contacted: date and time of last contact between account manager and the account owner - num_contacted_notes: number of times the account manager has contacted the owner - free_trial_start_date: date at which the free trial for the dashboard began - free_trial_end_date: date at which the free trial for the dashboard expired - date_meeting: date for when the onboarding is booked for - onboarding_stage: stage on where the onboarding is currently at, when completed is set to ‘no value’ - onboarding_owner: responsible for onboarding, could be the same account manager but not always - onboarding_call_completed: boolean for completed onboarding - onboarding_owner__cloned_: owner of onboarding that could replace onboarding_owner - meeting_scheduled: boolean for scheduled onboarding - contacts: Contact information for user deals - form_submissions: - forms: - tickets **(All host tickets go to host services or account managers and guest tickets go to guest services)**: - id: unique id for each ticket - hs_object_id: should be the same as the one on id - hs_ticket_category: categorization of the ticket set by the account manager based on the conent on the ticket, manual process - createdate: creation date - closed_date: date at which the ticket was closed - hs_num_times_contacted: amount of times there was any kind of contact between the account manager and the owner - department_involved: if there are any other or others departments involved into solving the ticket - csat_account_management_sentiment: csat raitng for account manager; happy - neutral - unhappy (all these surveys are send to the owner once the ticket is closed) - csat_account_management_response: free text for the resolution of the ticket - csat_host_services_sentiment: csat raitng for host; happy - neutral - unhappy - csat_host_services_response: free text for the resolution of the ticket - hs_pipeline: shows the apartment that is currently responsible for handling the ticket - first_agent_reply_date: date of when the first reply was sent from our side - hs_lastactivitydate: date of last occurrence regarding the ticket - hs_lastcontacted: date of last contact with the ticket owner - last_reply_date: date of last reply from the customer - hubspot_owner_id: hubspot id of person on superhog responsible of the ticket - guest_ticket_category: category selected by person dealing with the ticket (Only for guest related tickets) - content: free text describing the ticket from the customer - source_type: source of where the ticket comes from, email, phone call, etc… - engagements: - id_engagements: - Include engagement tables so we can have more details into the contact/relationship between account managers and owners