Google counts every LeadsPedia post, but buyers only pay for sold leads
Google Ads says a debt relief or loan campaign is cheap per lead, then LeadsPedia shows many of those leads sitting in the Queue, rejected to the Trash, or returned by the buyer. LeadsPedia documents no Google Ads, GA4 or Meta connection, which leaves a thank-you page tag as the easy default. We carry the ad click into the lead you post and report back only what a buyer kept, from LeadsPedia's webhooks or API.
Free30 minutesNo obligation
LeadsPedia · what breaks
What goes wrong when your ads feed LeadsPedia
- 01
Google pays for leads LeadsPedia trashed
The thank-you page fires the conversion the moment your form posts. LeadsPedia may then park that lead in Review, hold it in the Queue because every contract is capped, or reject it to the Trash. Smart Bidding still logs a win and hunts for more like it.
- 02
Returns never leave the ad account
A mass tort or installment loan buyer returns a lead inside the contract's Max Return Age, and unless Replace Returns is on, LeadsPedia drops its price to $0.00. Google and Meta keep the conversion, so the campaign looks profitable after it stopped being so.
- 03
The Request ID goes missing and so does the source
On your own hosted landing page, LeadsPedia needs a valid Request ID posted with the lead or it can't credit the lead to its source. The same page rebuild that breaks it can drop the GCLID too, and revenue by campaign quietly stops adding up.
- 04
Calls get paid on duration, ads count every ring
A pay-per-call offer may only pay once a call or transfer passes a set number of seconds. If your ad account's call conversion uses a shorter length, or counts calls LeadsPedia never paid on, 20-second hang-ups report as well as filled transfer slots.
LeadsPedia · the fix
What changes after the fix — LeadsPedia
Bidding trained on what buyers paid for
Google and Meta receive a conversion when LeadsPedia sells a lead to a contract, valued at the revenue on that sale, instead of credit for every post.
Revenue per click by keyword and ad set
Each sold lead keeps the click ID it arrived with, so LeadsPedia revenue lines up with ad cost per campaign, ad group and ad set instead of per offer.
Returns corrected where the platforms allow it
An approved return triggers a Google Ads retraction inside Google's adjustment window. Meta can't take a conversion back, so its sale event waits until your Max Return Age has passed.
LeadsPedia · architecture
What LeadsPedia actually lets you hook into
LeadsPedia is lead and call distribution software, not an analytics tool, and its public docs name no ad platform integration. These are the documented pieces we build on; anything its docs don't spell out is a check.
- 1
Posting from a web form or your server
Documented: a form whose action is the LeadsPedia posting URL, or a server post from your landing page carrying the Request ID. The click ID rides along here.
- 2
Post webhooks with token mapping
Documented: a webhook POSTs, GETs or sends headers to your URL on a chosen event, with parameters mapped to tokens. The event list isn't public, so we confirm a sold-lead event and a click ID token in your account.
- 3
Webhook rules by affiliate and campaign
Documented include and exclude rules by vertical, offer, affiliate, campaign, advertiser and contract, which lets us fire only for your own paid search traffic.
- 4
Returns and contract settings
Documented Max Return Age, return caps per billing cycle, auto-approval and Replace Returns, which set how long a sale stays reversible.
- 5
Tracking numbers and call payout rules
Documented numbers per campaign and sub affiliate, paid per call, per transfer, or past a set duration. Per-visitor number swapping isn't described, so we check it.
- 6
Developers API and Zapier
An API key and secret are documented. Zapier appears only as a homepage logo, so we test it before relying on it.
LeadsPedia · diagnose
Where LeadsPedia tracking breaks, in diagnostic order
Start at the post, because a lead that reaches LeadsPedia without its click ID can never be matched later, however good the webhook is.
- 01
Post one test lead from an ad-tagged URL
Open the lead in LeadsPedia and confirm the GCLID or Meta click ID landed on the record, since a field can be posted and still dropped.
- 02
Check what the ad accounts treat as the conversion
A thank-you tag counts posts; a webhook counts sales.
- 03
Confirm the Request ID survives your landing page
Without it, LeadsPedia can't credit the source and revenue by campaign falls apart.
- 04
Compare sold leads with reported conversions
Per lead, for your paid search campaign only, over a closed week.
- 05
Check returns against Max Return Age
Any returned lead still counted in Google or Meta inflates return on ad spend.
LeadsPedia · prove
How we prove it on LeadsPedia
Run on real posts through your live landing pages and real calls to your tracking numbers, not on a test campaign nobody advertises.
Source of truth
LeadsPedia Sold Leads report and returns, filtered to your paid search campaign, with revenue per lead and return status
- One lead posted from an ad-tagged URL, with the click ID visible on the LeadsPedia lead.
- Exactly one sold-lead conversion per sale in Google Ads and Meta, sharing the LeadsPedia lead ID as event ID.
- Trashed, queued and duplicate leads absent from primary conversions.
- An approved return retracted in Google Ads inside its adjustment window.
- A call under the payout duration absent from the call conversion.
- Repeated after your longest return window closes and after any landing page change.
LeadsPedia · free audit
What we check in the free audit
- Post one test lead from an ad-tagged URL
- Check what the ad accounts treat as the conversion
- Confirm the Request ID survives your landing page
- Compare sold leads with reported conversions
- Check returns against Max Return Age
Checked against
LeadsPedia Sold Leads report and returns, filtered to your paid search campaign, with revenue per lead and return status
Free30 minutesNo obligation
LeadsPedia · when not to buy
When you don't need this on LeadsPedia
Plenty of LeadsPedia accounts never touch Google or Meta, and for those this work adds nothing.
- If every lead comes from affiliates posting server-to-server, attribution lives in your campaigns and payouts, and ad tracking is theirs to fix.
- If you're a mass tort or debt relief firm using LeadsPedia only to receive vendor leads, judge vendors on LeadsPedia's own reports instead.
- If nearly every post sells and returns are rare, a correctly gated thank-you tag may be close enough; we'll say so.
- If your only problem is a Request ID dropped by a page edit, putting it back is a developer task, not a tracking rebuild.
LeadsPedia · what we deliver
The event map on LeadsPedia
Form posted
Browser signal when your page posts to LeadsPedia, kept as a secondary action that doesn't steer bidding.
Lead accepted
Cleared Review and moved on to the Queue or a contract, logged for funnel reporting only.
Lead sold to a contract
The primary conversion, sent from the LeadsPedia webhook with the lead ID as the deduplication key and the sale revenue as value.
Qualified call or transfer
Calls on your tracking numbers that clear the offer's payout duration, kept apart from web leads.
Lead kept past the return window
Sent once Max Return Age has expired. On Meta this is the primary event, because a returned sale can't be withdrawn there.
Excluded
Queue leftovers, Trash, rejected and scrubbed leads, returned leads, and your own test posts.
Written guarantee
95%+ tracking accuracy
Measured against LeadsPedia Sold Leads report and returns, filtered to your paid search campaign, with revenue per lead and return status. Miss it and we keep working at no cost.
From $400 · See packages
FAQ
LeadsPedia questions, answered
Not natively, going by its public docs and homepage: no Google Ads, GA4, Tag Manager or Meta connection is listed. The route is LeadsPedia webhooks or its API feeding a server container that sends the conversions.
Capture it on your landing page and post it with the lead, alongside the Request ID if you post server-side. We then confirm it's stored on the lead and available as a webhook token.
Yes, within limits. Google accepts retractions as conversion adjustments for up to 54 days, but bidding only reads ones uploaded within 7 days of the conversion being recorded. Meta has no retraction, so the Meta sale waits until your Max Return Age passes.
Sold leads, valued at what the buyer paid. Optimizing to posts teaches Google to find more form fillers, including the ones that end up queued, trashed or returned.
No. Webhook rules can be limited to your own paid search affiliate and campaign, so publisher campaigns, payouts and posting instructions stay as they are.
Calls that meet the offer's payout duration go out as their own conversion. Whether a call ties to one ad click depends on how numbers are assigned in your account, which we check on the first call.
More on LeadsPedia
- Enhanced ConversionsEnhanced Conversions enrich the conversions that already fire. First we make sur…
- Meta CAPIA one-click CAPI integration sends thin events. That's why your Event Match Qual…
- Cross-Domain TrackingYour checkout provider is the best performing traffic source in your GA4 account…
RELATED GUIDES
Booking tools beside LeadsPedia, and what their bookings feed
- BuildiumGoogle Ads keeps counting leads. Buildium shows almost no applications.
- LineLeaderLineLeader shows who enrolled, but not which ad sent them
- MarketSharpMarketSharp conversion tracking: your ROI report says "Google" sold the job, and Google Ads never hears about it
- ZapierYour Zap says "Success," so why can't Google Ads see the jobs you closed?
- PopuliYour ads fill the Populi inquiry list, but Google can't see who enrolls
- LeapLeap shows the window job your rep signed in SalesPro. Google Ads still thinks it was a form fill.
- IgnitionIgnition shows who signed, but not which ad brought them in
- LeadPerfectionYour ads say leads. LeadPerfection says who sat and who signed. We connect the two.
Free · 30 min
Make your ads learn from LeadsPedia sales
Free30 minutesNo obligation
