How to Track Influencer Sales on WooCommerce with PixelYourSite

The problem with influencer attribution on WooCommerce

You pay ten influencers to promote your store. They post your link. People click, browse for a while, leave, come back later, eventually buy.

Your WooCommerce reports show 30 sales for the week. Some came from the influencers. Some came from your ads. Some came from organic search. You have no idea which were which.

The usual fix is to hand out a discount code per influencer and count orders that used the code. That works only for the customers who actually use the code at checkout. The ones who buy at full price disappear into the same anonymous pile as everyone else.

You can do better with what is already inside PixelYourSite Pro.

The solution

Three pieces:

1. Each influencer gets a unique URL parameter, for example ?infl=mike or ?infl=sara.
2. PixelYourSite captures the landing URL when the visitor first arrives and keeps it for the whole session.
3. A Custom Event (a new event you define inside PYS Pro) fires whenever the visitor lands on the WooCommerce thank-you page AND the landing URL had that influencer’s parameter.

Send these events to Google Analytics 4. GA4 has the right tools for the job: Key Events, Explorations, and audience sync with Google Ads. Meta can receive the events too, but only as a way to build Lookalike audiences. Per-influencer volume is too small for Meta’s bidding to learn from, and your standard Meta Purchase event is already handling that work.

This runs alongside your standard Purchase event

PixelYourSite already fires a standard WooCommerce Purchase event for every order. Your normal revenue tracking, Meta Purchase optimization, and GA4 purchase reports keep working exactly as they do today. The Custom Event you are about to build is a second, separate event that fires only when the influencer condition matches.

One detail to know: the trigger called “WooCommerce purchase” inside the Custom Event editor is not the standard Purchase event. It is a built-in condition meaning “the visitor is on the WC thank-you page right now.” It does not send a Purchase event itself, it just tells your Custom Event when to check whether to fire. So for one influencer-driven order you will see two events in GA4: the standard purchase, and your MikePurchase.

Step by step

1. Give each influencer their link

Pick a parameter name and stick with it. infl, inf, ref, or full UTMs all work. Keep it short, lowercase, and don’t change it once the campaign starts.

Examples:

• https://yoursite.com/?infl=mike
• https://yoursite.com/product/blue-shirt/?infl=sara
• https://yoursite.com/?utm_source=influencer&utm_campaign=mike (more verbose, but shows up in GA4’s standard acquisition reports too)

Both at once is fine: ?infl=mike&utm_source=influencer&utm_campaign=mike. The Custom Event you set up next will read whichever part you point it at.

2. Build the Custom Event in PYS Pro

In your WordPress admin, open PixelYourSite Pro → Events → Custom Events and click Add new event.

General card:

• Event Name: MikePurchase.
• Leave the “Fire this event only once in N hours” throttle OFF. You want every sale.

Event Triggers card:

• Trigger Logic: leave as OR (you only have one trigger).
• Add trigger: WooCommerce purchase.
• Turn ON Fire this event for transaction only. Prevents the Custom Event from firing twice if the customer refreshes the thank-you page.
• Turn ON Track transaction ID. The WooCommerce order ID then flows into GA4 with the event, so you can cross-reference any line back to a real order.
• Turn ON Track value and currency. The order total flows through too. You need this for revenue reporting and for paying commissions accurately.

Conditions card:

• Switch on Enable Conditions.
• Logic: AND.
• Add condition: Landing page.
  • Rule: Landing page URL parameters contains
  • Value: infl=mike

The rule choice matters. Landing page contains and Landing page match compare the landing URL with its query string stripped, so they will not see your ?infl=mike at all. Landing page URL parameters contains keeps the query string. Pick that one. URL parameters match requires an exact match on the full URL, which breaks the moment anything else gets appended.

3. Pick the destinations

Lower on the same edit page, enable the platform cards you use and set the event name for each. Do not name it Purchase. That is the standard event PYS is already sending for every order.

Recommended order:

• Google Analytics (GA4) — primary. Event action MikePurchase. After the first event shows up in DebugView, mark it as a Key Event under GA4 → Admin → Events. Because you turned on “Track value and currency” in the trigger, GA4 sees the order total automatically, and the order ID is attached.
• Meta — optional. Custom event name MikePurchase. Useful only for building Custom Audiences and Lookalikes.
• TikTok, Pinterest, Bing — optional. Same name, same purpose as Meta.

Save the event.

4. Repeat for each influencer

Use the Duplicate button in the Events List, change the event name to SaraPurchase, change the condition value to infl=sara, save. Repeat once per influencer.

If you have a long roster (twenty or more), this gets old fast. You can collapse them into a single event by using infl= as the condition value (matches any infl parameter at all), adding a per-event custom parameter that captures the value from the landing URL via PYS’s dynamic value from page option, and segmenting in GA4 on that parameter. For most stores, one event per influencer is easier to read and easier to wire into payout reports. Start there. Switch later only if the list gets too long to maintain.

The GA4 Exploration, step by step

The report to build right away. Takes about three minutes.

1. In GA4, go to Explore in the left sidebar.
2. Start a new Blank exploration. Set Technique to Free form.
3. Pick a Date range. Last 30 days is fine for most stores.
4. Under Dimensions, click the + and import Event name. Drag Event name into the Rows slot.
5. Under Metrics, click the + and import Event count and Total revenue. Drag both into the Values slot.
6. Under Filters, drag Event name in. Set the condition to matches regex and enter:

   .+Purchase$

That pattern catches every event whose name ends in Purchase (so MikePurchase, SaraPurchase, JuliaPurchase, and so on) and skips the standard purchase event, because the regex requires at least one character before Purchase and is case-sensitive. 7. Rename the tab to Influencer sales — last 30 days and save the Exploration.

One row per influencer. Sort by Total revenue descending. Top earners at the top. Export to CSV at payout time using the share menu in the top right.

To slice it further, add a secondary dimension like Session source / medium or Landing page in the Columns slot. Useful if an influencer uses different UTMs per surface (Instagram bio vs. story vs. TikTok caption).

Build the Google Ads audience

In GA4, go to Admin → Audiences → New audience → Build a custom audience.

• Name: Bought after landing from Mike
• Include users when: Event name equals MikePurchase
• Membership duration: 30 days (longer if your sales cycle is longer).
• Save.

Once GA4 is linked to Google Ads (Admin → Product links → Google Ads links), the audience appears in Google Ads under Audience manager → Audience sources within a day or two. Use it for remarketing or as a similar-audience source.

If revenue shows zero

If the event count climbs but Total revenue stays at zero, two things to check:

• The WooCommerce purchase trigger on the Custom Event has Track value and currency turned on. If it doesn’t, no monetary value is sent at all.
• The GA4 card on the same event has the value parameter mapped (it usually is by default). Open GA4 → Admin → DebugView, place a test order, and look at the incoming event. The value parameter should be there with the order total.

Bonus uses in the ad platforms

If you also send the event to Meta, build a Custom Audience of users who fired MikePurchase and create a 1% Lookalike. The audience is usually small, so the Lookalike works better once a few hundred users have fired the event.

If you want to compare influencer-driven sales against your paid ads on the same scale, build another Custom Event in PYS for paid traffic (utm_source=google, utm_source=facebook) using the same landing-URL pattern. Now you can sit in GA4 and look at cost per sale across all your acquisition channels in one report.

Things to know before you trust this

Some platforms rewrite or strip URL parameters. Instagram bio links go through Instagram’s redirector. TikTok bios go through TikTok’s. Linktree is its own redirect. Test the link from inside the platform the influencer actually posts on, on a real phone, in a real browser, before assuming it works. If the platform strips your parameter, set up a short redirect URL on your own domain (https://yoursite.com/go/mike that 301-redirects to https://yoursite.com/?infl=mike) and give the influencer the redirect link.

Direct-search buyers won’t fire the event. If a customer hears about you from Mike in a video, doesn’t click the link, types your brand name into Google, lands via organic, and buys, that sale won’t be attributed to Mike by this method. This is a known limit of any URL-parameter attribution. A workaround is to also give Mike a discount code, and pay him on the sum of attributed events plus discount-code usage.

Test once before paying anyone. Open your site in an incognito window, hit https://yoursite.com/?infl=test, place a small test order, and confirm the event arrives in GA4 DebugView. Then create the real per-influencer events.

The stack

• WooCommerce running your store
• PixelYourSite Professional for the Custom Events feature and the per-platform server-side connections
• A configured GA4 Measurement Protocol connection (and any other destination you want the event to land in) inside PYS Pro