<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Nevect]]></title><description><![CDATA[Nevect]]></description><link>https://nevect.hashnode.dev</link><generator>RSS for Node</generator><lastBuildDate>Wed, 18 Nov 2026 14:33:02 GMT</lastBuildDate><atom:link href="https://nevect.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[The postback returned 200. Nothing attributed.]]></title><description><![CDATA[If you run paid traffic into an offer and use server-to-server (S2S) postbacks, you will eventually see this: the partner's log says the postback was sent…]]></description><link>https://nevect.hashnode.dev/the-postback-returned-200-nothing-attributed</link><guid isPermaLink="true">https://nevect.hashnode.dev/the-postback-returned-200-nothing-attributed</guid><category><![CDATA[Affiliate marketing]]></category><category><![CDATA[tracking]]></category><category><![CDATA[Advertising]]></category><category><![CDATA[marketing]]></category><dc:creator><![CDATA[Nevect]]></dc:creator><pubDate>Tue, 17 Nov 2026 08:51:52 GMT</pubDate><content:encoded><![CDATA[<p>If you run paid traffic into an offer and use server-to-server (S2S) postbacks, you will eventually see this: the partner's log says the postback was sent, your access log or their dashboard shows HTTP 200, and your report still has a click with no conversion.</p>
<p>That is not usually "the tracker is down." It is usually a matching problem. Two different click IDs are in play, and one of them went to the wrong side.</p>
<h2>Who this is for</h2>
<p>This is for affiliates and media buyers who already have a tracker, a traffic source, and an offer that is supposed to fire a postback. You can read a URL. You have at least one test click you can fire yourself.</p>
<p>If you only use a thank-you-page pixel and never touch postback URLs, this will feel abstract. If you cannot or do not want to operate your own tracking domain, you can still use the same ID-matching idea on a hosted tracker. The mistake does not depend on who runs the box.</p>
<h2>Two directions, two IDs</h2>
<p>Keep these separate. Most "200 but nothing attributed" cases come from swapping them.</p>
<p><strong>Incoming — the network or offer calls you.</strong><br />The partner hits <em>your</em> postback URL and must return the click ID <em>your tracker</em> stamped on the visit. In Nevect that identifier is <code>cnv_id</code>. The tracker uses it to find the original click and attach a payout or status. If that value is missing, truncated, or is actually the traffic source's ID, the request can still return 200. The server accepted a well-formed HTTP call. It just could not match a click it knows.</p>
<p><strong>Outgoing — you call the traffic source.</strong><br />After a conversion is already recorded, your tracker may notify the source so that source can attribute, optimize, or stop the click. The source has never heard of <code>cnv_id</code>. It only knows the external click ID it stamped when it sent you the visitor. You had to capture that ID on the landing click and send <em>that</em> value back. If you send the Nevect ID instead, the source will often return 200 too. Their endpoint is up. They just cannot attach the event to a click in their log.</p>
<p>A 200 means "we received the request." It does not mean "we matched it."</p>
<h2>A way to tell which side broke</h2>
<p>Do this on one authorized test click, not on live spend.</p>
<ol>
<li>Click your own campaign link. In the tracker, open that click and copy the tracker click ID (<code>cnv_id</code>) and the source's external ID, if one was stored.</li>
<li>Confirm the offer or network actually received <em>the tracker ID</em>. If their postback URL was built with the source ID, or with a macro that never filled, the incoming call cannot match.</li>
<li>In your tracker, look at the incoming postback result for that click: status, the ID that arrived, payout, and whether a conversion was created. A 200 with an unknown or empty ID is an incoming match failure.</li>
<li>Only after the conversion exists in <em>your</em> report should you inspect the outgoing postback to the source. Check that the URL contains the source's ID, not <code>cnv_id</code>, and read the source's response body, not just the HTTP status.</li>
</ol>
<p>If step 2 or 3 fails, fixing the outgoing URL will not help. You are notifying the source about a conversion you do not have yet.</p>
<p>If step 3 succeeds and the source still shows nothing, the incoming side is fine. The outgoing ID or the source's endpoint specification is the problem.</p>
<h2>Other reasons a 200 still helps no one</h2>
<p>ID mix-ups are the common case, not the only one.</p>
<ul>
<li>The partner fired the postback before the click was written, or fired it twice. You will see a conversion on the wrong click, a duplicate, or a reject, depending on how uniqueness and statuses are set.</li>
<li>The ID was passed through a redirect that truncated the query string, or through a lander that never appended the tracker parameter.</li>
<li>The offer does not accept a tracker click ID at all. Then S2S matching will not start, and you are back to a pixel or to manual reconciliation on that offer. Do not expect a postback template to invent a protocol the partner does not have.</li>
<li>Timezone, currency, or "lead vs sale" status can make a matched conversion look "wrong" in a report even though it did attach.</li>
</ul>
<p>The setup details belong in the docs, not here. For the incoming URL, see <a href="https://nevect.com/docs/tracking/postbacks/?utm_source=hashnode&amp;utm_medium=content&amp;utm_campaign=acq_202611">S2S postbacks</a>. For talking back to the traffic source, see <a href="https://nevect.com/docs/tracking/source-postbacks/?utm_source=hashnode&amp;utm_medium=content&amp;utm_campaign=acq_202611">outgoing source postbacks</a>.</p>
<h2>What this has to do with self-hosting</h2>
<p>Self-hosting does not prevent the ID mistake. It changes where the incoming call lands: on a domain and a server you operate, so the conversion intake is first-party. You can also read your own access logs when a partner swears the postback was sent.</p>
<p>It does not remove the need to capture the source's external ID on the click, or the need for the partner to send your ID back. If you do not want to run a server, a hosted tracker can do the same matching. The operators who should self-host are the ones who already want the log on their own box.</p>
<h2>If you are about to scale a campaign</h2>
<p>Fire one test click and one test conversion first. If the incoming postback, the row in your report, and the outgoing notice to the source do not line up, do not add budget. A 200 in someone else's log is not a green light.</p>
<p>To see how Nevect wires this, start with the <a href="https://nevect.com/docs/tracking/postbacks/?utm_source=hashnode&amp;utm_medium=content&amp;utm_campaign=acq_202611">postback docs</a>, then the <a href="https://nevect.com/docs/start/quickstart/?utm_source=hashnode&amp;utm_medium=content&amp;utm_campaign=acq_202611">quickstart</a>. Confirm current license prices on <a href="https://nevect.com/pricing/?utm_source=hashnode&amp;utm_medium=content&amp;utm_campaign=acq_202611">pricing</a> before you treat any figure as final. Hosting is separate, and a 7-day trial exists at the time of writing (16 November 2026, Asia/Shanghai); check the live page.</p>
]]></content:encoded></item><item><title><![CDATA[Self-hosted affiliate tracking with Nevect (S2S postbacks)]]></title><description><![CDATA[Media buyers who send traffic to affiliate offers usually depend on a network pixel or a shared tracking domain. That works until the domain is flagged…]]></description><link>https://nevect.hashnode.dev/self-hosted-affiliate-tracking-with-nevect-s2s-postbacks</link><guid isPermaLink="true">https://nevect.hashnode.dev/self-hosted-affiliate-tracking-with-nevect-s2s-postbacks</guid><dc:creator><![CDATA[Nevect]]></dc:creator><pubDate>Thu, 29 Oct 2026 01:39:29 GMT</pubDate><content:encoded><![CDATA[<p>Media buyers who send traffic to affiliate offers usually depend on a network pixel or a shared tracking domain. That works until the domain is flagged, the pixel is blocked, or you need the raw click and conversion log on infrastructure you control. Self-hosted tracking keeps the click record, the offer rules, and the conversion history on a server you operate, instead of renting them from a hosted tracker.</p>
<p>Server-to-server (S2S) postbacks are the reliable way to record a conversion. The visitor's browser does not have to fire a pixel. When a lead or sale is confirmed, the affiliate network calls a URL on your tracker and passes the click id, payout, and any status the network supports. Because that request comes from the network's server, ad blockers, ITP, and a lost cookie on the user's device do not drop the conversion.</p>
<p>A typical flow has three hops. Your tracker assigns a click id when the visitor hits the tracking link, stores the source and the offer, then redirects to the landing page or the network. You pass that click id through as a sub-parameter the network stores against the click. On conversion, the network fires your postback URL. The tracker matches the click id, writes the payout, and can forward the event to the traffic source (Meta, Google, TikTok, or another network) as its own postback.</p>
<p>Nevect is a self-hosted tracker for that workflow: click tracking, offer routing, and S2S postbacks you run yourself. The product site is <a href="https://nevect.com?utm_source=hashnode&amp;utm_medium=directory&amp;utm_campaign=backlinks_202610">Nevect</a>. The postback URL format, placeholders such as the click id and payout, and how to wire a network are documented in <a href="https://nevect.com/docs/tracking/postbacks/">S2S postbacks</a>.</p>
<p>If you already run a tracker, the same rules still apply. Prefer an S2S postback over a browser pixel for the conversion, keep one stable click id from the first hop through to the network, and store the raw postback so you can reconcile payouts when a network later rejects or revises a lead.</p>
]]></content:encoded></item></channel></rss>