If you’re a marketer or marketing ops person who juggles both HubSpot and Pathfactory, you’ve probably run into the “how do I actually get this content track into my email or landing page?” problem. The documentation is usually vague, the actual process is finicky, and there’s a gap between what the platforms say they can do and what actually works. This guide is for you. No buzzwords or magic promises—just the straight path to getting your Pathfactory tracks into HubSpot, with honest warnings about what’s worth your time (and what isn’t).
What You Need to Know Before You Start
First, a quick level set. Pathfactory is popular for building "content tracks"—curated experiences where you string together assets and landing pages to keep folks engaged. HubSpot is, well, HubSpot. The catch? Embedding interactive content or custom code (like iframes or scripts) in HubSpot emails is basically impossible, and HubSpot landing pages are only a little more flexible. So, temper your expectations: you’re not going to get a fully embedded, interactive Pathfactory experience inside an email. But you can drive clicks and embed tracks in landing pages with a few gotchas.
Here’s how to do it, what works, and what to skip.
Step 1: Get Your Pathfactory Content Track Link or Embed Code
You’ll need either a direct link to the content track or (for landing pages only) the embed code.
To grab your link or embed code: 1. Log in to your Pathfactory account. 2. Go to the Content Tracks section and pick the track you want. 3. Click to view the sharing options. 4. You’ll see: - A direct URL to the content track (works everywhere). - An embed code (usually an iframe or JavaScript snippet; works only on some web pages, not emails).
Pro tip:
Ignore any suggestion to “embed” Pathfactory tracks directly into email content. HTML emails don’t support iframes or JavaScript, no matter how much vendors hint otherwise.
Step 2: Embedding Pathfactory in HubSpot Emails
This is where you need to keep it simple. HubSpot emails don’t allow embedded iframes or scripts. Period.
What works: - Adding a call-to-action (CTA) button or image in your email that links to your Pathfactory track. - Using a thumbnail preview (screenshot of the first asset or the track's cover image) to entice clicks.
How to add a CTA to your Pathfactory track in HubSpot Email:
- Open your email draft in the HubSpot email editor.
- Insert a button or image where you want the CTA.
- Paste the Pathfactory content track URL as the destination link.
- (Optional) Track clicks by making sure you use HubSpot’s CTA or tracking features.
What doesn’t work: - You can’t embed interactive Pathfactory tracks inside email content. Ignore any workaround that claims otherwise—they won’t render in real inboxes.
Pro tip:
Always test your email in multiple clients (Outlook, Gmail, etc.). Even simple things can break, and it's better to find out before you hit send.
Step 3: Embedding Pathfactory Tracks in HubSpot Landing Pages
You’ve got more options here, but there are still limits.
Option 1: Link Out to the Pathfactory Content Track
This is the most reliable, lowest-maintenance approach.
How to do it: 1. In your landing page, add a button, image, or text link. 2. Link that element to the Pathfactory content track URL. 3. Done.
Why this works:
No embed code, no headaches. This keeps things simple and guarantees your content displays as Pathfactory intended.
Option 2: Embed the Track Directly (if your design calls for it)
If you want the Pathfactory track to appear inside your landing page, you can try embedding it.
Here’s how: 1. Open the HubSpot landing page editor. 2. Add a “Custom HTML” or “Embed” module where you want the track to appear. 3. Paste the Pathfactory embed code (usually an iframe). 4. Preview the page. If it looks right, publish.
What to watch out for: - Responsiveness: Embedded iframes may not scale well on mobile. Test thoroughly. - Tracking: Sometimes, embedding can interfere with analytics—double-check your reporting. - Load speed: Extra iframes/scripts can slow the page. Don’t cram too many embeds onto a single page.
What doesn’t work: - Embedding via JavaScript snippets can break if HubSpot’s security filters strip them out. If the embed code doesn’t display, this is probably why. - Some custom HubSpot themes or modules restrict where you can add custom HTML. If you don’t see the option, check your theme or ask your admin.
Pro tip:
If you run into display issues with the embed, fall back to just linking out to the Pathfactory track. It’s better than fighting with HubSpot’s editor for hours.
Step 4: Tracking Engagement
You want to know who’s clicking and what they’re doing. Here’s what you can and can’t expect:
In HubSpot: - You’ll see clicks on your CTA or links if you use HubSpot’s tracking features. - You won’t see granular engagement with specific assets inside the track (that’s Pathfactory’s job).
In Pathfactory: - You’ll see individual session data—what assets people viewed, how long they spent, and so on. - You can pass UTM parameters or HubSpot contact IDs into the Pathfactory track URL to tie engagement back to your contacts.
To pass contact info for better tracking:
1. In your email or page, modify the Pathfactory URL to include dynamic parameters (e.g., ?email={{contact.email}}).
2. In Pathfactory, set up your track to capture these parameters.
What doesn’t work: - Two-way, real-time sync of engagement data back into HubSpot without extra integration work. If you want automated scoring or workflows based on Pathfactory views, you’ll need to set up custom integrations (Zapier, APIs, etc.), and that’s well beyond plug-and-play.
Pro tip:
Don’t obsess over perfect tracking from day one. Start simple. Get the basics working, then layer in more advanced tracking if you actually need it.
Common Pitfalls (and How to Avoid Them)
- Relying on embedding in email: It just doesn’t work. Stick to links.
- Ignoring mobile: Both Pathfactory and HubSpot can look great on desktop but break on phones. Always preview.
- Chasing “seamless integration”: No matter what the sales slides say, the experience is rarely seamless. You’re stitching together two tools, and some friction is inevitable.
- Overcomplicating the landing page: If your page starts to look like a Frankenstein’s monster of widgets and embeds, simplify. You’ll get better performance and fewer support headaches.
Quick Reference: What Works and What Doesn’t
| Use Case | What Works | What Doesn’t Work | |---------------------------|-------------------------|--------------------------| | HubSpot Emails | Link to Pathfactory | Embedding, iframes, JS | | HubSpot Landing Pages | Link or embed (iframe) | JS snippets (sometimes) | | Tracking | Clicks (HubSpot), Views (Pathfactory) | Full sync without custom integration |
Wrapping Up
Getting Pathfactory content tracks into HubSpot emails and landing pages is mostly about knowing what not to fight. Use links for emails, embed or link out on landing pages, and don’t waste cycles on workarounds that don’t really work. Start simple, get your team comfortable with the process, and improve from there. If you hit a wall, remember that you’re not alone—these two platforms play nice enough, but they’re not mind readers. Keep it straightforward, and you’ll get the results you need without the headaches.