How to Connect HockeyStack to Your CRM and Ad Data
Connecting HockeyStack means three separate jobs: installing the tracking script on your site to capture web behaviour, syncing your CRM (HubSpot or Salesforce) to bring in deal data, and linking ad platforms so spend and campaign data join the same graph. Sources are managed under Settings → Data Sources.
Order matters more than most onboarding docs admit. If you connect the CRM before web tracking is live and clean, HockeyStack backfills deals with no touchpoint history and your first attribution report shows channels as “Direct” for months of pipeline.
What does HockeyStack actually connect to?
Three families of source:
- Web tracking — a JavaScript snippet capturing page views, form submits, UTM parameters, and anonymous-to-identified identity resolution.
- CRM — native connectors for HubSpot and Salesforce, pulling accounts, contacts, opportunities, and deal stages with history.
- Ads and channels — Google Ads, Meta, LinkedIn, Bing, plus G2 and review sites, bringing spend and campaign structure.
HockeyStack also supports warehouse sync (Snowflake, BigQuery) and a REST API for anything custom.
How do you install the tracking script?
- In HockeyStack, go to Settings → Data Sources → Web Tracking and copy the snippet.
- Put it in the the head section of every page — GTM is fine, but use a tag that fires on all pages rather than an exception list.
- Verify with the browser extension or the Live Events view: load your site and confirm events appear in under 30 seconds.
- Check form tracking. Most form submissions in modern stacks are JS-driven and produce no page reload; confirm the identify event fires.
The identity resolution setting people skip
Anonymous visitors become known contacts when they submit a form or when you match their email against your CRM. HockeyStack stores both identities and stitches them. If your form vendor (Typeform, Webflow forms, Marketo) does not pass the email into the page where HockeyStack can read it, the stitch fails and every anonymous touchpoint stays anonymous.
Test it: fill out a real form with a test email, then search that email in HockeyStack. If the earlier anonymous sessions do not appear on the profile, the stitch is broken and your attribution will underreport content and paid.
How does the CRM sync work?
Connect HubSpot or Salesforce from Data Sources and authorise with an admin account. HockeyStack then pulls objects on a recurring sync, typically every few hours depending on plan.
Things to check before you trust the numbers:
| Check | Why it matters |
|---|---|
| Deal stage mapping | Your custom stages must map to HockeyStack’s funnel model |
| Owner field | Needed for rep-level reporting |
| Amount currency | Multi-currency deals break totals silently |
| Closed-lost reasons | Required for the win/loss analysis to mean anything |
Historical backfill is limited. HockeyStack pulls deal history but web touchpoints before your script was installed simply do not exist. Expect the first month to look wrong, because it is.
What about ad platform connections?
Link Google Ads, Meta, and LinkedIn through OAuth. Each brings spend, campaign, ad group, and UTM-parameter mapping. The usual friction is that ad platforms report conversions on their own attribution model, and HockeyStack reports on yours — so the numbers will not match, and that is expected. Pick one source of truth and stop reconciling the other against it weekly.
Watch for double counting: if you run Google Ads with auto-tagging (gclid) and also append UTMs manually, HockeyStack may record two source rows for one click.
How long until the data is usable?
Roughly 30 days for a channel-level read, 60–90 days for anything involving deal cycles longer than a month. That is not a HockeyStack limitation, it is the shape of B2B data. Anyone promising useful attribution in week one is selling you a demo, not a measurement.
What breaks most often?
- Script in a tag manager with a page exception. Some pages missing = invisible sessions.
- CRM connected with a user account that lacks API scope. Sync stops when that user is offboarded.
- No UTM discipline. Paid traffic without consistent UTMs collapses into one bucket.
- Bot traffic. Filter internal IPs and known bots, or your direct channel inflates.
- Duplicate contacts. Multiple emails per person split their journey; merge in the CRM first.
Key Takeaways
- HockeyStack needs three connections: web tracking, CRM, and ad platforms — install tracking first.
- Verify the anonymous-to-known identity stitch with a real form submission before trusting attribution.
- Map custom deal stages and check currency handling in the CRM sync.
- Ad platform conversions will never match HockeyStack’s model; pick one source of truth.
- Plan on 30 days for channel reads and 60–90 days for multi-month deal cycles.
