> ## Documentation Index
> Fetch the complete documentation index at: /docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Admitad and ClickFlare Integration Guide

> Track Admitad offers in ClickFlare: pass the click ID in subid4, build the postback in Advanced mode, and pick the right action statuses.

![Admitad and ClickFlare Integration](https://mintcdn.com/clickflare/Yhae9Jga7DowS_ZL/images/integrations/covers/admitad.png?fit=max\&auto=format\&n=Yhae9Jga7DowS_ZL\&q=85\&s=6e305d541305cd4348c80b644f7b04fa)

Admitad is an affiliate platform, part of Mitgo Group, with programs in e-commerce, finance, travel, online services and games. You find programs in the **Admitad Store**, register your traffic as **ad spaces**, and join programs per ad space. Every conversion is an **action**, a lead or a sale, priced by a **rate**. Affiliate links sit on `ad.admitad.com/g/...`.

To track Admitad offers in ClickFlare, two links have to carry the ClickFlare click ID in both directions:

* **The offer URL** sends the ClickFlare click ID to Admitad in `subid4`.
* **The postback URL** sends it back to ClickFlare with every action, together with the payout and Admitad's action ID.

This guide covers the setup, why the click ID goes in `subid4`, the postback form's **Advanced** mode, and which action statuses to tick.

> [!TIP]
>
> Only need the two values? The [Click ID & postback macros](/docs/en/integrations/click-id-and-postback-macros.md?q=admitad) page has them ready to copy with your tracking domain.

***

## How the data flows

```text theme={null}
Ad click
  → https://trk.yourdomain.com/cf/r/CAMPAIGN?...
     (ClickFlare records the click and generates the click ID)
  → [optional lander → CTA uses the ClickFlare click URL]
  → https://ad.admitad.com/g/f469ae904cb7e16523942b59d5275c/?subid4=CF_CLICK_ID
     (Admitad stores the ClickFlare click ID in subid4)
  → Visitor buys or signs up on the advertiser's site
  → Admitad fires your postback:
     https://trk.yourdomain.com/cf/cv?click_id=CF_CLICK_ID&payout=12.50&txid=ADMITAD_ACTION_ID
     (ClickFlare matches the conversion to the original click)
```

The two links mirror each other:

| Link | Built from | Admitad side | ClickFlare side |
| - | - | - | - |
| **Offer URL** (in ClickFlare) | Admitad's parameter + ClickFlare's token | `subid4` | `{cf_click_id}` |
| **Postback URL** (in Admitad) | ClickFlare's parameter + Admitad's macro | `[[[subid4]]]`, `[[[payment_sum]]]`, `[[[action_id]]]` | `click_id`, `payout`, `txid` |

> [!NOTE]
>
> **Offer URL = their parameter + your token. Postback URL = your parameter + their macro.** Admitad writes the click ID into `subid4` on the way in and reads it back with the `[[[subid4]]]` macro on the way out. Admitad macros are wrapped in three square brackets, not braces.

***

## What you'll need

* An active ClickFlare account with your **own tracking domain** set up. Shared domains get flagged by networks and blocked by browsers. See [Tracking domains](/docs/en/settings/tracking-domains.md).
* An Admitad publisher account with an ad space that has joined the program. You only get a working link for programs your ad space is connected to.

***

## What the Admitad template contains

ClickFlare has an **Admitad** affiliate network template. It fills in the Admitad macros ClickFlare needs.

![The Admitad template in ClickFlare: Click Id is \[\[\[subid4\]\]\], Payout is \[\[\[payment\_sum\]\]\] and Transaction ID is \[\[\[action\_id\]\]\]](https://mintcdn.com/clickflare/Yhae9Jga7DowS_ZL/images/integrations/admitad/clickflare-admitad-template-parameters.png?fit=max\&auto=format\&n=Yhae9Jga7DowS_ZL\&q=85\&s=dd300bd4b57a5b93be99303dbff17b80)

| Field | Admitad macro (AN Token) | ClickFlare parameter | What it does |
| - | - | - | - |
| **Click Id** | `[[[subid4]]]` | `click_id` | Returns the ClickFlare click ID that the offer URL put in `subid4`. |
| **Payout** | `[[[payment_sum]]]` | `payout` | Your earnings for the action, as a decimal. Not the order amount. |
| **Transaction ID** | `[[[action_id]]]` | `txid` | Admitad's ID for the action. Pre-filled by the template. See [why](#why-the-action-id-is-the-transaction-id). |
| **Event Type** | leave empty | `ct` | The conversion type. See [Leads and sales](#leads-and-sales). |

The template's **Append Click ID to Offer Url** toggle adds `subid4={cf_click_id}`, which is exactly what Admitad expects. Use it.

***

## Setup

Everything in ClickFlare is done from inside the campaign editor. Create the offer and the affiliate network inline as you go.

**1. Set up your own tracking domain**

Add a custom tracking domain before anything else, for example `trk.yourdomain.com`. The postback URL is built on this domain, so changing it later means updating the postback in Admitad too. See [Tracking domains](/docs/en/settings/tracking-domains.md).

**2. Report conversions by postback time**

Go to **Settings → General Settings** and set **Conversion registration time reporting** to **Postback Timestamp**.

Admitad reports an action on the day it happened. With the default **Visit Timestamp**, ClickFlare reports it on the day of the original click, so a sale that comes in days later lands on a different date in each platform. See [Conversion registration time](/docs/en/settings/conversion-registration-time-reporting.md).

> [!NOTE]
>
> This is an account-wide setting. It changes the date conversions are reported on for every campaign.

**3. Create the campaign**

Go to **Campaigns → New Campaign**, choose **Redirect tracking**, pick your traffic source and select your tracking domain. See [Creating a campaign](/docs/en/campaigns/creating-a-campaign-in-click-flare.md).

**4. Create the Admitad affiliate network**

While creating the offer for the campaign, create a new affiliate network in its **Affiliate Network** field. You can also create it first under **Affiliate Networks → + New**. Either way:

1. Search for **Admitad** and pick the **Admitad** template.
2. Keep the name. One Admitad postback can cover all your ad spaces and programs, so one affiliate network in ClickFlare is enough.
3. Leave **Event Type** empty.
4. Under **Conversion tracking**, select your own **Tracking Domain** and keep **S2S Postback URL** as the tracking method.
5. Set **Payout currency** to the currency your programs pay in. See [Payout and currency](#payout-and-currency).

ClickFlare builds the postback URL from these fields:

```text theme={null}
https://trk.yourdomain.com/cf/cv?click_id=[[[subid4]]]&payout=[[[payment_sum]]]&txid=[[[action_id]]]
```

![The Conversion tracking section of the Admitad network in ClickFlare, with the generated postback URL](https://mintcdn.com/clickflare/Yhae9Jga7DowS_ZL/images/integrations/admitad/clickflare-admitad-postback-url.png?fit=max\&auto=format\&n=Yhae9Jga7DowS_ZL\&q=85\&s=6f2036cd279e9fbf7ca4f03875f3d7f4)

Copy the postback URL and save the network.

**5. Get the program's link from Admitad**

In Admitad:

1. Open **Admitad Store** and tick **Joined** in the filter.
2. Open the program by clicking its logo, its name or **More**.
3. Go to **Banners and Links** and copy the link with **Copy link**.

For a specific page, use **Deeplink** on the same page: paste the advertiser's page URL and copy the result with **Copy deeplink**. Programs without deeplink support only show the standard link. The link looks like this:

```text theme={null}
https://ad.admitad.com/g/f469ae904cb7e16523942b59d5275c/
```

> [!NOTE]
>
> **Tools → Deeplink Generator** builds many deeplinks at once, but it only fills `subid`, not `subid4`. Leave its SubID empty or use it for your own label, and let ClickFlare add `subid4` in the next step.

**6. Create the offer in ClickFlare**

In the offer form:

1. Name the offer, for example after the program.
2. Select the Admitad affiliate network you just created.
3. Paste the Admitad link into **Offer URL**.
4. Turn on **Append Click ID to Offer Url**. ClickFlare adds `subid4={cf_click_id}` when it redirects:

```text theme={null}
https://ad.admitad.com/g/f469ae904cb7e16523942b59d5275c/?subid4={cf_click_id}
```

![The ClickFlare New Offer form with the Admitad affiliate network selected and subid4=\{cf\_click\_id} in the Offer URL](https://mintcdn.com/clickflare/Yhae9Jga7DowS_ZL/images/integrations/admitad/clickflare-admitad-offer-url.png?fit=max\&auto=format\&n=Yhae9Jga7DowS_ZL\&q=85\&s=63e51d3e4095d42640dd5c6ca2b552ba)

You can also write `subid4={cf_click_id}` into the offer URL yourself and leave the toggle off. Use one or the other, not both.

> [!WARNING]
>
> Write `{cf_click_id}` with braces. Without them Admitad stores the literal text `cf_click_id`, the postback returns that text, and the conversion cannot be matched to a click.

Set the payout to **Auto** so ClickFlare uses the `payout` value from the postback.

**7. Add the postback in Admitad**

Back in Admitad, go to **Tools → Postback URL** and click **Add postback URL**. Fill in the form:

| Field | Value |
| - | - |
| **Event type** | **Action**. Not Program status, A referral joined, or Status of cooperation with the program. |
| **Ad space** | **All ad spaces**, or the ad space you run through ClickFlare |
| **Program** | Leave it on all programs ("Admitad Store"), or pick one |
| **Rate** | Leave empty for all rates. It only appears once you pick a program. |
| **Action type** | **All** |
| **HTTP method** | **GET** |
| **Action status** | **Created** and **Confirmed**. Not **Declined**. See [Which action statuses to tick](#which-action-statuses-to-tick). |
| **Link** | The ClickFlare postback URL you copied |
| **Editing mode** | **Advanced**. See [Simple or Advanced mode](#simple-or-advanced-mode). |

Click **Test**, then **Save**. The postback appears in the table, and you can edit or test it again under **Settings**.

**8. Add a lander (optional)**

If you send traffic through a lander before the offer, the lander's CTA must use the **ClickFlare click URL**, not the Admitad link. ClickFlare then adds the click ID when it redirects to the offer. See [Paths with landers and offers](/docs/en/campaigns/campaign-s-path-destination-to-landers-offers.md).

**9. Save the campaign and launch**

Save the campaign, copy the campaign URL from the **Tracking** tab and use it in your ads. Before you spend money on traffic, run the checks in [Verify the setup](#verify-the-setup).

***

## Why subid4

Admitad links have five SubIDs: `subid`, `subid1`, `subid2`, `subid3` and `subid4`. Use `subid4` for the click ID:

* **It's Admitad's own slot for click IDs**, in Admitad's documentation and in other trackers' integrations.
* **It's the only one with room.** `subid4` takes up to 120 characters. `subid` to `subid3` take 50.
* **It keeps the others free** for your own labels. The Deeplink Generator fills `subid`.

If you use a personal promo code, don't use `subid3` for anything: Admitad replaces its value with promo code information.

***

## Simple or Advanced mode

The **Editing mode** at the bottom of the postback form decides which parameter names Admitad sends:

* **Simple** sends Admitad's parameters under Admitad's own names, such as `subid4=...&payment_sum=...`. ClickFlare expects `click_id`, `payout` and `txid`, so it can't match them.
* **Advanced** lets you name each parameter and drag the Admitad value onto it. Map `click_id` to **subid4**, `payout` to **payment\_sum** and `txid` to **action\_id**. The **Generated link** line then shows:

```text theme={null}
https://trk.yourdomain.com/cf/cv?click_id=[[[subid4]]]&payout=[[[payment_sum]]]&txid=[[[action_id]]]
```

Pasting ClickFlare's full URL with the `[[[...]]]` macros into **Link** also works: Admitad replaces each macro. In Simple mode Admitad may add its own parameters after yours, so Advanced is the cleaner choice.

***

## Which action statuses to tick

The **Action status** setting decides which statuses send you a postback:

| Status | Meaning | Tick it? |
| - | - | - |
| **Created** | Recorded, waiting for the advertiser's decision | **Yes**: you see conversions right away |
| **Confirmed** | Approved by the advertiser | **Yes**: updates the conversion with the final payout |
| **Declined** | Rejected by the advertiser | **No** |
| **On hold** | Was confirmed, then put on hold again | No: adds nothing for ClickFlare |
| **Paid** | Reward is ready for withdrawal. Needs `[[[reward_ready]]]` in the link. | No: adds nothing for ClickFlare |

ClickFlare keeps **one conversion per click ID and transaction ID**: a later postback with the same `[[[action_id]]]` replaces the earlier one (the last one received). The status filter implies that each ticked status sends its own postback with the same action ID, though Admitad doesn't say so outright. With **Created** and **Confirmed**, an action arrives when it's created and is replaced when it's confirmed, without counting twice.

ClickFlare doesn't read Admitad's status, so a **Declined** postback would keep the conversion counted. Leave Declined off. An action declined after **Created** still stays in ClickFlare, so compare with Admitad's reports, or tick only **Confirmed** if you can wait for approved actions.

To see the status in ClickFlare, add `&param1=[[[payment_status]]]` to the postback. Admitad sends `new`, `approved`, `declined` or `pending` (confirmed, then put on hold).

***

## Why the action ID is the transaction ID

By default ClickFlare keeps **one conversion per click ID**. If several postbacks arrive with the same click ID and no transaction ID, ClickFlare treats them as the same conversion, and you only see one of them (the last one received). The `txid` value has to be **different on every conversion**, but the **same for every status update of one conversion**.

| Admitad macro | Value | Use it as txid? |
| - | - | - |
| `[[[action_id]]]` | Admitad's ID for the action | **Yes**: the template's default |
| `[[[order_id]]]` | The advertiser's order number | No: may be empty for leads, and can repeat across actions of one order |
| `[[[admitad_id]]]` | Admitad's "Payment ID" | No: not documented as unique per action |
| `[[[subid4]]]` | The ClickFlare click ID | No: the same for every action on the click |

With `[[[action_id]]]`, a lead followed by a sale on the same click, or a second purchase, arrives with its own ID and counts as its own conversion.

***

## Leads and sales

Each Admitad action has a type, `lead` or `sale`, and a rate name. To report leads and sales as separate columns in ClickFlare, add `&ct=[[[type]]]` to the postback and create two [custom conversions](/docs/en/settings/custom-conversions.md) with the parameters `lead` and `sale`:

```text theme={null}
https://trk.yourdomain.com/cf/cv?click_id=[[[subid4]]]&payout=[[[payment_sum]]]&txid=[[[action_id]]]&ct=[[[type]]]
```

`[[[action]]]` sends the rate name instead. You can also add one postback per **Action type** or **Rate**, each with a fixed `ct=` value.

> [!WARNING]
>
> The `ct` value must **exactly match** a parameter of a custom conversion in ClickFlare. If it doesn't, ClickFlare records a regular conversion instead.

***

## Payout and currency

`[[[payment_sum]]]` is your earnings, a decimal such as `12.50`. `[[[order_sum]]]` is the order amount. `[[[currency]]]` is the program's currency, which isn't always USD. Admitad doesn't say whether `[[[payment_sum]]]` is converted to your account currency, so assume it isn't: ClickFlare reads the number in the affiliate network's **Payout currency**. Add `&param2=[[[currency]]]` to the postback to see each program's currency, and if your programs pay in different currencies, compare revenue per program with Admitad's reports.

***

## Verify the setup

**1. Click through the campaign**

Open the ClickFlare campaign URL (with a lander, also click the CTA). Check that the request to `ad.admitad.com` has `subid4=` followed by a real ClickFlare click ID, not the literal text `{cf_click_id}`. Copy that click ID.

**2. Test the postback**

In the postback form, click **Test**. For a GET postback, Admitad shows the URL with test values, which you can edit. Replace the `click_id` value with the click ID you copied, then click **Test**. Admitad answers "The request has been sent to your address." If you see "An error occurred during the request. Check the address.", check the tracking domain in the URL.

**3. Check the conversion in ClickFlare**

The conversion should appear on the campaign with the test payout. In **Logs → Event Logs**, check that it arrived with a `txid`. If you see `[[[subid4]]]` or another macro literally, Admitad didn't replace it: check the spelling. If the test succeeds in Admitad but nothing reaches ClickFlare, contact Admitad support.

In Admitad, **Reports → on SubID** shows your actions by SubID4, so you can check the click IDs Admitad received.

***

## Troubleshooting

> **Actions show in Admitad but not in ClickFlare**
>
> Work through these in order:
>
> * **The postback is in Simple mode.** ClickFlare receives Admitad's parameter names. Switch to **Advanced**.
> * **The event type isn't Action.** Only **Action** fires on leads and sales.
> * **The status filter doesn't match.** A postback on **Confirmed** only doesn't fire for new actions.
> * **The filters exclude the program.** Check **Ad space**, **Program**, **Rate** and **Action type**.
> * **subid4 is empty in Admitad.** The offer URL is missing `subid4={cf_click_id}`, the link came from the Deeplink Generator without it, or the lander CTA links straight to Admitad instead of using the ClickFlare click URL.
>
> See [Troubleshooting S2S postbacks](/docs/en/tracking/troubleshooting-s2s-postback-url-in-clickflare.md) for the general checks.

> **Declined actions still count in ClickFlare**
>
> The action was sent when it was **Created**, and ClickFlare doesn't read Admitad's status. Make sure **Declined** isn't ticked, or tick only **Confirmed**. See [Which action statuses to tick](#which-action-statuses-to-tick).

> **Admitad's SubID report stopped grouping by SubID4**
>
> Admitad stops grouping a SubID in **Reports → on SubID** past 100,000 unique values in 30 days, which per-click IDs reach fast. Tracking and postbacks keep working, and the data stays in the **On actions** report and the API.

> **The payout is 0 or in the wrong currency**
>
> Check that the postback has `payout=[[[payment_sum]]]`, not `[[[order_sum]]]`, and that the offer's payout is set to **Auto** in ClickFlare. For the currency, see [Payout and currency](#payout-and-currency).

***

## FAQ

> **Can I pass more data to Admitad?**
>
> Yes. Use `subid` to `subid3` in the offer URL, for example `subid={campaign_id}&subid1={trackingField1}`. Each takes up to 50 characters, and Admitad shows them in its SubID reports. Keep `subid4` for the click ID.

> **Can I send the conversion back to my traffic source?**
>
> Yes. Once ClickFlare records the Admitad conversion, it can send it to the traffic source through the traffic source's postback or conversion API integration. Nothing changes on the Admitad side.

***

## Related

> **[Macro reference](/docs/en/integrations/click-id-and-postback-macros.md)**
>
> Every network's values

> **[Custom conversions](/docs/en/settings/custom-conversions.md)**
>
> Split leads and sales

> **[Postback issues](/docs/en/tracking/troubleshooting-s2s-postback-url-in-clickflare.md)**
>
> Troubleshoot S2S


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.