Why browser and server events work together
Browser tracking describes activity during a visit: the landing page, products viewed, cart actions, and checkout. Server-side tracking can confirm that an order was recorded even when a browser purchase event is incomplete.
The two sources answer different questions. A backend purchase can confirm the transaction while lacking the browser identifiers needed to connect it to an ad. WeProfit brings them together where the available data supports a match.
The path from your store to an ad network
For Shopify, platform webhooks supply order information. For WooCommerce, the WeProfit plugin sends signed server-side order events. WeProfit processes store events and forwards supported conversion events to the destinations you connect.
- Collect the shopping journey and available identifiers.
- Receive the order confirmation from the ecommerce platform.
- Associate the purchase with available journey evidence.
- Route supported events to the intended advertising destination.
- Inspect delivery status and destination diagnostics.
One purchase can arrive through more than one path
A customer’s purchase may be observed in the browser and confirmed by the store. Event identifiers help distinguish repeated submissions from separate orders. WeProfit uses deterministic purchase identifiers and deduplication in its processing.
Check any independent browser pixel, channel app, or server integration already installed. Matching your own sources does not automatically reconcile an unrelated sender with different event identifiers.
What server-side tracking does not remove
Server-side delivery does not guarantee complete tracking, identical reports, or ad platform attribution for every order. Consent choices, unavailable identifiers, connection errors, and each network’s processing rules still affect the result.
Treat collection, delivery, and attribution as separate checks. Confirm the order exists, verify the event was sent, then inspect how each report gives credit. This makes it easier to find a setup problem without assuming every reporting difference is a lost purchase.
Check collection, consent and destination acceptance separately
A server connection does not eliminate the need for browser context, a valid destination configuration or appropriate consent handling. Missing click identifiers can still limit network matching. A retry should reuse the original event identifier, while independent integrations may use incompatible identifiers.
| Observation | Interpretation |
|---|---|
| A server order arrives | The order has reached WeProfit; campaign identity may still be incomplete. |
| A destination accepts the request | The handoff succeeded; attribution and reporting still depend on the destination. |
| An order has exact matching confidence | Direct linking evidence exists; this does not prove the ad caused the sale. |
| The storefront consent banner appears | The banner is visible; test that its choices actually reach browser and server tracking. |