Custom Integration Params

This page is a complete reference for the parameters the AnyTrack Custom Integration endpoint accepts in a postback or webhook payload.

If you want to learn how to set up the integration, see Postback URL Integration. If you want to decide whether a custom integration is the right approach, see Is a Custom Integration Right for You?. For the full list of event attributes across all of AnyTrack, see Event Attributes.

🚧

Limited

AnyTrack does not offer setup support for custom integrations not listed in the Integration Catalog. The behavior documented here is provided so you can build the integration yourself.

How the Endpoint Reads Parameters

When you install a Custom Integration, AnyTrack gives you an endpoint URL. Your platform sends conversions to it as query parameters or a JSON body:

https://t1.anytrack.io/<account-id>/collect/<integration-slug>

For the core conversion fields below (click_id, value, transaction_id, and similar), names are matched flexibly: case is ignored, and underscores and hyphens are stripped. So click_id, clickid, and click-id all resolve to the same field. Customer traits, conversion_type, and passthrough parameters are matched exactly as listed in their sections.

Identity Parameters

Every payload must include at least one of these so AnyTrack can match the conversion to the original click. If none are present, the conversion is rejected with a "Missing click_id, ref_id and email" error.

📘

Note

When only ref_id or email is sent, AnyTrack uses that value as the match reference instead of the click ID. click_id always produces the most reliable attribution.

Conversion Value

Event Classification

AnyTrack decides which event the conversion becomes from three inputs, in this order of priority:

1. event_name — if present, the conversion is recorded as a custom event with this exact name.
2. conversion_type — if present (and event_name is not), it is mapped to a standard event using the table below.
3. Automatic — if neither is sent, AnyTrack infers the event from the conversion value.

conversion_type to Event Mapping

conversion_type is matched case-insensitively against these values:

⚠️

Warning

A conversion_type value that is not in this table is rejected with an "Unknown conversion_type" error, unless you also send event_name. Send a value from the list, or use event_name for anything custom.

❗

Important

For predictable classification, always send conversion_type or event_name. When you omit both, AnyTrack records a Purchase only if a positive value is sent as commission. A value sent under another alias (such as value) with no conversion_type is recorded as a Lead.

Transaction and Timing

Customer Traits

Customer traits raise Event Match Quality. AnyTrack normalizes and hashes them automatically before sending to ad platforms, so send raw values and never pre-hash them. These names are matched exactly as written.

Items Array

For eCommerce conversions, send an items array (also accepted as line_items or products). Each object in the array accepts these fields:

Passthrough Parameters

Any parameter whose name starts with xat_ is stored on the conversion as a passthrough value, with the xat_ prefix removed. For example, xat_plan=gold is stored as plan=gold. Use these to carry your own custom data through to AnyTrack.

🚧

Beta

Passthrough parameters are limited to 5 per conversion and may change. Only parameters with a non-empty value are kept. If you send more than 5, the first 5 are stored and the rest are dropped.

Limits and Defaults

• Match key — At least one of click_id, ref_id, or email is required. Missing all three rejects the conversion.
• Currency — Defaults to the property default currency when currency is omitted.
• Timestamp — Defaults to the time AnyTrack receives the conversion when timestamp is omitted.
• Passthrough parameters — Maximum 5 (xat_ prefix). Extra parameters beyond 5 are dropped.
• Unknown conversion_type — Rejected unless event_name is also sent.

Example

A Purchase sent as a JSON payload with identity, value, traits, and items:

{
  "click_id": "f8e3bf8dfba8b51ce3340",
  "conversion_type": "purchase",
  "value": 120.00,
  "currency": "USD",
  "transaction_id": "24356562534585",
  "brand_name": "Acme",
  "email": "[email protected]",
  "full_name": "John Smith",
  "country": "US",
  "state": "CA",
  "zipcode": "94025",
  "items": [
    { "id": "20291", "name": "ZX Series Headphones", "quantity": 1, "price": 20.00 },
    { "id": "49292", "name": "Audio Connector", "quantity": 1, "price": 100.00 }
  ],
  "xat_plan": "gold"
}

The same conversion as a query string:

https://t1.anytrack.io/<account-id>/collect/<integration-slug>?click_id=f8e3bf8dfba8b51ce3340&conversion_type=purchase&value=120&currency=USD&transaction_id=24356562534585