Domains & integrations
Partner conversion integrations
Verify each network's identifier, status and notification format.
Start with the partner contract
Different affiliate and commerce platforms return conversions through different mechanisms. Some support a simple S2S postback; others provide a signed notification or a dedicated integration. A generic query-string example does not replace those requirements.
Configure the matching workflow
- Identify the integration supported by the current panel and the partner.
- Pass the tracker click ID using the partner's approved tracking field.
- Configure the return endpoint from your installation's generated instructions.
- Preserve exact field names, signature requirements and required identifier formats.
- Select the intended status and payout processing behavior.
Validate a complete event
Use the partner's approved test facility or an authorized controlled transaction. Compare the ID passed to the partner, the notification received and the resulting tracker record. Verify whether an approval, refund or recurring payment updates an existing record.
Keep ownership clear
Nevect licensing and partner accounts are separate. Provider credentials should be stored only in their dedicated settings. Do not publish a webhook secret in a campaign URL.
If a notification fails
Keep the provider request time, non-sensitive error and the expected click association. Confirm endpoint reachability and signature configuration before replaying anything. Replaying a live billable event can duplicate its effects if the integration is not idempotent.