How a dealer group can bring CDK Drive customers, vehicles, sales deals and service repair orders into HubSpot through CDK's Fortellis APIs, so marketing can run lease, finance and service-due campaigns and leaders can report across every rooftop.
CDK Drive is the dealer management system many franchised dealers run sales, F&I, service and parts on. Marketing teams need the same customers, vehicles, deals and service visits in HubSpot to plan campaigns, keep owners coming back to the service drive, and see which campaigns sell cars.
Public documentation, but production access needs vendor approval, certification, a paid license or a specific plan.
Open with conditions. A free Fortellis developer account and sample data are self-serve. Production needs Fortellis certification, paid API subscriptions and activation by an authorized signer at each dealership.
Based on the vendor's public documentation. Access terms are confirmed with the vendor and the client in discovery.
CDK publishes customer, deal, repair order and appointment data as REST APIs on Fortellis, so HubSpot can follow each customer and vehicle from purchase through every service visit.
Campaign Creators assessment
Fortellis is CDK's API platform and marketplace. It lists CDK Drive APIs for customers, vehicle make and model, service appointments, F&I sales, repair orders, op codes, employees and parts sales, all REST/JSON, plus Async APIs that push appointment, repair order and customer events. CC builds the integration directly on these APIs. Access is the deciding factor: each API is used under a Fortellis subscription, and an authorized signer at the dealership activates the app with their CDK credentials before any data flows. CDK's Data Your Way export tools are a second path for history and data sets the APIs do not cover.
Ratings are CC judgments from CDK and Fortellis public materials. API availability, field lists, fees and limits are confirmed with CDK and the dealer group during discovery.
One DMS holds the customer, the vehicle by VIN, the deal and every repair order. That is the full ownership story HubSpot needs for lifecycle marketing.
Deal jackets hold credit and identity data covered by the FTC Safeguards Rule. The integration brings deal facts and dates into HubSpot, never Social Security numbers, credit applications or credit scores.
The app is registered on Fortellis, certified, and subscribed to each API. An authorized dealership signer then activates it, rooftop by rooftop, before production calls work.
Seven parts of the CDK platform matter to HubSpot. Five carry the integration, one fills gaps for history, and one stays inside CDK by design.
The DMS customer: name, contact details and addresses for buyers and service customers at each dealership.
Sold deals: the vehicle, new or used, sale date and the deal type, including finance and lease terms where the deal carries them.
Service visits: customer, vehicle, open and close dates, mileage and the work performed, with op codes looked up through the Op Code API.
The vehicle by VIN with year, make and model, queried by VIN, license plate or customer.
Service appointments, with Async APIs that push appointment, repair order and customer changes with ordered, durable delivery secured by OAuth 2.0.
CDK's data tools for dealers: scheduled SFTP exports of sales, service, parts and accounting data, and on-demand extract and write-back through legacy API packages.
Credit applications, Social Security and driver's license numbers, credit scores and dealership accounting stay in CDK. HubSpot receives deal facts and dates only.
A CC-hosted integration layer calls the CDK APIs on Fortellis for each subscribed rooftop, receives Async API events, matches customers and vehicles to HubSpot records, and writes in batches. HubSpot runs marketing and reporting; CDK stays the system for deals, service and accounting.
Deals, repair orders and accounting are created and changed in CDK. HubSpot receives them and never edits them.
Each VIN is a HubSpot Vehicle linked to its current owner, its deal and its service visits, so campaigns target the car as well as the person.
The field list is approved by the dealer's security lead. Credit and identity numbers never leave CDK, which keeps HubSpot out of the most sensitive scope.
Each phase ends on a gate the dealer group signs off before the next begins. Rooftops go live in waves, so the first store runs on HubSpot while the next is activated.
List the rooftops and CDK products in use. Register the app on Fortellis, choose the APIs, and test against Fortellis sample data. Identify the authorized signer at each dealership.
Agree the field list with the dealer's security lead under its written information security program, and confirm what customer data HubSpot may hold.
Create the Vehicle, Service Visit and Rooftop custom objects, the sales pipeline, association labels, and rollup properties in a HubSpot sandbox.
Build the Fortellis client, event intake, identity resolver, privacy filter and batch writer with replay. Complete Fortellis certification, then the dealer activates the app.
Load customers, vehicles, sold deals and repair orders for an agreed history window, from the APIs or a Data Your Way export, then compute rollups once.
Build lease and finance maturity, service-due, first-service and post-sale workflows, and rooftop and campaign dashboards.
Run live for two weeks with sends paused, compare HubSpot to CDK daily, then enable sends and activate the remaining rooftops in waves.
CDK fields are described plainly. Exact field names and paths come from each API's specification on Fortellis and are confirmed during discovery.
| CDK field | HubSpot property | Object | Direction | Notes |
|---|---|---|---|---|
| Customers · Customer API | ||||
| Customer ID (per dealership) | cdk_customer_id | Contact | CDK → HS | Primary external key, stored with the rooftop. Confirm in discovery. |
| Contact | ↔ Both | Match key #1. Fill blanks only. | ||
| Phone numbers | phone, mobilephone | Contact | ↔ Both | Match key #2. Normalized before matching. |
| First and last name | firstname, lastname | Contact | CDK → HS | Never overwrite with empty values. |
| Mailing address | address, city, state, zip | Contact | CDK → HS | Used for market area segments. |
| Business customer name | name, cdk_business_customer_id | Company | CDK → HS | Fleet and business buyers. |
| Contact preferences | Subscription types | Contact | CDK → HS | Where the DMS holds them. Confirm in discovery. |
| Vehicles · Vehicles & Make Model APIs | ||||
| VIN | cdk_vin | Vehicle (custom) | CDK → HS | Unique key for the Vehicle record. |
| Year / make / model / trim | cdk_year, cdk_make, cdk_model, cdk_trim | Vehicle (custom) | CDK → HS | Model names from the Make Model API. |
| Owner (customer) | Contact association | Vehicle (custom) | CDK → HS | Label: current owner. Prior owners kept as history. |
| Last known mileage | cdk_last_mileage | Vehicle (custom) | CDK → HS | From the latest repair order. |
| Sales · F&I Sales API | ||||
| Deal number | cdk_deal_number | Deal | CDK → HS | Unique per rooftop. |
| Sale type (new / used) | cdk_sale_type | Deal | CDK → HS | Drives pipeline reporting. |
| Sale date | closedate | Deal | CDK → HS | Deal closed won in the sales pipeline. |
| Selling price | amount | Deal | CDK → HS | Confirm which price field the dealer reports on. |
| Deal type (cash / finance / lease) | cdk_deal_type | Deal | CDK → HS | Confirm field in discovery. |
| Term and contract date | cdk_term_months, cdk_contract_date | Deal | CDK → HS | Used to calculate maturity date. |
| Calculated maturity date | cdk_maturity_date | Vehicle (custom) | CDK → HS | Contract date plus term. Computed in the integration layer. |
| Salesperson | hubspot_owner_id | Deal | CDK → HS | Matched through the Employee API. |
| Service · Repair Order & Appointment APIs | ||||
| RO number | cdk_ro_number | Service Visit (custom) | CDK → HS | Unique per rooftop. |
| Open and close dates | cdk_ro_open_date, cdk_ro_close_date | Service Visit (custom) | CDK → HS | Close date updates last service date. |
| Op codes performed | cdk_op_codes | Service Visit (custom) | CDK → HS | Descriptions from the Op Code API. |
| Customer-pay total | cdk_ro_customer_pay | Service Visit (custom) | CDK → HS | Confirm labor and parts split in discovery. |
| Last service date | cdk_last_service_date | Vehicle (custom) | CDK → HS | Latest closed RO for the VIN. |
| Service appointment date and status | cdk_next_appointment | Vehicle (custom) | CDK → HS | From the Service Appointment API and Async events. |
Fortellis handles authentication and access for CDK APIs. Values CDK does not publish are marked for confirmation.
| Topic | CDK | HubSpot |
|---|---|---|
| Authentication | OAuth 2.0 client credentials from Fortellis identity, using the app's key and secret. Calls carry a Subscription-Id header for the dealer's activation and a Request-Id. | Private app access token or OAuth 2.0 public app, scoped per object. |
| Access model | Free developer account and sample data. Production needs Fortellis certification and API subscriptions; a dealership authorized signer activates the app with their CDK credentials. | Self-serve in the client portal. Custom objects need an Enterprise hub. |
| Multi-rooftop | Activations are made per dealership. Confirm in discovery how each rooftop (CMF account) is covered by the group's subscriptions. | One portal for the group; a Rooftop custom object separates stores in lists and reports. |
| Real time | Async APIs push appointment, repair order and customer events with ordered, durable delivery secured by OAuth 2.0. Other data is polled. | Webhooks and workflows for HubSpot-side changes such as unsubscribes. |
| Bulk / backfill | API queries by date and status, or Data Your Way scheduled SFTP exports (PGP encrypted) for history. | Batch create and update endpoints, and CRM imports for the first load. |
| Fees & limits | API pricing and rate limits: not published. Confirm with CDK. | Per-10-second burst and daily limits by subscription tier. |
| Sensitive data | Customer financial information falls under the GLBA and the FTC Safeguards Rule. Credit applications, SSNs, driver's license numbers and credit scores are excluded. | Sensitive data properties on Enterprise if needed; field permissions by team. |
Severity reflects impact on the SOW, not technical difficulty alone.
No production call works until the app is subscribed on Fortellis and each dealership's authorized signer activates it. Put activation per rooftop in the SOW as a client-owned, dated dependency.
The dealer must oversee service providers that touch customer information. Plan for the dealer's vendor review, a written field list, MFA on every admin login, and encryption in transit and at rest.
CDK does not publish API pricing or full field lists publicly. Budget a discovery spike to confirm the fields each API returns, especially finance and lease terms, and the subscription cost.
A customer can exist at several dealerships with different CDK customer IDs. Matching runs on email, phone and VIN in a set order, and each rooftop's ID is kept on the record.
Service customers often have missing or shared emails. Measure the identified rate in the audit, and report service retention by vehicle when the contact is unknown.
CDK is moving integrations to modern REST APIs on Fortellis in waves. Build against the current Fortellis APIs and confirm the version for each one in discovery.
Each vehicle carries a maturity date, so owners nearing the end of a lease or loan enter a timed series with trade-in and new-model offers.
Last service date, mileage and op codes drive reminders that bring owners back to the service drive, by rooftop.
Owners of older or high-mileage vehicles who visit service become sales opportunities with a task for the right salesperson.
HubSpot form and ad leads are linked to sold deals, so marketing reports cars sold and gross by campaign and rooftop.
Delivery and repair order close start thank-you and survey emails; low scores open a ticket for the store manager.
One contact shows every vehicle, deal and service visit across all rooftops in the group.
The integration follows one customer and one vehicle through the dealership lifecycle, with CDK running sales and service and HubSpot running every campaign and report around them.
All custom properties use the cdk_ prefix in a CDK property group. Rollups and maturity dates are calculated in the integration layer so every report agrees.
| Internal name | Label | Object | Type | Source / logic |
|---|---|---|---|---|
| cdk_customer_id | CDK Customer ID | Contact | Single-line text | DMS customer ID with rooftop; unique |
| cdk_total_vehicles_purchased | Vehicles Purchased | Contact | Number | Count of sold deals |
| cdk_last_purchase_date | Last Purchase Date | Contact | Date | Latest sale date |
| cdk_vin | VIN | Vehicle | Single-line text | Vehicle identification number; unique |
| cdk_make | Make | Vehicle | Dropdown | Make Model API |
| cdk_model | Model | Vehicle | Single-line text | Make Model API |
| cdk_maturity_date | Lease / Finance Maturity | Vehicle | Date | Contract date plus term |
| cdk_last_service_date | Last Service Date | Vehicle | Date | Latest closed repair order |
| cdk_last_mileage | Last Mileage | Vehicle | Number | From latest repair order |
| cdk_sale_type | Sale Type | Deal | Dropdown | New or used |
| cdk_deal_type | Deal Type | Deal | Dropdown | Cash, finance or lease |
| cdk_ro_number | RO Number | Service Visit | Single-line text | Repair order number; unique per rooftop |
Choose the fields for this engagement and the direction each one syncs. Required fields are the keys the integration cannot run without. Copy the summary into the SOW or a reply to the dealer group.
Based on public documentation. API subscriptions, fees, field lists and dealer activation are confirmed with CDK and the dealer group during discovery.
Yes, through Fortellis, CDK’s API platform. It lists CDK Drive REST APIs for customers, vehicles, F&I sales, repair orders and service appointments, plus Async APIs that push events. Campaign Creators builds a custom integration on these; production access needs Fortellis certification, API subscriptions and activation by an authorized signer at each dealership.
Customers sync to HubSpot contacts and business customers to companies; each VIN becomes a Vehicle custom object; sold deals sync to HubSpot deals with term and contract dates; and repair orders sync to a Service Visit custom object, with service appointments updating as they change. Credit applications, Social Security numbers and credit scores never leave CDK.
CDK owns the transaction: deals, repair orders and accounting are created and changed in CDK, and HubSpot receives them and never edits them. HubSpot runs marketing and reporting across rooftops. Contact updates go back to CDK only where a write API is subscribed.
Seven phases, each closed by a dealer group sign-off: discovery and access, privacy and field approval, the HubSpot data model, build and Fortellis certification, backfill, campaigns and reporting, and a two-week parallel run before the remaining rooftops are activated in waves.
Timeline and cost depend on the rooftops, APIs and fields in scope (for example the Fortellis API subscriptions, the history window to backfill and the campaigns to build). Campaign Creators confirms these in discovery and provides a fixed scope before the build starts.