Loading...
Page tree
Skip to end of metadata
Go to start of metadata

Experimental features will help you to configure the custom parameters that were introduced upon requests of Roistat users. 

To use the Experimental features, open Settings, expand Additional tab and click the Experimental button:



To use Experimental features, you must have the Owner or Reading/Writing access permission.

The list of experimental features

 Create the deal based on a call even if the client is already registered in CRM

Normally, Roistat does not create a deal if it is based on a repeated call from a telephone number that is already registered in CRM.

Set the slider in position to enable the creation of deals based on calls from numbers that are already saved in CRM.

(информация) Contacts are verified by proxy lead.

  Disable the automatic creation of deals based on a call

By default, automatic creation of deals based on a call is enabled in the Call tracking scenario settings.

Set the slider in position, and Roistat will stop automatic creation of deals, even if it is enabled in Call tracking scenario settings.

 Create the deals based on a call even if there are deals from "In work" status group

Normally, Roistat does not create the new deal based on a call that is processing by call tracking service if a deal based on a call with similar phone number with status from "In work" status group is already registered in the CRM.

Set the slider in position, and Roistat will create the deals based on calls processed by call tracking even if "In work" status group has deals based on calls with similar numbers.

 Send Roistat SIP account instead of dialed number when using this account in the INVITE request
Set the slider in position to enable the sending of Roistat SIP account in the INVITE request instead of the dialed number.
 Forbid the listening of calls from deals in CRM without access to the Roistat project

Each deal in CRM has a link to the record of a call.

Set the slider in position, and the listening of calls from deals will be unavailable without an account that has access to the Roistat project.

 Do not send the record of a call to CRM

Normally, Roistat sends to integrated CRM the record of a call from the deal based on this call. 

Set the slider in position, and Roistat will stop sending the record of the call to the integrated CRM. 

 Do not send the information about marketing channel to CRM while creating deals with the help of proxylead mechanism

Set the slider in position, and Roistat will not send the information about the source of a visit on the landing page to the deal in CRM if the information about the deal is sending to CRM via Roistat service.

 Do not record the phone calls from call tracking

Normally, Roistat records the phone calls from call tracking.

Set the slider in position, and Roistat will stop recording the calls processed by the call tracking service.

 Use the deals from previous integrations

Set the slider in position, and deals from previously used CRM will be displayed in Analytics. This is needed in case when deals are not transferred from previously used CRM to the new one. 

(warning) This option must be activated before the integration with new CRM.

 Do not normalize the phone numbers from the Lead Hunter

Disable this option, and all phone numbers from the Lead Hunter will have the ХХХ ХХХ ХХ ХХ format.

Illustration:

Your client has an international business, and the visitor of the client's website entered his number in the Lead Hunter using the Polish format: 06 001 60 90

If this option is disabled, the system transforms this number to +456 001 60 90 (code 45 added instead of 0)

Enabling this option will allow transmitting the international numbers in the same format as visitors entered them in the Lead Hunter.

 Do not normalize the phone numbers from CRM

This option works for telephone numbers from CRM just like the previous option works for telephone numbers from Lead Hunter. 

 Do not remove the last " / " symbol in the address of a landing page

After saving the landing page, Roistat deletes the last " / " symbol in its URL, and website address website.com/ takes the form of website.com.

This may lead to the following error in diagnosis of technical problems: Error! tracking code was not found on website.com

Enabling this option solves the problem during the diagnosis. After the option is enabled, you have to wait 3-4 days, as the diagnosis of technical problems verifies the webpages URLs for the last 3 days. 

 Use the Projected ROI indicatior instead of ROI to optimize the rates management

If the Projected ROI is used instead of ROI in the sales cycle, you can change the principle of rates optimization via Rates Management option. 

 Do not cut HTML tags while sending requests to CRM.

After enabling this option, Roistat will stop deleting the HTML tags from the data of requests. This will allow using the page making in CRM, for example, to transmit the clickable links to the comments section or configure the word wrapping. 

Enabling this feature will turn off the built-in protection from XSS-attacks.


 Email address for sending letters about missed calls

Enable this option, and Roistat will send letters about missed calls processed by call tracking to the specified e-mail address.

Calls will be counted as missed in the following cases: 

  • the client did not wait for the response and hung up;
  • the dial was canceled;
  • the number was busy.

    You may specify several e-mail addresses using coma. 

 Email for sending letters about failed calls

Enable this option, and Roistat will send the messages about failed calls processed by call tracking to the specified e-mail address. Any calls except accepted or missed are counted as failed. 

You may specify several e-mail addresses using coma. 

 The delay in seconds of closing the call tracking widget in Google Chrome

The delay in seconds after which the call tracking widget in Google Chrome will be closed. 

 Redefine the forwarding numbers for substitution numbers

This feature may be needed when you use two substitution numbers that must be forwarded to different numbers. After enabling this feature, the first substitution number must be specified in the call tracking scenario, and the second substitution number must be specified in the field of this feature.

SIP-address for call-forwarding should be stated in the following format: 12121111111=12122222222.

 Choose the priority country code that will be used while normalizing telephone numbers

If a number suits several countries during the number normalization, Roistat will use the country code specified in the configuration page. 

 Specify the name of the field of a deal or the name of contact with telephone number in CRM or SMS if you want to define the source of deals that were created while using the Roistat calltracking

 (warning) To make this feature work, please specify the names of fields in CRM, for example, calltracking_phone, roistat_phone, etc. Fields of contacts have client_ prefix, for example, client_phone_number.  If you want to use your default system field with a phone number, name this field "client_". Specify the phone number of the client in the related field using the format from Call History. 

This experimental feature can be used in the following cases:
  • You utilize the outside telephony with your CRM and decide to use Roistat call tracking to define the source of calls.
  • You integrated the telephony with CRM and want to create a deal for every incoming call. 
  • Your CRM is integrated into Roistat, but requests from calls processed by your telephony come to the Roistat project without the information about the source of the call.
  • When the Roistat call tracking proceeds all the calls from your telephony.
  • You need to bind the requests from calls to the sources of the calls.

How this feature works:

After the deal without visit number is loaded to the project, Roistat begins to check the project for calls with the same phone number that were made within an hour before the creation of the deal. If such call was found, the deal receives the visit number from the information about this call. 

When you specify the name of the field in CRM that contains the data of the call, and the deal without visit number loads to the project, Roistat begins to check the project for calls with the same phone number that were ended within several minutes before the date from the CRM field. If there are several calls with the same phone number, the deal receives the visit number from the information about the latest call. 

 Call tracking blacklist

Using a coma, add the phone numbers to the call tracking blacklist. After this, you will not receive the calls from these numbers. 

(информация) We do not recommend you to use more than 10 000 numbers. 

 Specify the name of the field from which you need to load the date of sale

Specify the name of the field in CRM, and Roistat will receive the date of the sale from this field. If this field is empty, the date of the sale will be specified by Roistat default algorithm. 

(информация) The data format of this field must be in timestamp or look the following way: YYYY-MM-DD HH-MM-SS.

 The minimal time of a call in seconds, after which the call will be counted as accepted

Specify the time in seconds after which Roistat will count the call as accepted. 

Illustration:

When Roistat detects the call, an answering machine is activated, and the call is counted as accepted even if a manager did not get to respond. 

To avoid this situation, specify the duration of the answering machine, for example, 10 seconds. After that, the call will not be counted as accepted for the first 10 seconds of the call. 

 The maximal lifetime of orders loaded to the project

Specify the creation date of the order in YYYY-MM-DD format. After that, the orders created before this date will not be loaded to the project.  

 Cycle of a deal that will be counted in rates management while using the optimization by ROI

If the cycle of a deal does not allow to use the optimization by current ROI, specify the approximate cycle of your deal.

Illustration: if you specify 30 days deal cycle, ROI will be calculated for a period that was ended 30 days ago.

 Specify the format of transmitting the phone number to CRM

If you need to standardize all the requests, use the following pattern of number format: X (XXX) XXX-XX-XX or +XXXXXXXXXXX

 Specify the time zone of loading the deals from CRM

If you want Roistat to load the deals from CRM properly, you need to enter the Roistat project settings and specify the time zone of deals from CRM.

(warning) If the data is transmitting in timestamp format, Roistat will not be able to use this experimental feature.

 Specify the name of the field of a deal in CRM/CMS to load the infromation about the city from this field of a deal

If you want to manually transmit the information about the city in the loaded fields, specify the field that will contain the information about the city. 

 Specify the numbers of scenarios, for which you need to transmit the dialed number instead of caller number while readdressing

If you need to process the number dialed by your client instead of the client's number, specify the numbers of scenarios in this experimental feature using a coma. 

 Specify the pairs of Roistat tags and cities to define the city of the marketing channel

If all marketing channels are bound to some city, specify these pairs in this feature's settings using the following format: channel_dnv=Denver,channel_ber=Berlin.

 Advanced filtering configuration while loading deals

If you need to define some difficult conditions of deals filtering while loading deals to the project, use the following filters in JSON format:

  • Valid operators: ">", "<", "<=", ">=", "=", "!=", "in", "not_in", "or", "and", "like", "like%", "not_like", "not_like%", "null"
  • Filter looks the following way: ["Field", "Operator", "Value"]
  • If the operator is in or not_in, the values must be an array and placed in square brackets [].
  • The value of other operators should not be an array.
  • The valid value of operator null is 0 and 1.
 Specify the GET-parameters you want to see in Analytics

If you use additional data in the GET-parameters of the landing page, specify this data to make it visible in Analytics using a coma. 

 Specify the names of fields you want to include to reports

Additional fields have a limited number of symbols while loading deals. When the limit is exceeded, Roistat Analytics will not receive some information and will not be able to create a report on this information. To solve this problem, specify the ID of additional fields from CRM to give them a priority while loading to Analytics. 

 Backup number or SIP for readdressing the calls in calll tracking

The backup number will receive calls if the main number in the call tracking scenario was busy or unavailable.

 Time out waiting for a response in seconds before readdressing to the backup number of SIP
Use this feature if you need to readdress the call when the manager did not answer it in time. 
 Additional header for SIP calls (INVITE) received from Roistat telephone exchange

If you need to process the additional variable from Roistat telephone exchange, enter the values in the following format: {header name}={header value}, {header2 name}={header2 valie}.

Illustration: my-city={city}, my-domain={domain}. 

 Specify the name of the field in CRM from which you want to receive the source of request (if the Roistat field is empty)

If the roistat field is empty and the source of the request contains in another field, specify the name of this field to track the requests in the Analytics

 Specify the name of the field from which you need to load the date of sale

If the date of sale is calculated in a specific way and placed in some field of CRM, you need to specify this field. If this field is empty, the date of sale will be set by Roistat default algorithm. 

 Specify the fields of the deal with confidential information that should not be loaded to Roistat

If some fields in CRM contain confidential information that should not be loaded to Roistat project, specify these fields in the configuration of this feature. 

 Add the pages and marketing channels for which you do not need to record individual visits if the visitor already was on the website

If you want to exclude the branded requests from SEO to the main page for a repeated visit, specify these requests using the following format: site.com/landing=seo,direct;site.com/landing2=seo

 Specify the address for sending the information after receiving the proxylead

The format of webhook will be sent to the specified address: 

{
  "id": "198",
  "title": "Catched lead: Alex, +1(212)111-11-13",
  "text": "Form data: Alex, +1(212)111-11-13\nPromocode: 3217\nChannel: Direct visits\nLanding page: https://test.com/Contacts/\nReferer: \n",
  "name": "Alex",
  "phone": "12121111113",
  "email": "",
  "data": "{\"source\":\"organic\",\"sourceLevel1\":\"organic\"}",
  "contact_data": "[]",
  "visit_id": "3217",
  "date_create": "2019-05-13 13:49:14"
}


 Sending of all emailtracking letters to the Webhook address

By default, email tracking creates the deals by letters received only from substitute email addresses. 
Activating this feature allows creating the deals not only by letters from substitute addresses but also by letters sent directly to the client's email.

To make this feature available, configure the creation of deals via Webhook!

  • No labels