Accounts (Signup)

The accounts (signup) API event relates to the member’s trusted users. this event is usually called at the end of the signup process.

API Example

{
    "queryParameters": {
        "scores": [
            "signup"
        ]
    },
    "tags": {
        "userAgent": "Mozilla/5.0 (iPhone; CPU iPhone OS 5_1_1 like Mac OS X) AppleWebKit/534.46 (KHTML, like Gecko) Version/5.1 Mobile/9B206 Safari/7534.48.3",
        "country": "US",
        "accountCreationDate": "2017-09-10T15:46:51Z"
    },
    "entity": {
        "account": {
            "accountId": "72c1fd9d-de6c-4593-a21f-b3218b417f6a",
            "ip": "8.200.85.15",
            "email": {
                "address": "[email protected]",
                "verified": true
            },
            "address": {
                "phone": {
                    "number": "155555555",
                    "country": "US",
                    "verified": true
                },
                "streetAddress": {
                    "address1": "123 Woodfield Drive",
                    "address2": "PO-BOX 321"
                },
                "firstName": "John",
                "lastName": "Doe",
                "city": "London",
                "region": "Barnet",
                "postCode": "44444",
                "country": "US",
                "device": "cccc3482-4a31-4508-a964-3786948bc42b",
                "dateOfBirth": "2000-02-22"
              
            }
        }
    }
}

Datapoints table

The table below describes the various account data points, descriptions, and possible values.

Data Point Description
accountIdThe unique identifier that represents the user/account
ipThe IP listed for the account. If there are multiple IPs listed, you may send multiple update events via the API for each, along with the unique account identifier
email (object)The object includes the following parameters:

1. address - The email of the account
2. verified - an indication of whether the email has been through a process of being checked and authenticated, to ensure that it’s authentic and valid. This indication may contribute to the trust level of the data. In case there is more than one email listed in the account, you may send two update events to reflect each.
address.phone (object)The object includes the following parameters:

1. number - The phone number of the account.
2. country - country code (2/3 letters ISO. i.e. US). it's recommended to provide the country code in any case (even if the country prefix is provided in the number parameter).
3. verified - an indication of whether the phone number supplied has been through a process of verification. Verification processes typically involve checking that a phone number is valid, reachable, and accessible by the user. Phone number verification is often used as a form of two-factor authentication for certain online accounts. This indication may contribute to the trust level of the data.
address.streetAddressThe account street address
firstNameThe account’s registered first name
lastNameThe account’s registered last name
cityThe account's city
regionThe account's region
deviceThe device ID which identified and provided by an external vendor, and listed for the account.
A device ID (device identification) is a distinctive alphanumeric value, associated with a computer, smartphone, or similar handheld device.
If there are multiple Devices listed, you may send multiple update events via the API for each, along with the unique account identifier.
dateOfBirthThe birth date of the account user