Admitad

Admitad (now Mitgo) is a global affiliate network. This destination sends server-to-server conversion postbacks to https://ad.admitad.com/r so Admitad can credit the originating publisher when one of your customers converts.

Server-side postbacks are the recommended integration mode for Admitad: they avoid browser cookie loss, ad-blocker drop-off, and the ITP/cross-domain tracking penalties Admitad applies to client-side pixels.

How attribution works

1. A publisher (affiliate) sends a user to your site through an Admitad-tracked link.
2. Admitad attaches a click identifier (admitad_uid) to the landing URL.
3. The Ours Privacy SDK reads admitad_uid from the URL and stores it on the visitor (default cookie window: 395 days, matching Admitad's recommendation).
4. When the visitor converts (e.g. completes an order), Ours Privacy sends a postback to Admitad with the stored uid plus order metadata.
5. Admitad uses uid to look up the originating click and credits the right publisher.

If uid is missing on a conversion event the dispatch is skipped with a logged reason — sending an unattributable hit would only inflate your "no source" bucket in Admitad reporting.

Configuring Admitad

In the Ours Privacy dashboard, click Destinations → Add destination → Admitad (Mitgo).

Required settings

Optional settings

Default event mapping

The Admitad destination ships with mappings grouped by purpose so each field's role is obvious:

Attribution

Order details

Customer data

Product details

Use these only when your Admitad program pays per-product commission or you need item-level reporting.

Capturing admitad_uid

The Ours Privacy Web SDK captures admitad_uid from the URL automatically and stores it on the visitor — no extra configuration needed. The destination reads it back on conversion via event.default_properties.admitad_uid.

If you fire conversions from the Server-Side API (HTTP) rather than the Web SDK, include the click ID on the event payload:

{
  "event": "Order Completed",
  "default_properties": {
    "admitad_uid": "abc123def456"
  },
  "event_properties": {
    "order_id": "ORDER-9001",
    "value": 199.99,
    "currency": "USD"
  }
}

Tracking a conversion

ours('track', 'Order Completed', {
  order_id: 'ORDER-9001',
  value: 199.99,
  currency: 'USD',
  coupon: 'SUMMER10',
  product_id: 'SKU-42',
  quantity: 2,
});

When it dispatches

• The destination dispatches whenever an event matched to its mapping has both uid and order_id available.
• Missing uid → dispatch skipped with a logged reason (no retry, no error). This prevents unattributable hits from inflating your reporting.
• Missing order_id → non-retryable error logged. Order ID is mandatory for Admitad's deduplication system.
• Missing destination settings (Campaign Code / Postback Key / Default Action Code) → non-retryable error logged.

Error handling and retries

After 5 retries, dispatch is abandoned and the event is logged as failed.

Operational notes

• Idempotency. Admitad deduplicates by (campaign_code, action_code, order_id), so retrying the same order_id is safe and never double-counts.
• Postback latency. Conversions can take a few minutes to appear in the Admitad dashboard.
• Secrets. Your Postback Key is stored encrypted and is redacted from every log line and dispatch payload.

Additional information

• Admitad postback URL reference
• Admitad Advertiser API
• Admitad Publisher API

Reach out to support@oursprivacy.com to enable this destination for your account.