API launch, App push and improved performance
The highlights of the Agillic Release 18.3 is the new and improved App Push editor and the official launch of our public APIs in a dedicated Agillic Developers Portal. Also, we are introducing a new section in the 'Administration' module which among others holds the Credentials Manager corresponding to the API’s. Check out the new 'Integrations' section in your administration module.
Get to know Agillic 18.3
- New Features
- New App Push Content Editor
- Official API Launch
- New 'Integrations' Section
- Personalise SMS Sender
- Add web tracking data to activity exports
- Google Customer Match Integration optimisation
- Spaces in Event name for Inbound SMS
- General Improvements
- Performance improvements
- UX improvements
New App Push Content Editor
We are releasing a new content editor for the App Push channel. It is located under Content - Outbound and is the foundation for future improvements to the App Push Channel. All existing templates will work with the new editor.
The new App Push editor introduces a new way of searching for and inserting merge fields, when writing messages. It works similar to what you may be used to when using Facebook or LinkedIn, i.e. one can @mention fields when writing e.g. one might write "Hi @firstname, how is your @day_of_week?" – and you can trigger a search by using the symbols @ or $.
Stay tuned, more improvements are coming in coming releases.
- Introducing a new, quick and intuitive way to insert merge fields when writing push messages
- Located more intuitively in the App
- Forms the foundation for coming improvements
- Better testing features
Read more about creating a push notification here
Official API Launch
The API credentials manager is in the new 'Integrations' section in the 'Administration' module of Agillic. You can use the manager to create new credentials, see existing credentials as well as renew and delete credentials. Credentials can be managed for Staging and Production separately. All credentials which have been manually made for beta users of the new APIs will be available in the new manager.
The new public APIs are based on REST and provides API developers with a unified, concise and predictive experience. Additionally, the APIs are now well documented in our dedicated Agillic Developers Portal.
Info about the depreciation of the legacy APIs will be announced in August 2018.
Benefits of the new APIs
Personalise SMS Sender
Agillic SMS editor now supports merging of Person Data into the sender field. This enables personalisation of the sender. Use cases could be sending the SMS from:
- The customers' primary store, in a retail chain of stores
- The name of the agent responsible for the customer
Merge fields can be used in conjunction with a static text.
Read more about creating an SMS here
Add web tracking data to activity exports
We have added the possibility of including web tracking data in Activity Exports. The exports default to include data for all known recipients, but you can also choose to include data for unknown recipients.
This change makes it easier to get data from web tracking feature out of the system for external analysis.
Read more about creating an Activity Report here
Google Customer Match Integration optimisation
The Google Customer Match connection has been optimised so that you will be able to take advantage of the Agillic standard connection, instead of using your own API to Google AdWords.
This has made the process of setting up the service simpler. The settings in the interface are clearer and the info text guides will help you set up the connection. An automatic test of the connection is now the last step in setting up the connection. Should the authentication or test fail, you will see a warning.
The Google AdWords step has been changed so that all actions/buttons are inactive until the settings are entered and the connection authenticated and tested. If the connection is terminated for any reason the step is marked with the red exclamation mark and you will be guided to refresh the settings.
Should a selected custom audience be deleted in the Google AdWords interface, this missing link is indicated on the Google Customer Match Step in your Flow.
Read more about setting up Google Customer Match here
Spaces in Event name for Inbound SMS
In the inbound SMS format, we now support defining an event with spaces as part of the message.
To define an event with spaces, put the event name in quotation marks - e.g. “candy register” or “candy stop”. When in quotation marks, a single event called candy register or candy stop is achieved, rather than two events.
The quoted version can be used anywhere in a message or as the only part of the message - e.g. “candy start” EMAIL or signup “trigger welcome email”
Read more about setting up inbound SMS here
As part of our strategic focus on performance improvements across all major platform sections, we have once again made several improvements in this release.
Most notable is that we have improved the performance of every front-end element which loads lists, e.g. dropdowns, file trees, etc.
We have made several improvements related to UX. This can be everything from changes to copy, design, menus, validation, errors, etc.
Most notable is that we have changed the look and functionality of the Facebook Custom Audience Step to improve usability and to match what was made in the Google Customer Match Step. It now shows you a drop down with a list of all audiences available in your Facebook account to choose from and you can create new audiences using the +.