Having specific data attached to each call or event increases significantly the value of each interaction for you and for your customers. It's important to know when a call took place and for what dealer, but what about the listing that they are interested in, the specifics of that ad, your platform, the package and more? Having all these details attached to each Kaisa Dynamic number (whether via javascript or DNCS API) will ensure you can have detailed reports, custom tailored actions, and fully detailed information in your integrated systems at all times. 

There are different ways to have custom parameters or custom values attached to Kaisa numbers:

Custom Parameters for Static numbers

With help from our Support team, you can have up to 20 custom fields*, named and allocated to all your static numbers. While the fields themselves will remain consistent for all numbers in your account, you can change the values individually in each Static number.

The custom values are visible in each static numbers, and the values in each field can be customised in each number, either directly in the dashboard when creating or editing static numbers, or via rest API:

*bear in mind some of these fields may be in use by integrations already

Custom Parameters with Dynamic Numbers

When sending requests to Kaisa for dynamic numbers you can also append customer parameters along with other details (like the account identifiers). There are different ways to do this based on the solution implemented with us. 

Please note you can append more than 20 parameters when using dynamic numbers (as opposed to the fields available to static numbers). 

Javascript

Replacing numbers on page load:

<script type="text/javascript">
    var __fs_conf = __fs_conf || [];
    __fs_conf.push(['setAdv',{'id': 'API_TAG'}]);
    __fs_conf.push(['setParameterString','&custnr=CUST_NR&custname=CUSTNAME&adId=123456&adTitle=ABCDEFG&adPrice=12345678']);
</script>
<script type="text/javascript" src="//analytics.freespee.com/js/external/fs.js"></script>

WARNING: adding customer parameters to number replacement on page load may increase your dynamic number usage

Or using our getNumber solution replacing numbers on click

<script>
  function replaceNumber(c) {
    __fs_dncs_instance.getNumber(
       function(ref,res) { 
          ref.innerHTML=res.local;
          ref.href = 'tel:'+res.e164;
       },
       c,
       c.getAttribute('data-phone'),
       'ADV_ID',
       SUM,
       '&custnr=0000001&custname=customer1&adId=123456&adTitle=ABCDEFG&adPrice=12345678',
       null
    );
  }
</script>

NOTE: Passing on your own parameters will not work straight out of the box, and our Support team will need to create rules in our system to expect and store these parameters, please contact us on support@kaisa.io so we can set these for you. 

DNCS API

When using our DNCS API solution, you will need to include the customer parameters or values you want to pass on to us inside the Parameters section in your payload, as:

{
  "advId": "string","fullUrl": "string”,
  "trackingId": "string",
  "numbers": "string",
  "type": "web",
  "fullReferrer": "string",
  "parameters": 
    {
        "custnr": "string",
        "custname": "string",
        "custemail": "string",
        "adMileage": "string",
        "adTitle": "string",
        "adYear": "string",
        "adEmail": "string",
        "adPrice": "string"
        ...
    },
    "userAgent": "string",
    "requestIpAddress": "string",
    "sessionId": "string"
}

NOTE: Passing on your own parameters will not work straight out of the box, and our Support team will need to create rules in our system to expect and store these parameters, please contact us on support@kaisa.io so we can set these for you. 

Any questions at all, please feel free to reach out to our Support team!