Personal and dynamic content made even easier
Release 19.1 will help you easily make more personal and dynamic content with Unique Lookups. You can also look forward to a set of new functionalities to the Agillic SMS channel which provides you with a better overview of both reach and cost. Finally, we have improved our Facebook connector to be: easier to set up, useable on multiple accounts and more precise at targeting audience.
Any feedback is very welcome on firstname.lastname@example.org
Get to know Agillic 19.1
- Facebook Connector V2
- Improvements for Arrays in Template Parameters
- Fixed Global Data - WEEK_NUMBER
Message parts and Character Counter
Counts characters and calculates message parts. The counter adjusts for special characters and emojis to match current SMS standard. This will provide you with an overview of how much specific content will influence the cost of sending an SMS.
Validation for Phone Numbers
As part of 19.1, we have introduced a new library that will evaluate all phone numbers present in the MSISDN field based on the phone number standard of the country behind a recipients’ country code (If the recipient does not have a country code Agillic will use the system default fall back number). The results of the analysis will be available in the new fixed Person Data field MSISDN_TYPE and will be one of the following values:
- Fixed Line
- Mobile or Fixed Line
- Premium Rate
- Shared Cost
- Personal Number
- You can then choose to only target the numbers which you find relevant.
SMS cost Prediction
To predict the cost of an SMS send out, you need to know how many SMS is being sent to which countries and at which price. We are now providing you with the first 2 – then all you need to know is how much you pay per SMS per country.
When you do a Flow Prediction on flows which contain SMS Steps you will now get an evaluation of how many SMS's (message parts) will be sent if a flow with the given configuration is executed.
The SMS prediction can be viewed in total and by countries based on the recipient’s international area code (or the default fall back area code which is set in System Settings).
You can see the results for the entire flow and per SMS step.
One of the powerful capabilities of this feature is that it will evaluate the precise number of message parts of the SMS(s) per recipient, taking in to account the use of dynamic/personal content (merge fields or promotions) in the SMS body (or Sender field) which means the content and hence the length and potentially the encoding of a message can vary from recipient to recipient
Learn how to predict Flows here.
Now it has become easier to make personal and dynamic content with Unique Lookups. Unique Lookups is similar to Data Lookups but only returns one match. You can do Person Data to Global Data Table or One-to-Many table to Global Data Table Unique Lookups. The results of a Unique Lookup is not limited to a certain block type (as the normal data lookups), but can be merged into all the same destinations as you can merge Person Data:
- Email, Print, Web, SMS body
- App Push templates
- Promotion fields
- Email Subject Line
- Email from address
- Email from name
- Email reply-to address
- SMS sender
Learn more about Unique Lookups here.
Learn how to create a Unique Lookup here.
Facebook Connector V2
Now you can use Facebook login to authorise your accounts for faster set up. Add multiple Facebook accounts to your instance and gain higher flexibility.
Where v1 only matched Agillic recipients against Facebook Audiences using the email, v2 also allows you to match against MSISDN (Phone number), First Name, Last Name, Gender, and Country.
Learn how to set up Facebook Custom Audience here.
Improvements for Arrays in Template Parameters
Arrays can now be used in Template Parameters for both internal and external Links as well as internal and external Images.
Arrays on COLOR Template Parameter now support custom colours, which are not in the Array.
Learn more about template development in our Developers Portal.
Fixed Global Data - WEEK_NUMBER
Will show the current number of the week. Can be used in conditions or merged into content, similar to any Global Data.
Read about Fixed Global Data here.
Inclusion of Global Data in Webhooks
It is now possible to use Global Data in Webhooks.
Read about how to create Webhooks here.
- Columns in exports of One-to-Many and Data Lookup data are now always sorted by a field's 'created time'
- Improved Publish Framework for faster performance and improved stability
- Legacy API System Settings has been removed