Nevect

Clicks & conversions

Track custom events

Record intermediate funnel events and interpret their scope correctly.

Checked for Nevect 1.0.6 · Updated

Choose an event

Use events for an intermediate action you want to analyze, such as a page interaction or another supported funnel step. Define its meaning consistently across the campaign before adding the code.

Use generated event instructions

Open the event or tracking-link controls in the panel. Copy the generated code or URL for the intended event and campaign context. Preserve the event identifier and click context rather than constructing a new identifier by guesswork.

Implement and test

  1. Add the code only to the action that represents the event.
  2. Start a controlled visit through the campaign.
  3. Trigger the action once.
  4. Inspect the recorded event in the available click or report fields.
  5. Repeat the action to establish whether it updates, counts again or is limited by the configured behavior.

Compare with conversions

An event is not automatically a paid conversion. Keep event counts, leads, payout and source notifications separate unless you have explicitly connected them through supported processing settings.

Troubleshoot

Check that the code executed, that a valid click context exists and that the event belongs to the selected reporting period. A button handler attached twice can send two requests. A browser restriction can prevent a request even when the page looks correct.