Using the Experimental features section, you can configure custom parametres that were requested by Roistat clients.
To open the Experimental features section, open Settings, expand Additional tab and click the Experimental button:
To use experimental settings, you must have the Owner or Reading/Writing access permission. |
Normally, Roistat does not create the deal of repeated call from the telephone number that is already registered in CRM. If the slider is set in |
By default, automatic creation of deals of call is enabled in the Call tracking scenario settings. If the slider is set in ![]() |
Roistat does not create the new deal of call that is processing by call tracking service if a deal of the call with the same phone number with status from "In work" status group is already registered in the CRM. If the slider is set in![]() |
If the slider is set in![]() |
CRM deal has a link to the record of the call. Is the slider is set in the |
Roistat sends the record of the call with the deal of the call to integrated CRM. If the slider is set in the |
If the slider is set in the |
Normally, Roistat records the phone calls from call tracking. If the slider is set in the |
If the slider is set in the
|
If this option is disabled, all phone numbers from 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) |
This option works for numbers from CRM just like the previous option works for numbers from Lead Hunter. |
When you save the landing page After saving the landing page, Roistat deletes the last " / " symbol in the URL, and website address website.com/ takes the form of website.com. This may lead to the error while the diagnosis of technical problems (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. |
If the Projected ROI can be used instead of ROI in the sales cycle, you can change the principle of rates optimization via Rates management option. |
After enabling this option, Roistat will stop deleting the HTML tags from requests' data. This will allow using the page making in CRM, for example, to pass the clickable links into the comments section or configure the word wrapping.
|
Roistat will send the messages about missed calls processed by call tracking to the specified e-mail address. Calls will be counted as missed when:
|
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.
|
The delay in seconds after which the call tracking widget in Google Chrome is closed. |
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 this field. SIP-address for call-forwarding should be stated in the following format: 12121111111=12122222222. |
If during number normalization the number suits several countries, Roistat uses the country code specified in the configuration page. |
This experimental feature can be used in the following cases:
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. |
Using a coma, add the phone numbers to the call tracking blacklist. After this, you will not receive the calls from these numbers.
|
Specify the name of the field in the CRM system, 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.
|
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 the 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. |
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. |
If the deal cycle 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. |
If you need to standardize all the requests, use the following pattern of number format: X (XXX) XXX-XX-XX or +XXXXXXXXXXX |
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.
|
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. |
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. |
If all marketing channels are bound to the city, specify these pairs in this feature's settings using the following format: channel_dnv=Denver,channel_ber=Berlin. |
If you need to define the difficult conditions of deals filtering while loading the deals to the project, use the following filters in JSON format:
|
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. |
Additional fields have a limited number of symbols while loading deals. If the limit is exceeded, Roistat Analytics does not receive some information and can not 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. |
The backup number will receive calls if the main number in the call tracking scenario was busy or unavailable. |
Use this feature if you need to readdress the call when the manager did not answer it in time. |
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}. |
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. |
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. |
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. |
Например, если вы хотите исключить брендированные запросы с SEO на главную страницу для повторных визитов, укажите их в формате: site.ru/landing=seo,direct;site.ru/landing2=seo |
The format of webhook will be sent to the specified address:
|
By default, email tracking creates the deals by letters received only from substitute email addresses.
|