Getting started
Your first tracking setup
A checklist from account creation to a verified click and conversion.
Before you begin
You need a Nevect account, a supported Ubuntu server with root access, a domain you control, and an offer or destination you are authorized to test. Your Nevect account manages licenses; the tracking panel runs on your server. These are separate sign-ins.
Find your next step
| Your current situation | Start here | Finish this checkpoint |
|---|---|---|
| Still deciding which tracker to use | Tracker selection guide and current plans | Confirm the required tracking workflow, hosting responsibility and available terms |
| Ready for a new installation | Server requirements | Confirm Ubuntu, x86_64, root access and a dedicated host |
| Already installed | Binding and activation | Match the full Tracker ID, apply a term and confirm expiry |
| Already active | Create your first campaign | Record one controlled click and its matching conversion |
Check the trial or paid terms actually available in your account. Binding an installation, obtaining an available term and applying it are separate operations. You can use an existing healthy installation; renewing its license does not require another installation.
Follow the setup in order
- Prepare the server and connect over SSH.
- Sign in to your account. Copy both personalized installation commands and follow the installation guide.
- Open the login URL printed by the installer. Save the credentials securely.
- Bind the Tracker ID and apply a term. Confirm the intended server, license state and absolute expiry, then continue to the tracking domain.
- Add your domain and verify HTTPS.
- Add a traffic source and an offer, then create your first campaign.
- Verify the tracking chain before you purchase traffic.
What success looks like
A controlled campaign visit appears in Clicklog. The destination receives the same click ID you can find in the tracker. A test conversion is matched to that visit, with the intended payout and status. When you enable outgoing postbacks, the traffic source receives its own external click ID.
If a step fails
Work forward from the last successful step. A license problem is different from a missing click parameter or an unreachable destination. Keep the time, campaign ID and exact error so you can compare the panel, server and partner logs.
| Last completed checkpoint | Next guide |
|---|---|
| Installer finished and panel login opens | Bind the installation and apply a term |
| The correct installation is active | Configure its tracking domain |
| The domain works | Create one campaign |
| A click is visible but no conversion is matched | Verify the click and postback |
| The conversion is matched but figures differ | Check cost, payout and reporting scope |
Keep a small setup worksheet
Before opening the editors, prepare the following values. Keep credentials outside this worksheet if you share it for support.
| Item | Example or source | Used for |
|---|---|---|
| Server | Your dedicated Ubuntu host | Installation and persistent tracking data |
| Tracker ID | Printed by the installer | Portal binding and license activation |
| Tracking domain | A domain you control | Generated campaign and callback links |
| Source external ID macro | Your traffic source’s documented macro | Matching the outgoing source conversion |
| Offer sub-ID parameter | A partner-supported field, for example sub1 |
Carrying Nevect’s click ID to the offer |
| Incoming Postback URL | Settings → Tracking links | Receiving the partner’s conversion |
Know when the setup is ready
Do not judge readiness only by a successful installer exit. Confirm these results separately:
- The panel login opens, and your account contains the correct bound Tracker ID with an active term.
- Your tracking domain resolves to this server and the HTTPS certificate is valid.
- A controlled Campaign URL visit appears in Clicklog with the expected external ID and destination.
- The offer receives Nevect’s click ID, and a controlled incoming postback matches that same click.
- Payout and cost are recorded as intended, and the report’s date range and timezone include the test.
If you are still assessing the product, use the selection checklist and inspect the product workflow before preparing a server.