To write to support (add a ticket), you must:

• Go to the portal https://cp.flamix.solutions/
• Enter your mail and password. If you have not registered before, you need register. If, when you try to register, the system says that the user is found, you must reset the password;
• After successful authorization, click on the "Support" menu item, then the "Add" button;
• Describe the error in detail, attach screenshots and click the "Submit" button.

The ticket has been successfully created!
It is recommended not to close the tab until the problem is resolved since emails with replies sometimes end up in spam!

• Go to the module page and find the "Install" block;
  
• In the field next to the "Install" button, enter your Bitrix24 portal domain and click the "Install" button;
  
• Accept all agreements and click "Install";
• Click the button "Start Your Free Trial" (1), or paste your license key (2), if you have one;
  
• If you have activated the trial, be sure to enter your valid email, this is where we will send the license key (check the spam if you did not receive it).

• Open the application in the Bitrix24 portal, go to the "License" page (1) and select the desired subscription period (2).
  
• Go to the license verification page - https://flamix.solutions/license/ (1) and enter your license key (2), click the "Check" button (3). If the license key is correct, you will see the "Prolong" button at the bottom (4).
  

A 20-25% discount is given to anyone who purchases a yearly subscription. You can find the discount amount on the "License" page of the application.

Special prices if we become your Bitrix24 partner. In addition to the special price, and free setup, we can make basic settings for you, and advise on any issues related to the operation of Bitrix24 or the development and optimization of your business's Business Processes. The only thing you require is to buy Bitrix24 through us (the same price, additional benefits from the Bitrix24 gold partner). Write to us if you are interested in this offer.

Note! If you already have an integrator, we can’t become your integrator again even if you want to change it.

When something goes wrong or you need to send logs to support, then you need to follow these steps.

• Open the app and scroll to the bottom;
• Click on the "Log" link.

Here you can see all the information that we log. If you are a technical person, you can check the logs and find the problem.

In addition, we sometimes request a link to the log. To generate it, you simply press the "Generate link" button. Copy and send this link to us. The link is valid for 2 days.

Have you extended your license, but the term has not changed? The license key is cached upon purchase and is only reset upon automatic renewal. If for some reason it did not last, try to throw off the license cache in billing(Licenses are displayed on the Services -> Licenses page) and update the "License" page in the module.

If that doesn't work, please write to support.

An Enterprise license is required in the following cases:

• You regularly more than 500 hits to the plugin per day;
• We need a modification of the Bitrix24 plugin for you;
• You want the program to work on your servers.

Implementation

• We sign NDA and service contracts;
• We allocate a separate VPS for you;
• Setting up environments, deploying a repository with a plugin (if you need support and updates);
• We send separate assemblies of plugins for CMS or set up the integration ourselves;
• We organize monitoring and support 24/7.

For purchasing write in any convenient way.

Important! We do not share the code with the customer.

In order for our plugin to see your field, it must be created ONLY in the Lead. If you create a field in the Lead, then convert the Lead into a Deal, then Bitrix24 will automatically create the field in the Deal and "link" it with the field in the LEAD. Thus, our plugin will transfer information in the Lead field, and Bitrix24 will create a deal and automatically transfer this value to the Deal. How to do it:

1. Go to CRM Settings, Field Settings, LEAD and create the required field.

2. Create a new Lead through the site, for example, by filling out a form or placing an order, and check how our new field works.

The Bitrix24 system is built in such a way that you cannot do without Lead. Even if you do not work with Lead, but only with Deal, then "under the hood" you still work with Lead, which is hidden from you. That is why, in order to work properly, our plugin works exclusively with Lead. And in order to work with Deal, you only need a small setting at the Bitrix24 level.

Auto conversion of LEAD into a Deal.

To convert a LEAD into a Deal, you need to create a simple robot. The algorithm is this:

1. Create a field that will serve as an indicator that this Lead needs to be converted into a Deal. For example, it can be the "Order number" field or the "Source" field, where your site is listed (1).

2. We create a new robot that will work Immediately (1) if the Lead has our conversion indicator (2), and will create a Deal and Contact* (3) in the desired funnel (4).

3. Create a new Lead through the site, for example, by filling out a form or placing an order, and check how our setting works.

Contact* - The Contact will be created only if it is not found when creating the Lead. If you previously had this Contact in the CRM, it will be found and attached to the Lead (a duplicate of the Contact will not be created).

Video tutorial: https://youtu.be/mACtqEEAq-I?t=359

If you have a CRM without Lead, then you do not need to do this, Bitrix24 itself converts all Lead into Deal.

Orders in our system are usually sent immediately. However, if for some reason an order cannot be sent right away, it is placed in a queue to be sent after 1 minute. This queue is processed either on a schedule (cron), or when a user visits the site.

If the queue is set to be processed by cron, but cron is not running, then orders will not be sent. Similarly, if the queue is set to be processed when users visit the site, but users do not visit the site, orders will also not be sent.

Recommendation: For more reliable and timely order dispatch, it is recommended to move everything to cron processing and make sure that cron is active. You can read more about how to set up and activate cron in WordPress in this article.

If your site encompasses multiple directions, you can set up automatic distribution of Deals into different funnels using either a business process or a robot. The solution algorithm is the same in both cases, so let's consider an example with a robot, as they are simpler and supported by basic tariffs.

In the LEAD or Deal, we create a text field "Site Domain". In the plugin settings, we select the match "Site Domain" = HOSTNAME, where HOSTNAME is a standard field containing the domain name.

We move to CRM, select the necessary entity (LEAD or Deal), add a robot that will trigger if the "Site Domain" field contains the required domain. This robot will change the Deal stage only for requests coming from the specified site.

• When working with LEADs, at the first stage create a robot for conversion into a Deal, where you select the desired direction and stage.

• When working only with Deals, use the "Change Direction" robot. Important: the field must be passed from the LEAD, so create it there!

Important to know:

• Create the field in the LEAD, even if you are using Deals. When converting a LEAD into a Deal, Bitrix24 will automatically create the necessary field and transfer the value.
• Business processes are triggered before robots and have an extended functionality.

UTM tags are labels in a link that help determine where a visitor came from to your site.

Typically, these labels are added manually. Some advertising systems set them automatically when someone clicks on an advertisement. However, if a visitor comes to your site not from an advertisement, such labels usually aren't present.

Imagine that you ordered a promotional banner on SITE.COM. If the banner features a simple link like "https://mysite.com", no additional data will come to your site when someone clicks on it. For your site to recognize that the visitor came from SITE.COM, the link should look like this: "https://mysite.com/?utm_source=site.com". This way, your site will see this tag and understand that the visitor arrived from SITE.COM.

This mechanism dynamically sets UTM tags by detecting the click's source. Let's compare two scenarios when someone accesses your site from organic traffic:

• Without SmartUTM: Clicks from Google's organic search don't automatically set UTM tags, so your site won't show the "utm_source" tag.
• With SmartUTM: If someone clicks from Google's organic search, our plugin reads the referral and automatically sets “utm_source=google.com” on your site.

This functionality works for any website. Remember, manually-set UTMs take precedence over dynamic ones. So, if a link already contains “utm_source”, Smart UTM won't override it.

To understand the usefulness of this option, it is necessary to consider a small example. Let's imagine that you have a Contact who left a message in a simple form, where put only his first name, phone number, and comment. In Bitrix24, a Contact will only have a phone number and a first name. After some time, this Contact will make an order in-store and send ALL Contact info. In this case, we may lose some of the data, because the plugin will find a previously created Contact (which does not contain a phone number and last name) and link it to a Deal or a LEAD.

You must enable the "Enrichment contact" option to prevent this from happening. Go to settings, and turn it on. If this Contact is found, the plugin will add all the standard fields if they are not previously filled. For example, if you filled Contact name, then it will not change.

The functionality works with the following fields:

• First name;
• Middle name;
• Last name;
• Phone number;
• Email.

Statuses, unlike LEADs, do not have a guarantee of delivery due to various technical and logical reasons. Please note! We do not analyze why a status did not reach you, as it may fail for reasons beyond our control. Therefore, please read this description carefully to be able to check and correct errors yourself if they are detected.

Basic Rules

• 1.1. Enable status exchange in the plugin settings.
• 1.2. A status cannot change entities and directions. For example, a status cannot convert a LEAD into a Deal or change Deal directions.
• 1.3. A status is blocked for 20 minutes tied to the order. For example, if your site sent that order #2 changed status to PAID, then you immediately switched the status on the site to any other, and then returned it to PAID after 10 minutes, our plugin blocks this request as duplicate.
• 1.4. Statuses have the lowest priority in the queue, so they may be executed with a significant delay.
• 1.5. The entity must have an order number in the field specified in the plugin settings.
• 1.6. Your site must work correctly over the https protocol.

Transferring Status from Bitrix24 to the Site

Bitrix24 informs us about a change in the entity's status (problem 2.1). Our plugin searches for the order number in the entity (problem 1.5), retrieves from the settings which status to set on the site, forms a webhook (displayed in the application logs), and sends it to the site (problem 1.6).

Problems and Solutions:

• 2.1. Our plugin does not receive notifications of deal changes due to problems on the Bitrix24 side. You need to wait for Bitrix24 to fix the problem.
• 2.2. The application does not display the webhook for sending to the site. Check the basic rules and ensure the status is matched.
• 2.3. The webhook exists, but the status does not change. Copy the webhook and open it in a browser. If a technical reason appears, the site will display it. Consult with programmers or order a detailed analysis from us.

Transferring Status from the Site to Bitrix24

The site plugin, on the order change event, takes the authorization secret tokens, forms a webhook, and sends it to our plugin (Problem 3.1). Our plugin checks for a deal or LEAD with that number (Problem 3.2), finds which stage to change the entity to in Bitrix24, and initiates the change.

Problems and Solutions:

• Incorrect integration settings or the wrong Bitrix24 specified. If everything is correct, you will see in the Bitrix24 logs that the plugin received the status change task.
• The order number is not found in CRM. Check the settings and search for the entity manually.

For diagnostics, you can manually repeat the request via the browser (you need to substitute your data):
https://lead.app.flamix.solutions/api/v1/status/change?DOMAIN=your.bitrix24.com&api_token=secret_token&HOSTNAME=test.com&STATUS=NEW&ORDER_ID=1001

Incident Investigation. We offer an incident investigation service. Our specialists will check everything for you and determine the cause of the problem. If the problem is on our side, we will refund your money.
The service costs $99. You can order it here. Be sure to send access to your Bitrix24 and your site.

There are several ways to add additional fields in the plugin. Consider an example of adding custom fields in WordPress. Other CMS have similar functionality (look for the name of filters or hooks in the plugin documentation for the desired CMS). This instruction is intended for webmasters.

Universal way

This method is good because it is built on the basis of the SDK and is not tied to the CMS and is used for any submission. For example, let's consider a task where when submitting any form or order, you must always add HTTP_REFERER, SITE_DOMAIN and Google Client ID without GA. The disadvantage of this method is that it works until all fields are received, i.e. in fact, you will not know which fields you are passing. If this is WordPress, then the first and stable entry point of any file is functions.php. To solve this problem, add the following code to the functions.php file:

try {
	$flamix_extra_fields = [
		'HTTP_REFERER' => $_SERVER['HTTP_REFERER'] ?? '',
                'SITE_DOMAIN' => 'mysite.com',
	];

	$cookie_ids = \Flamix\Conversions\Conversion::getFromCookie();
	if(!empty($cookie_ids) && isset($cookie_ids['_ga']))
		$flamix_extra_fields['google_client_id'] = preg_replace('/GA[0-9].[0-9]./', '', $cookie_ids['_ga']);

    \Flamix\Bitrix24\Lead::getInstance()->setExtraFields($flamix_extra_fields);
    unset($cookie_ids, $flamix_extra_fields);
} catch (\Exception $e) {
    //$e->getMessage();
}

WordPress Filters

If you need to change order fields or goods using previously created fields (for example, order number, customer name, etc.), you must use filters. We place filters in the functions.php file. The available filters are:

• flamix_bitrix24_integrations_fields_filter $fields
• flamix_bitrix24_integrations_product_filter $products, $order_id
• flamix_bitrix24_integrations_filter $data

Pay attention! Filters are universal for all WordPress plugins! This means that if you change the fields using flamix_bitrix24_integrations_fields_filter, then the filter will be applied both for the WooCommerce module and for Contact Form 7 or Ninja Form. This restriction obliges you not to be 100% sure that some of the incoming parameters will definitely be. For example, ORDER_ID will only be in WooCommerce. An example of implementing the task of adding a title for a Lead with the necessary information:

function flamix_bitrix24_integrations_fields_example_callback($fields) {
    if(isset($fields['ORDER_ID']) && $fields['ORDER_ID'] > 0)
        $fields['MY_BITRIX24_LEAD_TITLE'] = 'Order #' . ($fields['ORDER_ID'] ?? 0) . ' from wp.app.flamix.solutions at ' . ($fields['DATE'] ?? date('Y-m-d H:m:s'));
    else 
        $fields['MY_BITRIX24_LEAD_TITLE'] = 'Request from wp.app.flamix.solutions at ' . ($fields['DATE'] ?? date('Y-m-d H:m:s'));

        return $fields;
}
add_filter( 'flamix_bitrix24_integrations_fields_filter', 'flamix_bitrix24_integrations_fields_example_callback', 10, 3 );