When you launch advertising (Facebook, TikTok, Google, and other sources) and drive traffic to offers through CPA networks, the main question is always one:

how to correctly link a click and a conversion, so that:

• it is clear in the tracker which link/campaign yielded results;
• conversions in the source (for example, Facebook) hit the right campaign and optimization works correctly.

This is where the link tracker → partner → postback → tracker → source is used.

---

Each participant has their own "click ID"

1. Traffic source (Facebook, TikTok, etc.)

The source always has its own click identifier — a conditional "check number" for each transition.
It is by this that Facebook (or another network) later understands: "aha, this conversion relates to this click."

2. Adset.pro (tracker)

Adset also creates its own internal ID — event_click_id.
It is needed to:

• store statistics and attribution,
• link the click to the offer,
• receive postback and find the correct transition.

At the same time, Adset additionally saves the native click id of the source in the ext_click_id field — so we have a "bridge":

• event_click_id — internal ID in Adset
• ext_click_id — click ID from the source

---

What happens in practice: user path

Step 1. Click from the ad goes to Adset

The user clicks on the ad → the tracking link opens.

At this moment, Adset:

• records the click and creates event_click_id,
• extracts the click id from the source and saves it as ext_click_id,
• understands which campaign/adset/creative brought the user.

Step 2. Adset leads the user to the CPA network / to the offer

Next, Adset redirects the user to the offer in the partner network.

And here is an important point:
Adset passes its own event_click_id to the CPA network — usually as sub1 (or clickId, depending on the network).

Why is this needed?
So that the CPA network returns this same ID back in the postback when the conversion occurs.

Step 3. An event occurs on the offer side

The user registers, makes a deposit, etc.
The offer reports this to the partner network.

Step 4. CPA network sends postback to Adset

The partner network calls your postback URL and passes:

• status/type of conversion (registration, deposit, sale…),
• and that very sub1, which contains event_click_id.

Step 5. Adset finds the click and sends the conversion to the source

Upon receiving the postback, Adset:

1. finds the original click in the database by event_click_id,
2. understands which source it came from (Facebook/ClickStar/…),
3. retrieves the saved ext_click_id,
4. and sends the conversion back to the source (pixel/CAPI, etc.), passing ext_click_id, so that the source correctly "recognizes" this click.

---

Why this is important

✅ Correct attribution
You see which specific creative/adset/campaign resulted in a registration or deposit.

✅ Correct optimization in the source
Facebook receives the conversion with the correct link to the click → learning and optimization go in the right direction.

✅ Independence from the CPA network
Even if the partner network has "its own click ids", Adset works stably because:

• the Adset ID (event_click_id) goes into the CPA,
• and the source ID (ext_click_id) goes into the source.

---

In short: the principle of "two keys"

• In the CPA network we pass event_click_id to receive the postback back and accurately understand which click converted.
• In the source we send ext_click_id so that the source correctly counts the conversion to that specific click/campaign.