Payment tracking
Tie every Stripe, Shopify, and Paddle payment back to its source
SourceLoop captures UTM parameters, click IDs (GCLID, fbclid, li_fat_id), referrer, and the visitor's full journey, then attaches them to every customer in Stripe, Shopify, Paddle, Polar.sh, Lemon Squeezy, and WooCommerce.
Free 7-day trial. No credit card required.
Used by 750+ marketing teams, agencies, and SaaS companies
Attribution stack
Revenue attribution from first click to closed payment
Stop guessing which channel actually pays for itself. SourceLoop ties the source captured on the first visit to the payment, and back to your CRM and ad platforms.
Every payment carries the source that drove it.
Revenue by channel, with true ROAS behind each.
See every touch before the card was charged.
Revenue lands in your CRM, attribution mapped.
How it works
Three steps from snippet to revenue tied back to source
One script, one OAuth connection, ROAS that reflects reality.
-
<script src="https://cdn.sourceloop.ai/sl.js" defer></script>
01Install the snippet
Drop one script tag in your <head>. Five minutes, no engineer required.
- 02
Connect your payment platform
One-click OAuth into Stripe, Shopify, Paddle, Polar.sh, Lemon Squeezy, or WooCommerce. We match each customer to the visitor session.
- A
Acme Co
- Source Google / CPC
- First touch LinkedIn / Paid
- Projected LTV $2,376
03Revenue ties back to channel
Each customer lands in your CRM with attribution, MRR, ARR, and LTV linked. ROAS and payback reports work day one.
Payment tracking by platform
Tie revenue from Stripe, Shopify, Paddle, Polar.sh, Lemon Squeezy, and WooCommerce
One snippet, one OAuth, every payment attributed.
-
Stripe
-
Shopify
-
Paddle
-
Polar.sh
-
Lemon Squeezy
-
WooCommerce
FAQ
Revenue attribution and Stripe tracking, FAQ
How do I tie Stripe customer revenue back to UTM source?
Install the SourceLoop snippet on your site and connect Stripe via OAuth. We match each new Stripe customer to the visitor session that brought them in, then attach the source, medium, campaign, and full journey to the customer record. The same flow works for Shopify, Paddle, Polar.sh, Lemon Squeezy, and WooCommerce.
Why does my Stripe customer arrive without source data?
Stripe sees the checkout, not the visitor's journey. By the time someone clicks an ad, browses your site, signs up, trials, and then pays a few weeks later, the original UTM is long gone from the URL. SourceLoop captures it on the first page view, persists it across the entire customer lifecycle, and writes it to the Stripe customer record at the moment of payment.
Does this work for subscriptions, renewals, and expansion revenue?
Yes. SourceLoop ties source data to the customer, not just the first invoice, so MRR, ARR, churn, and expansion all roll up by acquisition channel. Subscription billing through Stripe, Paddle, Polar.sh, and Lemon Squeezy reports revenue movement back to the source automatically.
Can I track Shopify and WooCommerce orders with UTM and ad source?
Yes. SourceLoop captures attribution on first visit, persists it through add-to-cart and checkout, and attaches it to each Shopify or WooCommerce order. Thank-you-page tracking, post-purchase upsell flows, and multi-currency checkouts are all supported out of the box.
Can I sync customer revenue back to Google Ads, Meta, or LinkedIn?
Yes. With Conversion Sync, we push revenue events back to Google Ads (using GCLID, Wbraid, Gbraid), Meta CAPI, and LinkedIn CAPI so Smart Bidding optimizes against actual revenue, not just leads.
How do I calculate LTV and ROAS by channel automatically?
SourceLoop ties every payment, every renewal, and every expansion event back to the original source, so LTV and ROAS by channel become standard reports in the dashboard. You can break them down by source, campaign, content, and landing page.
Does this work with consent banners and GDPR?
Yes. We integrate with OneTrust, Cookiebot, Iubenda, Osano, and custom CMPs. When a visitor declines analytics or marketing cookies, we collect only minimal aggregated data in line with GDPR and the ePrivacy Directive. All cookies and local storage are first-party on your domain.