But have you considered what the goal of your workflow is?

[Habib01]

Now that we understand standard objects, their properties, and the associations between them, let's explore HubSpot custom objects.

hubspot-custom-objects

Custom objects are exactly what their name suggests. They allow you to extend HubSpot's functionality, giving you the flexibility to define objects as your business data requires, beyond the scope of standard objects.

This means you can customize your CRM and website to fit your data schema, not the other way around.

HubSpot custom objects look and act exactly like standard objects, and can be iceland consumer email list used in reporting, marketing campaigns, and accessed by all users. They can even be associated with other standard or custom objects, just like your standard objects.

hubspot-custom-objects

When are custom objects used versus standard objects?
The biggest trigger for knowing that you need a custom object should be identifying whether the relationship between the information is one-to-one or one-to-many.

For example, if you are trying to determine whether to use a standard or custom object to store information in the email client a company uses, you would consider whether it is a single value or multiple values.

Do companies use one or more email clients for their business? In most cases, this is just one, and you could easily create a custom property to store the name of the email client they use.

But if you wanted to keep track of the certificates that one of your students has completed, would that also be one-to-one? No, because a student could have completed multiple certificates that you need to track. In this case, you could also create custom properties to keep track of certificates, but how many would you create? Certificate 1, certificate 2, certificate 3, and so on.