Integration Products | Campaign Creators

CDK Global HubSpot Integration | Campaign Creators

Written by Campaign Creators | Nov 17, 2026, 2:10:38 PM
Integration Assessment
Integration Assessment · Automotive

CDK Global × HubSpot

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 DMSFortellis APIsREST / JSONAsync APIs (events)Customers, vehicles, deals, ROsMulti-rooftop dealer groups
Platform ownerCDK Global
Integration typeCustom build on CDK APIs via Fortellis
Primary directionCDK → HubSpot
FeasibilityBuildable, dealer-authorized
API accessOpen with conditions
01 — Summary

Does CDK integrate with HubSpot?

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.

API access
Open APIOpen with conditionsGated API

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.

Scorecard
Data richnessHigh
API accessSubscription + dealer consent
Public docsPartial
Build complexityMod–High

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.

Strength

Sales and service in one source

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.

Plan for

Customer financial data stays out

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.

Gate

Fortellis subscription and dealer activation

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.

02 — API modules

Which CDK APIs does the integration use?

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.

Core

Customer API

CDK Drive · Fortellis

The DMS customer: name, contact details and addresses for buyers and service customers at each dealership.

  • Primary source for HubSpot contacts
  • Business customers become HubSpot companies
  • Field list confirmed in discovery
Core

F&I Sales API

CDK Drive · Fortellis

Sold deals: the vehicle, new or used, sale date and the deal type, including finance and lease terms where the deal carries them.

  • Each sale becomes a closed HubSpot deal
  • Term and contract dates drive maturity campaigns
  • Credit data excluded from the field list
Core

Repair Order API

CDK Drive · Fortellis

Service visits: customer, vehicle, open and close dates, mileage and the work performed, with op codes looked up through the Op Code API.

  • Each RO becomes a Service Visit record
  • Last service date and mileage on the vehicle
  • Op codes power service-due rules
Core

Vehicles & Make Model

Vehicles API · Make Model API

The vehicle by VIN with year, make and model, queried by VIN, license plate or customer.

  • VIN is the vehicle's unique key
  • One Vehicle custom object per VIN
  • Ownership links customer and vehicle
Real time

Service Appointment API & Async APIs

Appointments · event delivery on Fortellis

Service appointments, with Async APIs that push appointment, repair order and customer changes with ordered, durable delivery secured by OAuth 2.0.

  • Appointment booked or changed updates HubSpot
  • RO status changes reach HubSpot as events
  • Polling covers anything without an event
History & gaps

Data Your Way

Data Export Tool · Data Export/Import Tool

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.

  • Useful for the first backfill
  • Exports encrypted with PGP
  • Dealer chooses what is shared
Scope decision

Credit, identity & accounting data

Credit applications · SSNs · GL

Credit applications, Social Security and driver's license numbers, credit scores and dealership accounting stay in CDK. HubSpot receives deal facts and dates only.

  • Field list approved by the dealer's security lead
  • No credit or identity numbers in HubSpot
  • Any exception approved in writing
03 — Framework

How does the CDK HubSpot integration work?

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.

CDK Drive via Fortellis
Customer APIbuyers and service customers
F&I Sales APIsold deals, new and used
Repair Order APIservice visits, op codes
Vehicles & appointmentsVIN, year, make, model, bookings
CC integration layer
Fortellis clientOAuth 2.0 token, Subscription-Id per rooftop
Event intakeAsync API events, queued
Identity resolverCDK customer ID · email · phone · VIN
Privacy filterdrops credit and identity fields
HubSpot writerbatch upserts, associations, replay
HubSpot
Contacts & Companiesretail and business customers
Vehicles (custom object)one record per VIN
Dealssales pipeline, new and used
Service Visits (custom object)one record per repair order
Lists, workflows & reportsmaturity, service-due, rooftop views
CDK → HubSpot (customers, vehicles, deals, repair orders, appointments)HubSpot → CDK (contact updates only where a write API is subscribed)
Principle

CDK owns the transaction

Deals, repair orders and accounting are created and changed in CDK. HubSpot receives them and never edits them.

Principle

The vehicle is a record

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.

Principle

Least data, by design

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.

04 — Process

What does CDK HubSpot integration setup involve?

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.

1

Discovery & access

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.

Gate to next phaseAPIs selected and sample calls working
2

Privacy & field approval

Agree the field list with the dealer's security lead under its written information security program, and confirm what customer data HubSpot may hold.

Gate to next phaseSigned field list and data handling notes
3

HubSpot data model

Create the Vehicle, Service Visit and Rooftop custom objects, the sales pipeline, association labels, and rollup properties in a HubSpot sandbox.

Gate to next phaseSchema approved and created in sandbox
4

Build & certification

Build the Fortellis client, event intake, identity resolver, privacy filter and batch writer with replay. Complete Fortellis certification, then the dealer activates the app.

Gate to next phaseFirst rooftop activated and syncing in sandbox
5

Backfill

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.

Gate to next phaseCounts reconcile to CDK reports within an agreed tolerance
6

Campaigns & reporting

Build lease and finance maturity, service-due, first-service and post-sale workflows, and rooftop and campaign dashboards.

Gate to next phaseDealer walkthrough and sign-off of each automation
7

Parallel run & launch

Run live for two weeks with sends paused, compare HubSpot to CDK daily, then enable sends and activate the remaining rooftops in waves.

Gate to next phaseFive consecutive days with no unresolved sync errors
05 — Data mapping

What does the CDK HubSpot integration sync?

CDK fields are described plainly. Exact field names and paths come from each API's specification on Fortellis and are confirmed during discovery.

CDK fieldHubSpot propertyObjectDirectionNotes
Customers · Customer API
Customer ID (per dealership)cdk_customer_idContactCDK → HSPrimary external key, stored with the rooftop. Confirm in discovery.
EmailemailContact↔ BothMatch key #1. Fill blanks only.
Phone numbersphone, mobilephoneContact↔ BothMatch key #2. Normalized before matching.
First and last namefirstname, lastnameContactCDK → HSNever overwrite with empty values.
Mailing addressaddress, city, state, zipContactCDK → HSUsed for market area segments.
Business customer namename, cdk_business_customer_idCompanyCDK → HSFleet and business buyers.
Contact preferencesSubscription typesContactCDK → HSWhere the DMS holds them. Confirm in discovery.
Vehicles · Vehicles & Make Model APIs
VINcdk_vinVehicle (custom)CDK → HSUnique key for the Vehicle record.
Year / make / model / trimcdk_year, cdk_make, cdk_model, cdk_trimVehicle (custom)CDK → HSModel names from the Make Model API.
Owner (customer)Contact associationVehicle (custom)CDK → HSLabel: current owner. Prior owners kept as history.
Last known mileagecdk_last_mileageVehicle (custom)CDK → HSFrom the latest repair order.
Sales · F&I Sales API
Deal numbercdk_deal_numberDealCDK → HSUnique per rooftop.
Sale type (new / used)cdk_sale_typeDealCDK → HSDrives pipeline reporting.
Sale dateclosedateDealCDK → HSDeal closed won in the sales pipeline.
Selling priceamountDealCDK → HSConfirm which price field the dealer reports on.
Deal type (cash / finance / lease)cdk_deal_typeDealCDK → HSConfirm field in discovery.
Term and contract datecdk_term_months, cdk_contract_dateDealCDK → HSUsed to calculate maturity date.
Calculated maturity datecdk_maturity_dateVehicle (custom)CDK → HSContract date plus term. Computed in the integration layer.
Salespersonhubspot_owner_idDealCDK → HSMatched through the Employee API.
Service · Repair Order & Appointment APIs
RO numbercdk_ro_numberService Visit (custom)CDK → HSUnique per rooftop.
Open and close datescdk_ro_open_date, cdk_ro_close_dateService Visit (custom)CDK → HSClose date updates last service date.
Op codes performedcdk_op_codesService Visit (custom)CDK → HSDescriptions from the Op Code API.
Customer-pay totalcdk_ro_customer_payService Visit (custom)CDK → HSConfirm labor and parts split in discovery.
Last service datecdk_last_service_dateVehicle (custom)CDK → HSLatest closed RO for the VIN.
Service appointment date and statuscdk_next_appointmentVehicle (custom)CDK → HSFrom the Service Appointment API and Async events.
06 — Auth & API

How are authentication and API limits handled?

Fortellis handles authentication and access for CDK APIs. Values CDK does not publish are marked for confirmation.

TopicCDKHubSpot
AuthenticationOAuth 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 modelFree 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-rooftopActivations 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 timeAsync 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 / backfillAPI 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 & limitsAPI pricing and rate limits: not published. Confirm with CDK.Per-10-second burst and daily limits by subscription tier.
Sensitive dataCustomer 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.
07 — Issues & opportunities

What should you plan for, and what does the integration unlock?

Severity reflects impact on the SOW, not technical difficulty alone.

Challenges to plan for

Dealer activation sits on the critical pathHigh

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.

Safeguards Rule obligationsHigh

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.

API fees and field coverageMedium

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.

One customer, many rooftopsMedium

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.

Data quality in the DMSMedium

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.

APIs are changingLow

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.

Opportunities in HubSpot

Lease and finance maturity campaignsHigh value

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.

Service-due and first-service remindersHigh value

Last service date, mileage and op codes drive reminders that bring owners back to the service drive, by rooftop.

Service-to-sales signalsHigh value

Owners of older or high-mileage vehicles who visit service become sales opportunities with a task for the right salesperson.

Campaign attribution to sold unitsMedium value

HubSpot form and ad leads are linked to sold deals, so marketing reports cars sold and gross by campaign and rooftop.

Post-sale and post-service follow-upMedium value

Delivery and repair order close start thank-you and survey emails; low scores open a ticket for the store manager.

Group-wide customer viewMedium value

One contact shows every vehicle, deal and service visit across all rooftops in the group.

Core ownership journey

One customer, from purchase to the next car.

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.

  1. A sold deal in CDK creates the HubSpot contact, a closed deal and a Vehicle record for the VIN.
  2. Delivery starts a post-sale series and schedules the first-service reminder.
  3. Each repair order updates last service date and mileage, which drive service-due campaigns.
  4. As the maturity date approaches, the owner enters a trade-in series that hands a warm lead back to sales.
08 — Property schema

Which HubSpot properties does the integration create?

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 nameLabelObjectTypeSource / logic
cdk_customer_idCDK Customer IDContactSingle-line textDMS customer ID with rooftop; unique
cdk_total_vehicles_purchasedVehicles PurchasedContactNumberCount of sold deals
cdk_last_purchase_dateLast Purchase DateContactDateLatest sale date
cdk_vinVINVehicleSingle-line textVehicle identification number; unique
cdk_makeMakeVehicleDropdownMake Model API
cdk_modelModelVehicleSingle-line textMake Model API
cdk_maturity_dateLease / Finance MaturityVehicleDateContract date plus term
cdk_last_service_dateLast Service DateVehicleDateLatest closed repair order
cdk_last_mileageLast MileageVehicleNumberFrom latest repair order
cdk_sale_typeSale TypeDealDropdownNew or used
cdk_deal_typeDeal TypeDealDropdownCash, finance or lease
cdk_ro_numberRO NumberService VisitSingle-line textRepair order number; unique per rooftop
09 — Scope builder

Interactive scope builder

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.

Scope summary

0Fields
0Inbound
0Write-back
CDK × HubSpot Integration Assessment · Designed by Campaign Creators, Elite HubSpot Solutions Partner

CDK HubSpot integration FAQ

Does CDK integrate with HubSpot?

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.

What data syncs between CDK and HubSpot?

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.

Which system owns which data?

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.

What does setting up the CDK HubSpot integration involve?

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.

How long does the integration take and what does it cost?

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.