[PINPOINTE-1683] - Send to Lists / Exclude Lists: Exclude by email address vs exclude by subscriberID
[PINPOINTE-1386] - Stats: Batch Sending: -> Campaign stats, by default display/select only summary stat
Bug Fixes
[PINPOINTE-1717] - Contacts: Contacts -> View Lists -> Folder Mode: Recalculates counts on each page visit and hangs screen
[PINPOINTE-1703] - Segment: Search for 'Opened Automated Email' incorrectly searches by email address across ALL databases; should search only selected database
[PINPOINTE-1706] - SendPreview: Convert Social Media Links to valid links
[PINPOINTE-1709] - Dynamic Content: Editor should not modify html snippets when creating a dynamic content block
[PINPOINTE-1436] - Builder: Invalid image URL cannot be edited or removed; does not display
[PINPOINTE-1713] - WYSIWYG: Start New or Import link doesn't work
[PINPOINTE-1710] - Triggers: Missing option to add the delay when entering a date-based trigger; cannot create trigger based on specific date
[PINPOINTE-1714] - Triggers: Social icon links do not function in Triggered email received
[PINPOINTE-1712] - Triggers: "Based on... subscription" option modifies all checkboxes into sliders
[PINPOINTE-1705] - Campaign Queue: Campaigns -> View Campaign Queue fails when an audience includes semicolon
[PINPOINTE-1720] - Campaign Queue: Some Campaigns not showing campaign name/subject in queue
[PINPOINTE-1692] - API: List - GetListSubscribers should validate status argument
Pinpointe - Release 42 (April 2020) - Overview
Release 42 adds some exciting new functionality and improvements
A few of the major areas of focus are:
Drip rules can now be defined based on custom date fields.
Contacts can be auto-unenrolled from an existing drip when that contact is to be added to a new drip based on a change in custom field value.
Users can now exclude contacts from lists based on email address vs database-specific subscriberID.
Numerous additional improvements and bug fixes.
New Features
[PINPOINTE-1723] - Drips: Add option to define drips based on a custom date field
NOTE: Please contact support@pinpointe.com if you wish to have this feature enabled.
The user can now set rules for drip enrollment based on custom date fields. Fig 1 below presents the new enrollment parameters available for user-defined custom date fields. This screenshot shows the appropriate section on the Create New Automated Drip Email page.
Fig 1
[PINPOINTE-1722] - Drips: Add auto-unenrollment when a contact is added to a drip
If a contact is re-imported with an updated custom field value, AND is currently enrolled in an ongoing drip sequence based on that custom field, the contact will be unenrolled from any unsent / future drip emails that are part of the current drip. The contact will then be re-enrolled into the drip sequence at the beginning based on the new custom field value.
This allows the user to reset drip sequence enrollment based on the periodic updates of certain contact attribute values.
This powerful new feature allows you schedule a single campaign and optionally use the send-from values from each database, or even unique send-from values for each individual recipient, in a single campaign send. If the audience includes multiple databases, then the reporting will also be automatically split out for each database.
This feature is ideal for franchises, Universities and Corporate channel programs where ‘Corporate Marketing’ for example, might want to send a campaign on behalf of their respective channel partners, business units or university college divisions, and have the Send-from / reply-to for each respective database be used. This can now be done in a single Campaign Send instead of having to schedule a separate campaign with different send-from / reply-to values each time.
The “Send-On-Behalf” option allows the user to determine which valid send-from domain to use. The three options are (See Fig 1 below):
Default - when selecting “Default” the system will use its current method of determining which send-from to use. If sending to a single database, the system will use whatever database-specific send-from address the user entered at time of database creation. However, the user has the option of overwriting that send-from address and entering a different send-from for this particular campaign send. For example, if sending to multiple databases, the user can enter a single send-from address to use across all databases. See Fig 2 below.
Fig 2
Contact Owner - The user has the option of including a custom field called “Send-From” in their CSV file or API call. This allows a user to associate a specific send-from address per contact. A common scenario for this method would be where a user’s organization has multiple salespeople, and each salesperson has their own unique send-from address. The user can then assign a certain population of contacts to each respective salesperson send-from.
Database Owner - In the case where a user is sending to multiple databases and wants to use the send-from for each respective database. For example:
Database A uses marketing@pinpointe.com
Database B uses sales@pinpointe.com
Database C uses info@pinpointe.com
If a user sends the campaign to all three databases for this particular send event, each database would use its own respective send-from address.
Improvements
[PINPOINTE- 1683] - Send to Lists / Exclude Lists: Exclude by email address vs exclude by subscriberID
Contacts are now included or excluded based on their email address as opposed to using the contact’s database-specific subscriberID. What this means is that excluding a contact from a campaign send by use of a segment or list will now exclude that contact regardless of what database that contact is in (assuming the user has more than one database).
Ex:
john.doe@gmail.com is in Database A.
john.doe@gmail is also in Database B.
User creates an exclusionary list from Database B called “Exclude List”.
User now sets up campaign send rules as:
Include all contacts in Database A EXCEPT exclude all contacts in “Exclude List”
In the above example, even though the “Exclude List” was created from Database B, and NOT Database A, because the system now keys in on email address, john.doe@gmail.com will be excluded from the campaign send.
[PINPOINTE-1386] - Stats: Batch Sending: -> Campaign stats, by default display/select only summary stat
Campaigns sent in batches will now show by default only the aggregate campaign stats of all combined batches in a single row. To the left of the campaign name will appear a small green “+” icon. Clicking this icon will present a drop-down of all the individual batches. Clicking the resulting red “-” will collapse up the batch detail back to the single campaign summary stat row.
Fig 1 below shows the default summary stat row:
Fig 2 below shows a partial screenshot of the drop down batch detail:
Bug Fixes
[PINPOINTE-1717] - Contacts: Contacts -> View Lists -> Folder Mode: Recalculates counts on each page visit and hangs screen
This problem has been resolved.
[PINPOINTE-1703] - Segment: Search for 'Opened Automated Email' incorrectly searches by email address across ALL databases; should search only selected database
This issue has been fixed. Searches under this filter are now restricted to only the selected databases.
Fig 1
[PINPOINTE-1706] - Builder: Send Quick Preview: Convert Social Media Links to valid links
This issue has been resolved. Social Media Links will now be valid when a campaign template is viewed using Quick Send feature. Fig 1 below shows the Quick Send button in the D&D Builder and a small demo campaign with linked social icons.
Fig 1
[PINPOINTE-1709] - Dynamic Content: Editor should not modify html snippets when creating a dynamic content block
This problem has been fixed. If a user inserts an html code snippet (ex: <img> tag with valid ‘src=’ attribute ) as part of Dynamic Content creation, the system will no longer edit this code to ensure it is a valid html document by adding unwanted and unneeded document tags such as <html>, <head>, etc.
[PINPOINTE-1436] - Builder: Invalid image url cannot be edited or removed; does not display
This problem has been fixed.
Fig 1
[PINPOINTE-1713] - WYSIWYG: Start New or Import link doesn't work
This issue has been resolved.
Fig 1
[PINPOINTE-1710] - Triggers: Option to add the delay on a date-based trigger was not available.
This problem has been fixed.
Fig 1
[PINPOINTE-1714] - Triggers: Social icon links do not function in Triggered email received
This problem has been fixed. .
[PINPOINTE-1712] - Triggers: "Based on... subscription" option modifies all checkboxes into sliders
This problem has been resolved.
Fig 1
[PINPOINTE-1705] - Campaign Queue: Campaigns -> View Campaign Queue fails when an audience includes semicolon
This problem has been fixed.
[PINPOINTE-1720] - Campaign Queue: Some Campaigns were not showing campaign name/subject in queue
This issue has been fixed.
[PINPOINTE-1692] - API: List - GetListSubscribers should validate status argument
Dale Boyd
New Features
[PINPOINTE-1723] - Drips: Add option to define drips based on a custom date field
[PINPOINTE-1722] - Drips: Add auto-unenrollment when a contact is added to a drip
[PINPOINTE-1681] - Send: Advanced Send Option for Send On-Behalf / Database Owner / Default
Improvements
[PINPOINTE-1683] - Send to Lists / Exclude Lists: Exclude by email address vs exclude by subscriberID
[PINPOINTE-1386] - Stats: Batch Sending: -> Campaign stats, by default display/select only summary stat
Bug Fixes
[PINPOINTE-1717] - Contacts: Contacts -> View Lists -> Folder Mode: Recalculates counts on each page visit and hangs screen
[PINPOINTE-1703] - Segment: Search for 'Opened Automated Email' incorrectly searches by email address across ALL databases; should search only selected database
[PINPOINTE-1706] - SendPreview: Convert Social Media Links to valid links
[PINPOINTE-1709] - Dynamic Content: Editor should not modify html snippets when creating a dynamic content block
[PINPOINTE-1436] - Builder: Invalid image URL cannot be edited or removed; does not display
[PINPOINTE-1713] - WYSIWYG: Start New or Import link doesn't work
[PINPOINTE-1710] - Triggers: Missing option to add the delay when entering a date-based trigger; cannot create trigger based on specific date
[PINPOINTE-1714] - Triggers: Social icon links do not function in Triggered email received
[PINPOINTE-1712] - Triggers: "Based on... subscription" option modifies all checkboxes into sliders
[PINPOINTE-1705] - Campaign Queue: Campaigns -> View Campaign Queue fails when an audience includes semicolon
[PINPOINTE-1720] - Campaign Queue: Some Campaigns not showing campaign name/subject in queue
Pinpointe - Release 42 (April 2020) - Overview
Release 42 adds some exciting new functionality and improvements
A few of the major areas of focus are:
Drip rules can now be defined based on custom date fields.
Contacts can be auto-unenrolled from an existing drip when that contact is to be added to a new drip based on a change in custom field value.
Advanced sending options to allow either: Send On-Behalf (contact owner) / Database Owner / Default.
Users can now exclude contacts from lists based on email address vs database-specific subscriberID.
Numerous additional improvements and bug fixes.
New Features
[PINPOINTE-1723] - Drips: Add option to define drips based on a custom date field
NOTE: Please contact support@pinpointe.com if you wish to have this feature enabled.
The user can now set rules for drip enrollment based on custom date fields. Fig 1 below presents the new enrollment parameters available for user-defined custom date fields. This screenshot shows the appropriate section on the Create New Automated Drip Email page.
Fig 1
[PINPOINTE-1722] - Drips: Add auto-unenrollment when a contact is added to a drip
If a contact is re-imported with an updated custom field value, AND is currently enrolled in an ongoing drip sequence based on that custom field, the contact will be unenrolled from any unsent / future drip emails that are part of the current drip. The contact will then be re-enrolled into the drip sequence at the beginning based on the new custom field value.
This allows the user to reset drip sequence enrollment based on the periodic updates of certain contact attribute values.
[PINPOINTE-1681] - Send: Advanced Send Option for Send On-Behalf / Database Owner / Default
This powerful new feature allows you schedule a single campaign and optionally use the send-from values from each database, or even unique send-from values for each individual recipient, in a single campaign send. If the audience includes multiple databases, then the reporting will also be automatically split out for each database.
This feature is ideal for franchises, Universities and Corporate channel programs where ‘Corporate Marketing’ for example, might want to send a campaign on behalf of their respective channel partners, business units or university college divisions, and have the Send-from / reply-to for each respective database be used. This can now be done in a single Campaign Send instead of having to schedule a separate campaign with different send-from / reply-to values each time.
The “Send-On-Behalf” option allows the user to determine which valid send-from domain to use. The three options are (See Fig 1 below):
Default - when selecting “Default” the system will use its current method of determining which send-from to use. If sending to a single database, the system will use whatever database-specific send-from address the user entered at time of database creation. However, the user has the option of overwriting that send-from address and entering a different send-from for this particular campaign send. For example, if sending to multiple databases, the user can enter a single send-from address to use across all databases. See Fig 2 below.
Fig 2
Contact Owner - The user has the option of including a custom field called “Send-From” in their CSV file or API call. This allows a user to associate a specific send-from address per contact. A common scenario for this method would be where a user’s organization has multiple salespeople, and each salesperson has their own unique send-from address. The user can then assign a certain population of contacts to each respective salesperson send-from.
Database Owner - In the case where a user is sending to multiple databases and wants to use the send-from for each respective database. For example:
Database A uses marketing@pinpointe.com
Database B uses sales@pinpointe.com
Database C uses info@pinpointe.com
If a user sends the campaign to all three databases for this particular send event, each database would use its own respective send-from address.
Improvements
[PINPOINTE- 1683] - Send to Lists / Exclude Lists: Exclude by email address vs exclude by subscriberID
Contacts are now included or excluded based on their email address as opposed to using the contact’s database-specific subscriberID. What this means is that excluding a contact from a campaign send by use of a segment or list will now exclude that contact regardless of what database that contact is in (assuming the user has more than one database).
Ex:
john.doe@gmail.com is in Database A.
john.doe@gmail is also in Database B.
User creates an exclusionary list from Database B called “Exclude List”.
User now sets up campaign send rules as:
Include all contacts in Database A EXCEPT exclude all contacts in “Exclude List”
In the above example, even though the “Exclude List” was created from Database B, and NOT Database A, because the system now keys in on email address, john.doe@gmail.com will be excluded from the campaign send.
[PINPOINTE-1386] - Stats: Batch Sending: -> Campaign stats, by default display/select only summary stat
Campaigns sent in batches will now show by default only the aggregate campaign stats of all combined batches in a single row. To the left of the campaign name will appear a small green “+” icon. Clicking this icon will present a drop-down of all the individual batches. Clicking the resulting red “-” will collapse up the batch detail back to the single campaign summary stat row.
Fig 1 below shows the default summary stat row:
Fig 2 below shows a partial screenshot of the drop down batch detail:
Bug Fixes
[PINPOINTE-1717] - Contacts: Contacts -> View Lists -> Folder Mode: Recalculates counts on each page visit and hangs screen
This problem has been resolved.
[PINPOINTE-1703] - Segment: Search for 'Opened Automated Email' incorrectly searches by email address across ALL databases; should search only selected database
This issue has been fixed. Searches under this filter are now restricted to only the selected databases.
Fig 1
[PINPOINTE-1706] - Builder: Send Quick Preview: Convert Social Media Links to valid links
This issue has been resolved. Social Media Links will now be valid when a campaign template is viewed using Quick Send feature. Fig 1 below shows the Quick Send button in the D&D Builder and a small demo campaign with linked social icons.
Fig 1
[PINPOINTE-1709] - Dynamic Content: Editor should not modify html snippets when creating a dynamic content block
This problem has been fixed. If a user inserts an html code snippet (ex: <img> tag with valid ‘src=’ attribute ) as part of Dynamic Content creation, the system will no longer edit this code to ensure it is a valid html document by adding unwanted and unneeded document tags such as <html>, <head>, etc.
[PINPOINTE-1436] - Builder: Invalid image url cannot be edited or removed; does not display
This problem has been fixed.
Fig 1
[PINPOINTE-1713] - WYSIWYG: Start New or Import link doesn't work
This issue has been resolved.
Fig 1
[PINPOINTE-1710] - Triggers: Option to add the delay on a date-based trigger was not available.
This problem has been fixed.
Fig 1
[PINPOINTE-1714] - Triggers: Social icon links do not function in Triggered email received
This problem has been fixed. .
[PINPOINTE-1712] - Triggers: "Based on... subscription" option modifies all checkboxes into sliders
This problem has been resolved.
Fig 1
[PINPOINTE-1705] - Campaign Queue: Campaigns -> View Campaign Queue fails when an audience includes semicolon
This problem has been fixed.
[PINPOINTE-1720] - Campaign Queue: Some Campaigns were not showing campaign name/subject in queue
This issue has been fixed.
[PINPOINTE-1692] - API: List - GetListSubscribers should validate status argument
This problem has been resolved.
Fig 1