Conversion object

Object fields

{
  "id": "event_aeecb6aa93",
  "source": null,
  "currency": "USD",
  "amount": 50,
  "transaction_id": null,
  "first_name": "John",
  "last_name": "Doe",
  "email": "john.doe@email.com",
  "referrer": {
      "subscriber_id": "sub_09e98650cba1",
      "name": "Luigi",
      "email": "luigi@gmail.com",
      "extra_field": null,
      "extra_field_2": null,
      "code": "559-42c45d10",
      "people_referred": 15,
      "referral_link": "https://mywebsite.com?mwr=559-42c45d10",
      "points": 15,
      "last_referral_at": 1554735254
  },
  "confirmed": true,
  "confirmed_at": 1554735766,
  "created_at": 1554735766,
  "last_updated_at": 1554735766,
  "response": "conversion_created"
}

Fields

  • id - string
    Conversion's unique identifier.
  • source  - string
    Conversion's  source . This is used to generate reports.
  • currency - string
    The currency of the conversion (if any). It must be expressed as ISOCODE (eg: USD, EUR, GBP)
  • amount - number
    Monetary value of the conversion (if any).
  • transaction_id - string
    A string that identifies the transaction of this conversion. This can be used to identify transactions later when exporting all conversions.
  • email - string
    Email address of the person who has converted
  • first_name - string
    First name of the person who has converted
  • last_name - string
    Last name of the person who has converted
  • referrer - hash
    Hash containing info about the referrer. 
  • confirmed - boolean
    True if the conversion has been confirmed (by default is true).
  • confirmed_at - timestamp
    Unix timestamp (expressed in UTC) of when the conversion has been confirmed (for immediate confirmation, which is the default behaviour, this value will be identical to the value of "created_at").
  • created_at - unix timestamp
    Unix timestamp (expressed in UTC) of when the conversion has been created.
  • last_updated_at - unix timestamp
    Unix timestamp (expressed in UTC) of the last time the conversion has been updated.

Idempotency

Networks are unreliable. It might happen that your server will send the same event twice.

To avoid recording the same referral twice, we recommend that you send a unique "transaction_id" which will be used as a unique identifier.

This means that you can't have two conversions with the same "transaction_id" value. This way, even if you send a conversion multiple times, only the first one will be recorded and the other ignored.

It's up to you to generate unique transaction_id values, but we recommend that you use alphanumeric strings at least 12 chars long, eg: aa73067b7518.

Still need help? Contact Us Contact Us