Influencer conversion tracking: a practical guide

To measure an influencer campaign, verify three separate things: a click on the creator’s link, tracking loading on your website and receipt of the intended action. Detecting a pixel does not prove an attributed sale. An order in your store does not by itself prove that it came from a WeeGlad campaign.

What is an attributed conversion?

A conversion is the action defined in the offer, such as a lead or purchase. Attribution connects that action to a campaign and creator. The tracking link establishes the context; the website or connector must then report the appropriate event.

Attribution has limits. Refused consent, a blocker, changing browsers or losing campaign context can prevent a match. Store orders and attributed sales may therefore differ.

What does pixel detection prove?

Detection shows that tracking code loaded and sent its installation signal. That is useful, but it does not validate the complete journey.

You still need to check that the final action sends the correct event, that any required amount is consistent and that the event matches the right campaign. Distinguish a received signal from a financially confirmed payment when interpreting earnings or refunds.

How should you prepare Shopify?

Use the custom Shopify pixel guide for your site in WeeGlad tracking settings. Avoid installing duplicate versions through the theme and customer events.

Follow the guide’s customer privacy settings. Check pixel loading and the checkout completion event with Shopify’s test tools. Reconcile that signal with the order and WeeGlad’s recorded result; the signal alone is not an independent confirmation from the payment provider.

Leads without purchases require their own event. Testing checkout does not test a contact form. Follow the current instructions in your account rather than an old App Store installation procedure.

How should you prepare WooCommerce?

The WooCommerce connector links your store to the site declared in WeeGlad. Keep its private configuration inside WordPress administration, never in an article, public screenshot or third-party message.

Tracking depends on the configured consent mechanism. Check order reporting and payment state on both the store and connector sides. Simply visiting a confirmation page does not replace that verification.

What about another website or a service business?

Identify the real action: a confirmed booking, submitted form or completed purchase. Trigger the event on that action, rather than a button click or an invented thank-you page.

For a service business, a lead may be more appropriate than an online purchase. If the action ends in another tool or domain, check how campaign context is preserved. Do not assume phone calls or offline sales are tracked automatically without a suitable integration.

How can you test the complete journey?

1. Use a test campaign and suitable test store or environment with fictional data.
2. Open the creator’s link in the same browser that will complete the action.
3. Provide the consent required for the planned test journey.
4. Complete the action with the store’s test payment method, without a real purchase to check installation.
5. Reconcile the click, received event, order or lead reference and result shown in WeeGlad.

Also test refused consent and a repeated submission of the same event. The former helps explain measurement limits; the latter helps identify double counting.

How should you interpret the results?

A visit proves an arrival. An event proves a signal was received. An attributed conversion proves a match under the tracking rules. Payment and net earnings remain separate stages.

Choose a payment model that matches what you can measure. See the FAQ, pricing and privacy policy, published in French, for practical terms.