WEBVTT NOTE This file was generated by Descript 00:00:01.170 --> 00:00:02.700 This is a quick walkthrough of how 00:00:02.700 --> 00:00:04.110 personalized GIF templates work, 00:00:04.410 --> 00:00:05.850 how they integrate with your stack, 00:00:05.850 --> 00:00:07.950 whether it's a CRM custom, API 00:00:07.950 --> 00:00:10.020 build, or even a spreadsheet upload. 00:00:10.590 --> 00:00:12.780 So you might be wondering, are we 00:00:12.780 --> 00:00:14.670 just sticking names onto an image? 00:00:14.730 --> 00:00:16.260 Does it work with complex data? 00:00:16.470 --> 00:00:18.570 What about fallbacks or missing data 00:00:19.170 --> 00:00:21.099 and how does the data flow work? 00:00:23.310 --> 00:00:25.320 Put simply, each personalized GIF is 00:00:25.320 --> 00:00:26.939 driven by an intelligent template. 00:00:27.270 --> 00:00:28.980 That template creates a unique GIF for 00:00:28.980 --> 00:00:31.080 each person before an email is sent out. 00:00:32.159 --> 00:00:33.750 Each template is built from the ground 00:00:33.750 --> 00:00:36.180 up around your brief or objectives, 00:00:36.390 --> 00:00:37.830 the data points available, and 00:00:37.830 --> 00:00:39.600 obviously custom branded visuals. 00:00:41.040 --> 00:00:42.629 These are truly dynamic and they handle 00:00:42.629 --> 00:00:44.850 complex data and various scenarios. 00:00:46.349 --> 00:00:47.849 Looking at this example of an 00:00:47.849 --> 00:00:49.919 abandoned cart, if there's a discount 00:00:49.919 --> 00:00:51.540 available, we'll show it only when 00:00:51.540 --> 00:00:54.300 needed, or one customer qualifies for 00:00:54.300 --> 00:00:56.010 free shipping and another doesn't. 00:00:58.260 --> 00:00:59.199 In this scene, we're pulling 00:00:59.220 --> 00:01:00.569 images straight from the trigger 00:01:00.569 --> 00:01:02.190 event, and then scaling them 00:01:02.190 --> 00:01:03.929 for irregular dimensions first. 00:01:04.890 --> 00:01:06.750 We can run a discount calculation 00:01:07.170 --> 00:01:08.610 on their unique basket total, 00:01:08.850 --> 00:01:10.080 and then show that visually. 00:01:11.220 --> 00:01:13.110 Or we could take a static 00:01:13.110 --> 00:01:14.690 data point such as a suburb. 00:01:15.000 --> 00:01:17.040 And use that to show their nearest retail 00:01:17.040 --> 00:01:19.080 location via a Maps API enhancement. 00:01:20.520 --> 00:01:21.990 If you've got customers with super 00:01:21.990 --> 00:01:23.740 long names or no names, or you're 00:01:23.760 --> 00:01:25.230 concerned about profanities or 00:01:25.230 --> 00:01:27.150 missing information in profiles. 00:01:27.360 --> 00:01:28.800 Our templates handle all of that. 00:01:29.250 --> 00:01:31.470 Part of the template logic is that there 00:01:31.470 --> 00:01:33.330 are fallbacks built in for all possible 00:01:33.330 --> 00:01:35.850 scenarios so that recipients always 00:01:35.850 --> 00:01:37.320 see a motioned GIF that's on brand. 00:01:39.149 --> 00:01:40.740 Each project is unique and presents 00:01:40.740 --> 00:01:42.330 unique challenges and scenarios. 00:01:42.570 --> 00:01:43.979 We build your template to deliver 00:01:43.979 --> 00:01:45.570 the best possible experience 00:01:45.660 --> 00:01:47.100 no matter what the data says. 00:01:48.089 --> 00:01:49.679 Okay, so let's talk about what 00:01:49.679 --> 00:01:51.179 happens when the template is ready. 00:01:51.869 --> 00:01:53.639 There are a few ways to use personalized 00:01:53.639 --> 00:01:56.220 GIFs, either through a dynamic data 00:01:56.220 --> 00:01:57.509 integration, which is perfect for 00:01:57.509 --> 00:02:00.600 automated flows or with static data such 00:02:00.600 --> 00:02:02.830 as a CSV, which is perfect for campaigns. 00:02:04.140 --> 00:02:06.480 An example process for an automated flow 00:02:07.230 --> 00:02:10.020 would start when the trigger event runs. 00:02:10.680 --> 00:02:11.970 A webhook would then send the 00:02:11.970 --> 00:02:14.100 data, a GIF would be created. 00:02:14.760 --> 00:02:16.410 The URL for that GIF would then be 00:02:16.410 --> 00:02:18.880 sent back via API and added as a custom 00:02:18.900 --> 00:02:21.090 attribute, and then that would be merged 00:02:21.120 --> 00:02:22.800 into the email at the time of send. 00:02:24.240 --> 00:02:26.310 Another scenario is a once off campaign. 00:02:26.670 --> 00:02:28.530 You'd create a list or a segment. 00:02:29.040 --> 00:02:29.910 The data would then be 00:02:29.910 --> 00:02:31.745 exported or fetched via API. 00:02:32.775 --> 00:02:34.065 All the GIFs would be created 00:02:34.065 --> 00:02:35.745 ahead of the campaign going out. 00:02:36.225 --> 00:02:37.905 And then GIF URLs could be written 00:02:37.905 --> 00:02:39.915 back to profiles as custom attributes 00:02:40.275 --> 00:02:42.405 or a dynamic URL could be merged at 00:02:42.405 --> 00:02:44.355 the time of send using merge tags 00:02:44.355 --> 00:02:46.065 similar to liquid personalization. 00:02:47.235 --> 00:02:49.005 Another completely custom process 00:02:49.005 --> 00:02:51.165 used a combination of API and CRM. 00:02:51.555 --> 00:02:53.595 So this GIF takes betting odds directly 00:02:53.595 --> 00:02:55.365 from the Sportsbook API, and it 00:02:55.365 --> 00:02:57.795 combines that with CRM data, such as a 00:02:57.795 --> 00:02:59.295 person's name or their sport preference. 00:02:59.895 --> 00:03:00.945 And produces a truly 00:03:00.945 --> 00:03:02.115 dynamic piece of media. 00:03:04.275 --> 00:03:07.635 So to wrap up, our team has two parts. 00:03:07.815 --> 00:03:09.795 The creative side, which will assist in 00:03:09.795 --> 00:03:12.135 conceptualizing the visual experience 00:03:12.405 --> 00:03:13.905 and the technical side, which will 00:03:13.905 --> 00:03:15.525 connect any of the integration 00:03:15.525 --> 00:03:16.815 dots to get you up and running. 00:03:17.655 --> 00:03:18.885 We are official partners, these 00:03:18.885 --> 00:03:20.265 leading platforms, and are 00:03:20.265 --> 00:03:22.215 constantly adding new integrations. 00:03:22.275 --> 00:03:24.975 So whatever your stack or situation, 00:03:25.215 --> 00:03:27.585 creatively or technically, we can enhance 00:03:27.585 --> 00:03:29.025 any emails that you currently have. 00:03:29.325 --> 00:03:31.005 With one-to-one personalized media.