2. The Lifecycle stage sync is being toggled on. With this sync toggled on, any updates to a company's Lifecycle stage value will update its associated contacts: Manage lifecycle stages sync settings.
Could we check on these and see if that's the cause of it?
If you're still seeing contact that was created by API have their lifecycle stage automatically changed to subscriber, could you share with me:
And I still se contacts becoming subscribers as soon as they're created via API 🙂
So about your requests:
1. Portal ID: 6345104
2. We use both those endpoints:
/contacts/v1/contact/createOrUpdate/email/{email}
AND
/contacts/v1/contact/batch/
3. The post body is merely {properties: [{key: value},{key: value}...]} with custom properties from our platform.. (+email for each contact when using batch)
So it looks like contact are created with a default lifecycle stage of 'Subscriber' via API.
However, as a workaround, if you'd like to set the default lifecycle stage to i.e. 'Lead', you can set up a workflow and using the 'Set contact property value' action to set the lifecycle stage.
Problem with this solution is that we only push Contacts from our platform into theirs via API and we would like to have control on which Contacts are created as Subscribers and which aren't.
Our customers may have other Contacts in their Hubspot account that are not related to the ones we are pushing and we don't want to impact their workflow.
Also, I tried creating a Workflow from our Hubspot account and it seems like there is no "lower" stage for a Contact then Subscriber.
Isn't there a concept of a Contact that has not subscribed yet, meaning he does not want to receive any Marketing Email?
If so, is there any way to define this upon Customer creation via API (adding some flag into our post body)?