2020 - 6 March - release #41

New Features

  • [PINPOINTE-1626] - Campaigns: Enhanced ‘View Campaign Queue’ Display.

  • [PINPOINTE-1649] - API: New call: GetSegmentSubscribers()

  • [PINPOINTE-1687] - Centralized Login: Users can now login from Pinpointe website

  • [PINPOINTE-1625] - Customers can now fully brand Link tracking and sender-domain  (branded sender-domain)


Improvements

  • [PINPOINTE-1596] - API: Updated API calls for improved consistency; Updated documentation to properly reflect current API call functionality

  • [PINPOINTE-1669] - API: SendPreview() call has been updated and fully supports the same functionality as QuickSend via the UI

  • [PINPOINTE-1638] - Improvements to bounce processing accuracy

  • [PINPOINTE-1534] - AutoReporting: New enhancements to the post-campaign auto-report

  • [PINPOINTE-1642] - Campaigns: Improvements to Quick Send / Quick Preview feature

  • [PINPOINTE-1693] - Segments: Search for date added, modified, opened, clicked now can be searched with resolution to hours and minutes (previous resolution was 1 day)

  • [PINPOINTE-1656] - Social: Add Flickr to social setup / widgets

  • [PINPOINTE-1609] - Campaigns: Last Sent Date now shows 'Queued' if a campaign is scheduled and in queue (previously shown as ‘not sent’)

  • [PINPOINTE-1399] - Statistics: [Enterprise Edition] When sending to a database that is shared across accounts, the statistics are now only visible to the database+campaign owner, not the sharee.

  • [PINPOINTE-1603] - Statistics: Update to Account Summary -> 'Spam Complaints' Report.

  • [PINPOINTE-1612] - Statistics: Add Send-Text on Statistics Snapshot



Bug Fixes


  • [PINPOINTE-1636] - API: Subscribers.IsEmailOnList() now returns a Boolean (True|False). Previously it returned ‘FAIL’ (confusing)

  • [PINPOINTE-1657] - API: GetNewsletterSummary() now properly returns Detailed Stats results . Previously returned NULL when detailed stats were requested.

  • [PINPOINTE-1604] - Statistics: Stats Details Tab - Filtering on specific Links works correctly

  • [PINPOINTE-1610] - Statistics: Campaign Heat Map now includes results for links with _utm variables.

  • [PINPOINTE-1617] - Statistics: Export Link Report Stats with batch/predictive/timezone sends results in data export file with incorrect column headings

  • [PINPOINTE-1646] - Statistics:  Donut Graph image is now correct for Opens, Unsubs, Bounces.

  • [PINPOINTE-1686] - Manage Campaigns: Last Sent now updates for split tests.

  • [PINPOINTE-1690] - Send Campaign: Restricted-Send-From now can  have up to 20 selections

  • [PINPOINTE-1680] - Contacts: Delete Contacts from Database screen using Drop Down now properly updates List Counts.

  • [PINPOINTE-1550] - Contacts-Lists: “View Contacts” count incorrectly included deleted contacts

  • [PINPOINTE-1544] - Import Contacts: Importing a file resulted in 'over account limit error' if Email Address was not column A. This has been corrected

  • [PINPOINTE-1645] - Builder: Incorrectly showed extra bullet in Outlook if a list is the last item in a column.

  • [PINPOINTE-1662] - Builder: 'Save Block' did not save the block if the content included quote characters. 

  • [PINPOINTE-1658] - Subusers: When sending a campaign, segments are now visible to an account user  who should have visibility to see segments.

  • [PINPOINTE-1605] - Custom Field: Value of '0' was treated as NULL, so it was not possible to set a custom field to a value of ‘0’. A numeric custom field can now be set so ‘0’ or NULL

  • [PINPOINTE-1674] - [Enterprise] Campaigns -> Publish: Publish no longer fails with error  ‘Images not copied' if the campaign’s images are in a subdirectory.

  • [PINPOINTE-1659] - Drips: Vanity URL was not enabled when sending drip campaigns.

  • [PINPOINTE-1005] - Forms: Forms code now accepts field names (previously only accepted internal FieldID name)



Pinpointe - Release 41 (March 2020) - Overview


Release 41 adds some exciting new functionality and improvements

A few of the major areas of focus are:

  • An updated Campaign Queue screen with improved filter and sort capability as well as an improved layout.


  • A new API call that allows users to retrieve a segment’s population of contacts.


  • Centralized Login. Starting March 15 2020 you will be able to login directly from the Pinpointe website instead of having to remember your instance url. (Enterprise customers can request this option)


  • Improvements to the campaign Quick Send process when reviewing email templates.



New Features


[PINPOINTE-1626] - Campaigns: Enhanced ‘View Campaign Queue’ Display

The Campaign Queue page (found under Email Campaigns tab ⇒ Campaign Queue option) has been updated to improve data presentation and user interactivity. 


See Fig 1 below for an example of the new format. 

Users may sort the data based on the following columns:


  • Campaign Name / Subject

  • From / Reply To

  • Audience

  • Date

  • Type


Regardless of sort criteria, the Campaign Queue page will always present campaigns grouped as follows and in the order as presented below:


  1. Future-scheduled “Waiting to Send” campaigns

  2. In-Process campaigns

  3. “Scheduled-but-Waiting-to-Start-the-Send” campaigns

  4. Campaign sends that have completed

 

Uses may also do a search based on these column filters:


  • Campaign Name / Subject

  • From / Reply To

  • Audience



Fig 1
















Presented in Fig 2 is the expanded view when selecting a specific campaign by clicking on the “+” sign icon to the immediate left of the campaign name / subject column:


Fig 2





































[PINPOINTE-1649] - API: New call: GetSegmentSubscribers()

The GetSegmentSubscribers() API call has been added to the “seg” request type.

This call allows users to retrieve the contacts within a segment(s) by specifying one or more segment IDs.

Users may also select which type of contact status they wish to search for within the segment:


  • Any

  • Active

  • Inactive

  • Bounced

  • Unsubscribed


Fig 1 presents the AP call’s XML structure:


Fig 1
















[PINPOINTE-1687] - Centralized Login: Users can now login from Pinpointe website (effective March 15 2020).

All ‘Professional Edition’ customers can login to their account from the ‘Login’ tab on the Pinpointe website www.pinpointe.com.

Enterprise customers can request to have this enabled. Kindly contact support@pinpointe.com.


[PINPOINTE-1625] - Customers can now fully brand Link tracking and sender-domain (branded sender-domain)

Users now have the option to request a custom bounce address (return-path) -- called a ‘vanity bounce’ address for a given account. This feature is important for customers who:


  • Wish to maintain their own branding and completely mask that they are sending via Pinpointe. 

  • Customers who have implemented DMARC and want to ensure that emails sent via Pinpointe meet DMARC policies. DMARC requires that the ‘Sender (Pinpointe, or the domain of the bounce address) and the ‘Send-From’ (your sending email address domain) are the same. 

  • Improve responses. With proper ‘domain alignment’ (and by optionally also setting a custom tracking domain that is the same), many customers see improved response rates.



Improvements


[PINPOINTE- 1596] - API: Updated API calls for improved consistency; Updated documentation to properly reflect current API call functionality

For all “list” request-type API calls, the XML code structure has been edited to provide a more consistent and informative presentation. In addition, after additional testing, each call’s respective documentation was updated to reflect the change in structure and any improvements to functionality. 


The updated API documentation can be found at: https://help.pinpointe.com/support/solutions/5000117462


[PINPOINTE-1669] - API: SendPreview() call has been updated and fully supports the same functionality as QuickSend via the UI

The SendPreview() API call now functions the same as the QuickSend preview option within the user Pinpointe application, including sending both an HTML and Text version of the template. 


Fig 1 presents the XML structure of the API call: 


Fig 1

















[PINPOINTE-1638] - Improvements to bounce processing accuracy

Modifications were made to bounce processing rules to more accurately identify and categorize the type of bounce reported with particular focus on whether the reported bounce should be classified as “soft” or “hard”.


[PINPOINTE-1534] - AutoReporting: New enhancements to the post-campaign auto-report 

Several enhancements were made to both user-selectable options and to the general content delivered with each report.


Fig 1 presents the increased user options for the report:





















In addition, a thumbnail image of the campaign will now be included as part of the report body as well as an attached PDF version of the report.


[PINPOINTE-1642] - Campaigns: Improvements to Quick Send / Quick Preview feature

Test emails now sent via the Quick Send feature will behave more like an email sent via the “normal” send mechanism of selecting a database, list or segment. 


The current ‘quick send’ feature did not replace variable links, or custom field values and sent via a ‘shared preview IP pool’. This combination often caused an otherwise well implemented email to land in the spam folder. The modifications below greatly improve the chance of the ‘Quick Send’ email going to the inbox:


  • The %% has been removed from the placeholder merge tagged custom field when inserted into the template.

  • The “View Online” link now works in Quick Send mode.

  • The “Unsubscribe” link now displays a non-function form based on the user's settings. 

  • Links to Modify Preference form now displays a non-function form based on the user's settings.


[PINPOINTE-1693] - Segments: Search for date added, modified, opened, clicked now can be searched with resolution to hours and minutes (previous resolution was 1 day)

When creating search rules and using the filters:


  • Time Since Added

  • Time Since Updated

  • Last Opened a Campaign

  • Last Clicked on a Link


The user may now also use both hours and minutes in time-based searches. 


Figure 1 shows an example of the new drop down selection list:













[PINPOINTE-1656] - Social: Add Flickr to social setup / widgets

Ability to link to Flickr accounts has been added.


Fig 1














[PINPOINTE-1609] - Campaigns: Last Sent Date now shows 'Queued' if a campaign is scheduled and in queue (previously this displayed as ‘not sent’)


Fig 1







[PINPOINTE-1399] - Statistics: [Enterprise Edition] When sending to a database that is shared across accounts, the statistics are now only visible to the database+campaign owner, not the sharee.

This feature was modified to improve data / metrics control for the primary owner of the contact database.


[PINPOINTE-1603] - Statistics: Update to Account Summary -> 'Spam Complaints' Report.

This report has been updated to include the three summary information blocks above the graph.











[PINPOINTE-1612] - Statistics: Add Send-Text on Statistics Snapshot

The Send-text information has been added to the Statistics Snapshot email campaign report.











Bug Fixes


[PINPOINTE-1636] - API: Subscribers.IsEmailOnList() now returns a Boolean (True|False). Previously it returned ‘FAIL’ (This was a confusing response)

This problem has been resolved. If a user makes the call using the correct syntax BUT the email address being searched for is not included in the list, the call will return a notice of “Success” to indicate the call was successful, but the Subscriber ID tag will be given a value of “0”, which is synonymous with “false”, indicating that email address is not present.


 





















[PINPOINTE-1657] - API: GetNewsletterSummary() now properly returns Detailed Stats results. Previously returned NULL when detailed stats were requested.

This issue has been fixed.  The API call now properly returns a fully detailed stats result.


[PINPOINTE-1604] - Statistics: Stats Details Tab - Filtering on specific Links works incorrectly

This issue has been resolved.  Please note: this error only occurred in the contacts list displayed at the bottom of the Statistics Details page. Exported data contained the correct contact population. 


















[PINPOINTE-1610] - Statistics: Campaign Heat Map now includes results for links with _utm variables.

Previously, links that were coded with utm_tracking values were not included in the heatmap display. This problem has been fixed.


[PINPOINTE-1617] - Statistics: Export Link Report Stats with batch/predictive/timezone sends results in data export file with incorrect column headings

This problem has been fixed.


[PINPOINTE-1646] - Statistics:  Donut Graph image is now correct for Opens, Unsubs, Bounces.

This issue has been resolved.  Note that all underlying report data and statistics *was* previously correct. Only the donut graph in the statistics reports displayed the incorrect information.

































[PINPOINTE-1686] - Manage Campaigns: Last Sent now updates for split tests.

This problem has been fixed. Previously the ‘Last Sent’ value did not show the correct date.


[PINPOINTE-1690] - Send Campaign: Restricted-Send-From now can have up to 20 selections

This feature previously limited the user to set a maximum of approximately 7 values. This has been increased to 20 values.






















[PINPOINTE-1680] - Contacts: Delete Contacts from Database screen using Drop Down now properly updates List Counts.

This problem has been resolved. Number of contacts in a list associated with a given database will now update to the correct count when contacts are deleted from that database. 


[PINPOINTE-1550] - Contacts-Lists: “View Contacts” count incorrectly included deleted contacts in the count (this is a counter issue only)

This problem has been fixed. Number of contacts in a list associated with a given database will now update to the correct count (0) when the associated database the list was constructed from is deleted. 

Please note: this issue only affected the numerical count displayed for the list; the list itself was correctly depopulated. 


[PINPOINTE-1544] - Import Contacts: Importing a file resulted in 'over account limit error' if Email Address was not column A. 

This issue has been corrected. The “Email Address” column no longer has to be the first column in the CSV file being imported to avoid this erroneous warning message. 


[PINPOINTE-1645] - Builder: Incorrectly showed extra bullet in Outlook if a list is the last item in a column.

This issue has been resolved. 

 

[PINPOINTE-1662] - Builder: 'Save Block' did not save the block if the content included quote characters. 

This problem has been fixed.


[PINPOINTE-1658] - Subusers: When sending a campaign, segments are now visible to an account user who should have had visibility to see segments.

This problem has been resolved. Subusers can now see segments assuming their permission level grants such access. 

Under Account Settings -> Manage users, the permissions for the given user need to be set to ‘View’ or ‘Manage’ for contacts: 












[PINPOINTE-1605] - Custom Field: Value of '0' was treated as NULL, so it was not possible to set a custom field to a value of ‘0’. A numeric custom field can now be set so ‘0’ or NULL

This problem has been fixed. Custom fields can now be properly set to a value of ‘0’ or they can be NULL.


[PINPOINTE-1674] - [Enterprise] Campaigns -> Publish: Publish no longer fails with error  ‘Images not copied' if the campaign’s images are in a subdirectory.

This issue has been fixed. 


[PINPOINTE-1659] - Drips: ‘Vanity URL’ was not enabled when sending drip campaigns.

This issue has been resolved. 


[PINPOINTE-1005] - Forms: Forms code now accepts field names (previously only accepted internal FieldID name)

This problem has been fixed. When editing the HTML for a form, users can now simply specify a Custom Field using the variablized format of the Field name, such as %%First-Name%%. They no longer have to use the variablized format of the Custom Fields internal ID number, such as %%CustomField_345%%.


Comments to this discussion are now closed!