Admitad
Datafly Signal reports sales, registrations and leads to Admitad (Mitgo) as server-to-server postbacks, attributed by the admitad_uid click ID.
Prerequisites
Get your postback details
In your Admitad account, open Integration > Custom integration > Postback. Note the campaign code, the postback key, and the action code and rate (tariff) code of each target action.
Keep the admitad_uid parameter on landing URLs
Admitad appends admitad_uid to its links; the Datafly collector captures it.
Configure in Signal
Configuration Fields
| Field | Required | Description |
|---|---|---|
campaign_code | Yes | Your Admitad program/campaign identifier. Found in your Admitad account under Integration > Integration methods. Sent as campaign_code on every conversion request. |
postback_key | Yes | The private security key issued by Admitad at the integration stage. Authenticates the server-to-server postback. Found under Integration > Custom integration > Postback. Treat as a secret. |
sale_action_code | Yes | The target-action code for purchases (Order Completed). Found in Admitad account > Integration > Custom integration > Postback, in the Action column. |
sale_tariff_code | Yes | The rate/tariff code for purchases. Found in Admitad account > Integration > Custom integration > Postback, in the Rate column. |
registration_action_code | No | The target-action code for registrations (Signed Up). Leave blank if your program does not pay for registrations. |
registration_tariff_code | No | The rate/tariff code for registrations. Leave blank if not used. |
lead_action_code | No | The target-action code for leads (Lead Generated). Leave blank if your program does not pay for leads. |
lead_tariff_code | No | The rate/tariff code for leads. Leave blank if not used. |
Management UI Setup
- Go to Integrations > Add Integration > Admitad.
- Choose a preset: Default (
default), Retail (ecommerce), Lead Generation (lead_gen), Insurance (insurance), Travel (travel). - Fill in the fields above and click Save.
Request format
A sale:
GET https://ad.admitad.com/tt?action_code=1&adm_method_name=sale&campaign_code=1a2b3c4d5e&client_id=crm-user-9¤cy_code=GBP&order_id=ORD-1001&payment_type=sale&postback=1&postback_key=pKetl7uIt8GgZ3yDChh9y4cUKf5FblBS&price=259.99&promocode=SAVE10&response_type=json&tariff_code=1&uid=03b374fa9c2f34069e8df0bda61b8627Leads and registrations send price=0 and payment_type=lead; a registration’s order ID is reg_<user ID>, as Admitad asks.
Event Mapping
| Signal event | Vendor event | Presets |
|---|---|---|
purchase | sale | Default, Retail, Insurance, Travel |
generate_lead | lead | Default, Lead Generation, Insurance |
sign_up | registration | Default, Lead Generation |
quote_completed | lead | Insurance |
booking_completed | sale | Travel |
Identity
Attribution is by uid (the admitad_uid click ID); conversions without it are not sent. client_id is your user ID. No other personal data is sent.
Consent
Affiliate conversions are not gated on marketing consent by default: the network is in Signal’s attribution category, which the advertising consent default does not cover. Assign a consent category to the integration if your policy requires one. Admitad documents no consent parameter.
Troubleshooting
| Problem | Solution |
|---|---|
| Leads or registrations not sent | Set the lead or registration action code: without it those events are skipped. |
| Per-product rates | Signal sends one order-level postback; Admitad’s per-cart-line postbacks are planned. |
Blueprint
The Admitad blueprint version is 0.6.0. It was last reviewed against the vendor’s documentation on 2026-09-23.