Get your PayKickstart tracking to 95%+ accuracy guaranteed in writing.
PayKickstart powers thousands of subscription, course, and SaaS businesses. The default tracking fires Pixel on every initial purchase — but renewals, dunning recoveries, plan upgrades, and downgrades all stay invisible to Meta and Google. Smart Bidding optimizes for initial cart only, ignoring the LTV that actually pays your business. We rebuild PayKickstart tracking server-side with full subscription lifecycle events.
Free30 minutesNo obligation
PayKickstart · what breaks
Why PayKickstart subscription ROAS misleads
- 01
Renewals don't reach ad platforms
Recurring revenue invisible. Smart Bidding optimizes for $97 cart, not $1,164/year LTV.
- 02
Dunning recoveries aren't tracked
When PayKickstart recovers a failed payment, it's a real conversion — but never fires.
- 03
Plan upgrades / downgrades don't fire
Upgrade from $47 to $197 plan = +$150 revenue Meta never sees.
- 04
iOS-heavy info-product audience
30%+ of high-ticket buyers skew Apple — invisible to browser-only tracking.
PayKickstart · the fix
Outcomes — PayKickstart
Full subscription lifecycle CAPI
Trial · paid · renewal · upgrade · downgrade · cancel · winback
LTV-aware Smart Bidding
Optimize for total customer value
Dunning recovery counted
Failed-payment recoveries fire as conversions
Affiliate attribution preserved
affiliate_id flows through to ad platforms
PayKickstart · architecture
How a PayKickstart order should reach the ad platforms
PayKickstart handles checkout, affiliates and recurring billing, and the affiliate layer is what makes its attribution question different from every other cart.
- 1
Click identifiers captured at first touch
Click IDs are captured on the page preceding the checkout and passed in as custom fields, alongside the affiliate identifier so paid and affiliate sales can be told apart.
- 2
The browser sends the fast, fragile copy
The pre-checkout page fires browsing and checkout-start events. The checkout is hosted.
- 3
The order itself is the source of truth
The PayKickstart transaction is the truth, including bumps, upsells and every recurring charge.
- 4
A server container sends the authoritative event
The PayKickstart IPN or webhook posts each transaction to a GTM server container on your own subdomain, keyed on its transaction ID, with the affiliate flag carried through.
- 5
Customer identity raises match quality
The transaction carries buyer email and name, hashed server-side.
PayKickstart · events
The event set we build on PayKickstart, and where each one comes from
Affiliate sales must be distinguishable, or your paid campaigns are credited with revenue your affiliates produced.
| Event | Fires when, on PayKickstart | Key parameters | Sent from |
|---|---|---|---|
| begin_checkout | The PayKickstart checkout loads | value, currency, num_items, event_id | Browser + server, deduped |
| purchase | The main transaction succeeds, with the affiliate flag recorded | order_id, value, currency, items[], hashed email/phone/name/address, event_id | Server authoritative |
| subscription_started | A bump or upsell transaction succeeds | order_id, value, currency, plan, event_id | Server authoritative |
| subscription_renewed | A rebill succeeds | value, currency, plan | Server only |
| subscription_canceled | A subscription is cancelled or dunning fails | hashed email, plan | Server only |
| refund | A refund or chargeback is processed | order_id, value, currency | Server only |
PayKickstart · normal or broken
PayKickstart specifics
The affiliate channel is the thing that most distorts reported ad performance here.
Normal, not a fault
A large share of sales coming from affiliates
That is the model. Those sales belong in your revenue and not in your ad conversions.
Rebills arriving monthly with no session
Recurring revenue has no browser. Server-side only, by necessity.
Ad platforms report more conversions than you have orders
Meta credits a 7-day click and 1-day view; Google credits on click date. Two platforms can each claim the same sale. Compare each one to your order records separately and never add them together.
Recent days always look worse than they finish
Conversions are credited back to the date of the click, so yesterday's return on ad spend is understated and will keep improving for several days. This is attribution working, not data arriving late.
Actually broken
Affiliate sales counted as ad conversions
Every paid campaign's reported return is inflated by revenue affiliates produced.
Rebills and cancellations never reported
Lifetime value overstated at signup and never corrected when subscriptions lapse.
Click IDs not passed into the checkout
Nothing attributable.
PayKickstart · prove
How we prove the PayKickstart build is correct
The tag firing proves the tag fires. These prove the numbers are right.
Source of truth
PayKickstart transaction records
- Affiliate and direct sales confirmed distinguished, with affiliate sales excluded from ad conversions.
- Rebills and cancellations confirmed reporting.
- Click IDs confirmed reaching the transaction record.
- Revenue reconciled against PayKickstart records for a closed month.
- Purchase count within a few percent of paykickstart transaction records for a fully closed week, matched on order ID rather than on totals.
- No order ID appearing twice in any platform's event log.
- Deduplication confirmed at every destination that supports it.
- Test and staff orders excluded, with the exclusion confirmed active rather than merely configured.
- The same reconciliation repeated 30 days later, because a setup that works once and then drifts is the harder failure to catch.
PayKickstart · free audit
What we check in the free audit
- Renewals don't reach ad platforms
- Dunning recoveries aren't tracked
- Plan upgrades / downgrades don't fire
- iOS-heavy info-product audience
Checked against
PayKickstart transaction records
Free30 minutesNo obligation
PayKickstart · when not to buy
When a PayKickstart rebuild is not what you need
We would rather say this now than three weeks into an engagement.
- You run no affiliate program and no recurring billing. A simpler checkout build covers you.
- Sales come entirely from affiliates with no paid spend.
- You are moving to a different platform.
PayKickstart · what we deliver
Deliverables — PayKickstart
PayKickstart webhook integration
All subscription events
Server-side gateway
Worker or sGTM
Meta CAPI · Google EC · TikTok
Dedup-clean
Subscription lifecycle event spec
Schema-clean
Notion runbook + 30-day support
Replicable
Written guarantee
95%+ tracking accuracy
Measured against PayKickstart transaction records. Miss it and we keep working at no cost.
Pricing
Pick the package that fits your ad spend
Browser-side starter
$400One-time fee · lifetime ownership
Foundation pixel install for your PayKickstart store. Honest disclosure: this is a starting point only. If you spend $1K+/month on paid media you should be on the 1st-party server-side tier — rather than quote you a recovery percentage, we'll show you how to measure your own gap: compare what the platforms reported against the orders in your backend for the same week. That ratio is the entire argument, and it's yours to check — see trackingconsulting.com/measurement-accuracy-methodology.
- One-time fee · zero monthly · zero SaaS lock-in
- PayKickstart dataLayer (clean spec)
- GA4 e-commerce events
- Meta Pixel · Google Ads tag
- TikTok Pixel · Microsoft UET
- Consent Mode v2 banner integration
- QA test orders + 7-day support
- No CAPI · no iOS recovery
1st-party server-side
Recommended$800One-time fee · most popular
The done-for-you package every PayKickstart store running paid ads should start with. We build the entire 1st-party server-side stack on your subdomain — Meta, Google, TikTok, Microsoft, LinkedIn all fed from the server. Recovers the conversions iOS, Safari ITP, ad blockers and cookie deprecation hide today. You don't lift a finger. Built in 2–4 days · accurate data in 7 days.
- One-time fee · save vs SaaS subscriptions over 5 years
- Fully recovered + built in 2–4 days · accurate data in 7 days
- Everything in browser-side starter
- 1st-party server-side GTM (your subdomain)
- Meta CAPI · full advanced matching · 8+ EMQ
- Google Enhanced Conversions (Web + Leads)
- TikTok Events API · Microsoft UET server
- Deterministic browser ↔ server deduplication
- Live EMQ verification + screenshots
- Notion runbook + 30-day support · zero recurring
Full 1st-party stack
$1,800One-time fee · lifetime ownership
Every paid-media channel running 1st-party server-side, end-to-end. For PayKickstart brands spending $30K+/month who can no longer afford attribution leaks. Pay once. Own everything. Includes Pinterest + Snap + Reddit + LinkedIn CAPI, Klaviyo identity stitching, BigQuery + Looker Studio.
- One-time fee · save 6-figure SaaS subscriptions over 5 years
- Everything in 1st-party server-side tier
- Pinterest · Snapchat · Reddit · LinkedIn · X CAPIs
- Klaviyo identity stitching (if used)
- BigQuery export (server logs + GA4)
- Looker Studio attribution dashboard (branded)
- Multi-region / multi-currency / EU residency
- GDPR-audit-ready Consent Mode v2 wiring
- 60-day support · optional retainer · no lock-in
FAQ
PayKickstart questions, answered
Yes — multi-vendor accounts handled with proper routing.
More on PayKickstart
- GuideBigCommerce Conversion Tracking: GA4, Meta CAPI, and Google Ads Done Right
- GuideClickFunnels Conversion Tracking: The Complete Setup Guide for Google Ads and Meta
- Free toolFree PayKickstart audit
- 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…
Free · 30 min
Free PayKickstart audit
WhatsAppFree30 minutesNo obligation
