Overview
Aimbase has integration(s) with HubSpot that allows an OEM to capture leads from their OEM website and leverage Aimbase to distribute leads to their dealer network. This is mostly used when an OEM is set up with HubSpot lead forms on their website for data capture. Not only can Aimbase distribute leads to an OEM's dealer network, but Aimbase can also send lead updates and activity back to HubSpot for tracking and reporting purposes.
Dataflow
OEM Dealer Lead Distribution
Rollick Lead Integration
Lead Update
Lead Activity
Requirements
OEM Dealer Lead Distribution Integration
This is used to send leads to an OEM Aimbase for lead distribution. Reference the Aimbase Lead API documentation. Instead of connecting directly to the Aimbase Lead API, use Zapier to push leads to our end point.
The following is required to use this integration:
- The HubSpot unique identifier must be passed in (2) different fields when sending the lead to Aimbase, see the matrix below. Without a HubSpot unique identifier, HubSpot will only be able to match lead updates and/or activities sent back by Aimbase if the the unique identifier is sent to Aimbase on the lead.
- The HubSpot unique identifier should have matching logic based on email ONLY within the OEM's HubSpot account. If there is additional matching logic other than email, further effort will need to be considered in Aimbase to send lead updates/activity the correct corresponding record in HubSpot.
Aimbase Field |
Required |
Data Type |
Description |
ProspectExternalId |
X |
String |
Provide HubSpot's unique prospect identifier. (i.e. ContactId). |
HubSpotContactId |
X |
String |
Provide HubSpot's unique prospect identifier (i.e. ContactId). This will be the same value passed in the ProspectExternalId. This should be passed in the custom object in the Lead API. |
Rollick Lead Integration
The Rollick lead integration flow will send GoRollick, DR dealer/OEM leads from an OEM website to Aimbase, and push the lead into an OEM HubSpot. This flow is used when there is a Rollick lead involved - GoRollick, Digital Retail leads on the OEM or dealer website.
Logic:
- Once the Rollick lead is created in Aimbase it will look to see if the contactid (email) already exists in the OEM HubSpot before sending the lead.
- If the contact does not exist, the contact will be created and the returned contactid will be used to send over the lead information.
- If the contact DOES exist, then the returned contactid will be used to send over the lead information to append to the existing contact.
Note: If a contactid already exists, it would be good to setup HubSpot to append the lead data that is being sent over so the user can see there is new data for that contact.
Below is the available mapping for this integration. The required field mapping will need to have a field created in HubSpot - the field name is indicated under the HubSpot field column.
Aimbase Field |
HubSpot Field |
Required |
Data Type |
Description |
Aimbase Identfier |
aimbase_identifier | X |
String |
Aimbase's internal lead identifier. |
Lead Date |
aimbase_date | X |
String |
Date the lead was sent to Aimbase. |
| Lead Type | aimbase_type | The type of lead. | ||
| Lead Source | aimbase_source | The source of the lead. | ||
| Lead Category | aimbase_category | The category of the lead. | ||
| ProductYear | aimbase_prodyear | X |
The year of the product associated with the lead. | |
| ProductName | aimbase_prodname | X |
The name of the product associated with the lead. | |
| ProductBrand | aimbase_prodbrand | X |
The brand of the product associated with the lead. | |
| Comment | aimbase_comment |
The lead's comments associated with the lead. |
||
| TimeToPurchase | aimbase_timetopurchase | The timeframe in which the lead has indicated they would like to purchase. | ||
| OptInText | aimbase_smsconsent | The lead's consent to receive SMS messages. | ||
| OptinEmail | aimbase_emailconsent | The lead's consent to receive email notifications. | ||
| stockno | aimbase_stock | The stock number associated to the product. | ||
| DealerName | aimbase_dealername | X | The name of the dealer the lead was sent to by Aimbase. | |
| MSRP | aimbase_msrp | The MSRP associated to the production on the lead. | ||
| DisplayPrice | aimbase_displayprice | The display price associated to the product on the lead. |
Lead Update Webhook
The lead update webhook sends updates back to HubSpot to provide confirmation the lead was created in Aimbase (used in conjunction with the Lead API to distribute leads to dealers), lead status changes and dealer reassignment (applies if OEM has the lead re-route feature turned on in Aimbase).
Below is a matrix identifies the HubSpot end point that each Aimbase lead update is sent to. Aimbase will include the HubSpot ContactId value with each lead update to match back to allow HubSpot to match back to the appropriate lead
| Aimbase Field | Action | Expected Values | HubSpot End Point | HubSpot Field |
| LeadCreatedDate | A lead created in Aimbase. Sending the date back to Hubspot can be used as a confirmation the lead was successfully created in Aimbase. | YYYY-MM-dd ±hh:mm |
PATCH /crm/v3/objects/contacts/{contactId} |
aimbase_lead_create_date |
| Lead Status |
Lifecycle of a lead within Aimbase. Actions such as dealer viewing a lead, customer touchpoints, closing a deal, etc would trigger these statuses to updates to HubSpot. |
· Pending (default starting point) · Viewed (lead has been opened or viewed) · Assigned (lead has been assigned to a sales rep) · Working (actively being worked to convert to a sale) · Sold (closed the lead and sold a vehicle) · Lost (purchased at another dealership) · Abandoned (gone silent, no longer returning contact attempted touch points) |
PATCH /crm/v3/objects/contacts/{contactId} |
aimbase_lead_status |
| Dealer Reassignment | When a dealer has not viewed a lead in the allotted amount of time, the lead is reassigned to the next closest dealer. OEM must have the Aimbase lead re-route feature turned on. |
PATCH /crm/v3/objects/contacts/{contactId} |
dealer_assignment-aimbase
|
|
| Rollick Score | Numeric |
PATCH /crm/v3/objects/contacts/{contactId} |
aimbase_rollick_score |
Lead Activity Webhook
The lead activity webhook sends lead activities back to Hubspot. Aimbase will include the HubSpot ContactId value with each activity to match back to allow HubSpot to match back to the appropriate lead.
The below matrix identifies the HubSpot end point that each Aimbase lead activity is sent.
| Aimbase Activity | Action | Expected Values | HubSpot End Point | HubSpot Timeline |
| PhoneCall/Concierge Call | Dealer has logged a call to the lead in their CRM. Or, Rollick's concierge has called the lead. |
· Call |
/crm/v3/objects/calls |
Call |
| Email/Autoresponders/E-Newsletter/Nurture/Campaign | Dealer touch points with the prospect are captured from their CRM. | · Email |
/crm/v3/objects/emails |
Email |
| Appointment/Concierge Appointment | Dealer has logged an appointment in their CRM. Or, Rollick's concierge has scheduled appointment on dealer's behalf. | Meeting |
/crm/v3/objects/meetings |
Meeting |
| SMS | Dealer has logged sending a SMS in their CRM. | SMS |
/crm/v3/objects/communications |
? |
| Comment | Dealer or corporate users add a comment on a lead within Aimbase. |
Notes |
/crm/v3/objects/notes | Notes |