fdForge - Release notes 2.4.0 and 2.5.0
We are pleased to tell you a bit about two of the most recent updates to our fdForge system. We added even more flexibility to the platform in matters of adaptation to changes in the business processes of the projects on which it is integrated.
Both releases - 2.4.0 and 2.5.0 were aimed at giving platform administrators and analysts new opportunities for registering and creating users, working with external systems, as well as adding the functionality of triggers based on customer actions.
Form filling triggers
Now, when users fill out a form on the website or in a mobile application, the system can launch a trigger that can start one of two actions - send a communication message or send a request to a third-party service based on a previously created template. It may sound complicated, but let's show an example.
Let's assume that the user fills out the service request form on the website, indicating his name, email and phone number. Also, we know which advertising channel the user got to the site from. So, for such a case, we can create several triggers that should work for this event:
- Immediately send a personalized message on the user's email, which he indicated in the form (telling that his request has been received and the project manager will contact him to clarify the details);
- An automatic letter with all the details of the application is sent to the manager's email;
- All data from the request is sent to a third-party CRM system;
- Also, if the client came through the partner network and this data is stored in the UTM tags, then we automatically send a postback request to the partner with information on a new CPA-conversion.
All of this can now be set up in fdForge in minutes. Moreover, when switching to a new CRM system or CPA network, you can easily update the integration or send an additional SMS message to the user at the right time (say at 9 am the next day to let them know that you remember about them).
We will also remind you that you can also create the forms themselves in the fdForge management system and they are immediately integrated with our Web Kit and Mobile Kit.
User profile editing capabilities
This functionality simplifies both the initial development of the project and adds opportunities to expand the profile of your users in the future.
The idea is that system administrators can set which properties system users can edit about themselves in their personal account.
What can it be used for?
First, as we have already said, it speeds up the initial development of the project and adds more flexibility to the profile creation process.
Secondly, for example, during the operation of the platform, you realized that you need to store not only the home address, but also the work address of your users. Having the appropriate rights in the system, you can:
- Add a new property of type "Location" to users;
- Add this property to the list of those available for editing and add them to a specific group of settings;
- Make a mass mailing to all users with a request to sign into their account and fill in the information.
API access roles
The fdForge system integrates with other platforms through a large number of API services. And now, to simplify configuration and to increase the level of data security, system administrators can configure access roles to platform API services depending on user properties.
For example, access to editing a profile or creating orders is available only to a user with the "Verified" role, who has previously confirmed his contact phone number.
Or, for example, for a marketplace of services, the ability to create advertisements may be available only to users with "Premium" status.
Such a restriction, although more technical, allows you to significantly change the rules of operation of the platform during projects lifetime and has many opportunities for use.
Automatic tracking of marketing parameters
We've already talked about this functionality a bit, so let's add some more details. In the new version of fdForge, it is possible to automatically save the transferred UTM tags of the link by which the user got to the site.
UTM tags are special parameters that are present in URL of the page and are used by marketers to monitor the effectiveness of advertising campaigns on the Internet.
By default, fdForge Web Kit stores UTM tags in a cookie for each user session for a period set by the administrator (for example, 30 days) and works according to the “Last Cookie Counts” rule. That is, the last marketing parameters that the user followed are stored. Note that this cookie storage can be disabled for your project.
Thus, for each completed form, conversion information is stored - where the user who left a specific request on the site came from. Also, as we said, these UTM tags can be used to trigger various actions.
And working with forms is just the beginning! In the next releases of fdForge, we plan to expand the source tracking functionality for both Web and Mobile kits.