Tax and accounting
54% better lead quality after using LeadJourney for marketing
Karsten Guhr
Managing Director
Read the storyTransparent logs
Tracking logs that show every click and postback, not a total you trust.
A blocked bot, a failed postback or a duplicate is a line in the log, not a support ticket.
- Real time, every event
- Postback status per platform
- Included on every plan
Rated by teams that stopped trusting black boxes
- Trustpilot4.9 out of 5 on Trustpilot
- G25.0 out of 5 on G2
- Capterra5.0 out of 5 on Capterra
Tracking audited in the logs at
Four minutes of the log, one blocked bot
Your workspace
Transparent logsEvery event as it happens, last four minutes
Live
Click recordedgclid kept · Search, non-brandMira SchulzRecorded- Form submitted, /pricingLead created · matched to click 8f3aLena Vogt · FintoryConversion
Postback sent to Meta CAPIQualified lead · event_id deduplicated200 OKMatched- Click blockedData centre IP · headless user agentNot countedBot
Every line carries what was captured, when, and what the platform answered.
The definition
What are transparent tracking logs?
In short
Transparent tracking logs are a real-time, event-level record of everything a tracking tool captured and sent: every click with its click ID and UTMs, every conversion with the click it was matched to, and every API postback to an ad platform with the status the platform returned. They exist so a team can verify conversion tracking line by line instead of trusting a total.
Real time
Events appear as they happen, so you can click your own ad, submit a test form and watch the click, the conversion and the postback arrive while you look at the screen.
Event level, not aggregated
Every line is one event with what was captured and when: click ID, UTMs, landing page, source, campaign, device, timestamp. No sampling, no thresholding, no modelled fill.
Both directions
What came in from your traffic and what went out to Meta, Google, LinkedIn and Microsoft, with the payload and the response status. See server-side tracking.
Searchable and exportable
Filter by date, event type, source, campaign or status, find a specific click ID or lead, and export the slice for a developer, a client or an auditor.
Case studies
What changes once the attribution is right
One measured result per customer, with the person, the role and the company behind it.
SEO agency
€500k MRR reached profitably, scaling an SEO agency on performance marketing
Nikita Yatsun
Managing Director
Read the story
Klickkraft GmbH
Business coaching
€10-20k in monthly Meta spend, tied to qualified leads and revenue per ad
Florian Buck
Managing Director
Read the story
LinkedIn growth agency
2x customer retention, once every LinkedIn touchpoint was tracked to revenue
Marc Richard
CEO
Read the story
Digital publishing
Which article produced the lead and the revenue, across AI and organic search
Andreas Malkow
CEO & Head of PR
Read the story
SEO and GEO agency
Proven ROI on every retainer, from organic and AI search leads through to revenue
Philipp Nessmann
Managing Director
Read the story
Getreach
Backlinks marketplace (SaaS)
What the logs hold
Every event, in both directions, with its status.
Click logs with the full attribution data
Every click LeadJourney records is logged with the click ID, the UTM parameters, the landing page, source, campaign, ad set, creative, device, country and timestamp. Search a traffic source and read exactly what arrived from it.
Conversions with the click behind them
Form submissions, calls, booked meetings, CRM stage changes and offline deals are logged with the click they were matched to, so any conversion traces back to its ad, campaign and channel, weeks after the click.
Postback logs with the platform's answer
Every signal sent to an ad platform is logged with its payload and the response: accepted, rejected or an error with its message. See offline conversion tracking.
Blocked, duplicate and dropped events, visible
A bot from a data centre, an IP on your blacklist, a duplicate submission, an event the server already had: each is logged with the reason it was filtered.
Cost updates logged too
Spend pulled from the ad platforms is logged the same way, so a sync that did not run shows up the day it happens rather than at month end.
Proof for the client, the auditor and the developer
Logs live per workspace, so an agency can show a client exactly what was tracked on their account. The security page lists the controls around the data.
In the product
The log, from one postback to one lead.
Your workspace
Postbacks by platformLast 7 days, what left and what the platform answered
1,284postbacks sent
1,271accepted
13failed, one cause
PlatformEventSentAcceptedLast status
Meta Conversions APIQualified lead512512200 · matchedGoogle AdsEnhanced conversion438425401 · token expired
LinkedIn Conversions APIBooked call196196200 · accepted
Microsoft AdsOffline conversion138138200 · importedThirteen failures, one cause, fixed by reconnecting Google Ads. Without the log they would have been thirteen missing conversions.
Postback status
What was sent to each platform, and what it answered.
The log grouped by destination: how many events went to each platform, how many were accepted, how many failed and why. A broken token shows up the hour it breaks. See tracking transparency.
- Sent, accepted and failed per platform
- The error message the platform returned
- Match fields on every event: hashed email, phone, click ID
- Browser and server events deduplicated, with the event ID
Your workspace
One lead in the logEvery event for one person, in order
LVLena VogtFintoryQualified
- LinkedIn AdsClick recorded, li_fat_id kept, Sponsored content ABMDay 1, 09:12
- WebsiteForm submitted on /pricing, matched to click 8f3aDay 3, 14:05
HubSpotStage changed to Qualified, synced backDay 5, 10:40- LinkedIn CAPIPostback sent, qualified lead, 200 acceptedDay 5, 10:41
Events logged for this lead4 of 4
Every line here was visible the second it happened.
One lead in the log
Follow a single lead from the click to the CRM, line by line.
Search a click ID, an email or a lead and the log returns that person's trail: the click with its source, the visits, the form, the postbacks and the CRM stages that came back.
- Search by click ID, lead, form or campaign
- Click, visits, conversion and postbacks in order
- What was captured and when, on every line
- Export the trail for a developer, a client or an auditor
Live in 21 minutes
From black box to open log in three steps
No developer required, and the log is on from the first event.
- 1About 5 minutes
Install
Add one script on your own tracking subdomain. Clicks, visits and form fills start landing in the log immediately, each with what was captured and when.
- 2About 10 minutes
Connect
Sign in to your ad accounts and connect your CRM. From then on every postback to a platform and every cost update from it is logged beside the tracking events.
- 3Same day
Run your first audit
Click one of your own ads, submit a test form, and follow the click, the conversion and the postback through the log. That loop is the whole product working in front of you.
Original reviews
What our customers wrote, word for word
4.9 out of 5 across 11 public reviews. Quoted as they were left, shortened only by dropping whole sentences.
- 5 out of 5 starsGoogle
“Before LeadJourney, we had no reliable tracking concept for our five-figure ad spend. We were manually building spreadsheet and CRM reports, inaccurate and time-consuming. Within two days, everything was set up. For the first time, I know exactly what I pay per lead and which campaigns actually bring in the best-qualified prospects.”
Florian BuckCEO, Klickkraft GmbH “With LeadJourney we are able to track all our leads and connect them with sales and attribution data to make better decisions. In the first month of using it we scaled from 0 to 100k revenue from paid ads only.”
GetreachBacklinks Marketplace (SaaS)- 5 out of 5 starsG2
“LeadJourney finally fixed my Marketing Analytics. It goes way beyond basic Ad Tracking Software. The Customer Journey Report saves hours of digging, and capturing everything from Offline Conversions to AI Search Tracking makes it the Best B2B Attribution Platform available.”
Sascha LenzMarketing Manager
- 5 out of 5 starsTrustpilot
“Connected LeadJourney for 2 clients, setup took literally 20 minutes each. The data became more accurate, the reports actually make sense. Now clients look at the dashboard and the 'why don't the numbers match?' questions are gone.”
Alexander SamarPerformance Marketing Agency - 5 out of 5 starsGoogle
“With LeadJourney, we have finally found a tool that provides us with the data we need to scale our performance marketing campaigns. The most important KPI is no longer lead price but cost per qualified lead.”
Steffen SiesingCEO, Bilanzmanufaktur GmbH
- 5 out of 5 starsG2
“The ability to track both online and offline conversions in one unified dashboard has given us insights we never had before. Our ROI has improved dramatically since we started integrating LeadJourney with our CRM. We're finally able to see the full customer journey, and it's been a game changer for our strategy.”
Andre WitzelFounder, Trading.de - 5 out of 5 starsTrustpilot
“The ability to seamlessly integrate data from multiple channels and see real-time insights has significantly improved our campaign results. We now focus on metrics that truly matter, like ROI and qualified leads.”
Nikita YatsunCEO, RLV Media GmbH
Read the reviews where they were left
Common questions
Transparent logs, the questions teams ask
What marketers, agencies and developers want to know before they audit their tracking for the first time.
What events do the tracking logs record?
Every click, with its click ID, UTM parameters, landing page, source and campaign. Every conversion: form submissions, calls, booked meetings, CRM stage changes and offline deals, with the click each was matched to. Every API postback sent to Meta, Google, LinkedIn or Microsoft, with the payload and the response. And every cost update pulled from the ad platforms. All of it in real time.
Can I see whether a postback to Meta or Google was accepted?
Yes. Every postback is logged with the response the platform returned, so you can see whether it was accepted, rejected or answered with an error, and what the error message said. An expired token or a rejected payload shows up in the log the hour it happens, not weeks later as a gap in the campaign results.
Are the logs real time, and how far back do they go?
Events appear as they happen, which is what makes the log useful for testing: click your own ad, submit a test form and watch the click, the conversion and the postback arrive. Logs stay searchable and filterable for the retention period of your plan, so historical attribution questions can be answered from the record.
Can I use the logs to verify a partner's, a platform's or an agency's numbers?
That is their main job. When an affiliate's dashboard, an ad platform and your CRM disagree, the log shows which events were recorded and which were sent, so the argument ends on a record rather than on whoever argues loudest. See affiliate traffic verification for the partner case.
Can I export the logs?
Yes. Filter to the event type, source and date range you need, then export the slice for a developer, a client or an auditor. The search covers click IDs, leads, forms and campaigns, so the export can be as narrow as one lead's trail or as wide as a month of postbacks.
Are the logs an add-on or an enterprise feature?
No. Full logs for clicks, conversions, API postbacks and cost updates are included on every plan. Transparency is what makes the 95%+ accuracy a number you can check rather than one you have to believe, so it is not something we sell back at a higher tier.
Audit it yourself
Watch your own tracking work, event by event.
Book a demo, click one of your own ads, and watch the click, the conversion and the postback arrive in the log while we talk.
Your workspace
Black box against the logThe same week, two ways of knowing
Conversions you can check0of 214 reported: a total, and no events behind it
Conversions you can check236of 236 recorded: click, form and postback on every one
Postbacks confirmed by the platform13 failures found, one fix
PlatformBlack boxIn the log
Meta CAPIA total512 sent · 512 matchedGoogle AdsA total438 sent · 13 failedLinkedIn CAPIA total196 sent · 196 acceptedMicrosoft AdsA total138 sent · 138 importedThe thirteen failures were one expired token. In a black box they would have been thirteen conversions that never existed.
