PixelYourSite saves the traffic source, landing page, and full UTM set for every Easy Digital Downloads payment. The data lives in your site’s database, attaches to each payment, and powers a built-in reports page that shows what your ads, channels, and pages actually sold.
What gets saved on every EDD payment
For every payment PYS stores two sets of attribution data: first visit (the very first time the buyer landed on your site) and last visit (their most recent landing before the order).
Per set, PYS records:
- Traffic source — the referrer captured on landing.
- Landing page — the first URL the visitor opened in that session.
- utm_source / utm_medium / utm_campaign / utm_term / utm_content — pulled from the URL.
That’s seven attribution signals, twice — fourteen pieces of data per payment. Stored in dedicated tables on your WordPress database, linked by payment ID. The payment value is stored alongside, so reports can roll up revenue per source, per campaign, per ad.
Where to see the data
- Downloads → Payment History → view a payment — a PYS enrich block appears below the order details with all the captured fields for that payment.
- PixelYourSite Pro → Easy Digital Downloads Reports — a dedicated reports page (
admin.php?page=pixelyoursite_edd_reports) breaks down payments, revenue, and downloads sold per:- Traffic source
- Landing page
- utm_source
- utm_medium
- utm_campaign
- utm_term
- utm_content
- CSV export — download any breakdown from the reports page for spreadsheet work.
Each report row links back to the payments that produced it, so you can drill from a campaign down to the individual payments and the downloads in them.
Where to configure it
PixelYourSite Pro → Easy Digital Downloads → Save data to orders.
One switch: Save data to orders (default on). When it’s on, PYS hooks into every EDD payment lifecycle event — creation, status change, save, delete — and keeps attribution synced with the payment.
Capture UTMs with the built-in templates
For the report to fill, your ads have to land visitors with UTMs in the URL. PixelYourSite ships copy-paste UTM templates that pre-fill source, medium, campaign, ad set, and ad names for Meta, Google, Pinterest, Bing, and TikTok.
Where: PixelYourSite Pro → Global Settings → UTM Builder.
For anything else — newsletter links, affiliate links, partner placements — build a UTM with the same builder and paste it into the link.
What this gives you that ad-platform reports don’t
- Real download attribution. Meta and Google can tell you which campaign drove a purchase event, but they don’t tell you which downloads were in the order. The reports page lists downloads per campaign, ad set, or ad.
- First-visit attribution. Ad platforms use last-touch by default. PYS keeps both first-visit and last-visit, so you can credit the source that actually opened the door, not just the one that closed it.
- Works when the pixel doesn’t. iOS 14.5+, Safari ITP, Firefox ETP, ad blockers — they all reduce what Meta and Google see. The first-party reports are built from your site’s own server-side data, so they capture payments the ad platforms underreport.
- Channels Meta and Google can’t see at all. Direct, email, organic search, affiliate, podcast, QR code, offline. All of it lands in the reports as long as the entry URL carries a recognisable referrer or UTMs.
What’s actually first-party here
- The data is collected on your site by PYS, not by a third-party script.
- It’s stored in your WordPress database, on tables PYS creates. Nothing is sent to an external server.
- Cookies used (
pys_landing_page,pysTrafficSource, plus thelast_*versions) are set on your domain. - You own it. No vendor can take it away.
Limits
- Attribution covers UTM-tagged and referrer-detectable traffic. A visitor who lands from a paid ad without UTMs and a stripped referrer (some apps and privacy browsers do this) shows up as
direct/ no source. - Cookie loss. If the visitor clears cookies between the first visit and the payment, the first-visit set falls back to the last-visit set.
- Cross-device. Tracking is per-browser. A visitor who landed from a Meta ad on their phone and purchased on their laptop shows up as two different sessions with the laptop’s source attached to the payment.
- Cache and consent. A cache that ignores PYS’s first-visit cookie can lose the original landing page. A visitor who declines consent before the cookies are set won’t be tracked.