P PayhoundAugust 2026 Monthly Report - Chado OS
August 2026 - Monthly client report

Paid leads increased. Client-validated leads fell.

The budget sheet reports 74 paid-ad leads in August versus 36 in July, while client-validated leads fell from 43 to 21 across all leads. August actual spend was EUR 16,354.00. Paid-channel attribution and record-level matching remain to be reconciled.

Reporting month: 1-31 August 2026Comparison: July 2026Historical coverage: May-August 2026Cadence: monthly
LinkedIn conversion coverage expanded

Five campaigns represented in the May-August conversion export. Lead results come from the checked budget sheet.

August Google is Search-only

No PMax spend or clicks in August. July still had PMax delivery.

Conversion mix changed

July includes button actions; August lists form-success actions only.

Client validation confirmed

Good Quality Leads are client-validated leads. Paid-channel attribution and raw record matching remain open.

August executive readout

1-31 August 2026. Lead results use the budget sheet, checked against GA4 by the report owner. Good Quality Leads are client-validated leads.

Budget sheet: lead source of truth
Actual media spendEUR 16.35kEUR 354 above the EUR 16,000 budget.
All leads113Total lead pool; paid ads may influence leads beyond tracked attribution.
Paid-ad leads74Budget-sheet result checked against GA4 by the report owner.
Client-validated leads2118.6% of 113 all-source leads; not a paid-only count.
Actual cost per validated lead€ 779Actual media spend / 21 client-validated leads.

August lead progression

1 - All leads113

Total leads received. Paid media may contribute beyond directly tracked paid-ad leads.

2 - Paid-ad leads74

Leads attributed to paid ads in the source sheet. This is the tracked paid count.

3 - Client-validated leads21

Leads the client confirmed as good quality. Channel and campaign matching remains open.

All leads → Paid-ad leads → Client-validated leads is the reporting sequence. These counts are not yet a matched subset funnel: July has 43 validated leads versus 36 tracked paid-ad leads. No paid-to-validated conversion rate is calculated until the overlap is reconciled.

August performance interpretation

Performance commentary for August, using July only as the comparison month.

Client-validated lead counts available
Management interpretation
What happened in August

Actual spend was EUR 16,354.00: EUR 9,856.49 Google and EUR 6,497.51 LinkedIn. The sheet reports 113 total leads, 74 paid-ad leads and 21 client-validated leads. Google delivery was entirely Search.

What changed versus July

Paid-ad leads increased from 36 to 74 and reported paid CPL improved from EUR 294.14 to EUR 221.00. Client-validated leads fell from 43 to 21, and their share of all leads fell from 34.7% to 18.6%.

What this means

Paid ads may influence the wider lead pool, beyond the directly tracked paid-ad count. Report all leads, tracked paid-ad leads and client-validated leads together. Paid attribution and client validation measure different things; matching them will clarify which paid activity produces validated demand.

August priorities and next steps

Follow-ups from this reporting month. Owners and due dates are to be confirmed.

Reporting priorities

  • Complete LinkedIn delivery metrics: the conversion export now covers five campaigns; a full campaign-performance export is still needed for account-wide clicks and impressions.
  • Attribute validated leads: establish the channel and campaign mix behind August's 21 client-validated leads.
  • Keep measurement layers separate: use LinkedIn and Google actions to diagnose performance; retain the checked budget sheet for lead results.
  • Confirm completion: record owners, due dates and status before the next monthly issue.
Downstream commercial outcomes still to confirm.

Client validation is confirmed for the Good Quality Leads metric. Qualified opportunities, signed business and channel return are not evidenced.

May-August monthly performance history

One row per month. Actual spend from the read-only budget sheet; missing monthly lead summaries are labelled.

Historical coverage: four months
MonthGoogle actualLinkedIn actualTotal actualAll leadsPaid-ad leadsClient-validated leadsPaid CPLCost / validated lead
May 20263,136.5879.993,216.57Not suppliedNot suppliedNot suppliedNot availableNot available
June 20267,634.962,515.1210,150.08Not suppliedNot suppliedNot suppliedNot availableNot available
July 20266,028.844,560.2610,589.101243643294.14246.26
August 20269,856.496,497.5116,354.001137421221.00€ 779

EUR amounts. Good Quality Leads are client-validated leads, as confirmed by the report owner. Channel attribution and downstream CRM outcomes remain separate. The May-June Webflow quality screen is a combined diagnostic and is not apportioned into monthly counts.

Meta Ads - not launched in this reporting period.

Meta actuals are intentionally blank. Launch is anticipated in October 2026 under Scope 2 of the approved works; timing is still tentative. Meta will enter monthly performance reporting once activity begins. May-August spend totals cover Google and LinkedIn.

August campaign performance with July comparison

August is the reporting month; July columns provide context. Conversion actions are diagnostics, not lead totals.

Campaign familyJuly spendJuly conversionsAugust spendAugust conversionsAugust platform CPA
Google - PMax Competitors777.96234.800.000Not applicable
Google - PMax #4253.51123.880.000Not applicable
Google - Search Non-Brand2,619.9636.504,266.438450.79
Google - Search Verticals / iGaming1,524.8113.501,520.193741.09
Google - World Cup631.6860.000Not applicable
Google - Search Brand220.05570.830Not defined
Google - MiCA Financial Institutions0.8701,999.095399.82
Google - MiCA iGaming0.0001,999.954499.99
LinkedIn - Phase 1 Engagement935.7612940.789104.53

EUR amounts. LinkedIn daily ad rows aggregated by campaign: 451 July rows and 734 August rows, with all 31 days represented and no duplicate date/ad/ad-set keys. Campaign status is export-time state, not proof of a pause date.

July-August source files and calculation basis
  • JUL26 / Payhound Google Ads Report 1- 31 - JUL 2026: Campaign performance.csv and Conversions.csv. Period: 1-31 July 2026.
  • AUG26 / PH Google Ads Report - 1 -31 AUG 2026: Campaign performance.csv and Conversions.csv. Period: 1-31 August 2026.
  • Payhound LinkedIn Ads - Performace Report 1 - 31 JUL 2026.csv. Daily ad-level report in UTC, generated 7 August 2026.
  • Payhound LinkedIn Ads Report - 1 - 31 - AUG 2026.csv. Daily ad-level report in UTC, generated 11 September 2026.
  • Source folder: Payhound / [PH] Internal Reports [NEW]. Ratios calculated from summed spend, clicks, impressions and conversions; no averaging of row-level rates. No live platform or billing data used.

Historical platform delivery - May-August

Supporting platform data. Lead results and actual account spend remain in the monthly history above. LinkedIn delivery rows cover Engagement only.

Channel / periodSpendImpressionsClicksCTRCPCTracked conversionsPlatform CPA
Google - May3,136.58452,0204,4940.99%0.705627.32
Google - June7,634.961,185,06651,0514.31%0.15958.307.97
Google - July6,028.84228,06813,0835.74%0.46419.6814.37
Google - August9,856.4931,4931,7965.70%5.4913075.82
LinkedIn Engagement only - July935.7671,8281,1761.64%0.801277.98
LinkedIn Engagement only - August940.7848,2357291.51%1.299104.53
Weighted ratios, with source-native definitions.

CTR = total clicks / impressions; CPC = spend / clicks; platform CPA = spend / tracked conversions. LinkedIn clicks include engagement clicks: landing-page clicks were 126 in July and 65 in August. Platform CPA is not cost per validated lead.

Google conversion diagnostics - August vs July

August form-success actions, with July shown to explain the change in conversion mix.

Google conversion actionJulyAugustMeaning
Button - Get Started183.70Not listedEngagement action; not a submitted lead.
formSubmissionSuccess - GAds129.9973Tracked form-success action; match to actual submissions.
formSubmissionSuccess - merchant-crypto-solution105.9957Tracked path-specific form success; overlap with other tags not ruled out.
Total tracked conversions419.68130Reconciles to each campaign export, within rounding.

Search tracked conversions

61 to 130

Search spend rose from EUR 4,997.37 to EUR 9,856.49. Search platform CPA moved from EUR 81.92 to EUR 75.82; attribution and goal comparability remain unvalidated.

August core Search

121 actions

Non-Brand + iGaming produced 121 of 130 Google conversions on EUR 5,786.62 spend. Combined platform CPA: EUR 47.82.

August MiCA Search

9 actions

Financial Institutions + iGaming MiCA campaigns spent EUR 3,999.04. Combined platform CPA: EUR 444.34. Qualified-lead value is unknown.

LinkedIn actions are detailed separately below.

The new conversion export expands beyond Engagement to Lead Gen, Remarketing, Traffic and World Cup. Lead totals continue to use the GA4-checked budget sheet.

LinkedIn conversion diagnostics - May-August

Conversion export generated 6 October 2026. Campaign coverage: Engagement, Lead Gen, Remarketing, Traffic and World Cup.

Tracked actions, not lead results
Conversion actionMayJuneJulyAugustReporting role
Button - Book A Free Demo - LiNo rows1Not listedNot listedButton engagement.
Button - Get Started - LiNo rows14299Button engagement, not form submission.
LinkedIn InsightTag 2.0No rowsNot listed238Not listedKey Page View; World Cup diagnostic.
formSubmissionSuccess - LiNo rows265Tracked form success; not unique or validated lead count.
formSubmissionSuccess - support-page - LiNo rowsNot listedNot listed2Support-path form success, reported separately.
Total listed conversion actionsNo rows1727316Mixed actions; not a lead-performance total.
Post-click actionsNo rows5867Source-native LinkedIn attribution.
View-through actionsNo rows121879Source-native LinkedIn attribution.

August button actions

9

4 post-click + 5 view-through Get Started actions. Engagement diagnostics only.

August form-success actions

5

2 post-click + 3 view-through. These actions are not substituted for the 74 paid-ad leads in the checked budget sheet.

August support-form actions

2

1 post-click + 1 view-through. Kept separate from new-business form actions; unique submission overlap is unknown.

Conversion mix changes the headline.

July's 273 actions include 238 World Cup key-page views. August's 16 actions comprise 9 buttons, 5 form successes and 2 support-form successes. Their difference is not a lead decline. May has no rows in this export, which is not evidence of zero May leads.

LinkedIn conversion source and method
  • account_513880243_conversion_performance_report.csv; account Payhound; EUR; 1 May-31 August 2026, in UTC; generated 6 October 2026 at 11:38 AM UTC.
  • 34 rows grouped by reporting month and conversion action; post-click and view-through totals kept separate.
  • Total Spent repeats across conversion-action rows for the same month/ad set and is not summed. Total Conversion Value is a platform-assigned value, not verified revenue.
  • Form-action metadata shows a last-modified date of 15 September 2026. This is a later export snapshot than the earlier ad exports; historical attribution may differ.
  • All leads, paid-ad leads, client-validated leads and lead costs are sourced from the checked budget sheet, never derived from this conversion export.

August GA4 acquisition evidence

1-31 August 2026. Session acquisition, form-success events and landing-page performance.

Supporting evidence; sheet controls lead results
Website sessions7,265

1,779 engaged sessions. Traffic volume, not lead volume.

Form-success events113

Matches the budget sheet's August All leads total. Event count alone does not establish unique leads.

Users with form success98

113 form-success events across 98 users. Users and events are not interchangeable with unique leads.

August session acquisition

Session source / mediumSessionsForm-success key events
google / cpc2,05074
LinkedIn / (not set)1,7110
(direct) / (none)95521
LinkedIn / paid_social6541
google / organic6496
LinkedIn / referral4820
(not set)4496
linkedin.com / referral890
linkedin / paid_social590
bing / organic371

Visible rows 1-10 of 58, not the complete source inventory. Selected key event: formSubmissionSuccess - GA4. LinkedIn traffic includes missing mediums and inconsistent source spelling; attribution needs reconciliation.

August landing-page contribution

Landing pageSessionsAverage engagement / sessionForm-success key events
/merchant-crypto-solution2,40210s66
Homepage1,05927s18
/crypto-payments2,7074s11
/contact6623s6

Selected landing pages, not all 94 rows. Merchant crypto solution accounts for 66 of 113 selected key events; crypto payments has more sessions but fewer form-success key events. The screenshot's session key-event rate is set to All events and is not presented as a form conversion rate.

May-August tracking reconciliation

Session acquisition history

MonthAll sessionsEngaged sessionsAverage engagement / sessionGoogle / CPC sessionsGoogle / CPC form key eventsAll form key events
May5,7091,67217s3,38100
June38,5789,5589s35,26500
July14,1323,66210s10,97687128
August7,2651,77911s2,05074113

Selected key event: formSubmissionSuccess - GA4. May-July screenshots show the first 10 source rows only (43, 88 and 72 total rows respectively); total rows above are GA4 report totals, not sums of visible sources. May and June zero key-event counts do not establish zero leads.

July paid attribution remains unresolved.

Google / CPC records 87 form key events in July, while the checked budget sheet reports 36 paid-ad leads. August records 74 in both. Reconcile July's event definition, counting method and lead inclusion rules before treating the acquisition view as the accepted lead result.

Events, key events and checked leads

MonthLanding-page sessionsForm-success event countUsers with eventLanding-page form key eventsChecked sheet: all leads
May5,709410Not supplied
June38,5782592320Not supplied
July14,132195160128124
August7,26511398113113
Historical definitions need reconciliation.

May and June show form events but zero selected landing-page key events. July shows 195 events, 128 selected key events and 124 checked leads. These are different measures; the screenshots do not establish why they differ. No historical lead totals have been replaced. A separate repeated-name form event also appears in Events and needs a tagging review before combining counts.

Next source-of-truth controls: confirm the intended lead event, its key-event counting method and activation history; export complete monthly source/medium and landing-page tables using that event; reconcile submissions to client validation without sending personal information to GA4.

August first-user attribution comparison
First-user source / mediumTotal usersForm-success eventsInterpretation
google / cpc1,49074Google paid-source row; 65.49% of all form-success events.
LinkedIn / (not set)1,3240Medium missing; paid attribution cannot be established from this row.
(direct) / (none)1,24227Direct first-user source does not rule out later paid influence.
LinkedIn / paid_social5601Additional paid-tagged form-success event; kept separate from the sheet's 74.
google / organic4936Organic first-user source.
LinkedIn / referral4810Referral-tagged traffic.
linkedin.com / referral670Separate source spelling in GA4.
linkedin / paid_social570Separate lowercase source spelling in GA4.
(data not available)513Source detail unavailable.
bing / organic271Organic first-user source.
Lead totals remain 113 → 74 → 21.

The checked budget sheet remains the source of truth. Its 74 paid-ad leads matches Google / CPC in both acquisition views, while LinkedIn / paid_social shows one additional form-success event. This is a scope difference to reconcile, not an automatic change to the accepted lead total.

Source: screencapture-analytics-google-analytics-web-2026-10-06-13_52_10.pdf, captured 6 October 2026. The screenshot shows rows 1-10 of 53; visible rows are not a complete source inventory. First-user attribution differs from session or campaign attribution. Platform key events are not used as lead totals.

Additional GA4 screenshots captured 6 October 2026: 13_54_44 (August session acquisition), 13_55_04 (August Events), 13_55_51 (August landing pages), 13_56_19 (July landing pages), 13_56_35 (June landing pages), 13_56_49 (May landing pages), 13_57_23 (May Events), 13_57_36 (June Events), 13_57_52 (July Events). All use the filename prefix screencapture-analytics-google-analytics-web-2026-10-06- and .pdf extension.

Session acquisition history sources: screencapture-analytics-google-analytics-web-2026-10-06-13_58_21.pdf (July), screencapture-analytics-google-analytics-web-2026-10-06-13_58_48.pdf (June), and screencapture-analytics-google-analytics-web-2026-10-06-13_59_04.pdf (May). The insight banners reference September and are excluded from this reporting period.

Data coverage and governance - May-August

Full means usable export; partial means diagnostic or incomplete; missing means no reliable decision file in the supplied evidence.

SourceMayJunJulAugDecision useNext control
Google AdsFullFullFullFullSpend, clicks, conversions, search termsSeparate Primary, Secondary, diagnostics, and validated leads.
LinkedIn AdsPartialPartialPartialPartialFive campaigns in conversion diagnostics; Engagement-only Jul-Aug delivery exports.Obtain full-account campaign delivery metrics; use sheet for actual spend and leads.
GA4 / budget sheetPartialPartialCheckedCheckedReport owner checks lead counts against GA4; budget sheet is lead source of truth.Refresh checked sheet lead results for each monthly issue.
Microsoft ClarityFullFullMissingMissingBehaviour quality, bots, shallow visitsRefresh July-August source and intent diagnostics.
Webflow leadsFullFullMissingMissingLead row and quality classificationSupply July-August rows and classify intent and outcomes.
Client validationMissingMissingSummarySummaryGood Quality Leads: client-validated counts.Match validated leads to paid sources and downstream CRM outcomes.

Sources, confidence and reporting definitions

Budget sheet for lead results and account spend; platform exports for delivery and conversion diagnostics.

Budget-sheet definitions and source references

Budget and lead definitions - July-August

MetricJulyAugustSource / interpretation
BudgetEUR 14,100.00EUR 16,000.00H34 / K34
Planned allocationEUR 11,704.00EUR 17,910.00I34 / L34; distinct from budget and actual spend.
Google actual spendEUR 6,028.84EUR 9,856.49J16 / M16; matches campaign exports.
LinkedIn actual spendEUR 4,560.26EUR 6,497.51J3 / M3; exceeds the supplied Engagement campaign exports.
Total actual spendEUR 10,589.10EUR 16,354.00J34 / M34; July EUR 3,510.90 under budget; August EUR 354.00 over budget.
All leads - sheet labelled GA4124113J39 / M39; total lead pool. Paid media may influence leads beyond tracked paid attribution.
Paid-ad leads - checked GA4 result3674J41 / M41; budget sheet is the lead source of truth, checked against GA4 by the report owner.
Client-validated leads - sheet label: Good Quality Leads4321J43 / M43; client validation confirmed by the report owner. Paid-only scope not confirmed.
Good-quality share of all leads34.7%18.6%Quality count / all-lead count. A decline of 16.1 percentage points.
Actual spend / all leadsEUR 85.40EUR 144.73J40 / M40; blended spend-to-all-lead ratio, not paid CPL.
Actual spend / paid-ad leadsEUR 294.14EUR 221.00J42 / M42; sheet-reported paid CPL.
Actual spend / client-validated leadsEUR 246.26€ 779J44 / M44; August rounded to the nearest euro. Blended ratio using all-source client-validated leads, not paid-only CPL.
LinkedIn delivery coverage remains partial.

The new conversion report represents five campaigns. The earlier clicks/impressions exports cover only Engagement, with EUR 935.76 July spend and EUR 940.78 August spend. Account-wide actual spend remains EUR 4,560.26 and EUR 6,497.51 from the budget sheet. Conversion-report spend repeats across actions and is not summed as account spend.

Lead reporting source of truth.

[PH] Paid Ads Budget 2026 - Budget 2026 + Breakdown is the source of truth for All leads, Paid-ad leads and Client-validated leads. The report owner checks the data against GA4; Good Quality Leads means client-validated leads. Platform actions never replace these counts. This report uses a read-only snapshot; channel matching and downstream commercial outcomes are separate reporting work.

Attribution and record-level reconciliation

Attribution and reconciliation

Connect platform activity to received leads, qualification and commercial outcomes. July-August CRM and Webflow exports are missing.

Record-level matching required

August paid-ad leads

74

GA4-checked budget-sheet result. Campaign-level credit remains separate from this accepted lead total.

Qualified commercial outcomes

To confirm

Client confirmation is needed for qualified leads, opportunities and signed business.

Spend reconciliation

Coverage gap

Sheet actuals total EUR 26,943.10 for July-August; supplied exports total EUR 17,761.87. Google spend matches. The EUR 9,181.23 difference is in LinkedIn. Billing reconciliation has not been performed.

Lead reconciliation checks

  • Match form-success events to Webflow submissions by timestamp, form and landing path.
  • Deduplicate emails and separate test, support and new-business enquiries.
  • Confirm original source, campaign, company context and intent tier.
  • Attach client/CRM outcomes before calculating cost per validated lead.

Current evidence boundary

The 28 GA4 exported form_submit events, 366 Clarity submit-form sessions and 893 Webflow rows measure different things. They are not interchangeable lead totals.

Commercial attribution remains open.

No channel ROAS, signed-contract count or qualified-lead rate is supported by the supplied evidence.

Tracking architecture and monthly reporting controls

Measurement architecture and data quality

The next decision should improve truth, not increase reporting complexity.

LayerCurrent signalReporting roleConfidence
Secondary button actionsBook A Free Demo, Get Started, industry buttonsEngagement only; not headline lead CPA.High
Aggregate form successformSubmissionSuccess - GA4Aggregate form-submission view.Medium
Merchant crypto formformSubmissionSuccess - merchant-crypto-solutionMain PPC landing-page sales intent.Medium
Support pageformSubmissionSuccess - support-pageExisting-client/support path going forward.Medium
Sales contact pageformSubmissionSuccess - sales-contact-pagePreferred new-client CTA path.Medium
Legacy form tagOld formSubmissionSuccessLegacy/noise; exclude from decision totals.High
Client-validated leadSheet metric: Good Quality LeadsJuly 43; August 21. Confirmed client-validated counts; channel matching open.Client validation confirmed
Lead reconciliation rule.

Classify every Webflow lead by source, landing path, form event path, business email, company context, sector, intent tier, outcome, and whether client confirmation is required.

Monthly reporting controls

Each new issue uses the report owner's GA4-checked budget sheet for all lead results, advances the executive commentary to the selected month and retains previous months in history. Platform conversions remain diagnostics.

Budget sheet remains read-only

Monthly reporting cycle

  1. Set the reporting month and prior-month comparison explicitly.
  2. Collect Google and LinkedIn exports with consistent account and date scope.
  3. Refresh Webflow lead rows, mapped GA4 events and Clarity diagnostics.
  4. Reconcile duplicates, lead sources, intent tiers and client/CRM outcomes.
  5. Calculate costs from matched totals after resolving spend differences.
  6. Write the evidence, business impact and next decision.
  7. Assign the top actions with confirmed owners and due dates.

Acceptance criteria

  • Dates and source scopes are visible.
  • Platform actions, submitted rows and commercial outcomes remain separate.
  • Spend totals reconcile to the selected source exports.
  • Unavailable values are labelled; missing outcomes are not reported as zero.
  • Recommendations state evidence and confidence.
  • Tables, charts and labels remain readable on phones and in PDF exports.

Required lead fields

Submission time, form path, original source, campaign, company, business email, sector, intent tier, first response, outcome and client validation status.

Confidence rule

  • High: source totals reconcile and validated outcomes support the claim.
  • Medium: evidence is useful directionally, with visible gaps.
  • Low: resolve measurement or matching before making performance claims.
Historical review appendix - May-June 2026

Combined diagnostic evidence and original recommendations from the earlier review. These are not August results or current action instructions.

May-June diagnostic baseline

Historical evidence retained for context. These lead-quality and behaviour metrics have not been refreshed for July-August.

Confidence: medium
Google spendEUR 9.18kMay-June export total.
Google conversions960.3Do not treat as validated leads.
Webflow rows893461 unique emails.
Clarity sessions53.7k12.85% bot sessions.
LinkedIn leads0No native leads in supplied export.

May-June performance and planning context

Spend is large enough to justify optimisation, but source quality and form quality decide the next budget move.

Platform results are not validated leads
Monthly paid spend

Relative bars by platform. Google dominated May-June actual spend; July-December planning should balance Google and LinkedIn at EUR 8k/month each.

May actualEUR 3,216.57
June budgetEUR 14,100.00
June actualEUR 10,150.08
Jul-Dec planEUR 16,000.00
Google AdsLinkedIn Ads
SignalReadingConfidenceDecision impact
Google Ads spendEUR 9,184.09HighMaterial enough to justify optimisation review.
Google tracked conversions960.3LowBlended conversion volume should not be business truth.
Apparent CPAEUR 9.56LowLikely overstates performance until validated leads are known.
Clarity average pages/session1.04HighVisits are shallow; source and landing-page clarity need review.
Clarity average scroll depth21.15%HighEngagement is weak on the main paid path.
LinkedIn native leads0HighLinkedIn is not yet proven as direct lead capture.

Commercial lead funnel and quality - May-June baseline

Webflow confirms Payhound is reaching some real B2B demand, but the lead base needs classification before optimisation claims.

Client validation required
Platform conversions960.3Google source-native actions; diagnostic only.
Submitted rows893Webflow rows; repeated emails included.
Unique emails461Email deduplication; qualification still required.
Qualified opportunitiesTo confirmClient/CRM validation missing; signed outcomes also unknown.
Separate layers, not a matched conversion funnel.

These source totals have not been joined record by record. No lead-to-opportunity rate or commercial return can be derived yet.

Webflow quality screen
893Rows supplied
461Unique emails
88.8%Rows with at least one risk signal
PatternReadAction
Personal email + investment/balance languageWeak fitDisqualify or route out of sales pipeline.
Very short or vague messagesUnknown/low intentRequire structured form context.
Consumer recovery/help enquiriesLow fitAdd page copy and form filters to reduce submissions.
PSP, iGaming, settlement, API enquiriesStronger B2B fitClassify as medium/high-intent and feed back into channel learning.
The intent ladder is the fix.

Move from consumer/investment language, personal emails, shallow visits, and broad PMax traffic toward business payment use cases, company context, engaged sessions, exact/phrase B2B search, and validated qualified leads.

GA4 and digital behaviour - May-June baseline

Historical raw diagnostics. July-August lead summaries are available in the budget sheet above, but raw GA4 and Clarity behaviour exports remain unavailable.

Raw behaviour refresh required

Traffic quality

Microsoft Clarity

Sessions53,668
Bot sessions12.85%
Pages / session1.04

Website intent

Clarity behaviour diagnostics

Average scroll depth21.15%
Active time23 seconds
Submit-form sessions366

GA4 event evidence

3 May-30 June 2026 export

Google / CPC sessions38,117
Exported form_submit28
Mapped form successesTo reconcile
The mapped success events are the next reporting control.

Use the formSubmissionSuccess family for Payhound's form-success view. The exported form_submit count is diagnostic; it does not replace Webflow or validated CRM outcomes.

Historical campaign and channel decisions

Recommendations from the May-June review, retained as historical context. August now shows no PMax delivery; refresh decisions against validated lead evidence.

May-June review
Channel / campaign familyEvidenceCommercial confidenceRecommended decision
Google PMaxPMax Competitors: 31,135 GA4 sessions and 19 exported form_submit events.Low; form-success and CRM outcomes unreconciled.Review broad exposure and release budget against validated intent.
Google Search Non-Brand93 Clarity sessions: 3 high, 49 medium and 41 low intent in the Search-only slice.Directional; small behaviour sample.Tighten B2B terms, ad messaging and landing-page qualification.
Google Search Verticals59 Clarity sessions: 0 high, 25 medium and 34 low intent.Directional; small behaviour sample.Improve vertical fit before increasing spend.
LinkedInZero native leads in the supplied export.Direct lead capture unproven; assisted impact unknown.Test tighter audiences and reconcile landing-page leads.

Historical forward budget plan

Plan from the May-June review, not the latest sheet allocation. The read-only budget sheet above reports July actual EUR 10,589.10 and August actual EUR 16,354.00.

Scale only after validation
PlatformLine itemSuggested monthly amountWhy
GoogleSearch BrandEUR 1,200Protect demand without over-weighting brand in acquisition analysis.
GoogleSearch Non-BrandEUR 1,500Push learning into controllable B2B intent.
GoogleSearch Verticals / iGamingEUR 1,500Focus on vertical intent with stronger query and copy controls.
GoogleSearch CompetitorsEUR 1,500Capture competitor intent with query control instead of broad PMax.
GoogleDisplay RemarketingEUR 1,500Retarget only high-intent audiences and engaged visitors.
GoogleHeld reserveEUR 800Do not release until medium/high-intent lead share improves.
LinkedInLead Gen iGamingEUR 2,000Test high-fit vertical demand.
LinkedInLead Gen PSP/EMI/PaymentsEUR 2,000Test high-fit payment buyer segment.
LinkedInFinance/Treasury/ComplianceEUR 1,500Test problem-led buyer group.
LinkedInRemarketingEUR 1,500Warm engaged users before conversion asks.
LinkedInEngagement/proofEUR 1,000Support credibility and audience learning.

Historical action plan - May-June review

Original recommendations retained for context. July-August lead reconciliation is now required; August already shows no PMax delivery. Completion status for website and tracking changes is unconfirmed.

1 - Immediate

Fix lead reconciliation

Create a May-June table that classifies each Webflow lead by source, campaign, form path, sector, intent tier, outcome, and validation requirement.

2 - Immediate

Pause broad PMax exposure

Hold PMax Competitors and PMax #4 until spam risk, form quality, exclusions, and validated lead feedback improve.

3 - Next cycle

Rebuild Search around B2B terms

Use exact/phrase intent around merchant crypto payments, stablecoin settlement, PSPs, iGaming, MiCA, CASP, API, and business payment operations.

4 - Immediate

Use the landing page to qualify

Add reCAPTCHA plus one or two B2B-specific dropdowns for solution interest and industry/business type.

5 - Next cycle

Separate support from sales

Route new-client CTAs to contact/sales-contact, while preserving support-page tracking for existing-client enquiries.

6 - Ongoing

Reframe LinkedIn as quality testing

Judge LinkedIn by target-account engagement, assisted quality, and qualified lead forms before calling it a proven direct lead channel.

Approval gate.

This report recommends measurement and optimisation fixes. Any budget, campaign, tracking, CRM, or website changes require client and Chado approval before implementation.