I need our AWIN affiliate programme moved from the current browser-side pixel to a robust server-to-server implementation so every conversion is reported with zero loss. AWIN’s documentation (which I will share in full) outlines three supported routes—S2S via Google Tag Manager, S2S via their public API, or a direct S2S postback. Any of those approaches is acceptable; whichever you feel will be quickest and most reliable for our stack is fine with me. The core event I must see inside AWIN is Conversions. Click-through and revenue numbers are already handled elsewhere, so the job is laser-focused on firing the conversion event, passing the transaction ID, order value and any other mandatory parameters AWIN requires, and confirming that the AWIN interface shows the sale immediately after a successful test order. You’ll need to: • Review the AWIN doc and choose/justify the method that best fits • Create the server endpoint or GTM server container logic, along with any API authentication needed • Map and pass mandatory & optional parameters (order ID, sale amount, currency, etc.) • Run test conversions, capture AWIN’s “validated” response, and supply screenshots or logs as proof • Leave me with concise install notes so future devs can replicate the setup Acceptance criteria: an AWIN test transaction appears in the interface under “Pending” within minutes, and a real purchase in our production site is logged without browser cookies. Please factor in a short handover call or Loom walkthrough at the end so I’m comfortable maintaining the integration. The above is a Freelancer AI created project brief and I am not sure whether it corresponds in all details to the project I have in mind. I have complete AWIN instructions that should take precedence over anything outlined above.