2017-05-05 (Sprint 14)

Release Date: May 5, 2017

This release focuses on new API Grid Requests, Landing Pages, and Informz’s new Socializer feature.

API Grid Request – Campaign Summary

There is a new API Grid Request that shows summary data for Campaigns.

Request Example

<GridRequest xmlns="http://partner.informz.net/aapi/2009/08/">
<Password></Password>
<Brand id="xxxx">Brand Name</Brand>
<User>admin</User>
<Grids>
<Grid type="campaign_summary">
<ReturnFields>
<DataElement>average_finish_time</DataElement>
<DataElement>bounces_count</DataElement>
<DataElement>brand_id</DataElement>
<DataElement>campaign_end_date</DataElement>
<DataElement>campaign_goal_perc</DataElement>
<DataElement>campaign_id</DataElement>
<DataElement>is_campaign_valid</DataElement>
<DataElement>campaign_name</DataElement>
<DataElement>campaign_start_date</DataElement>
<DataElement>campaign_status</DataElement>
<DataElement>campaign_type</DataElement>
<DataElement>clicks_count</DataElement>
<DataElement>dollar_generated</DataElement>
<DataElement>folder</DataElement>
<DataElement>goal_target_group_id</DataElement>
<DataElement>goal_target_group_name</DataElement>
<DataElement>interactions_count</DataElement>
<DataElement>modify_date</DataElement>
<DataElement>num_added</DataElement>
<DataElement>num_completed</DataElement>
<DataElement>num_excluded</DataElement>
<DataElement>num_in_progress</DataElement>
<DataElement>opens_count</DataElement>
<DataElement>purchases_count</DataElement>
<DataElement>re_entry</DataElement>
<DataElement>sent_count</DataElement>
<DataElement>unique_web_visitors_count</DataElement>
<DataElement>unsubscribes_count</DataElement>
</ReturnFields>
</Grid>
</Grids>
</GridRequest>

API Grid Request – Landing Pages Summary

There is a new API Grid Request that shows Landing Page summaries.

Request Example

<GridRequest xmlns="http://partner.informz.net/aapi/2009/08/">
<Password></Password>
<Brand id="xxxx">Test Brand</Brand>
<User></User>
<Grids>
<Grid type="landing_pages_summary">
<ReturnFields>
<DataElement>brand_id</DataElement>
<DataElement>month_id</DataElement>
<DataElement>year_id</DataElement>
<DataElement>page_name</DataElement>
<DataElement>page_type</DataElement>
<DataElement>page_status</DataElement> (Active/In Progress/Archived)
<DataElement>url</DataElement>
<DataElement>views_count</DataElement>
<DataElement>submits_count</DataElement>
<DataElement>unsubscribes_count</DataElement>
<DataElement>modified_date</DataElement>
<DataElement>folder</DataElement>
</ReturnFields>
</Grid>
</Grids>

API Grid Request – Scoring Summary

There is a new API Grid Request that shows scoring summaries.

Request Example

<GridRequest xmlns="http://partner.informz.net/aapi/2009/08/">
<Password></Password>
<Brand id="xxxx">Brand Name</Brand>
<User>admin</User>
<Grids>
<Grid type="scoring_summary">
<ReturnFields>
<DataElement>brand_id</DataElement>
<DataElement>last_calculated_date</DataElement>
<DataElement>scoring_group_description</DataElement>
<DataElement>total_subscribers_in_scoring_group</DataElement>
<DataElement>subscribers_not_in_scoring_group</DataElement>
<DataElement>score_type_name</DataElement>
<DataElement>a_score_subscribers</DataElement>
<DataElement>a_score_description</DataElement>
<DataElement>a_score_subscriber_Percentage</DataElement>
<DataElement>b_score_subscribers</DataElement>
<DataElement>b_score_description</DataElement>
<DataElement>b_score_subscriber_Percentage</DataElement>
<DataElement>c_score_subscribers</DataElement>
<DataElement>c_score_description</DataElement>
<DataElement>c_score_subscriber_Percentage</DataElement>
<DataElement>d_score_subscribers</DataElement>
<DataElement>d_score_description</DataElement>
<DataElement>d_score_subscriber_Percentage</DataElement>
<DataElement>f_score_subscribers</DataElement>
<DataElement>f_score_description</DataElement>
<DataElement>f_score_subscriber_Percentage</DataElement>
</ReturnFields>
</Grid>
</Grids>
</GridRequest>

API Grid Request – Subscriber Status History

There is a new API Grid Request that shows subscriber status history.

Request Example

<GridRequest xmlns="http://partner.informz.net/aapi/2009/08/">
<Password></Password>
<Brand id="xxxx">Brand Name</Brand>
<User>admin</User>
<Grids>
<Grid type="subscriber_status_history">
<ReturnFields>
<DataElement>brand_id</DataElement>
<DataElement>email</DataElement>
<DataElement>status</DataElement>
<DataElement>status_date</DataElement>
<DataElement>status_description</DataElement>
<DataElement>subscriber_id</DataElement>
<DataElement>user_id</DataElement>
</ReturnFields>
</Grid>
</Grids>
</GridRequest>

API Grid Request – Web Tracking Summaries

There are four new API Grid Requests that provide Web Tracking Summary details:

  • Web Tracking Summary
  • Web Tracking Page Summary
  • Web Tracking Interaction Summary
  • Web Tracking Purchase Summary

The subsections below provide examples of these grid requests.

Web Tracking Summary

<GridRequest xmlns="http://partner.informz.net/aapi/2009/08/">
<Password></Password>
<Brand id="xxxx">Brand Name</Brand>
<User>admin</User>
<Grids>
<Grid type="web_tracking_summary">
<ReturnFields>
<DataElement>brand_id</DataElement>
<DataElement>month</DataElement>
<DataElement>year</DataElement>
<DataElement>sessions</DataElement>
<DataElement>users</DataElement>
<DataElement>pages</DataElement>
<DataElement>pageviews</DataElement>
<DataElement>pageviews_per_session</DataElement>
<DataElement>num_purchases</DataElement>
<DataElement>total_purchase_value</DataElement>
<DataElement>avg_purchase_value</DataElement>
<DataElement>last_purchase_date</DataElement>
<DataElement>known_users</DataElement>
<DataElement>anonymous_users</DataElement>
<DataElement>new_users</DataElement>
<DataElement>existing_users</DataElement>
<DataElement>know_users_perc_of_users</DataElement>
<DataElement>anonymous_users_perc_of_users</DataElement>
<DataElement>new_users_perc_of_users</DataElement>
<DataElement>existing_users_perc_of_users</DataElement>
<DataElement>bounces</DataElement>
<DataElement>bounces_perc_of_sessions</DataElement>
<DataElement>referral</DataElement>
<DataElement>informz_email</DataElement>
<DataElement>social</DataElement>
<DataElement>search</DataElement>
<DataElement>direct</DataElement>
<DataElement>referral_perc_of_sessions</DataElement>
<DataElement>informz_email_perc_of_sessions</DataElement>
<DataElement>social_perc_of_sessions</DataElement>
<DataElement>search_perc_of_sessions</DataElement>
<DataElement>direct_perc_of_sessions</DataElement>
<DataElement>linkedin</DataElement>
<DataElement>facebook</DataElement>
<DataElement>twitter</DataElement>
<DataElement>linkedin_perc_of_sessions</DataElement>
<DataElement>facebook_perc_of_sessions</DataElement>
<DataElement>twitter_perc_of_sessions</DataElement>
<DataElement>first_place_search</DataElement>
<DataElement>second_place_search</DataElement>
<DataElement>third_place_search</DataElement>
<DataElement>fourth_place_search</DataElement>
<DataElement>first_place_search_num</DataElement>
<DataElement>second_place_search_num</DataElement>
<DataElement>third_place_search_num</DataElement>
<DataElement>fourth_place_search_num</DataElement>
<DataElement>first_place_search_perc_of_sessions</DataElement>
<DataElement>second_place_search_perc_of_sessions</DataElement>
<DataElement>third_place_search_perc_of_sessions</DataElement>
<DataElement>fourth_place_search_perc_of_sessions</DataElement>
<DataElement>first_place_country</DataElement>
<DataElement>second_place_country</DataElement>
<DataElement>third_place_country</DataElement>
<DataElement>fourth_place_country</DataElement>
<DataElement>first_place_country_num</DataElement>
<DataElement>second_place_country_num</DataElement>
<DataElement>third_place_country_num</DataElement>
<DataElement>fourth_place_country_num</DataElement>
<DataElement>first_place_country_perc_of_sessions</DataElement>
<DataElement>second_place_country_perc_of_sessions</DataElement>
<DataElement>third_place_country_perc_of_sessions</DataElement>
<DataElement>fourth_place_country_perc_of_sessions</DataElement>
<DataElement>first_place_browser</DataElement>
<DataElement>second_place_browser</DataElement>
<DataElement>third_place_browser</DataElement>
<DataElement>fourth_place_browser</DataElement>
<DataElement>first_place_browser_num</DataElement>
<DataElement>second_place_browser_num</DataElement>
<DataElement>third_place_browser_num</DataElement>
<DataElement>fourth_place_browser_num</DataElement>
<DataElement>first_place_browser_perc_of_sessions</DataElement>
<DataElement>second_place_browser_perc_of_sessions</DataElement>
<DataElement>third_place_browser_perc_of_sessions</DataElement>
<DataElement>fourth_place_browser_perc_of_sessions</DataElement>
</ReturnFields>
</Grid>
</Grids>
</GridRequest>

Web Tracking Page Summary

<GridRequest xmlns="http://partner.informz.net/aapi/2009/08/">
<Password></Password>
<Brand id="xxxx">Brand Name</Brand>
<User>admin</User>
<Grids>
<Grid type="web_tracking_page_summary">
<ReturnFields>
<DataElement>brand_id</DataElement>
<DataElement>month</DataElement>
<DataElement>year</DataElement>
<DataElement>type</DataElement>
<DataElement>name</DataElement>
<DataElement>pageviews</DataElement>
<DataElement>avg_duration</DataElement>
<DataElement>users</DataElement>
<DataElement>known_users</DataElement>
<DataElement>entrances</DataElement>
<DataElement>exits_perc</DataElement>
<DataElement>bounces_perc</DataElement>
<DataElement>create_date</DataElement>
</ReturnFields>
</Grid>
</Grids>
</GridRequest>

Web Tracking Interaction Summary

<GridRequest xmlns="http://partner.informz.net/aapi/2009/08/">
<Password></Password>
<Brand id="xxxx">Brand Name</Brand>
<User>admin</User>
<Grids>
<Grid type="web_tracking_interactions_summary">
<ReturnFields>
<DataElement>brand_id</DataElement>
<DataElement>month</DataElement>
<DataElement>year</DataElement>
<DataElement>category</DataElement>
<DataElement>action</DataElement>
<DataElement>interaction_num</DataElement>
</ReturnFields>
</Grid>
</Grids>
</GridRequest>

Web Tracking Purchase Summary

<GridRequest xmlns="http://partner.informz.net/aapi/2009/08/">
<Password></Password>
<Brand id="xxxx">Brand Name</Brand>
<User>admin</User>
<Grids>
<Grid type="web_tracking_purchase_summary">
<ReturnFields>
<DataElement>brand_id</DataElement>
<DataElement>month</DataElement>
<DataElement>year</DataElement>
<DataElement>sku</DataElement>
<DataElement>name</DataElement>
<DataElement>purchases_num</DataElement>
<DataElement>purchases_value</DataElement>
</ReturnFields>
</Grid>
</Grids>
</GridRequest>

Campaigns – Editing Mailings in Active Campaigns

Informz now allows campaign mailings to be edited in active campaigns. Deactivating a campaign is longer necessary to edit such mailings. There are two ways to edit a campaign mailing in an active campaign:

  • From the Flow tab of the campaign report.
  • From the Mailings tab of the campaign report.

Editing from the Flow Tab

On the Flow tab of the Campaign Report (for an active campaign) find the campaign step with your desired mailing. Click the step to open the Send Mail Options window.

Click Edit Mailing to edit the mailing.

Editing from the Mailings Tab

On the Mailing tab of the Campaign Report (for an active campaign), hover over the Menu icon for your desired mailing and click Edit.

This opens the mailing in edit mode (Campaign Mailing Designer).

Additional Notes

The Campaign Designer shows warning modals if messages are dependent on decide steps or if messages have already been sent.

If users edit an active campaign mailing, the Mailing Activity Report (MAR) Options tab will not reflect any of these changes. However, all other data in the MAR reflect the edited version.

Home Page – Client Name

In the site wrapper, the client name now displays as many characters as possible in the available space at the top of the screen (it is no longer truncated after 25 characters). This is dependent on the screen size.

Home Page – Prepaid Panel

The Prepaid Block panel has been renamed Email Balance: [Number of Emails for both Parent/Child]. It shows the number of emails for both parent and child accounts, regardless of user permissions.

When an account has the Share Email Blocks extension active, the Email Balance header shows the total number of parent email blocks only. If a child account has its own blocks, they are not included in the calculation.

There is a View Child link available on the panel for all parent accounts with child accounts. This is visible for all users. It navigates to a new page with the child account’s Prepaid Blocks table (the table has Brand Name, Purchased, Date of Purchase, Expires, and Total Remaining columns). The link is not available on the panel if the account has the Share Email Blocks extension active. The table itself is neither sortable nor draggable. It shows the first ten records and is scrollable thereafter; it is sorted by purchase date (descending).

Home Page – Scheduled Mailings List

The Informz Home Page now features a new Scheduled Mailings panel. It shows columns for the mailing name and scheduled send date for the eight mailings with the nearest scheduled send date. Mailings from all users display in this panel; however, campaign and triggered mailings are not displayed.

If you have no scheduled mailings, the panel remains empty.

Please note that you cannot click on the mailings in this panel – they display for information purposes only. To view any scheduled mailings, navigate to Mailings > View > Scheduled tab. Alternatively, click View More to view the Scheduled tab.

iMIS Landing Page Personalization Validation

Informz’s iMIS Landing Pages validate if a form contains iMIS personalization fields. If there are iMIS personalization fields present, Informz displays the message below in the Process tab:

Checking Enable Auto-fill removes the message; unchecking causes the message to return.

Additionally, the message does not display if there are no iMIS personalization fields.

The Activate tab displays the warning message if a Landing Page has iMIS personalization fields and the Auto-fill checkbox is unchecked.

Landing Pages – Email Format Checkbox

There is a new Landing Page Item – Email Format Checkbox – that allows Landing Page visitors to choose if they would like to receive emails in Plain Text format. This changes the visitor’s delivery status in Informz.

Users can only add this checkbox to Form Landing Pages.

To add an Email Format Checkbox, open the Items Flyout menu and click Email Format Checkbox.

The checkbox appears on the page with the text “Receive Plain Text Emails” (this message can be modified). Additionally, when visitors hover over the checkbox on the Landing Page, they’ll see the following tooltip: “check to receive plain text emails.”

If Auto-fill is activated for the form, the checkbox reflects the visitor’s preferred delivery method. When Auto-fill is deactivated, the checkbox is unchecked by default.

Landing Pages – Follow-Up Mailings Report

There is a new tab in the Landing Page Report for Form Landing Pages that shows details for a follow-up mailing. The new tab (Mailing) only shows the follow-up mailing that is currently used with the Landing Page. Any previously-used follow-up mailings are not displayed.

If you click the mailing name in list view, Informz navigates to the Mailing Activity Report for the follow-up mailing (note that this is unavailable if the mailing has not been sent).

Landing Pages – iMIS Integration

Users can now add nine different iMIS Personalizations to their form Landing Pages.

These values, located in the Personal Information Fields item, are as follows:

  • First Name
  • Last Name
  • Prefix
  • Title
  • Address 1
  • Address 2
  • City
  • State
  • Zip

If an iMIS subscriber submits the form, personalizations update in the iMIS database in real time (unless the bridge/connection is down, in which case Informz receives an error message). iMIS First Name and Last Name fields are always required fields; users cannot change this setting. These fields accept a maximum of 100 characters each (users see an error message for anything greater). All other fields are not required.

iMIS personalization fields do not display on live Landing Pages for subscribers without an iMIS ID. However, iMIS personalization fields display during test modes. Submitting a Landing Page in test mode by a subscriber who has an iMIS ID also updates the corresponding data in the iMIS database!

You must have the auto-fill option checked for personalizations to automatically populate on your Landing Page.

Salesforce – Deleted Target Groups

Salesforce mailings were failing because of deleted and/or broken compound target groups. The Salesforce target groups were deleted on one list refresh and the re-added in the next refresh. This created new target groups with the same name as an old target group. Both mailings and compound target groups that referenced the old target group ID failed because the old group was created. This has been fixed, and there should no longer be errors.