When creating contacts records on Hubspot, they are automatically marked as Marketing Contacts which would automatically increase the plan and costs as the account would move into an upgraded tier. There should be a way to be able to select non-marketing contact as a status
We don't have a direct setting to automatically set contacts as non-marketing by default when creating records in HubSpot through our integration. However, you can achieve this by customizing the contact properties when creating or updating contacts.When using our "Create or Update Contact with HubSpot" action, you can include a custom field for the marketing status. Set this field to indicate the contact should not receive marketing communications. This approach allows you to control the marketing status of new contacts, potentially helping manage your HubSpot plan costs.To better assist you, could you clarify if you're currently using our native HubSpot integration or if you're on a plan that requires using the HubSpot API directly? Source: Create or Update Contact with HubSpot
Wondering what the current state of the Hubspot Marketable Contacts capability is?
I've realized I'm not seeing the hs_marketable_status field when I import contacts, however, if I subsequently perform an Object Lookup using the contact's ID I will get the field.
I also don't have a way to set the property when creating contacts that are written back to Hubspot. That said, I suppose this is a preferred default state to the above so that Contacts can be toggled to Marketable via a workflow, rather than incurring the Marketable cost upfront.
Currently, our HubSpot integration doesn't have a direct setting to automatically set contacts as non-marketing by default when creating records. However, you can manage this through our "Create or Update Contact with HubSpot" action. To set the "hs_marketable_status" property when creating contacts: 1. Use the "Create or Update Contact with HubSpot" action. 2. Include a custom field for the "hs_marketable_status" property. 3. Set this field to indicate the contact should not receive marketing communications. This approach allows you to control the marketing status of new contacts, potentially helping manage your HubSpot plan costs. To better assist you, could you clarify if you're using our native HubSpot integration or if you're on a plan that requires using the HubSpot API directly?
I'm using the native Hubspot integration. I don't know what you mean about "including a custom field for the hs_is_marketable_status property" unless that's a capability only exposed in the legacy integration.
Hey, youāre right ā we donāt currently expose the hs_marketable_status property in our integration for contact creation. Thatās why youāre only seeing it appear after doing an Object Lookup using the contact ID. If you need to update that field, the best workaround is to use a custom HTTP API call directly to HubSpot. Alternatively, you can manage the marketable status through a HubSpot workflow after contact creation. Let me know if youād like help setting up that API call or workflow.
Awesome; thank you for the confirmation on creation. Would you happen to know about the visibility of the hs_is_marketable_status property or the various Hubspot/Salesforce sync properties, particularly from the Bulk Load operation (e.g. when initially populating the table using the Explorer+ tier integration)? On Contact that would be:
.png){kind=logo}
salesforcedeleted
salesforcecontactid
salesforceaccountid
salesforceleadid
salesforcecampaignids
salesforcelastsynctimeOn Account that would be:
salesforcedeleted
salesforceaccountid
salesforcelastsynctimeOn Deal that would be:
salesforcedeleted
salesforceopportunityid
salesforcelastsynctime(Unfortunately I don't have visibility into the salesforce properties of the Lead model). Here's why this matters: it is of vital importance when using both Salesforce and Hubspot together to know if a Hubspot record is also syncing with a corresponding record in Salesforce. A shocking number of organizations will use Salesforce for their sales teams and active customer account management, but rely on HubSpot for tracking marketing activities (unfortunately this includes my organization). Hubspot maintains a record for ALL contacts, but will treat records in Salesforce as sacrosanct by default if it also exists there. More specifically, if a record exists in Salesforce, then there is a populated value for that field. The HubSpot UPDATE APIs will accept the change and then automatically revert back to the state in Salesforce. Clay (and the user) would get no notification that this field reversion happened. Knowing ahead of time means the builder of the Clay workflow could decide to:
avoid enriching entirely records that exist in Salesforce
only enrich the fields that are blank
Make an update to these records in Salesforce, rather than Hubspot
Hey! Yes, most of the Salesforce sync properties you mentionedālike salesforcedeleted, the various IDs, and sync timestampsāare typically available when using Bulk Load, depending on your integration settings. If youāre referring to the ālast syncā field, it could be lastmodifieddate, lastreferenceddate, or another similar timestampāthis can vary based on how your Salesforce instance is set up. Feel free to connect your Salesforce account, and I can help you troubleshoot or confirm exactly whatās showing up in your setup.
I've just started to do the workaround of batch loading records to get IDs then having a subsequent individual record lookup to get associated properties. Working pretty well so far, though I do wish the pattern were more self-evident. Meanwhile for newly loaded contacts: I think the best course of action is to just have a Hubspot Workflow flip their status.
Glad to hear itās working so far ā definitely keep us posted if anything comes up or if you hit any snags.