Getting started
Verify a click and conversion
Use one controlled visit to check IDs, cost, payout and postback processing.
Isolate the test
Use a test campaign and an authorized destination. Keep outgoing partner postbacks disabled until their configuration is ready. A manual test must not report a fabricated sale to a live advertising account.
Verify the click
- Copy the generated Campaign URL.
- Replace source macros with recognizable test values where needed. An unreplaced macro is not a valid click ID.
- Open the link once in a browser.
- Find the visit in Clicklog, using the campaign and a narrow time range.
- Compare source tokens, external ID, destination, selected path and cost with your expected values.
Verify the conversion
Copy the Postback URL from Settings → Tracking links. Use the click ID from the test visit and a known payout. For an isolated manual test, the following illustrates the query fields. Replace the placeholders on your generated endpoint and preserve its actual path:
cnv_id=ACTUAL_TEST_CLICK_ID&payout=1&disable_postback=1
The disable_postback=1 parameter prevents this test from triggering an outgoing source postback. Inspect the matching click and conversion record; an HTTP response alone is not proof that a conversion was attributed.
Check the chain
| Check | Expected result |
|---|---|
| Incoming click | Visible in the intended campaign |
| Offer parameter | Contains the same tracker click ID |
| Postback ID | Matches an existing click |
| Payout/status | Matches the test values and processing scheme |
| Source postback | Sent only when intentionally enabled, with the external ID |
If records are missing
Check the date range and timezone, then inspect actual URLs rather than template text. A wrong domain, encoded placeholder, missing click ID, status rule or duplicate postback can explain a discrepancy. See postbacks and troubleshooting.
Use one record as the reference
Keep a short test log with the visit time and timezone, campaign, source external ID, Nevect click ID, expected destination, test cost and test payout. Compare that record with the actual URL and panel result at each step.
For example, with one isolated click, a cost of $0.10 and an accepted conversion payout of $1.50, the matching scope should contain that click and conversion with those inputs. This is an arithmetic example, not a promise about actual campaign profitability or a reason to send a fabricated sale to an advertising platform.
Locate the first failed checkpoint
| Last successful checkpoint | Next thing to inspect |
|---|---|
| Campaign saved | Open the generated URL and check request reachability |
| Destination opened | Find the click in Clicklog with the same campaign and time |
| Click recorded | Inspect the offer’s resolved sub-ID and any redirects |
| Partner received the ID | Inspect the returned cnv_id, payout and status |
| Conversion accepted in Nevect | Inspect the source external ID and outgoing postback configuration |
| Source accepted the request | Confirm the source actually attributed the conversion |
Change one mapping at a time and use a new controlled click when retesting repeat-notification behavior. Keep production conversion records intact. For the full incoming parameter example, see S2S postback tracking.