Cue + HubSpot

CRM
Last updated By the Cue team5 minutes to point a code; about 15 minutes for Zapier logging

The short version

The simplest Cue-and-HubSpot pairing needs no setup at all: point printed codes at your HubSpot landing pages and forms, and every scan feeds your existing funnel. From there, Zapier can log Cue code changes into HubSpot automatically, and a developer can pull scan numbers into your campaign reporting using Cue's developer access.

Works on: Pointing codes at HubSpot pages: every plan. Automation: Business and Enterprise

What you can do with HubSpot

  • Send print traffic into your funnel

    Point codes on brochures, stands, and direct mail at HubSpot landing pages — scans arrive as visits and form fills HubSpot already knows how to track and attribute.

  • Keep the CRM aware of your codes

    Via Zapier, each new or changed Cue code can create a note, task, or record in HubSpot — so campaign records show which physical assets exist and where they point.

  • Scan numbers in campaign reports

    A developer can pull scans per code and per campaign from Cue on a schedule and write them into HubSpot as campaign data — print performance next to email and ads.

Before you start

  • For pointing codes at HubSpot pages: nothing but the page address — any Cue plan.
  • For automatic logging: a Cue Business plan and a Zapier account with premium apps.
  • For scan numbers inside HubSpot reports: a developer, using Cue's developer access (Dashboard → API).

Set it up

  1. Point codes at HubSpot pages

    Copy the address of your HubSpot landing page or form. In Cue, create a dynamic code with that address as the destination — one code per placement so you can compare them.

  2. Add Zapier if you want the CRM kept in the loop

    Follow our Zapier guide to connect Cue, then pick a HubSpot action — "Create Engagement" for a note on the campaign, or whatever fits how your team uses HubSpot.

  3. Hand the reporting wish to a developer

    If you want scan totals inside HubSpot dashboards, share Cue's developer docs with your developer — pulling numbers on a schedule is a small, well-documented job.

Good to know

  • UTM tags work well here: add them to the destination address so HubSpot attributes the visit to the right campaign and placement.
  • Cue never sends data about the people scanning — attribution happens in HubSpot from the page visit, exactly like any other traffic.
  • Cue updates flow when codes are created, changed, or retired; scan totals come from analytics on a schedule, not per scan.

Questions, answered

Can HubSpot tell me which contact scanned my code?
Only the way it already identifies any website visitor — for example, when they fill in a form after scanning. Cue deliberately doesn't identify scanners; it hands them to your page and counts the visit.
How do scans show up in HubSpot?
As visits to the landing page the code points at. Add UTM tags to the destination and HubSpot will attribute those visits to the campaign and placement, like any other tracked channel.
Do I need a developer to use Cue with HubSpot?
Not for the main uses — pointing codes at pages needs nobody technical, and Zapier logging is copy-paste. Only pushing scan totals into HubSpot reports is a developer job.

Cue

Put a code to work with HubSpot

Start free — no credit card, and printed codes that never stop redirecting.