WEBVTT 00:00:00.000 --> 00:00:01.966 Hi! Welcome to Circle. 00:00:01.966 --> 00:00:07.732 This video introduces two new email reporting features recently released in Circle. 00:00:07.733 --> 00:00:16.466 In version 7.2, released in June, is a Geolocation report to help identify the location where emails were opened. 00:00:16.466 --> 00:00:24.132 Version 7.4, released in August, adds a devices report that lists the device used to open the email. 00:00:24.133 --> 00:00:27.966 Let’s look at a Circle project that includes an email touchpoint. 00:00:27.966 --> 00:00:35.866 The new reports will be there automatically – you don’t need to create them in Marketing Console – just scroll down to see the new reports. 00:00:35.866 --> 00:00:42.499 The first thing to note is that the geolocation and devices reports measure non-unique opens. 00:00:42.500 --> 00:00:48.500 Each time a recipient opens the email, perhaps from a different location or using a different device, 00:00:48.500 --> 00:00:50.733 the report will be updated. 00:00:50.733 --> 00:00:58.599 The data for the report is captured from the information provided by the email client that the recipient uses to open the email. 00:00:58.600 --> 00:01:03.766 There are many different email clients and way they report this information can vary. 00:01:03.766 --> 00:01:08.032 In some cases, Gmail for instance, this information is blocked, 00:01:08.033 --> 00:01:14.433 so email opens from Gmail are not included in the geolocation map, and in the devices report, 00:01:14.433 --> 00:01:18.599 emails opened with Gmail will be shown as “unknown”. 00:01:18.600 --> 00:01:24.633 The geolocation map will open to display the region that encompasses all tracked opens. 00:01:24.633 --> 00:01:31.599 For example, if everyone that opened the email was in one country, then the map will open to a closer view. 00:01:31.600 --> 00:01:37.766 You can also click on the state or city to get a closer look at the distribution within that area. 00:01:37.766 --> 00:01:40.699 You can click and drag the map around, 00:01:40.700 --> 00:01:44.733 and also zoom in and out using these controls. 00:01:44.733 --> 00:01:50.599 Because they are non-unique reports, and the data from the email clients is not always reliable, 00:01:50.600 --> 00:01:54.666 these reports are designed to provide “guidance” only. 00:01:54.666 --> 00:02:02.899 They provide basic information on the email clients used by your recipients, and where they are when they open the email. 00:02:02.900 --> 00:02:07.133 This information will help ensure that you test your future email designs 00:02:07.133 --> 00:02:11.899 in the email clients that are most commonly used by your specific recipients; 00:02:11.900 --> 00:02:16.333 and to help validate that your regional targeting is successful. 00:02:16.333 --> 00:02:23.733 Also, for multi-national campaigns the report may identify that you need to add additional language options. 00:02:23.733 --> 00:02:32.433 A final couple of points: In order to capture the report data XMPie Email Services version 3.5 is required. 00:02:32.433 --> 00:02:41.099 To check your XES version, login to your XMPie Dashboard, go to Settings and then Delivery providers. 00:02:41.100 --> 00:02:46.966 Select your XES delivery provider and check the XES version here. 00:02:46.966 --> 00:02:53.999 The devices and geolocation data is only captured for mass emails and not for triggered emails. 00:02:54.000 --> 00:03:00.866 If your project has been running for some time, take note of the report date range under the report heading. 00:03:00.866 --> 00:03:12.366 The devices and geolocation data can only be collected for email opens after the date the feature was released and version 3.5 XES was installed. 00:03:12.366 --> 00:03:18.732 Also, the devices and geolocation data is not stored in Marketing Console’s tracking database, 00:03:18.733 --> 00:03:25.033 so deleting events in Marketing Console will not clear the devices or geolocation data. 00:03:25.033 --> 00:03:29.733 For the best performance, PersonalEffect v9.5 or later is recommended. 00:03:29.733 --> 00:03:38.066 Versions earlier than this will work OK, but the new devices and geolocation events can take up to 1 hour to be reported.