Effinity

Datafly Signal delivers affiliate conversions to Effinity (Effiliation) server-to-server. Sales and leads are posted directly from your Signal server to the Effiliation tracking servlet, so commissions are attributed to your publishers reliably, even when ad blockers or Intelligent Tracking Prevention (ITP) would block a client-side pixel.

Prerequisites

Before configuring Effinity in Signal, you need:

1. An active Effinity advertiser account with at least one live programme.
2. Your Effinity ID (your unique advertiser identifier). Ask your Effinity account manager if you do not have it — it is the same value used in the Effinity tag.
3. Your affiliate tracking links must carry the eff_cpt parameter (and optionally eff_sub1, eff_sub2, eff_pid). This is how a click is tied to the publisher who drove it.

How attribution works

When a visitor arrives from an Effinity publisher link, the URL carries eff_cpt (the click / counter id) plus optional eff_sub1, eff_sub2, and eff_pid. Datafly.js captures these on the landing page and stores them in a first-party cookie. When the visitor later completes a purchase or submits a lead, Signal includes the stored click id (id_compteur) in the conversion postback so Effinity can credit the correct publisher.

Configure in Signal

Configuration Fields

Management UI Setup

API Endpoint

Effinity uses two GET endpoints — one for sales, one for leads. Signal selects the right one automatically based on the event:

GET https://track.effiliation.com/servlet/effi.revenuemobile?<params>   (sale)
GET https://track.effiliation.com/servlet/effi.leadmobile?<params>      (lead)

All conversion data is sent as URL query parameters. There is no request body and no secret token — your Effinity ID travels as the id parameter.

Identity Signals

Effinity is an affiliate attribution network, not an audience-matching platform, so no PII is hashed or sent. Attribution is based entirely on the click identifiers captured from the affiliate landing URL:

These are captured automatically by Datafly.js on the landing page and persisted in a first-party cookie until the conversion fires.

Event Mapping

The default preset maps two Signal events to Effinity conversions:

All other events (including page) are dropped — Effinity only needs the final conversion.

Sale parameters

Lead parameters

Example: Sale conversion

Datafly.js call:

datafly.track("Order Completed", {
  order_id: "ORD-001",
  revenue: 129.99,
  currency: "EUR",
  coupon: "WELCOME10",
  new_customer: true
});

Effinity postback sent by Signal:

GET https://track.effiliation.com/servlet/effi.revenuemobile
    ?id=12345
    &id_compteur=abc123clickid
    &ref=ORD-001
    &montant=129.99
    &monnaie=EUR
    &voucher=WELCOME10
    &newcustomer=1
    &consent_performance=1

Example: Lead conversion

Datafly.js call:

datafly.track("Lead Generated", {
  lead_id: "LEAD-789"
});

Effinity postback sent by Signal:

GET https://track.effiliation.com/servlet/effi.leadmobile
    ?id=12345
    &id_compteur=abc123clickid
    &ref=LEAD-789
    &consent_performance=1

Testing Your Integration

Troubleshooting