Clicks & conversions
Send conversions to a traffic source
Return the source's external ID and inspect outgoing postback results.
When to use an outgoing postback
An outgoing S2S postback tells a traffic source about a conversion already processed in Nevect. You need a source that supports server conversion notifications, its current endpoint specification, and a working incoming conversion.
The source expects its own external click ID. Returning the Nevect click ID in that field will not identify the source’s original visit.
Record the external ID first
- Open Traffic sources and edit your source.
- Configure the external ID parameter with the source’s actual click-ID macro.
- Select that source in the campaign and copy the newly generated Campaign URL.
- Make an approved test visit, then open Clicklog and confirm the resolved external ID.
A literal macro or empty ID must be fixed before enabling outgoing conversion reports. For example, SOURCE_CLICK_001 and NV_CLICK_001 are different identifiers even when they describe the same visit.
Configure the outgoing URL
In the traffic source settings, enter the source’s S2S conversion endpoint. Use the editor’s External ID token for the source’s ID parameter, and map payout or event fields only as the receiving platform supports them. Select tokens from the editor rather than guessing their syntax.
| Setting | What to verify |
|---|---|
| Source ID parameter | Receives the recorded external ID, not Nevect’s cnv_id |
| Postback URL | Correct source endpoint and encoding |
| Postback % | Intended proportion of conversions to forward |
| Payout % | Intended share of revenue to report |
| Status-related postbacks | Correct event URL for each configured status |
| Campaign override | Advanced campaign settings may define a separate S2S URL |
Do not put an incoming Nevect Postback URL into this outgoing source field. Review effective campaign settings as well as the source defaults.
Verify the round trip
- Confirm a click with a known external ID in Nevect.
- Confirm its incoming conversion inside Nevect.
- Enable the intended outgoing behavior in an isolated or provider-approved test.
- Inspect the actual outgoing URL and the source’s response where available.
- Confirm the source associated the event with its original click.
An accepted HTTP request is separate from an attributed source conversion. Avoid fabricated sales in a live optimization campaign; use the source’s testing facility when available.
Troubleshoot the correct direction
| Symptom | Check |
|---|---|
| No conversion in Nevect | Fix the incoming partner callback first |
| Nevect conversion exists, no outgoing request | Suppression flags, postback percentage, status processing and campaign override |
| Source rejects the request | Endpoint, authorization, external ID, required event and encoding |
| Source accepts but cannot match | Compare its click ID with Clicklog; check its attribution rules |
| Duplicate or wrong revenue | Repeated partner notifications, Upsell, payout percentage and status mapping |
Keep the time, campaign, redacted resolved URL and exact response for support. Never publish source credentials or a live user’s full click URL. See tokens and macros for the value mapping.