Website leads with their source in your CRM: HubSpot, Pipedrive, Brevo, Salesforce or webhook
Where did the lead come from? The CRM handover writes source, campaign and click ID into the CRM with every enquiry, without a form plugin.

Without its source, a lead is worth half as much
The CRM has the name, the email and the message. What is missing is the most important question for marketing: did the enquiry come from a Google ad, from Instagram or from normal search? Without it, you cannot tell which advertising brings in customers.
How the handover works
After a form has been submitted successfully, Tag Manager sends the fields and the campaign data to the Trackum service, which forwards them to your destination. The CRM keys stay on the server, not on the website.
- Source, medium and campaign from the UTM parameters
- Click IDs from Google, Meta, Microsoft, TikTok and LinkedIn
- Landing page and referring page
- First and last touch kept separately
→ Cookie banner with Consent Mode v2: compliant, with no monthly licence
What arrives in the CRM
In HubSpot, we create properties whose names start with trackum_. In Pipedrive, person fields such as "Trackum Quelle" and "Trackum Kampagne" are created. With Brevo, contacts can also go into a list, and in Salesforce they arrive as leads. With a webhook, you get everything as JSON.
Data protection
Campaign data is only collected after marketing consent. The enquiry itself is not stored permanently, only forwarded. A data processing agreement covers the processing.
→ Setting up Google Consent Mode v2 correctly: no warning in Tag Assistant
Cost
Setup costs a one-off 150 euros, running it costs 19 euros per month.
Frequently asked questions
Which destinations are available?
Email, HubSpot, Pipedrive, Brevo, Salesforce via Web-to-Lead, and a webhook for Zapier, Make, n8n or your own system.
What happens if my CRM is down?
Trackum then sends the enquiry to you by email, so that none get lost.
How secure is the webhook?
Every request carries a signature in the X-Trackum-Signatur header, created with HMAC-SHA256 and a secret that only you know.
Read more
FeaturesCookie banner with Consent Mode v2: compliant, with no monthly licence
Reject on the first layer, settings per purpose, Consent Mode v2 with every consent type and a record of each choice. No monthly licence.
FeaturesSetting up Google Consent Mode v2 correctly: no warning in Tag Assistant
The most common warning in Tag Assistant says a tag read consent before a default was set. How to avoid it, and what else matters.
FeaturesMarketing dashboard with GA4 and Google Ads: every number on one page
Visitors, leads, orders, ad spend and ROAS per campaign on one page, compared with the previous period. One link, nothing to set up.
FeaturesRevenue from your CRM, shop and ERP in one dashboard: HubSpot, Shopify, Odoo and more
Google Analytics only sees what happens on the website. Orders by phone or email are missing. With a data connection, the real revenue from your system appears in the dashboard.
FeaturesOffline conversions: report sales from your CRM to Google Ads and Meta
Google Ads and Meta learn from what you report to them. If they only get form fills, they optimise for form fills. With offline conversions, they optimise for sales.
FeaturesSaving UTM parameters and gclid in forms: so no campaign gets lost
A visitor arrives from an ad, clicks through three pages and then submits the form. By then, the UTM parameters have long gone from the address. This is how they are kept.