Technical requirements for integrating wetracked.io with a Payload CMS + Netopia payment flow

Hello team,
Here is the technical context you requested regarding our setup and what we need in order to implement wetracked.io on our website.

1. Platform details Our website (Pro Travel) is built on Payload CMS — a custom Node.js/React headless CMS.
   This means we do not use Shopify, WooCommerce or any platform with a native plugin.

We need a custom integration path.

2. Checkout & payment flow Our booking and payment flow works like this:

3. User selects a travel package (product page).

4. User fills in personal details and accepts contractual terms.

5. User is redirected to Netopia Payments (Romanian payment processor).

6. After payment, Netopia sends a server-to-server IPN webhook to our backend.

7. We generate the contract + invoice and send them by email.

We need wetracked.io to support this flow.

3. What we need from wetracked.io

A. Front-end tracking We need documentation for:

• loading the wetracked script in a custom React/Next.js front-end

• triggering events manually, such as:

  • PageView

  • ViewContent (travel package page)

  • InitiateCheckout

  • AddPaymentInfo

  • Lead (when user fills data but does not pay)

We need the exact JS functions or API calls to trigger these events.

B. Server-side Purchase event This is the critical part.

We need documentation for sending a server-side Purchase event from our backend when Netopia confirms the payment.

Specifically:

• endpoint URL

• required headers

• required parameters

• hashing rules for email/phone

• deduplication rules (browser + server)

• example payload for a Purchase event

We need to send:

• transaction value

• currency (EUR)

• booking ID

• product name (travel package)

• customer email (hashed)

• customer phone (hashed)

• payment status (success)

C. Webhook compatibility We need to confirm that wetracked.io can receive server-side events triggered after a third‑party payment processor (Netopia) sends us the confirmation.

This is essential because the payment does not happen on our domain.

D. Testing & validation We need instructions for:

• validating events in Meta Events Manager

• checking deduplication

• verifying server-side event delivery

• debugging mismatched or missing events

4. Summary To integrate wetracked.io with our Payload + Netopia setup, we need:

• front-end JS event documentation

• server-side API documentation for Purchase events

• deduplication rules

• examples for custom platforms

• confirmation that your system supports external payment processors via webhook-triggered server events

Once we have these, we can implement everything on our side.

Thank you.