- US device IDs in the graph
- 750M+
- Match rate on events
- 90%+
- Identity window, per customer
- Lifetime
- Most brands are live
- <20 min
How it flows
How a Funnelish event reaches HubSpot. Tracked on the funnel page, resolved to a person, then sent.
01 Capture
Captured from Funnelish
Add the Upstack Pixel to your Funnelish funnels to track what shoppers do there. When Funnelish creates the order in Shopify, Upstack records it like any other Shopify order.
See the Funnelish integration →
FunnelishWhat it sends page / eventsfrom the Upstack Pixel in each funnel’s headfbclid / gclid / ttclidclick IDs kept on the way to checkoutorder_idthe Shopify order Funnelish createsorder sourceshows as Funnelish in Upstack reports
02 Understand
Resolved to one person before it leaves
Every Funnelish event is matched against a 750M+ device graph, so a phone browse and a desktop checkout resolve to one customer rather than two strangers.
How resolution works →
Resolved before it is sent - IdentityMatched against a 750M+ device graph, so a phone browse and a desktop checkout resolve to one customer.
customer_typeNew or returning, resolved before send.- DeduplicationOne person, one record, across devices and identifiers.
- Bot and fraud filteringAutomated traffic never becomes a contact.
03 Activate
Delivered to HubSpot
Push identity-resolved events and contacts into HubSpot so CRM records match what actually happened.
See the HubSpot integration →
HubSpotWhat it receives emailthe contact keylifecycle propertiesstage and pipelinedeal / order valuerevenue on the record
The catch
A funnel visit and the order it produced come from two systems: the funnel page and the Shopify order Funnelish creates.
Upstack records the order once per Shopify order ID, with Funnelish as its order source, and resolves the buyer against the same graph as the funnel visit.
Where to check in HubSpotRecords you can audit
HubSpot › the contact timeline
and the duplicate-management view, which should stop growing.
What changes
What changes when Funnelish feeds HubSpot. Two gains on the HubSpot side, two on the Funnelish side.
HubSpot
Server-side delivery
Events reach HubSpot through its server API rather than the browser, so ad blockers and ITP don’t cost you conversions.
HubSpot
Identity-resolved events
Events sent to HubSpot carry the resolved customer whenever Upstack can identify one, matched against a 750M+ device graph.
Funnelish
Funnel pages tracked
The pixel loads in the head of every funnel page, so visits and the events you configure are recorded on pages your theme never touches.
Funnelish
One setup, every destination
Connect Funnelish once and forward to every ad platform and email tool you run.
Setup
Live in under 20 minutes.
Connect Funnelish once and every destination, HubSpot included, is forwarded the same resolved events.
Upstack dashboardExample
HubSpot Destination Healthy
Read the full HubSpot setup guide → -
01
Add the Upstack Pixel to each funnel
In Funnelish, add the Upstack Pixel snippet to each funnel as a tracking code placed with Append To Page Head. If the funnel links to Shopify, add the script that keeps click IDs and UTMs on the link.
-
02
Add the HubSpot destination
Under Destinations, add HubSpot. Every resolved Funnelish event is then forwarded to it.
-
03
Check delivery to HubSpot
Trace any property back to the event that set it.
FAQ
Questions about Funnelish and HubSpot.
How do I check that Funnelish events are reaching HubSpot?
Open HubSpot › the contact timeline, and the duplicate-management view, which should stop growing.
Will this create duplicate contacts?
No. One person, one record, across devices and identifiers.
How long does it take to connect Funnelish to HubSpot?
Most brands are live in under 20 minutes. Once Funnelish events reach Upstack, every destination receives the same resolved events, HubSpot included.