Konnektive CRM tracking pixel setup: a full walkthrough

Why Konnektive trips up most advertisers

Konnektive does not store affiliate click IDs natively. Out of the box, a click from Everflow, HasOffers, or Trackier hits your order form, the customer converts, and the click ID vanishes — because there is nowhere on the order record to put it. The fix is a custom field plus a small form-side script, and it has to be done in the right order or the postback fires with an empty parameter.

I have onboarded 30+ advertisers onto Konnektive in the last four years. The setup below is the one that survives audit, scale, and the occasional theme change.

Step 1 — Create a custom order field for the click ID

In Konnektive, go to Admin > Custom Fields > Order Custom Fields and create a new field. Name it something unambiguous like affiliate_click_id. Set the type to Text and mark it as required only if 100% of your traffic is paid (otherwise organic orders will fail validation).

Write down the field's internal name exactly as Konnektive stores it — you will reference it in the postback URL and the order form. A typo here is the #1 cause of empty postbacks.

Step 2 — Capture the click ID on the order form

On your landing page or order form, add a hidden input that reads the click ID from the URL query string and posts it with the order. The standard Everflow macro is transaction_id; HasOffers uses aff_sub or transaction_id; Trackier uses click_id.

• Add a hidden input: <input type="hidden" name="affiliate_click_id" id="affiliate_click_id" />
• On page load, parse the URL with new URLSearchParams(window.location.search).
• Read the network's macro key (transaction_id, click_id, etc.) and write it into the hidden field's value.
• Persist it in sessionStorage so refreshes, multi-step funnels, and upsell paths do not lose it.
• On every step that POSTs to Konnektive, re-attach the value — do not assume the form library carries hidden fields across steps.

Step 3 — Map the field to the order payload

Konnektive's importOrder and importLead endpoints accept arbitrary custom field values via custom_<fieldname> parameters. When you POST the order, include custom_affiliate_click_id=<value>. If you use Konnektive's hosted checkout, the hidden input name has to match exactly — case sensitive.

Verify in the Konnektive admin: open a test order and confirm the Affiliate Click ID field is populated. If it is blank, your form is not posting the field or the name is mismatched. Fix this before touching the postback.

Step 4 — Build the outbound postback URL

In Konnektive, go to Campaigns > [Your campaign] > Postbacks and add a new postback for the network. The URL template uses Konnektive macros — wrap field references in tildes: ~custom_affiliate_click_id~.

• Everflow: https://www.<your-network>.com/?nid=<network_id>&transaction_id=~custom_affiliate_click_id~&amount=~orderTotal~&adv1=~orderId~
• HasOffers / Tune: https://<your-domain>.go2cloud.org/aff_lsr?transaction_id=~custom_affiliate_click_id~&amount=~orderTotal~
• Trackier: https://<your-tracking-domain>/conversion?clickid=~custom_affiliate_click_id~&txn_id=~orderId~&amount=~orderTotal~

Step 4b — Fire on the right event

Fire the postback on the SALE_APPROVED event, not SALE_CREATED. Created fires before payment processing finishes, and a 3DS challenge or fraud decline will leave you paying out on orders that never collected. Test this by triggering a decline in your gateway sandbox — the postback should not fire.

Step 5 — Handle voids, refunds, and rebills

Most advertisers stop after step 4 and then spend the next quarter arguing with affiliates about voided orders that were never reversed on the network. Konnektive supports reversal postbacks: configure a second postback on the VOID and REFUND events that hits the network's reversal endpoint with the original transaction ID.

For subscription offers, fire a separate rebill postback on REBILL_APPROVED with a different event type so the network credits the affiliate on the lifetime value model you negotiated — not the initial sale only.

Step 6 — End-to-end QA

• Click a tracking link with a unique sub1=qa-<date> value.
• Complete a $1 test order in Konnektive's test gateway.
• Open the order in Konnektive admin — confirm the click ID field is populated.
• Check Konnektive's Postback Log — confirm outbound fire with the correct URL.
• Check the network's inbound postback log — confirm receipt and recorded payout.
• Void the order in Konnektive — confirm the reversal postback fires and the network removes the conversion.

Where this fits with the rest of your stack

Konnektive is one node in the chain. If you are still diagnosing failures upstream, the Everflow postback checklist covers the network side. If you are choosing between server-side and browser tracking, the S2S vs pixel piece walks through the trade-offs. And if you want this set up for you end-to-end, I do this as a fixed-scope engagement — see the Konnektive consultant page.