Personalization, Analytics and AB testing with Accelerate

Personalization, Analytics and A/B testing with Accelerate 🔗 **Source:** [Personalization, Analytics and A/B testing with Accelerate](https://www.youtube.com/watch?v=F7N1GAf0dVw) > [!note]+ Document Notes > tags: [wordpress, personalization, analytics, ab-testing, accelerate-plugin, human-made, content-optimization] > author: Chris Reynolds > source: Pantheon > reference: https://www.youtube.com/watch?v=F7N1GAf0dVw > date created: 2024-12-19 10:30 > > # 🏷️ Title: Personalization, Analytics and A/B testing with Accelerate >  ## 🧰 Action Inbox - [H1] Install Accelerate plugin for WordPress personalization — check WordPress.org repository #wordpress #personalization - [H2] Create audience segments based on analytics data — use geographic and behavioral targeting #analytics #segmentation - [H3] Set up A/B testing for headlines and featured images — test post performance variations #ab-testing #optimization ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ### 🔗 References - [Accelerate Plugin](https://accelerateplugin.com) - [WordPress.org Plugin Repository](https://wordpress.org/plugins/) ## 📝 Summary - Human Made's Joe Hoy demonstrates Accelerate, a WordPress plugin for content personalization, A/B testing, and analytics - Plugin enables dynamic content delivery based on audience segments like geography, time, and user behavior - All personalization happens client-side via JavaScript, maintaining single page cache while delivering targeted content - Includes built-in analytics dashboard that provides immediate insights without external integrations - Free up to 1 million views per month, designed as accessible alternative to enterprise solutions like Optimizely ## 📖 Main Content The Accelerate plugin represents Human Made's approach to democratizing personalization and A/B testing for WordPress sites. Unlike enterprise solutions that require complex integrations and separate tooling, Accelerate operates entirely within the WordPress ecosystem using synced patterns and the block editor. The plugin's architecture is noteworthy: all content variations are delivered to the browser in a single cached response, then JavaScript determines which variant to display based on audience criteria. This approach maintains CDN and page cache efficiency while enabling sophisticated personalization. Key features include audience segmentation based on geographic location, time of day, referrer data, and custom attributes; A/B testing at the block and post level with automatic winner selection; and integrated analytics that surface actionable insights directly in the WordPress admin. The plugin addresses a common enterprise challenge where organizations want personalization capabilities but face procurement delays, integration complexity, or cost barriers with traditional solutions. It's particularly effective for high-traffic sites like PlayStation.com and Recipe Tin Eats. ## 🗒️ Notes #### ⏱️ [00:00](https://www.youtube.com/watch?v=F7N1GAf0dVw?t=0) — [H1] Introduction and Background - Key idea: Accelerate plugin evolved from Human Made's Altus DXP platform experience - Evidence: "It grew out of what we had been doing several years ago with a thing called Altus DXP" #### ⏱️ [05:30](https://www.youtube.com/watch?v=F7N1GAf0dVw?t=330) — [H2] Live Demo of Personalization - Key idea: Content changes dynamically based on audience preview settings - Evidence: "That's probably where you will get a rough idea of what Accelerate allows you to do is ultimately personalize and test content" #### ⏱️ [08:45](https://www.youtube.com/watch?v=F7N1GAf0dVw?t=525) — [H2] Geographic and Time-Based Targeting - Key idea: Headers display different content for evening vs France audiences - Evidence: "One is based off of a time of day. So that's the evening. Or if you switch to being France, so a geolocation based one" #### ⏱️ [12:30](https://www.youtube.com/watch?v=F7N1GAf0dVw?t=750) — [H2] Broadcast Block for Content Rotation - Key idea: Content queue rotates different internal ads and recirculation modules - Evidence: "That is a recirculation module but if you reload the page then there is actually like a content queue of different content" #### ⏱️ [16:20](https://www.youtube.com/watch?v=F7N1GAf0dVw?t=980) — [H2] A/B Testing Implementation - Key idea: Tests run on post headlines and images, not just homepage elements - Evidence: "This is something that isn't exactly content personalization, right? We also have a system to be able to do headline and featured image testing" #### ⏱️ [22:15](https://www.youtube.com/watch?v=F7N1GAf0dVw?t=1335) — [H2] Analytics Dashboard Overview - Key idea: Built-in analytics provide immediate insights without external tools - Evidence: "We have like a traditional analytics layer. You get some top level view metrics of your site" #### ⏱️ [25:40](https://www.youtube.com/watch?v=F7N1GAf0dVw?t=1540) — [H2] Content Editor Experience - Key idea: Block-level conversion tracking shows performance metrics directly in editor - Evidence: "I see the amount of views it has, the overall conversion rate, the conversion rate for each version" #### ⏱️ [30:10](https://www.youtube.com/watch?v=F7N1GAf0dVw?t=1810) — [H2] Audience Creation and Management - Key idea: Audiences built from analytics data using boolean logic and demographic criteria - Evidence: "Audiences are is ultimately a facet of your analytics data" #### ⏱️ [35:25](https://www.youtube.com/watch?v=F7N1GAf0dVw?t=2125) — [H2] Practical Use Cases - Key idea: PlayStation uses plugin for region-specific game ratings and content - Evidence: "It is used on blog.playstation.com PlayStation.com for the different rating images" #### ⏱️ [40:50](https://www.youtube.com/watch?v=F7N1GAf0dVw?t=2450) — [H3] Technical Architecture - Key idea: All data collection happens client-side via JavaScript navigator API - Evidence: "Virtually all of the analytic stuff is all front end. So, it's coming from the navigator" #### ⏱️ [44:30](https://www.youtube.com/watch?v=F7N1GAf0dVw?t=2670) — [H3] Cache-Friendly Design - Key idea: Single cached page serves all variants, JavaScript shows appropriate version - Evidence: "All of those variants are sent down to the browser and then it's ultimately the JavaScript layer that chooses which one to show" #### ⏱️ [48:15](https://www.youtube.com/watch?v=F7N1GAf0dVw?t=2895) — [H2] Block Editor Integration - Key idea: Synced patterns serve as foundation for personalized content variations - Evidence: "Synced patterns is actually how we do this content personalization thing" #### ⏱️ [52:40](https://www.youtube.com/watch?v=F7N1GAf0dVw?t=3160) — [H2] Success Stories and Scale - Key idea: Plugin handles enterprise-scale traffic including top 10 recipe sites globally - Evidence: "Recipe Tin Eats that has a lot of traffic. I think they're within maybe the top 10 recipe sites in the world" #### ⏱️ [57:20](https://www.youtube.com/watch?v=F7N1GAf0dVw?t=3440) — [H2] Enterprise vs Accessibility Balance - Key idea: Plugin fills gap between enterprise tools and immediate implementation needs - Evidence: "We're not trying to be better than an enterprise performance marketing tool. But where it actually gets used is in situations where it's going to be migrate to the Adobe suite" ## 📚 References - [Accelerate Plugin Website](https://accelerateplugin.com) - [WordPress.org Plugin Repository](https://wordpress.org/plugins/) - [Human Made Agency](https://humanmade.com) - [WP Consent API](https://wpconsentapi.org) ## 🗣️ Paraphrase - Accelerate transforms WordPress sites into dynamic platforms that adapt content based on visitor characteristics like location, time, and behavior without requiring complex server configurations - The plugin's client-side architecture delivers all content variations in a single cached response, then uses JavaScript to display the appropriate version based on audience rules - Built-in analytics provide actionable insights directly within WordPress, eliminating the need for external tools while enabling data-driven content decisions ## 📰 Newsletter **Transform Your WordPress Site with Smart Personalization** The Accelerate plugin from Human Made brings enterprise-level personalization capabilities directly into WordPress. Instead of juggling multiple tools and complex integrations, you can now create dynamic, targeted content experiences right from your familiar block editor. **Key Benefits:** - **Cache-Friendly**: All personalization happens client-side, maintaining your site's performance - **Built-in Analytics**: Get actionable insights without external tools - **Block Editor Native**: Works seamlessly with synced patterns and full site editing - **Free Tier**: Up to 1 million views monthly at no cost Perfect for sites with significant traffic looking to optimize conversion rates through A/B testing and audience targeting. Whether you're personalizing content by geography, testing headlines, or rotating promotional content, Accelerate simplifies what traditionally required enterprise-level solutions. Resources: [Accelerate Plugin](https://accelerateplugin.com), [Learn WordPress](https://learn.wordpress.org/), [Developer Docs](https://developer.wordpress.org/) ## ✅ Action Items #### WordPress - Core: Evaluate personalization patterns for inclusion in core block patterns library - Core Performance: Assess impact of client-side personalization on Core Web Vitals - Plugins: Review Accelerate plugin architecture for security and performance best practices - Documentation: Create guides for personalization workflows using synced patterns - Community: Share personalization case studies and success metrics #### DevRel - Developer advocacy: Create tutorials on implementing custom audience criteria - Education: Workshop on privacy-compliant personalization techniques - Developer experience: Document integration patterns with existing analytics tools - Community management: Facilitate discussions on personalization ethics and best practices ## 🧪 Hypotheses - Client-side personalization reduces server load while maintaining cache efficiency compared to server-side implementations - Integrated analytics within WordPress admin increases usage rates compared to external analytics requiring separate login - Block editor native personalization tools have lower adoption barriers than standalone personalization platforms - Geographic personalization shows higher conversion rates than time-based personalization for most content types ### 📊 Methodology - A/B test client-side vs server-side personalization implementations measuring page load times and cache hit rates - Compare user engagement metrics between sites using Accelerate's integrated analytics versus external tools - Survey WordPress users on personalization tool preferences and adoption barriers ### ❓ Questions - How does client-side personalization impact SEO and search engine content indexing? - What privacy compliance considerations arise when implementing behavioral targeting? - How can personalization effectiveness be measured beyond conversion rates? ### 🔮 Future Research - Integration patterns between Accelerate and customer data platforms - Performance benchmarks for personalization at enterprise scale - Privacy-preserving personalization techniques in WordPress ecosystem ### 💡 Implications - Practice: WordPress personalization becomes accessible to smaller organizations without enterprise budgets - Policy: Need for clear guidelines on ethical personalization and data collection practices - Security: Client-side personalization reduces server attack surface but increases JavaScript security considerations - Education: Training needed on audience segmentation and conversion optimization - Funding: Budget allocation shifts from expensive enterprise tools to internal content creation resources ### 🧠 Learning Styles Assessment Reading level estimate: Flesch-Kincaid Grade Level 10 #### 👀 Visual learners - Present: Live demo showing content variations, analytics dashboard screenshots - Improve: Architecture diagrams showing client-side vs server-side data flow #### 🔊 Aural learners - Present: Video demonstration with verbal explanations - Improve: Audio summary of key personalization concepts #### 🗣️ Verbal learners - Present: Clear definitions of audience, personalization, A/B testing concepts - Improve: Glossary of personalization terminology #### 🧩 Kinesthetic learners - Present: Step-by-step plugin installation and configuration demo - Improve: Hands-on workshop exercises for creating audience segments #### 🧠 Logical learners - Present: Technical architecture explanation, performance metrics - Improve: Decision tree for choosing personalization strategies #### 🧑‍🤝‍🧑 Social learners - Present: Live Q&A session, discussion of use cases - Improve: Community forum for sharing personalization strategies #### 🧘‍♀️ Solitary learners - Present: Comprehensive documentation and self-guided examples - Improve: Self-assessment checklist for personalization readiness #### 🌿 Naturalistic learners - Present: Real-world examples from PlayStation and Recipe Tin Eats - Improve: Ecosystem thinking about personalization's role in user journey ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Clear heading structure, descriptive alt text for interface elements - Improve: ARIA labels for dynamic content areas #### Keyboard navigation - Present: Standard WordPress admin keyboard navigation - Improve: Keyboard shortcuts for switching between content variants #### Contrast and readability - Present: Standard WordPress admin contrast ratios - Improve: High contrast mode for analytics dashboards #### Text resizing and reflow - Present: Responsive admin interface - Improve: Ensure personalization controls remain usable at 200% zoom #### Media and captions - Present: Video includes clear audio explanation - Improve: Closed captions for technical terminology #### Forms and interactions - Present: Standard WordPress form patterns - Improve: Clear error messaging for audience criteria setup ### 🌍 DEIB Assessment #### Cultural breadth - Present: Geographic personalization examples from multiple countries - Improve: Non-Western personalization use cases and cultural considerations #### Inclusive language - Present: Gender-neutral technical terminology - Improve: Avoid marketing jargon that assumes business context #### Neurodiversity support - Present: Structured demonstration with clear sections - Improve: Option to skip demo sections, consistent UI patterns #### Representation - Present: Technical discussion with multiple perspectives - Improve: Include diverse personalization scenarios beyond e-commerce #### Psychological safety - Present: Respectful discussion of privacy concerns - Improve: Clear guidelines on ethical personalization practices ### ✅ Logical Validity #### Strong reasoning - Deductive strength: Plugin architecture logically follows from cache efficiency requirements - Inductive strength: Success stories from PlayStation and Recipe Tin Eats support scalability claims - Causal reasoning: Client-side implementation directly enables cache efficiency benefits - Analogical strength: Comparison to enterprise tools effectively illustrates accessibility gap #### Fallacies - Appeal to authority: Mentioning top 10 recipe site without verification - minor weakness, could provide specific metrics - False dilemma: Implies choice between expensive enterprise tools or Accelerate - ignores middle-ground solutions #### Tone of voice - Overall tone: Professional and educational with appropriate technical detail, balanced between accessibility and expertise ### 🛡️ DARVO Analysis - Deny: No denial patterns observed - Attack: No attacks on competing solutions, respectful comparison - Reverse victim/offender: No victim/offender dynamics present - Emotional cues and rhetoric: Balanced presentation without manipulative language ## 🎯 Conclusion Accelerate represents a significant step toward democratizing personalization in WordPress by removing traditional barriers of cost, complexity, and integration challenges. The plugin's client-side architecture cleverly maintains performance while enabling sophisticated audience targeting, making enterprise-level personalization accessible to a broader range of WordPress sites. For practitioners, this tool offers immediate value through its integrated analytics and block editor native approach --- ## Full Transcript [00:24] Hello internet. I am Chris Reynolds, [00:27] senior developer advocate at Pantheon. [00:29] Today on the stream, we're going to be [00:30] talking about personalization inside [00:33] WordPress. And to do that, I've got Joe [00:35] Hoy on the stream today uh to talk about [00:37] what Human Made's been working on for a [00:39] while. Uh a plugin called Accelerate. Uh [00:42] welcome to the stream, Joe. Joe is the [00:44] chief technology officer of Human Made, [00:46] I guess I should say. Uh and yeah, tell [00:49] tell us about yourself and what you've [00:50] been working on. [00:52] >> Thanks, Chris. uh excited to be on um [00:56] tout our our latest wear um which is our [00:59] accelerate plug-in. Um but I guess more [01:03] generally uh I guess I've been working [01:05] with WordPress for [01:08] 15 16 17 years something like that. Uh [01:12] obviously human's whole existence which [01:14] is about [01:16] I don't know must be claimed close to 15 [01:18] years. [01:19] >> Yeah. Um so done a lot with WordPress [01:21] and this is our latest I guess uh yeah [01:25] for into building a plug-in. [01:27] >> Yeah. And I mean Accelerate has been [01:30] baking in the oven for a while. Uh talk [01:33] about sort of the journey of like what [01:35] you were looking for uh what you were [01:37] trying to build and and what what I [01:39] guess because it's gone through a couple [01:40] different iterations too, right? Uh so [01:43] like where how did it get to be the [01:45] thing that it is today and how has it [01:46] changed uh over time? [01:48] Yeah, sure. So, um, yes, it grew out of [01:52] what we had been doing several years ago [01:54] with a thing called Altus DXP. There was [01:56] like a digital experience platform which [01:58] essentially took WordPress and added a [02:01] bunch of uh what is kind of in the [02:04] industry term DX features around like [02:06] personalization, AB testing and things. [02:08] Um ultimately that um [02:13] didn't exactly pan out as a unified [02:15] platform, but we took a lot of the ideas [02:17] there of these kind of extra uh [02:20] functions that we built on top of [02:21] WordPress and some of that span out into [02:24] what is now the Accelerate plugin um [02:26] which is just a a standalone plugin that [02:28] anybody can use. um the Altus DXP [02:31] platform, you know, went more in the [02:33] direction of just being uh kind of, you [02:35] know, solid WordPress enterprise host [02:37] and then some other bits and pieces also [02:39] span out of that. So ultimately it's [02:41] from our kind of learnings of uh from [02:44] technically what we were able to do in [02:46] the Altus DXP platform, but also we've [02:50] really tried to simplify as much as [02:52] possible. So hopefully we'll get stuck [02:54] into it obviously today but really uh [02:57] hopefully it comes across of what we've [02:59] built is like very simple but those [03:01] building blocks allow uh a large amount [03:04] of like possibility and creativity in [03:06] what you're able to do with the tool. [03:08] >> Yeah. Awesome. Well, I will bring up my [03:10] screen over here uh because I've got a [03:13] site that uh has the Accelerate plugin [03:16] installed. Um, and I'm just gonna kind [03:18] of let you uh walk me through. Tell me [03:21] what I'm looking at. [03:24] >> That's a a great start. So, I guess uh [03:28] on the right side obviously we have the [03:30] the website using the Accelerate plugin [03:32] which will probably look like a normal [03:34] WordPress site. Uh on the left you have [03:37] the the admin dashboard. Um so I guess [03:40] you know I'm I'm tempted to take this [03:42] from the front end first of like what [03:43] does it mean that you can do with your [03:45] site? what does it look like as as a [03:46] user? So, right now you're landed on [03:49] this site. You have a header um you know [03:52] for uh for for the site and then if you [03:54] scroll down um you have like a latest [03:56] post block there with the latest post [03:58] and then you have like a kind of [04:00] recirculated internal ad kind of in the [04:02] footer. Um so as as you as the user [04:06] viewing this then um that is how the [04:09] site appears. However, um if you go to [04:12] the top where it says audience preview [04:14] there and then you switch uh on one of [04:16] those. So if you put evening um so it [04:19] changes the page. So um that's probably [04:22] where you will get a rough idea of what [04:24] Accelerate allows you to do is [04:26] ultimately personalize and test content [04:28] on your site depending on either who who [04:31] is viewing it or on like an AB test a [04:33] kind of randomized assortment. Um, so [04:35] right now, for example, I've preset up [04:38] some content on this site for the [04:40] header, which has three different [04:42] versions of a header. Um, one is based [04:44] off of a time of day. So that's the [04:46] evening. Um, or if you switch to being [04:49] France, so a geoloccation based one, [04:51] then we have different header for that. [04:53] And then the the default one that you're [04:55] seeing is is what we term the fallback. [04:57] So if you're not part of any audience [04:59] that I've kind of chosen what to see, [05:01] then then that's what you're going to [05:02] get. Um so that's kind of um what we [05:06] term content personalization. So that is [05:09] ultimately um you want to do multiple [05:12] variants of either you know literally [05:15] content on pages or sitewide elements [05:18] via full-sight editing and um ultimately [05:22] do different content for different [05:23] audiences. Uh could be audiences based [05:26] off of location. It could be uh [05:29] audiences based off of um like a [05:31] marketing campaign. Maybe they clicked [05:33] in through an email. So now they're [05:34] considered a certain type of user. You [05:36] want to change their experience of the [05:38] site. Uh so so that is content [05:40] personalization broadly. And we the [05:43] example here is the header, but [05:45] obviously that could be kind of any any [05:46] element of your site. Um if you scroll [05:48] down a little bit, there's a couple of [05:50] other um areas here. So what you're [05:52] seeing in the bottom here of this kind [05:54] of like internal ad, right? we've got [05:56] like free skiing or whatever. Um that is [06:00] a recirculation module but if you reload [06:02] the page then there is actually like a [06:05] content cue of different content that is [06:09] coming in through that slot. Um, so [06:11] where something like personalization or [06:13] AB testing is about testing the just the [06:16] specific content and you know you're [06:19] probably always going to get that [06:20] variant at least for that session [06:21] because you know you're you're not [06:23] moving uh countries whilst you're [06:25] reloading the pages or anything. uh the [06:27] broadcast block which is the way that [06:29] you can uh rotate in different content [06:32] in in a given area and again it will [06:35] will be measuring um the conversion [06:37] rates of that content for that specific [06:40] location that you've put it in. Um so [06:42] that's another thing that uh ultimately [06:45] is I guess ultimately bringing the [06:48] WordPress site to life more right making [06:50] it more dynamic allowing you to do [06:52] different variations of different [06:54] things. because I just got a two pieces [06:55] of content in that queue. Another thing [06:57] that you will see, well, you won't see [06:59] this, you'd actually have to open up the [07:01] site in an incognito window. Um, but we [07:03] also have a um AB test that is running [07:08] on this page as well. So, I think [07:10] hopefully if you go to the website here, [07:13] you just scroll down. Okay, you if close [07:16] your window and try it again because [07:17] you're you're randomly now getting [07:20] assigned to different audiences. [07:23] We've we've we've got a uh 50/50 chance [07:26] of of uh of the site that you're [07:29] actually going to see uh sorry of the [07:30] specific content. [07:31] >> Oh, here we go. [07:32] >> Um yeah, so e either on the homepage [07:34] block here where it's pushing you [07:36] through to that other post or if you [07:38] scroll down to where the latest post [07:39] block is is there there as well. So this [07:42] is something that isn't it's not exactly [07:44] content personalization, right? I [07:46] haven't had to do two versions of that [07:48] latest post block. Um, we also have a [07:51] system to be able to do headline and [07:52] featured image and other testing at the [07:55] kind of more meta level. So that's [07:57] actually a test running on that post, [07:59] right? It's not a test of my homepage. [08:01] That is a test of me trying different [08:03] headlines and images. And then wherever [08:05] that post may be shown across the site [08:07] in things like latest post blocks or [08:09] whatever else, uh, then I'm going to see [08:13] um, uh, randomly um, one one of those. [08:16] And again, I've been assigned to a [08:18] specific audience here. So, so whenever [08:21] you reload the page, you're going to get [08:22] the same one when you just clicked [08:24] through it there from the homepage that [08:26] is going to be attributed to that [08:28] version of the AB test. So, obviously [08:30] we're measuring the performance, right, [08:32] based off of the clickthroughs to the [08:33] posts. Well, which headline did you come [08:35] through on? And then we'll surface that. [08:38] And then when the ten test is actually [08:39] finished over a configurated amount of [08:41] days, it'll automatically pick whatever [08:43] the the highest performing uh one was. [08:46] So that's a very quick just kind of like [08:49] run through a few of the things that I [08:50] set up on the demo site here just to be [08:53] hopefully give you an idea of the kind [08:55] of things that accelerate is trying to [08:56] do. It's ultimately around being able to [09:00] iterate on your content, your designs, [09:02] and be able to measure the impact and [09:04] performance of those iterations and then [09:06] kind of keep doing that. So, um that's [09:09] that's how it looks for a user on the [09:11] front end, which is uh as an individual [09:14] user, you're probably actually not [09:15] seeing that much of that stuff because [09:17] you know you're you're not seeing all [09:18] the people and what they're getting [09:19] apart from the recirculator module at [09:22] the bottom. Um if you jump over to the [09:24] admin I can just show a couple of things [09:26] therefore that we have on the analytics [09:28] to understand um how how your site is [09:31] used. So one thing that you'll notice [09:32] when you come onto the accelerate main [09:34] dashboard in the admin straight away is [09:37] we have like a traditional analytics [09:40] layer. So you get some top level view [09:42] metrics of your site. You can see data [09:45] coming in things like that. We also have [09:47] this thing that we call a content [09:48] explorer which is essentially just a [09:50] different um way to get at your your uh [09:55] existing content just as you would go [09:57] through p post pages synced patterns [10:00] things like that. It's just kind of a [10:01] unified view that is going to give you [10:03] analytics uh alongside that. If you jump [10:06] into something like um the uh header for [10:11] example in this um yeah in the center [10:14] there I'll show you exactly kind of what [10:16] it looks like to be editing this from a [10:19] uh content authoring point of view. [10:21] >> Nice. [10:21] >> Um so hopefully it's fairly kind of [10:23] obvious what's happening here. Um I have [10:26] three variants right now. I can click [10:28] between them to edit different different [10:30] ones of those. Um, and within that [10:33] editor, um, below that is just your, you [10:36] know, your usual block editor there. Um, [10:38] so I can change anything that I would [10:40] want. And at a per block level there, I [10:42] see the amount of views it has, the [10:45] overall conversion rate, the conversion [10:47] rate for each version. So, it's it's [10:49] very kind of important that not only do [10:52] we show different variants depending on [10:55] what audience might be looking at the [10:56] website. Ultimately, if you don't have a [10:58] way to measure it, there's not really [11:00] any point in doing that because you're [11:01] never really going to know how effective [11:03] is it that I show a different message to [11:07] uh somebody in a different country or if [11:09] I, you know, have have a different uh uh [11:12] call to action for somebody coming from [11:14] a marketing campaign. you need to be [11:15] able to track the conversion rate to [11:17] understand whether that was a good thing [11:19] to personalize or or not. So, we have a [11:22] um fairly robust um off-site analytics [11:26] layer that isn't, you know, stored in [11:27] the WordPress database or or something [11:29] like that where we push a lot of user [11:32] interaction behavior to be able to give [11:34] editors and site authors like the the [11:37] information that they need to to edit. [11:40] Um, so that's what the experience looks [11:42] like. Whether that's an AB test or a [11:44] personalized test for at the block [11:47] level. Um, you can kind of see hopefully [11:50] it's a fairly intuitive experience based [11:52] off already being able to use the block [11:54] editor. [11:55] >> And then I can see you've got different [11:57] conversion goals. So you can be tracking [11:58] different things depending on uh what [12:01] you [12:01] >> Exactly. Yeah. Yeah. So so typically, [12:04] you know, I think the default Yes. would [12:06] be any like clicking of a link or [12:07] submitting anything any kind of um event [12:11] that can happen within the block by [12:13] default that would be considered a [12:14] conversion but yeah you can scope it [12:16] down there. [12:17] >> Um so so that's what it looks like to to [12:20] create personalized content. U maybe you [12:22] can yeah jump back to the main dashboard [12:24] and we could have a quick look at the uh [12:26] analytics um page in the back end. [12:29] >> Um so we're not a you know we're not [12:31] Google Analytics. We're not like a full [12:33] deep analytics suite, but ultimately um [12:37] we do have really good analytics data [12:40] because we have to track so many things [12:42] at the block level as well and at the [12:44] page level that um we think that we [12:48] provide a really good out of the box [12:49] just like how do I get analytics on my [12:51] site for free? Just install this plug-in [12:53] and it's done kind of thing. we already [12:55] need all of this data for the [12:56] personalization stuff. Um with things [12:59] like you know uh Google Analytics and uh [13:02] cookie law and cookie optin on Google [13:03] and things like that. It's definitely um [13:06] providing a kind of anonymized analytics [13:09] solution out of the box I think is like [13:11] a good win and certainly a immediate [13:13] benefit that people can get from using [13:15] the accelerate plug-in. Whereas like [13:17] personalization AB testing you do need [13:19] to go and do things right. [13:22] >> Yeah. You got to do the stuff. got to [13:24] write the content. Um whereas uh [13:26] analytics we're just obviously [13:28] collecting from day one. So it's it's [13:29] fairly typical of what you would expect. [13:31] Um but it does give you an idea what is [13:34] my breakdown by you know countries, by [13:37] browsers, pages, things like that. So [13:39] you can start to think about how can I [13:41] create audiences because ultimately and [13:43] accelerate what audiences are is [13:45] ultimately a facet of your analytics [13:47] data. Um, so though we don't show [13:50] everything here that's in the analytics [13:51] database yet, something like if you come [13:55] in through a UTM link to the website, [13:58] that is stored in our analytics data and [14:00] therefore that's how you create a [14:02] audience based off of that value. So [14:04] that's kind of how the data pipeline [14:06] works. [14:08] >> Um, yeah, tell me about audiences. Um, [14:10] obviously we have to have some audiences [14:12] if we're going to have uh different [14:14] views for different uh different things. [14:16] So let's let's pop in there. I'm [14:19] interested in in this because uh well I [14:24] don't see anything. [14:25] >> Yeah. Yeah. This is just I think it [14:27] takes takes a couple of seconds to load [14:28] in. So the the general idea with with [14:31] audiences again is like create criteria [14:34] of the um kind of demographic type data [14:38] that might come in via analytics. So by [14:40] default uh most of it is going to be [14:43] based off of things that are determined [14:45] on the front end from the browser. Um [14:48] you can uh certainly uh like hook into [14:51] this at a developer level to add other [14:53] things maybe like you would hook in and [14:55] add some like I don't know has purchased [14:57] this product via WooCommerce or [14:59] something right like you you could do [15:00] those kind of things. [15:01] >> Um or you can have like yeah the logged [15:03] in attribute here is like a WordPress [15:05] you know specific if if you're logged [15:07] into X Y or Z. So we have um generally a [15:11] bunch of different things that you can [15:12] facet by and you can do groups of those [15:14] you can do andors you can do you know [15:16] yada yada all of that boolean logic to [15:19] build up your audience of like uh how [15:21] how you might want so here yeah then I'm [15:24] saying if the hour is more than 16 [15:26] consider part of the evening audience [15:28] and that's going to be local time for [15:29] the user uh so that's quite a a basic [15:33] one that's that's simple to do but as [15:35] well as that you could do you know if [15:38] the referer includes github.com, [15:40] consider them a developer. And then [15:42] maybe, you know, right when I'm writing [15:43] my like um uh my call to actions or [15:48] something, I might vary those based off [15:50] of which audience is is viewing the [15:52] site. [15:54] >> And then I guess for for country, it's [15:56] actually telling me this is the [15:58] percentage of of pe visitors that I'm [16:00] getting from that country. So in this [16:02] case, it says France, 25% because 25% of [16:05] my audience is coming from France. So, [16:07] >> exactly. [16:08] >> In that way, I can really be targeted [16:11] for like, oh, I've got a lot of German [16:13] uh audience or I've got a lot of uh [16:15] French people coming to my website. I'm [16:17] going to have this this content or this [16:20] page or this header or whatever, this [16:21] advertisement that is specific to that [16:24] group of people. [16:26] >> Exactly. Yeah. Because there's [16:27] ultimately not much point putting in a [16:28] load of effort maybe targeting Canada [16:30] here that's at 3%. Sure. [16:32] >> So, uh, a lot of the personalization is [16:35] kind of like what is the what is the [16:38] returns on all of the work that you [16:40] might need to do to create variations on [16:42] your content? Um, and and how much [16:45] impact is is that likely to have. So, [16:47] there are um that's that's come at it [16:50] from purely I would say like a [16:52] performance marketing point of view. [16:53] There are other are other use cases [16:56] where uh you may want to have uh [17:01] more functional things like if they're [17:02] logged in show them this otherwise show [17:04] them this. Okay, that's not that that's [17:06] probably you're actually just trying to [17:07] like use the boolean logic of of the [17:10] plug-in which it can definitely be used [17:12] that way. Um I know that it is used on [17:15] uh blog.playstation.com PlayStation.com [17:17] for example for the different rating [17:20] images on whether you're in Europe or [17:22] whether you're in the US etc. So again [17:24] not really somewhere where they're [17:26] looking to like maximize conversion [17:27] rates on those clickthroughs of like [17:29] Peggy ratings or whatever but ultimately [17:31] it can be just a tool in the tool belt [17:33] of how can I uh you know [17:38] ultimately solve the functional problem [17:40] of like different audiences means [17:42] different functionality on the site as [17:43] well. Yeah, I mean I was actually going [17:45] to ask about uh what sort of practical [17:48] uses have you seen of of this sort of [17:50] stuff in the field and PlayStation's a [17:51] really good example because not only you [17:54] know the the rating system is different [17:56] but like a lot of times like uh the the [17:58] covers for a game in the US is going to [18:00] be different or even the games that are [18:02] available in the US are going to be [18:03] different than the games that are [18:04] available in Japan for example uh things [18:06] like that. And so you might want to have [18:08] like uh those images or or those titles [18:11] being you know different content for [18:13] depending on on the region. Yeah. [18:16] >> Yeah. Yeah. Exactly. GIO I would say is [18:18] the most obvious one that comes to mind [18:20] when when people start using this. We've [18:23] got we've had other um I would say more [18:26] custom use cases where you're hooking it [18:28] into the functionality of the site. So, [18:30] for example, we had a site build where [18:34] um they have like a newsletter signup [18:35] box and if you're already subscribed to [18:38] the newsletter, right, this is a site [18:40] where people are logging into the site [18:41] so you know whether they're subscribed [18:43] already. Then you we've registered that [18:46] as an attribute of an audience. So then [18:48] you can target the audience ultimately [18:50] and then use fullsight editing, right, [18:51] to say well uh if they haven't [18:53] subscribed, show them that widget. If [18:55] they have, then show them a different [18:57] widget instead. Um, so there's there's [19:00] those kind of sight specific use cases [19:02] of what is the functionality of your [19:04] site? Can you actually hook those things [19:06] in to start u making the site a bit more [19:09] dynamic? What you often would have done [19:11] right there would be in a traditional [19:13] theme, right? You're just embedding all [19:14] of those conditionals directly in your [19:16] PHP templates. [19:17] >> In the world of full-sight editing, [19:19] that's actually a little bit different [19:20] now because all of this stuff is shifted [19:22] to the admin layer. doing dynamic things [19:25] in the full in full-sight editing is [19:27] actually a lot more difficult because [19:28] you need the abstraction to be at the [19:31] editor and block level. You can't kind [19:33] of just drop in these quick like PHP [19:36] oneliner to switch out a different [19:37] template part or something like that. [19:39] So, so we're definitely um uh using it [19:42] in that like block conditional kind of [19:44] sense as well. [19:45] >> Yeah. Yeah. Where is this from a nerdy [19:47] perspective? Where is this data coming [19:48] from? Is it all coming from like the [19:50] HTTP headers that that the site is like [19:52] seeing reading coming in? [19:54] >> Yeah. So, uh virtually all of the [19:56] analytic stuff is all front end. So, [19:59] it's coming from the brow like uh I [20:01] guess what's it called? Uh [20:03] document.navigator or whatever the [20:05] JavaScript API is. So, it's not HTTP [20:07] headers. Um it's coming from uh the [20:10] navigator. And again, all of the uh data [20:13] and everything is all sent through a [20:15] JavaScript front-end tracking just like [20:18] many other, you know, web web tracking [20:20] type stuff. So, for one thing, you're [20:22] not going to get any data from like just [20:24] um let's say like HTTP crawling bots or [20:27] something like that. You will from like [20:29] sophisticated headless bots obviously [20:31] that are running a full browser. Um and [20:34] >> interesting. Yeah. [20:36] >> Also, all of the variants that are [20:38] shown. So, if you're doing AB testing or [20:40] personalization, it's worth saying again [20:43] like getting into the nerdy details [20:45] here. Um, all of those variants are sent [20:48] down to the browser and then it's [20:49] ultimately the JavaScript layer that [20:51] chooses which one to show based off of [20:53] what audience you might be a part of. [20:55] So, it means a single cache on your on [20:57] your CDN and page cache for example. So, [20:59] there's no need to have any custom [21:02] server configuration here. I think [21:03] Pantheon, right, you're running this [21:05] with page caching. Is that right? [21:06] >> Mhm. Yeah. Yeah. No, I was we were [21:08] talking earlier before we we hit record [21:10] and I I was looking under the hood [21:12] because I wanted to see uh like I saw [21:15] the image changing. I'm like, how's that [21:17] how's that done? And the way that that's [21:19] done is okay, we've got we've got the [21:21] image that is this one. Um and then the [21:24] other one is over here. Uh which is the [21:27] can't really see because it's super [21:28] small, but like um [21:31] it's now it's too big. Uh [21:34] um yeah. So you can see the other images [21:36] right there. So like basically both both [21:38] sets of content are being are being [21:40] downloaded. They're in the browser cache [21:42] and it's it's uh it's just you're hiding [21:45] and showing one specific one depending [21:46] on uh what the conditions are. Yeah. [21:49] >> Yeah. Yeah. Effectively there is some [21:51] nuances there like when the browser will [21:53] download those images and things. it it [21:55] it won't literally have to download [21:57] every image but but ultimately what the [21:59] browser is seeing is a custom HTML [22:01] element and when it comes to rendering [22:03] it the JavaScript is looking up what [22:05] audience am I a part of and therefore [22:07] which one should I pick um so it it [22:09] means that um yeah no no issues for like [22:12] server caching server load or anything [22:13] again all of the analytics of like when [22:15] you interact it's not sending the data [22:18] to the WordPress PHP side it's sending [22:21] the data to our analytics database um in [22:24] the cloud so to speak. [22:26] >> Yeah. And the other thing that's uh [22:28] relevant to our Pantheon audience, I'm [22:30] using this uh really old internal uh uh [22:34] page cache sort of like viewer that [22:36] tells me that it is actually in fact uh [22:38] cached and it says age is 915 seconds. [22:41] Um and that change I mean that stays the [22:43] same. It's like it's the same page cache [22:46] depending on uh the thing. So again, [22:48] like from a Pantheon perspective, like [22:50] this is still just coming from the edge [22:53] and it's already it's like cached. [22:55] You're not you're not going to have [22:57] like, oh, there's there's this one [22:59] variant and there's a cache uh tag for [23:01] that one and there's a separate variant [23:02] and there's a cache tag for that one [23:04] independently. It's just one one thing. [23:07] Yeah. Yeah. I would say there there's [23:08] one small exception to this which is for [23:11] anybody you know really astute might be [23:14] wondering how we do geoloccation because [23:15] that is not a thing that you get in the [23:17] browser. So we have our own separately [23:20] hosted endpoint that essentially will do [23:23] a geo geo IP lookup based off of the IP [23:26] address that is requesting. So when you [23:28] request our JavaScript library drop in [23:32] that's also going to inject as part of [23:35] that response here's the country that [23:36] you're coming from um as the viewer. Uh [23:39] so we do have a little bit of you know [23:41] clever goip stuff in the mix there but [23:43] again it's not running on the server of [23:46] the WordPress site or anything. Um, so [23:48] it's ultimately it's a scalable solution [23:51] from that point of view, right? Like if [23:52] if if you got a site with many millions [23:55] of visitors, um, then you're not going [23:57] to be bogging down your WordPress site [23:58] with that. Um, so that yeah, it's [24:01] definitely an important design goal for [24:02] us. [24:03] >> Yeah. Um, what else? What else do we [24:06] got? What else we have under the hood? [24:07] Like, uh, we talked about, uh, like [24:10] blocks specifically a little bit or you [24:13] mentioned them. [24:14] >> Yeah. Yeah. So that's like blocks is how [24:16] you're going to do your different [24:17] variations of things. Audiences is going [24:19] to be how you're going to target them. [24:21] If you you can drop into one of those [24:22] pages there, you can kick me out of that [24:24] demo page and personalization one [24:28] >> take over. [24:29] >> Um so so this is effectively just [24:31] showing the same thing that you would [24:32] have seen on the homepage, right? I have [24:34] a embedded uh synced pattern. Synced [24:37] patterns is actually how we do this [24:39] content personalization thing. So [24:41] there's three variants within that one. [24:43] But you can obviously just drop those in [24:44] anywhere you can show a synced pattern. [24:46] So, so that's really what we're showing [24:47] here. It'd be quite typical maybe you [24:50] have a marketing page um like a landing [24:52] page that's quite a fancy layout design [24:54] and you want to vary uh have variations [24:57] of some elements within that page for [24:59] example. Um so so that's how you can do [25:01] that. Um [25:05] yeah so the the block here all come [25:07] under under the um I think that's the [25:10] sync patterns that you're showing core [25:12] keeps changing where it shows sync [25:14] patterns but [25:16] um it's I called the sync pattern header [25:19] uh confusingly so uh it's also the name [25:22] of a template. [25:26] >> Yeah. Yeah. [25:27] >> There we go. Yeah. Yeah. So I also have [25:28] some other sync patterns in there as [25:30] well. [25:30] >> Yeah. [25:32] Um and then the last thing that I could [25:35] probably quickly show is the broadcast [25:37] um block on on how that is managed. [25:40] >> Uh that is a block. [25:42] >> Uh yeah, but sorry you'll need to jump [25:44] back to the main admin in this in the um [25:47] accelerate sidebar. [25:49] >> Okay. [25:50] >> Yeah. So there's this that's how we're [25:53] managing this content queue. So I have a [25:55] footer rearch broadcast here and then um [25:59] you can see the two that the two [26:01] different um pieces of content that I'm [26:04] recirculating through. So any synced [26:06] pattern can be inserted as a uh a [26:10] circulation piece of content. And then [26:12] if you went to the site edit into the [26:14] footer, that's where I'm putting in the [26:16] broadcast block. So there has to be like [26:17] two levels of abstraction here. I have [26:19] the broadcast block with all of the [26:21] different options in it and then I need [26:22] to put the broadcast block somewhere and [26:25] that is in if you go to template parts I [26:28] think it is in the site header [26:30] >> which is confusingly underpants. Yeah. [26:34] Uh footers. [26:35] >> Uh footer, I guess. Uh is it just the [26:38] main footer? Maybe. [26:42] I think if you click Oh, yeah. No, it's [26:44] >> No, I'm out. [26:46] >> Wait, is that it? [26:47] >> It's definitely I think you can. Yeah, I [26:49] think that's it. Yeah. Yes, you can see [26:51] that I have the broadcast block embedded [26:53] there. Um and that that's showing me. [26:56] >> I think that will bounce you through. [26:57] >> Yeah. [26:59] >> Um yeah, that that'll take you back to [27:01] the the screen that we were on. So, so [27:03] that's how broadcast works. Again, in [27:05] situations where um you kind of got a [27:09] content cue or internal ad network, you [27:11] can kind of think of it like that as [27:13] well. Um which is like, okay, if the [27:16] user didn't click it, you know, once, [27:18] let's show them something else the next [27:20] time they view the page kind of stuff. [27:22] >> Yeah. or like a you know an alternative [27:24] to the dreaded uh um scrolling like anim [27:29] you know slider uh in your [27:32] >> carousel. Yeah. [27:33] >> Yeah. Exactly. [27:34] >> Yeah. [27:35] >> Um so that that's pretty much uh what we [27:38] have. So that's really like I would say [27:40] there's um a few primitives there around [27:43] how we do synced patterns and the [27:45] analytics and then broadcast and then [27:47] being able to convert sync patterns into [27:49] either AB test or personalized. That's [27:51] really everything that there is. But [27:53] hopefully you can kind of see once you [27:56] combine that with the block editor and [27:58] full sight editing, you actually now [28:01] have quite a lot of uh different options [28:03] of how those things can be combined, how [28:05] those blocks can be combined to create a [28:07] site that is ultimately a bit more [28:10] dynamic or a lot more dynamic depending [28:12] how much work you put in um based off of [28:15] the different types of users that are [28:16] using the site. And that's ultimately [28:17] the design goal is is to be able to um [28:21] allow for that kind of dynamic nature of [28:24] the WordPress site. Um I will say that [28:27] you know to to go through the effort of [28:29] doing that you kind of do need a website [28:31] with a good amount of uh viewership [28:34] otherwise yeah you you are putting in a [28:36] lot of work. I you know on my personal [28:38] site that maybe like five people visit a [28:40] month right [28:41] >> it's not really worth me you know uh AB [28:44] testing my headlines. So, so there's [28:47] definitely kind of a certain scale where [28:49] this makes more sense, I think. You [28:51] know, [28:51] >> well, I'm going to take this a little [28:54] bit personal because Joe, I have a [28:56] problem that I discovered because of uh [29:01] >> Okay. [29:01] >> having the Accelerate plugin installed. [29:03] And the problem uh is uh make my window [29:08] a little bit bigger, too. That wasn't [29:10] what I wanted to do. um is that I [29:13] discovered that I have a great deal of [29:18] traffic that is coming from China that [29:21] is definitely not the normal traffic of [29:24] my site. [29:25] >> Yeah. Yeah. Except for China that's [29:27] about like what my website looks like [29:30] >> and like so my site is just a normal [29:32] blog. Uh it just has some stuff. It's [29:34] got like you know I I have do Devril [29:37] stuff so I have like all presentations [29:38] and stuff that I've given and things [29:40] like that. So like nothing nothing super [29:43] special but I I happened to to update [29:45] accelerate log into to the uh analytics [29:49] page and I saw this this big thing from [29:50] China. So uh I created an audience uh [29:55] for China and then everything except [29:57] China. [29:58] >> Okay. so that I can go into here and [30:01] look at my analytics and basically see [30:04] >> this is what I would expect. This is the [30:07] traffic that seems normal. [30:10] >> Yeah. [30:11] >> Um but now that I have this audience for [30:13] China, um what sorts of things could I [30:18] do uh either through the plug-in itself [30:21] or even maybe with code that would like [30:25] with with like this China audience that [30:27] I have? So, these people that are coming [30:28] from China that I assume are probably [30:30] robots because my site isn't written in [30:32] Chinese. Like, you know, I could [30:34] probably use uh put a header that is [30:37] only visible to China and like say maybe [30:41] even in Chinese uh hey robot like you [30:45] know like have a special message for [30:47] them like what what sorts of things uh [30:49] could I do uh now that I I've identified [30:51] that sort of thing. [30:53] >> Yeah. Yeah. So you could uh if you [30:55] wanted to, it depends if this is a [30:57] problem that you feel like you want to [30:59] combat or something where you know maybe [31:01] there are some maybe you do have a [31:03] genuine audience from China that you [31:05] never knew about. U you you never know. [31:08] So it could prompt you to do some actual [31:10] personalization for China. Do something [31:12] like, hey, if you're Chinese, let me [31:14] know here if you want to understand my [31:16] site or something. Um so yeah, you you [31:18] can definitely segment that way. Um, [31:21] like you said, you I mean you could [31:23] maybe if there were things on your [31:25] website, I don't know if you had [31:27] sensitive things on there or just I [31:29] don't know for for for whatever reason, [31:31] right? Content that you wanted to [31:33] restrict, you could you could use [31:35] accelerate for something like that. It's [31:37] obviously not like the most secure way [31:38] of achieving that because it is [31:40] ultimately all a kind of front-end tool. [31:42] Um but but I think yeah the most obvious [31:45] thing to me would be to have a big [31:46] banner to say like please stop scraping [31:48] my site or something. [31:51] >> Is there like [31:54] is there a code level uh like hook or [31:57] something that I could do that would uh [31:58] basically allow me to like for those [32:01] China visitors give them like a redirect [32:03] to some other page or a different like [32:06] google.com or something like that. [32:07] >> Yeah. Yeah. So we have uh we have [32:10] documentation on how to like hook into [32:12] our um uh it it would be a front-end [32:15] JavaScript based hook, right? Because [32:17] again everything is essentially running [32:18] on the client here. Um so there you [32:21] would basically hook into um we have a [32:24] little thing that fires every page load. [32:26] This is the data for the user and then [32:27] you can check their country and then [32:29] change their you know document.loation [32:31] or whatever and and do it at the code [32:33] level. So on um accelerateplugin.com we [32:37] have uh documentation linked I believe [32:40] in in the header there um and that is uh [32:44] may maybe it's actually in the footer [32:46] maybe we relegated the importance of the [32:48] documentation [32:51] >> documentation [32:52] >> uh there we go yeah so that's that's [32:53] something where we are kind of um as as [32:57] more use cases and questions emerge like [32:59] integration with the consent API for [33:01] example um anal yeah analytics [33:04] integration things like that we're kind [33:06] of adding those as additional um [33:11] additional kind of guides. So so the [33:12] more that we hear from people on how [33:14] they're looking to use this or questions [33:15] that they have then we're trying to kind [33:17] of bake that into our docs and uh you [33:19] know have have it be useful for more [33:20] people ultimately. [33:22] >> Awesome. Yeah. Um [33:25] >> first time I've seen that that specific [33:27] you know problem though of having like [33:29] all of this I don't know. Well, [33:32] >> that that you didn't want. [33:33] >> Yeah, I'm as I'm looking at it, there [33:35] seems to be a lot of hits to WP Signup [33:37] for some bizarre reason. So, [33:39] >> okay. Which presumably doesn't even [33:40] exist on your site because it's not [33:42] multicight. I know. [33:43] >> Oh, it is multiight. It is multicight. [33:45] >> Okay. [33:47] >> Uh well, thanks a lot. I mean, I think [33:50] that's really awesome. Um I'm super [33:52] impressed. Like, uh I've obviously [33:54] watched uh this plugin develop for for [33:57] quite a while. Uh for for those of you [34:00] at home, uh I you know, [34:03] >> Joe used to be my boss. I used to work [34:04] at Human Maid. So, uh I you've seen [34:08] >> I've seen this evolve over time and I've [34:11] seen a couple different uh incarnations [34:12] of it. Um, so, uh, I I definitely [34:16] noticed, uh, when it when it, uh, [34:19] changed and I really do like I really [34:22] like the idea of, you know, the the base [34:24] level like the analytics like just by [34:27] itself. I mean, [34:29] >> there's a lot of analytics plugins out [34:31] there. Um, [34:32] >> and like you can and some of them are [34:36] Google and some of them hook into Google [34:37] and some of them like you know there's [34:39] you know Jetack has its analytics thing [34:40] and whatever and they all kind of [34:42] approach it in a slightly different way. [34:43] Um, but I really like, you know, like [34:46] this. This actually gave me valuable [34:48] information in with like a couple clicks [34:51] that I don't know that I would have [34:52] gotten. I I mean, I could have gotten [34:54] that stuff from Google and I could have [34:55] gotten that stuff probably from Jetack, [34:57] but like I could do that in like five [34:59] minutes, whereas I don't like I'd have [35:02] to refer to documentation to do it in [35:03] Google. [35:04] >> Yeah. Yeah. that that's kind of the [35:06] thesis of the whole tool to be honest is [35:09] like anybody that's watching this that [35:10] is like a marketer or performance [35:13] marketer or something is not going to be [35:14] wowed by like oh wow I didn't realize I [35:16] could run an AB test or something right [35:18] those tools have existed and like [35:20] frankly the suites for those tools are [35:23] really powerful and you can do way more [35:24] than you can do in accelerate but the [35:26] problem is it's like it's not close by [35:28] it's not something that is just like [35:30] plugandplay click install ready to go I [35:33] don't need to uh set set up a complex [35:35] integration. I don't need to log into [35:37] several tools. Really, the idea of uh [35:40] accelerate is more like a uh dare I say, [35:43] you know, use the WordPress buzzword, a [35:45] kind of democratization play in that [35:47] like you need to spend quite a lot of [35:49] money to set up something like uh uh [35:52] optimizely or you know a full kind of uh [35:56] enterprise suite like that. Um and then [35:58] what you also get at the end of the day [36:00] is still a very cumbersome process. [36:02] Whereas really what we're trying to do [36:04] with Accelerate is just have it be [36:06] install it. If you're in the block [36:08] editor, you're going to be ready to go. [36:09] If you're using full-sight editing, it's [36:11] even better because obviously you just [36:12] get all the same primitives at the [36:14] fullsite editing level and you never [36:16] have to go to another tool and you know, [36:18] you don't need to write your variations [36:21] for your headline in a different tool, [36:23] right? Those things should be in the [36:24] CMS. That's where you're writing. That's [36:26] where you're building your pages. Um [36:29] whereas I've seen literally demos from [36:31] other tools where yes you have your your [36:33] main version of the page there but then [36:35] you've got five versions of the page in [36:37] a separate tool where you don't have any [36:38] of the WordPress functionality. [36:40] >> Um so I think that it's it's just about [36:42] bringing the things together and like [36:44] you say analytics is just that it's just [36:46] like well it's right there on the [36:48] dashboard when you're viewing your uh [36:52] synced pattern that you're making. [36:53] You're seeing the views there over time. [36:55] you're understanding is this an [36:57] important piece of content because I [36:59] have the data right there in front of [37:00] me. I'm not flicking and not building [37:02] reports in Google Analytics or [37:03] something. So, while those tools are way [37:06] more powerful than what we have, [37:07] hopefully the kind of at the fingertips [37:10] useful when you actually need it nature [37:12] that we're trying to accelerate kind of [37:14] like actually balances out to be a net [37:16] plus and on top of that it's like it's [37:19] free up to like a million views a month [37:21] as well and things. So, like it's free [37:22] is always good. [37:24] >> Yeah. Yeah. And obviously this this tool [37:27] has come out of your sort of [37:30] professional services experience in the [37:32] field working as an agency with uh [37:35] companies and organizations who need [37:38] stuff like this. Are there any sort of [37:40] like success stories or interesting [37:43] things that you can share about like [37:45] sort of what what like that that this or [37:49] tools like this have enabled or unlocked [37:52] or things like that for for people that [37:54] you're working with. [37:55] >> Yeah. Sure. Yeah. So it's it's there [37:58] there's definitely the the the type of [38:01] situation we like to use it is an agency [38:03] and then there is kind of like probably [38:06] the 80% of your more standard let's say [38:09] setup. So so we definitely see on the [38:11] agency side we're working on stuff where [38:12] it's going to be more custom like I kind [38:14] of mentioned on uh PlayStation using it. [38:17] Um another site that is using it is [38:19] recipe tinets that has uh a lot a lot of [38:22] traffic. let's just say I think they're [38:23] within uh maybe the top 10 recipe sites [38:26] in the world or something. Um so so uh [38:30] we [38:31] had to engineer this to work at that [38:33] kind of scale. So I I think that's kind [38:36] of um hopefully a balance that we've [38:38] been able to strike is it works on very [38:41] big stuff but we've tried to make it [38:43] simple enough to use for anybody and [38:46] that is that is why it's valuable as [38:48] well at the enterprise level is like [38:50] enterprise technology is not always the [38:53] most usable and that's ultimately why [38:55] WordPress is is relatively successful in [38:57] enterprise is like it's the easy tool [39:00] that people kind of know how to use and [39:03] um if they don't get too bogged down [39:05] with kind of like millions of checklists [39:06] of what the software needs to do. [39:08] WordPress is a good option. And that's [39:09] just the same balance that we we have [39:11] kind of with uh Accelerate is like we're [39:14] not trying to be better than an [39:15] enterprise um uh performance marketing [39:18] tool. But um where it actually kind of [39:22] gets used is in the situations where uh [39:25] it's going to be like we're going to [39:27] migrate to um the Adobe suite for [39:30] analytics in one year. So then we're [39:32] going to do personalization, right? [39:34] Typical client thing is to do a site [39:36] build and then they've got some um uh [39:40] plan down the road to introduce these [39:42] things that Accelerate has. So it's just [39:45] kind of like well let's just use [39:46] Accelerate now then and then obviously [39:48] that thing down the road never even [39:49] happens because it never kind of does in [39:52] in uh enterprise tech anyway. It's it's [39:55] always a thing on the future road map, [39:57] right? So that's where we've seen [39:58] success with it is um we're not trying [40:02] to convince an organization that this is [40:04] needs to be their you know uh [40:06] personalization platform for their whole [40:08] team and everything cuz it's it's not [40:10] that. What it is is a tool that works [40:12] right now that allows your web team to [40:14] actually get stuff done right now and [40:16] not have to wait for that kind of like [40:18] future um big big platform. And um in in [40:22] our experience it's it's kind of filled [40:23] that gap pretty well. [40:25] >> Yeah. Yeah. I really like the example of [40:28] of a recipe site because I can I can [40:30] already think of like five different [40:31] things that Accelerate would be useful [40:33] for in that context from AB testing [40:36] headlines to like maybe different images [40:38] to all sorts of things. Um we do have a [40:40] a question coming in from LinkedIn. Is [40:42] is Accelerate only for WordPress sites? [40:44] I think the answer to that is yes. Human [40:45] Made is a WordPress agency. Um are there [40:48] any thoughts about like or or are there [40:50] things that could be uh extracted or [40:53] maybe shared from like a service [40:55] perspective? uh that accelerate into. [40:59] >> Yeah. So there's there's kind of two [41:00] sides to that. One is we have seen [41:03] situations where you have accelerate on [41:05] your uh main WordPress site and maybe [41:08] there's a couple of like micro sites or [41:11] pages that are just hosted on something [41:13] else and it would be valuable to unify [41:15] the data of those things. So um like [41:18] just drop our JavaScript embed [41:20] essentially on one of those other sites [41:22] and make sure that the data is is is [41:24] centralized between those. So that that [41:26] is possible but ultimately because our [41:29] whole well I actually want to write [41:30] personalized content now that's all got [41:32] to be in WordPress. Uh so like if if [41:34] you're not on a WordPress site at all no [41:36] don't don't don't uh go for Accelerate. [41:39] Again, that's kind of like that is the [41:41] point really is like this is a WordPress [41:43] solution and though general purpose [41:46] solutions are very powerful and [41:48] everything, the integration point is [41:50] just in my experience really painful. [41:52] Um, so we've ultimately just accepted [41:55] the tradeoff there. It's like we're go [41:57] for the WordPress people who have got [41:58] WordPress sites that don't really want [42:00] to leave WordPress. How can we make [42:02] something good enough for them? [42:04] >> Uh, and I've got one other question that [42:06] came in from LinkedIn as well. Um any [42:08] plans to integrate with CDP platforms? [42:12] >> Uh yeah so CDP CDP platform customer [42:15] data platform which is generally uh your [42:18] big business and you use terms like data [42:21] lake and data warehouses and like all of [42:24] your customer data just goes into this [42:27] you know kind of black box. Um how could [42:29] you integrate with something like that [42:31] for the website? That's kind of I think [42:33] what what the question is is getting at [42:35] here. Um so yeah we we definitely do [42:38] have there are ways that you can already [42:40] do that at a code level right I'm kind [42:41] of mentioned we have like developer APIs [42:44] that would look something like you know [42:46] when the um browser is gathering the [42:49] information that it has on the current [42:51] user right it knows the time of day [42:53] based off of you know the date in the [42:55] browser right you could ultimately pull [42:58] information from a CDP and feed that [43:00] into the same pipeline so then I can go [43:02] and create personalized content based [43:03] off of attributes on the user maybe in [43:05] my CDP, you know, that that's the [43:08] general flow. Um, so we don't have any [43:10] like plugandplay adapters right now for [43:13] specific CDPs, but but the um the the [43:17] lower level is there and we're still [43:20] looking to ultimately work on a kind of [43:22] case by case of like uh let's let's do a [43:26] specific integration when one arises [43:28] that there's something tangible to do [43:30] with because quite quite what happen [43:32] often happens with customer data is um [43:36] it's very like high level, move the [43:39] data, put the data there, connect the [43:40] data. Yeah, great. Sharing my data or [43:43] whatever. But like what is the actual [43:45] user journey and what specific data [43:47] would you use and when could you use it? [43:49] Because if I just open my iPhone now and [43:51] go to your website for the first time [43:53] ever, though I might be in your CDP, it [43:56] doesn't mean that there is a way to [43:57] meaningfully link me right now. So [44:00] there's all kinds of practical [44:01] challenges to do with you know good [44:03] things around data privacy and third [44:05] party cookies and why it's difficult to [44:07] do all those things. So so um there [44:09] definitely can be a tendency to look a [44:11] little too high level in terms of [44:12] connecting data and targeting users and [44:15] things like that. Right? If I go watch [44:16] something on Netflix and then I go on on [44:18] my phone on Netflix when I've never [44:19] visited before I'm not logged in. Well, [44:21] I'm not getting any personalization. [44:22] Right? There are a lot of limitations [44:24] around what you can do uh with with [44:26] customer data. So I would say the devil [44:29] is in the details when it comes to any [44:31] kind of CDP or CRM integration is you [44:35] kind of do need to be able to drop a [44:36] step lower. We usually have to talk to [44:38] clients you know okay what are you [44:39] specifically looking to do where is that [44:42] data how do you identify users to [44:44] understand how that could be achieved [44:46] because you know yeah there's there's [44:48] one thing kind of having the idea [44:50] there's another thing being out of [44:51] building into the product you know [44:53] >> right yeah for sure yeah and focusing on [44:55] the outcome that you're actually going [44:56] for particularly with uh personalization [44:59] is probably you know the most important [45:02] thing because personalization is hard [45:04] enough as it is I mean that's the thing [45:06] that I know that you all have been [45:08] looking at for a long time. Pantheon's [45:09] been looking at it for a long time. And [45:11] the problem with personalization is is [45:12] like what you said, like there's a lot [45:14] of work involved. So like if you don't [45:16] want to spend a ton of work on on on [45:18] something uh without knowing that it's [45:20] actually valuable work, [45:22] >> right? Right. Right. Exactly. It's it's [45:24] kind of a tricky one because uh it can [45:27] be that like you know the marketer's [45:29] dream is just to know everything about [45:30] everybody, right? And then like uh you [45:33] know sell as much stuff to them, right? [45:34] And then the kind of like uh users uh [45:37] dream is often just like I want to stay [45:39] anonymous and don't don't want to have [45:41] uh kind of anything specific uhly [45:44] targeted to towards me. So, you know, uh [45:46] we we're definitely um trying to play as [45:50] much as we can on the on the privacy [45:52] side of this, right? like we're not um [45:55] uh doing anything uh untoward of trying [45:58] to like circumvent the the the the user [46:02] in in terms of the the the data that [46:04] that uh might be held on them that that [46:06] kind of thing. Um but yeah, I I think uh [46:11] there's there is always a bit of a [46:12] tension there ultimately between uh more [46:15] data is better ultimately from um a uh a [46:21] marketer's point of view and less data [46:23] is is is better from the user. You have [46:24] you definitely have to strike the [46:26] balance. Um and there are certainly uh [46:29] yeah like ways that you can overstep [46:32] that line and definitely have to be [46:33] careful. Um it's definitely something [46:35] that is important to us like I mentioned [46:36] on the documentation right integration [46:38] we've had with the WP consent API from [46:40] day one because that is just a key thing [46:42] I mean not only for like regulation and [46:44] stuff in Europe but ultimately um we we [46:47] want to be playing nice and respecting [46:49] the privacy tools that are in place and [46:51] you know choices of users. [46:53] >> Yeah. Yep. Well and and anyone who's [46:56] watching this you can go find uh the [46:58] accelerate plugin either on [46:59] accelerateplugin.com which we talked [47:01] about earlier or just in the [47:02] WordPress.org or repository. Uh, where [47:05] can folks find you if they want to find [47:07] you, Joe Hoy, specifically? [47:10] >> Yeah. Yeah, you can go to my website [47:12] with Accelerate on with about five [47:14] people visiting a day, which is [47:15] jo.co.uk, though that's kind of changed [47:18] into a website about woodworking. Um, [47:21] and but I'm on I'm on uh I'm I I'm sorry [47:24] to say I am still on Twitter um as [47:27] Joe_HoY. That probably is the best way [47:30] to to contact me. [47:32] >> Well, awesome. I'm definitely going to [47:33] go uh play around some more with [47:36] Accelerate on my personal website. Uh I [47:38] hope all of you watching either live or [47:41] in the future uh check it out on on your [47:44] website. Uh thanks Joe for coming on to [47:46] the live stream and for everyone else uh [47:48] thank you for joining and we'll see you [47:50] on the internet. [47:51] >> All right. Thanks very much much for [47:53] having us Chris. [47:54] >> Yeah, no worries.  ## 📺 Video ![](https://www.youtube.com/watch?v=F7N1GAf0dVw) --- # 📄 Full Transcript *Auto-generated from YouTube captions · timestamps roughly every 30 seconds · [watch on YouTube](https://www.youtube.com/watch?v=F7N1GAf0dVw)* **[00:00]** [music] Hello internet. I am Chris Reynolds, senior developer advocate at Pantheon. [music] Today on the stream, we're going to be **[00:30]** talking about personalization inside WordPress. And to do that, I've got Joe Hoy on the stream today uh to talk about what Human Made's been working on for a while. Uh a plugin called Accelerate. Uh welcome to the stream, Joe. Joe is the chief technology officer of Human Made, I guess I should say. Uh and yeah, tell tell us about yourself and what you've been working on. >> Thanks, Chris. uh excited to be on um tout our our latest wear um which is our accelerate plug-in. Um but I guess more **[01:03]** generally uh I guess I've been working with WordPress for 15 16 17 years something like that. Uh obviously human's whole existence which is about I don't know must be claimed close to 15 years. >> Yeah. Um so done a lot with WordPress and this is our latest I guess uh yeah for into building a plug-in. >> Yeah. And I mean Accelerate has been baking in the oven for a while. Uh talk about sort of the journey of like what **[01:35]** you were looking for uh what you were trying to build and and what what I guess because it's gone through a couple different iterations too, right? Uh so like where how did it get to be the thing that it is today and how has it changed uh over time? Yeah, sure. So, um, yes, it grew out of what we had been doing several years ago with a thing called Altus DXP. There was like a digital experience platform which essentially took WordPress and added a bunch of uh what is kind of in the industry term DX features around like **[02:06]** personalization, AB testing and things. Um ultimately that um didn't exactly pan out as a unified platform, but we took a lot of the ideas there of these kind of extra uh functions that we built on top of WordPress and some of that span out into what is now the Accelerate plugin um which is just a a standalone plugin that anybody can use. um the Altus DXP platform, you know, went more in the direction of just being uh kind of, you know, solid WordPress enterprise host **[02:37]** and then some other bits and pieces also span out of that. So ultimately it's from our kind of learnings of uh from technically what we were able to do in the Altus DXP platform, but also we've really tried to simplify as much as possible. So hopefully we'll get stuck into it obviously today but really uh hopefully it comes across of what we've built is like very simple but those building blocks allow uh a large amount of like possibility and creativity in what you're able to do with the tool. **[03:08]** >> Yeah. Awesome. Well, I will bring up my screen over here uh because I've got a site that uh has the Accelerate plugin installed. Um, and I'm just gonna kind of let you uh walk me through. Tell me what I'm looking at. [laughter] >> That's a a great start. So, I guess uh on the right side obviously we have the the website using the Accelerate plugin which will probably look like a normal WordPress site. Uh on the left you have the the admin dashboard. Um so I guess **[03:40]** you know I'm I'm tempted to take this from the front end first of like what does it mean that you can do with your site? what does it look like as as a user? So, right now you're landed on this site. You have a header um you know for uh for for the site and then if you scroll down um you have like a latest post block there with the latest post and then you have like a kind of recirculated internal ad kind of in the footer. Um so as as you as the user viewing this then um that is how the site appears. However, um if you go to **[04:12]** the top where it says audience preview there and then you switch uh on one of those. So if you put evening um so it changes the page. So um that's probably where you will get a rough idea of what Accelerate allows you to do is ultimately personalize and test content on your site depending on either who who is viewing it or on like an AB test a kind of randomized assortment. Um, so right now, for example, I've preset up some content on this site for the header, which has three different **[04:42]** versions of a header. Um, one is based off of a time of day. So that's the evening. Um, or if you switch to being France, so a geoloccation based one, then we have different header for that. And then the the default one that you're seeing is is what we term the fallback. So if you're not part of any audience that I've kind of chosen what to see, then then that's what you're going to get. Um so that's kind of um what we term content personalization. So that is ultimately um you want to do multiple **[05:12]** variants of either you know literally content on pages or sitewide elements via full-sight editing and um ultimately do different content for different audiences. Uh could be audiences based off of location. It could be uh audiences based off of um like a marketing campaign. Maybe they clicked in through an email. So now they're considered a certain type of user. You want to change their experience of the site. Uh so so that is content personalization broadly. And we the **[05:43]** example here is the header, but obviously that could be kind of any any element of your site. Um if you scroll down a little bit, there's a couple of other um areas here. So what you're seeing in the bottom here of this kind of like internal ad, right? we've got like free skiing or whatever. Um that is a recirculation module but if you reload the page then there is actually like a content cue of different content that is coming in through that slot. Um, so where something like personalization or AB testing is about testing the just the **[06:16]** specific content and you know you're probably always going to get that variant at least for that session because you know you're you're not moving uh countries whilst you're reloading the pages or anything. uh the broadcast block which is the way that you can uh rotate in different content in in a given area and again it will will be measuring um the conversion rates of that content for that specific location that you've put it in. Um so that's another thing that uh ultimately is I guess ultimately bringing the **[06:48]** WordPress site to life more right making it more dynamic allowing you to do different variations of different things. because I just got a two pieces of content in that queue. Another thing that you will see, well, you won't see this, you'd actually have to open up the site in an incognito window. Um, but we also have a um AB test that is running on this page as well. So, I think hopefully if you go to the website here, you just scroll down. Okay, you if close your window and try it again because you're you're randomly now getting **[07:20]** assigned to different audiences. >> [laughter] >> We've we've we've got a uh 50/50 chance of of uh of the site that you're actually going to see uh sorry of the specific content. >> Oh, here we go. >> Um yeah, so e either on the homepage block here where it's pushing you through to that other post or if you scroll down to where the latest post block is is there there as well. So this is something that isn't it's not exactly content personalization, right? I haven't had to do two versions of that latest post block. Um, we also have a **[07:51]** system to be able to do headline and featured image and other testing at the kind of more meta level. So that's actually a test running on that post, right? It's not a test of my homepage. That is a test of me trying different headlines and images. And then wherever that post may be shown across the site in things like latest post blocks or whatever else, uh, then I'm going to see um, uh, randomly um, one one of those. And again, I've been assigned to a specific audience here. So, so whenever **[08:21]** you reload the page, you're going to get the same one when you just clicked through it there from the homepage that is going to be attributed to that version of the AB test. So, obviously we're measuring the performance, right, based off of the clickthroughs to the posts. Well, which headline did you come through on? And then we'll surface that. And then when the ten test is actually finished over a configurated amount of days, it'll automatically pick whatever the the highest performing uh one was. So that's a very quick just kind of like run through a few of the things that I set up on the demo site here just to be **[08:53]** hopefully give you an idea of the kind of things that accelerate is trying to do. It's ultimately around being able to iterate on your content, your designs, and be able to measure the impact and performance of those iterations and then kind of keep doing that. So, um that's that's how it looks for a user on the front end, which is uh as an individual user, you're probably actually not seeing that much of that stuff because you know you're you're not seeing all the people and what they're getting apart from the recirculator module at the bottom. Um if you jump over to the **[09:24]** admin I can just show a couple of things therefore that we have on the analytics to understand um how how your site is used. So one thing that you'll notice when you come onto the accelerate main dashboard in the admin straight away is we have like a traditional analytics layer. So you get some top level view metrics of your site. You can see data coming in things like that. We also have this thing that we call a content explorer which is essentially just a different um way to get at your your uh **[09:55]** existing content just as you would go through p post pages synced patterns things like that. It's just kind of a unified view that is going to give you analytics uh alongside that. If you jump into something like um the uh header for example in this um yeah in the center there I'll show you exactly kind of what it looks like to be editing this from a uh content authoring point of view. >> Nice. >> Um so hopefully it's fairly kind of obvious what's happening here. Um I have **[10:26]** three variants right now. I can click between them to edit different different ones of those. Um, and within that editor, um, below that is just your, you know, your usual block editor there. Um, so I can change anything that I would want. And at a per block level there, I see the amount of views it has, the overall conversion rate, the conversion rate for each version. So, it's it's very kind of important that not only do we show different variants depending on what audience might be looking at the **[10:56]** website. Ultimately, if you don't have a way to measure it, there's not really any point in doing that because you're never really going to know how effective is it that I show a different message to uh somebody in a different country or if I, you know, have have a different uh uh call to action for somebody coming from a marketing campaign. you need to be able to track the conversion rate to understand whether that was a good thing to personalize or or not. So, we have a um fairly robust um off-site analytics layer that isn't, you know, stored in **[11:27]** the WordPress database or or something like that where we push a lot of user interaction behavior to be able to give editors and site authors like the the information that they need to to edit. Um, so that's what the experience looks like. Whether that's an AB test or a personalized test for at the block level. Um, you can kind of see hopefully it's a fairly intuitive experience based off already being able to use the block editor. >> And then I can see you've got different conversion goals. So you can be tracking **[11:58]** different things depending on uh what you >> Exactly. Yeah. Yeah. So so typically, you know, I think the default Yes. would be any like clicking of a link or submitting anything any kind of um event that can happen within the block by default that would be considered a conversion but yeah you can scope it down there. >> Um so so that's what it looks like to to create personalized content. U maybe you can yeah jump back to the main dashboard and we could have a quick look at the uh analytics um page in the back end. **[12:29]** >> Um so we're not a you know we're not Google Analytics. We're not like a full deep analytics suite, but ultimately um we do have really good analytics data because we have to track so many things at the block level as well and at the page level that um we think that we provide a really good out of the box just like how do I get analytics on my site for free? Just install this plug-in and it's done kind of thing. we already need all of this data for the personalization stuff. Um with things like you know uh Google Analytics and uh **[13:02]** cookie law and cookie optin on Google and things like that. It's definitely um providing a kind of anonymized analytics solution out of the box I think is like a good win and certainly a immediate benefit that people can get from using the accelerate plug-in. Whereas like personalization AB testing you do need to go and do things right. >> Yeah. You got to do the stuff. got to write the content. Um whereas uh analytics we're just obviously collecting from day one. So it's it's fairly typical of what you would expect. Um but it does give you an idea what is **[13:34]** my breakdown by you know countries, by browsers, pages, things like that. So you can start to think about how can I create audiences because ultimately and accelerate what audiences are is ultimately a facet of your analytics data. Um, so though we don't show everything here that's in the analytics database yet, something like if you come in through a UTM link to the website, that is stored in our analytics data and therefore that's how you create a audience based off of that value. So **[14:04]** that's kind of how the data pipeline works. >> Um, yeah, tell me about audiences. Um, obviously we have to have some audiences if we're going to have uh different views for different uh different things. So let's let's pop in there. I'm interested in in this because uh well I don't see anything. [laughter] >> Yeah. Yeah. This is just I think it takes takes a couple of seconds to load in. So the the general idea with with audiences again is like create criteria **[14:34]** of the um kind of demographic type data that might come in via analytics. So by default uh most of it is going to be based off of things that are determined on the front end from the browser. Um you can uh certainly uh like hook into this at a developer level to add other things maybe like you would hook in and add some like I don't know has purchased this product via WooCommerce or something right like you you could do those kind of things. >> Um or you can have like yeah the logged in attribute here is like a WordPress **[15:05]** you know specific if if you're logged into X Y or Z. So we have um generally a bunch of different things that you can facet by and you can do groups of those you can do andors you can do you know yada yada all of that boolean logic to build up your audience of like uh how how you might want so here yeah then I'm saying if the hour is more than 16 consider part of the evening audience and that's going to be local time for the user uh so that's quite a a basic one that's that's simple to do but as **[15:35]** well as that you could do you know if the referer includes github.com, consider them a developer. And then maybe, you know, right when I'm writing my like um uh my call to actions or something, I might vary those based off of which audience is is viewing the site. >> And then I guess for for country, it's actually telling me this is the percentage of of pe visitors that I'm getting from that country. So in this case, it says France, 25% because 25% of my audience is coming from France. So, **[16:07]** >> exactly. >> In that way, I can really be targeted for like, oh, I've got a lot of German uh audience or I've got a lot of uh French people coming to my website. I'm going to have this this content or this page or this header or whatever, this advertisement that is specific to that group of people. >> Exactly. Yeah. Because there's ultimately not much point putting in a load of effort maybe targeting Canada here that's at 3%. Sure. >> So, uh, a lot of the personalization is kind of like what is the what is the **[16:38]** returns on all of the work that you might need to do to create variations on your content? Um, and and how much impact is is that likely to have. So, there are um that's that's come at it from purely I would say like a performance marketing point of view. There are other are other use cases where uh you may want to have uh more functional things like if they're logged in show them this otherwise show them this. Okay, that's not that that's probably you're actually just trying to like use the boolean logic of of the **[17:10]** plug-in which it can definitely be used that way. Um I know that it is used on uh blog.playstation.com PlayStation.com for example for the different rating images on whether you're in Europe or whether you're in the US etc. So again not really somewhere where they're looking to like maximize conversion rates on those clickthroughs of like Peggy ratings or whatever but ultimately it can be just a tool in the tool belt of how can I uh you know ultimately solve the functional problem **[17:40]** of like different audiences means different functionality on the site as well. Yeah, I mean I was actually going to ask about uh what sort of practical uses have you seen of of this sort of stuff in the field and PlayStation's a really good example because not only you know the the rating system is different but like a lot of times like uh the the covers for a game in the US is going to be different or even the games that are available in the US are going to be different than the games that are available in Japan for example uh things like that. And so you might want to have like uh those images or or those titles **[18:11]** being you know different content for depending on on the region. Yeah. >> Yeah. Yeah. Exactly. GIO I would say is the most obvious one that comes to mind when when people start using this. We've got we've had other um I would say more custom use cases where you're hooking it into the functionality of the site. So, for example, we had a site build where um they have like a newsletter signup box and if you're already subscribed to the newsletter, right, this is a site where people are logging into the site **[18:41]** so you know whether they're subscribed already. Then you we've registered that as an attribute of an audience. So then you can target the audience ultimately and then use fullsight editing, right, to say well uh if they haven't subscribed, show them that widget. If they have, then show them a different widget instead. Um, so there's there's those kind of sight specific use cases of what is the functionality of your site? Can you actually hook those things in to start u making the site a bit more dynamic? What you often would have done right there would be in a traditional **[19:13]** theme, right? You're just embedding all of those conditionals directly in your PHP templates. >> In the world of full-sight editing, that's actually a little bit different now because all of this stuff is shifted to the admin layer. doing dynamic things in the full in full-sight editing is actually a lot more difficult because you need the abstraction to be at the editor and block level. You can't kind of just drop in these quick like PHP oneliner to switch out a different template part or something like that. So, so we're definitely um uh using it in that like block conditional kind of **[19:44]** sense as well. >> Yeah. Yeah. Where is this from a nerdy perspective? Where is this data coming from? Is it all coming from like the HTTP headers that that the site is like seeing reading coming in? >> Yeah. So, uh virtually all of the analytic stuff is all front end. So, it's coming from the brow like uh I guess what's it called? Uh document.navigator or whatever the JavaScript API is. So, it's not HTTP headers. Um it's coming from uh the navigator. And again, all of the uh data and everything is all sent through a **[20:15]** JavaScript front-end tracking just like many other, you know, web web tracking type stuff. So, for one thing, you're not going to get any data from like just um let's say like HTTP crawling bots or something like that. You will from like sophisticated headless bots obviously that are running a full browser. Um and >> interesting. Yeah. >> Also, all of the variants that are shown. So, if you're doing AB testing or personalization, it's worth saying again like getting into the nerdy details here. Um, all of those variants are sent **[20:48]** down to the browser and then it's ultimately the JavaScript layer that chooses which one to show based off of what audience you might be a part of. So, it means a single cache on your on your CDN and page cache for example. So, there's no need to have any custom server configuration here. I think Pantheon, right, you're running this with page caching. Is that right? >> Mhm. Yeah. Yeah. No, I was we were talking earlier before we we hit record and I I was looking under the hood because I wanted to see uh like I saw the image changing. I'm like, how's that how's that done? And the way that that's **[21:19]** done is okay, we've got we've got the image that is this one. Um and then the other one is over here. Uh which is the can't really see because it's super small, but like um it's now it's too big. Uh um yeah. So you can see the other images right there. So like basically both both sets of content are being are being downloaded. They're in the browser cache and it's it's uh it's just you're hiding and showing one specific one depending on uh what the conditions are. Yeah. **[21:49]** >> Yeah. Yeah. Effectively there is some nuances there like when the browser will download those images and things. it it it won't literally have to download every image but but ultimately what the browser is seeing is a custom HTML element and when it comes to rendering it the JavaScript is looking up what audience am I a part of and therefore which one should I pick um so it it means that um yeah no no issues for like server caching server load or anything again all of the analytics of like when you interact it's not sending the data to the WordPress PHP side it's sending **[22:21]** the data to our analytics database um in the cloud so to speak. >> Yeah. And the other thing that's uh relevant to our Pantheon audience, I'm using this uh really old internal uh uh page cache sort of like viewer that tells me that it is actually in fact uh cached and it says age is 915 seconds. Um and that change I mean that stays the same. It's like it's the same page cache depending on uh the thing. So again, like from a Pantheon perspective, like this is still just coming from the edge **[22:53]** and it's already it's like cached. You're not you're not going to have like, oh, there's there's this one variant and there's a cache uh tag for that one and there's a separate variant and there's a cache tag for that one independently. It's just one one thing. Yeah. Yeah. I would say there there's one small exception to this which is for anybody you know really astute might be wondering how we do geoloccation because that is not a thing that you get in the browser. So we have our own separately hosted endpoint that essentially will do a geo geo IP lookup based off of the IP **[23:26]** address that is requesting. So when you request our JavaScript library drop in that's also going to inject as part of that response here's the country that you're coming from um as the viewer. Uh so we do have a little bit of you know clever goip stuff in the mix there but again it's not running on the server of the WordPress site or anything. Um, so it's ultimately it's a scalable solution from that point of view, right? Like if if if you got a site with many millions of visitors, um, then you're not going **[23:57]** to be bogging down your WordPress site with that. Um, so that yeah, it's definitely an important design goal for us. >> Yeah. Um, what else? What else do we got? What else we have under the hood? Like, uh, we talked about, uh, like blocks specifically a little bit or you mentioned them. >> Yeah. Yeah. So that's like blocks is how you're going to do your different variations of things. Audiences is going to be how you're going to target them. If you you can drop into one of those pages there, you can kick me out of that demo page and personalization one **[24:28]** >> take over. >> Um so so this is effectively just showing the same thing that you would have seen on the homepage, right? I have a embedded uh synced pattern. Synced patterns is actually how we do this content personalization thing. So there's three variants within that one. But you can obviously just drop those in anywhere you can show a synced pattern. So, so that's really what we're showing here. It'd be quite typical maybe you have a marketing page um like a landing page that's quite a fancy layout design and you want to vary uh have variations of some elements within that page for **[24:59]** example. Um so so that's how you can do that. Um yeah so the the block here all come under under the um I think that's the sync patterns that you're showing core keeps changing where it shows sync patterns [laughter] but um it's I called the sync pattern header uh confusingly so [laughter] uh it's also the name of a template. >> Yeah. Yeah. >> There we go. Yeah. Yeah. So I also have some other sync patterns in there as **[25:30]** well. >> Yeah. Um and then the last thing that I could probably quickly show is the broadcast um block on on how that is managed. >> Uh that is a block. >> Uh yeah, but sorry you'll need to jump back to the main admin in this in the um accelerate sidebar. >> Okay. >> Yeah. So there's this that's how we're managing this content queue. So I have a footer rearch broadcast here and then um you can see the two that the two **[26:01]** different um pieces of content that I'm recirculating through. So any synced pattern can be inserted as a uh a circulation piece of content. And then if you went to the site edit into the footer, that's where I'm putting in the broadcast block. So there has to be like two levels of abstraction here. I have the broadcast block with all of the different options in it and then I need to put the broadcast block somewhere and that is in if you go to template parts I think it is in the site header >> which is confusingly underpants. Yeah. **[26:32]** [laughter] Uh [clears throat] footers. >> Uh footer, I guess. Uh is it just the main footer? Maybe. I think if you click Oh, yeah. No, it's >> No, I'm out. >> Wait, is that it? >> It's definitely I think you can. Yeah, I think that's it. Yeah. Yes, you can see that I have the broadcast block embedded there. Um and that that's showing me. >> I think that will bounce you through. >> Yeah. >> Um yeah, that that'll take you back to the the screen that we were on. So, so **[27:03]** that's how broadcast works. Again, in situations where um you kind of got a content cue or internal ad network, you can kind of think of it like that as well. Um which is like, okay, if the user didn't click it, you know, once, let's show them something else the next time they view the page kind of stuff. >> Yeah. or like a you know an alternative to the dreaded uh um scrolling like anim you know slider uh in your >> carousel. Yeah. >> Yeah. Exactly. **[27:34]** >> Yeah. >> Um so that that's pretty much uh what we have. So that's really like I would say there's um a few primitives there around how we do synced patterns and the analytics and then broadcast and then being able to convert sync patterns into either AB test or personalized. That's really everything that there is. But hopefully you can kind of see once you combine that with the block editor and full sight editing, you actually now have quite a lot of uh different options of how those things can be combined, how **[28:05]** those blocks can be combined to create a site that is ultimately a bit more dynamic or a lot more dynamic depending how much work you put in um based off of the different types of users that are using the site. And that's ultimately the design goal is is to be able to um allow for that kind of dynamic nature of the WordPress site. Um I will say that you know to to go through the effort of doing that you kind of do need a website with a good amount of uh viewership otherwise yeah you you are putting in a **[28:36]** lot of work. I you know on my personal site that maybe like five people visit a month right >> it's not really worth me you know uh AB testing my headlines. So, so there's definitely kind of a certain scale where this makes more sense, I think. You know, >> well, I'm going to take this a little bit personal because Joe, I have a problem that I discovered because of uh >> Okay. >> having the Accelerate plugin installed. And the problem uh is uh make my window **[29:08]** a little bit bigger, too. That wasn't what I wanted to do. um is that I discovered that I have a great deal of traffic that is coming from China that is definitely not the normal traffic of my site. >> Yeah. Yeah. Except for China that's about like what my website looks like [laughter] >> and like so my site is just a normal blog. Uh it just has some stuff. It's got like you know I I have do Devril stuff so I have like all presentations **[29:38]** and stuff that I've given and things like that. So like nothing nothing super special but I I happened to to update accelerate log into to the uh analytics page and I saw this this big thing from China. So uh I created an audience uh for China and then everything except China. >> Okay. so that I can go into here and look at my analytics and basically see >> this is what I would expect. This is the traffic that seems normal. **[30:10]** [clears throat and snorts] >> Yeah. >> Um but now that I have this audience for China, um what sorts of things could I do uh either through the plug-in itself or even maybe with code that would like with with like this China audience that I have? So, these people that are coming from China that I assume are probably robots because my site isn't written in Chinese. Like, you know, I could probably use uh put a header that is only visible to China and like say maybe **[30:41]** even in Chinese uh hey robot like you know like have a special message for them like what what sorts of things uh could I do uh now that I I've identified that sort of thing. >> Yeah. Yeah. So you could uh if you wanted to, it depends if this is a problem that you feel like you want to combat or something where you know maybe there are some maybe you do have a genuine audience from China that you never knew about. U you you never know. So it could prompt you to do some actual personalization for China. Do something **[31:12]** like, hey, if you're Chinese, let me know here if you want to understand my site or something. Um so yeah, you you can definitely segment that way. Um, like you said, you I mean you could maybe if there were things on your website, I don't know if you had sensitive things on there or just I don't know for for for whatever reason, right? Content that you wanted to restrict, you could you could use accelerate for something like that. It's obviously not like the most secure way of achieving that because it is ultimately all a kind of front-end tool. **[31:42]** Um but but I think yeah the most obvious thing to me would be to have a big banner to say like please stop scraping my site or something. [laughter] >> Is there like is there a code level uh like hook or something that I could do that would uh basically allow me to like for those China visitors give them like a redirect to some other page or a different like google.com or something like that. >> Yeah. Yeah. So we have uh we have documentation on how to like hook into our um uh it it would be a front-end **[32:15]** JavaScript based hook, right? Because again everything is essentially running on the client here. Um so there you would basically hook into um we have a little thing that fires every page load. This is the data for the user and then you can check their country and then change their you know document.loation or whatever and and do it at the code level. So on um accelerateplugin.com we have uh documentation linked I believe in in the header there um and that is uh may maybe it's actually in the footer **[32:46]** maybe we relegated the importance of the documentation >> documentation >> uh there we go yeah so that's that's something where we are kind of um as as more use cases and questions emerge like integration with the consent API for example um anal yeah analytics integration things like that we're kind of adding those as additional um additional kind of guides. So so the more that we hear from people on how they're looking to use this or questions that they have then we're trying to kind **[33:17]** of bake that into our docs and uh you know have have it be useful for more people ultimately. >> Awesome. Yeah. Um >> first time I've seen that that specific you know problem though of having like all of this I don't know. Well, >> that that you didn't want. >> Yeah, I'm as I'm looking at it, there seems to be a lot of hits to WP Signup for some bizarre reason. So, >> okay. Which presumably doesn't even exist on your site because it's not multicight. I know. >> Oh, it is multiight. It is multicight. [laughter] >> Okay. **[33:47]** >> Uh well, thanks a lot. I mean, I think that's really awesome. Um I'm super impressed. Like, uh I've obviously watched uh this plugin develop for for quite a while. Uh for for those of you at home, uh I you know, >> Joe used to be my boss. I used to work at Human Maid. So, uh I you've seen >> I've seen this evolve over time and I've seen a couple different uh incarnations of it. Um, so, uh, I I definitely noticed, uh, when it when it, uh, **[34:19]** changed and I really do like I really like the idea of, you know, the the base level like the analytics like just by itself. I mean, >> there's a lot of analytics plugins out there. Um, >> and like you can and some of them are Google and some of them hook into Google and some of them like you know there's you know Jetack has its analytics thing and whatever and they all kind of approach it in a slightly different way. Um, but I really like, you know, like this. This actually gave me valuable information in with like a couple clicks **[34:51]** that I don't know that I would have gotten. I I mean, I could have gotten that stuff from Google and I could have gotten that stuff probably from Jetack, but like I could do that in like five minutes, whereas I don't like I'd have to refer to documentation to do it in Google. >> Yeah. Yeah. that that's kind of the thesis of the whole tool to be honest is like anybody that's watching this that is like a marketer or performance marketer or something is not going to be wowed by like oh wow I didn't realize I could run an AB test or something right those tools have existed and like frankly the suites for those tools are **[35:23]** really powerful and you can do way more than you can do in accelerate but the problem is it's like it's not close by it's not something that is just like plugandplay click install ready to go I don't need to uh set set up a complex integration. I don't need to log into several tools. Really, the idea of uh accelerate is more like a uh dare I say, you know, use the WordPress buzzword, a kind of democratization play in that like you need to spend quite a lot of money to set up something like uh uh optimizely or you know a full kind of uh **[35:56]** enterprise suite like that. Um and then what you also get at the end of the day is still a very cumbersome process. Whereas really what we're trying to do with Accelerate is just have it be install it. If you're in the block editor, you're going to be ready to go. If you're using full-sight editing, it's even better because obviously you just get all the same primitives at the fullsite editing level and you never have to go to another tool and you know, you don't need to write your variations for your headline in a different tool, right? Those things should be in the CMS. That's where you're writing. That's **[36:26]** where you're building your pages. Um whereas I've seen literally demos from other tools where yes you have your your main version of the page there but then you've got five versions of the page in a separate tool where you don't have any of the WordPress functionality. >> Um so I think that it's it's just about bringing the things together and like you say analytics is just that it's just like well it's right there on the dashboard when you're viewing your uh synced pattern that you're making. You're seeing the views there over time. you're understanding is this an **[36:57]** important piece of content because I have the data right there in front of me. I'm not flicking and not building reports in Google Analytics or something. So, while those tools are way more powerful than what we have, hopefully the kind of at the fingertips useful when you actually need it nature that we're trying to accelerate kind of like actually balances out to be a net plus and on top of that it's like it's free up to like a million views a month as well and things. So, like it's free is always good. >> Yeah. Yeah. And obviously this this tool **[37:27]** has come out of your sort of professional services experience in the field working as an agency with uh companies and organizations who need stuff like this. Are there any sort of like success stories or interesting things that you can share about like sort of what what like that that this or tools like this have enabled or unlocked or things like that for for people that you're working with. >> Yeah. Sure. Yeah. So it's it's there **[37:58]** there's definitely the the the type of situation we like to use it is an agency and then there is kind of like probably the 80% of your more standard let's say setup. So so we definitely see on the agency side we're working on stuff where it's going to be more custom like I kind of mentioned on uh PlayStation using it. Um another site that is using it is recipe tinets that has uh a lot a lot of traffic. let's just say I think they're within uh maybe the top 10 recipe sites in the world or something. Um so so uh **[38:30]** we had to engineer this to work at that kind of scale. So I I think that's kind of um hopefully a balance that we've been able to strike is it works on very big stuff but we've tried to make it simple enough to use for anybody and that is that is why it's valuable as well at the enterprise level is like enterprise technology is not always the most usable and that's ultimately why WordPress is is relatively successful in enterprise is like it's the easy tool **[39:00]** that people kind of know how to use and um if they don't get too bogged down with kind of like millions of checklists of what the software needs to do. WordPress is a good option. And that's just the same balance that we we have kind of with uh Accelerate is like we're not trying to be better than an enterprise um uh performance marketing tool. But um where it actually kind of gets used is in the situations where uh it's going to be like we're going to migrate to um the Adobe suite for **[39:30]** analytics in one year. So then we're going to do personalization, right? Typical client thing is to do a site build and then they've got some um uh plan down the road to introduce these things that Accelerate has. So it's just kind of like well let's just use Accelerate now then and then obviously that thing down the road never even happens because it never kind of does in in uh enterprise tech anyway. It's it's always a thing on the future road map, right? So that's where we've seen success with it is um we're not trying **[40:02]** to convince an organization that this is needs to be their you know uh personalization platform for their whole team and everything cuz it's it's not that. What it is is a tool that works right now that allows your web team to actually get stuff done right now and not have to wait for that kind of like future um big big platform. And um in in our experience it's it's kind of filled that gap pretty well. >> Yeah. Yeah. I really like the example of of a recipe site because I can I can already think of like five different things that Accelerate would be useful **[40:33]** for in that context from AB testing headlines to like maybe different images to all sorts of things. Um we do have a a question coming in from LinkedIn. Is is Accelerate only for WordPress sites? I think the answer to that is yes. Human Made is a WordPress agency. Um are there any thoughts about like or or are there things that could be uh extracted or maybe shared from like a service perspective? uh that accelerate into. >> Yeah. So there's there's kind of two sides to that. One is we have seen situations where you have accelerate on **[41:05]** your uh main WordPress site and maybe there's a couple of like micro sites or pages that are just hosted on something else and it would be valuable to unify the data of those things. So um like just drop our JavaScript embed essentially on one of those other sites and make sure that the data is is is centralized between those. So that that is possible but ultimately because our whole well I actually want to write personalized content now that's all got to be in WordPress. Uh so like if if you're not on a WordPress site at all no **[41:36]** don't don't don't uh go for Accelerate. Again, that's kind of like that is the point really is like this is a WordPress solution and though general purpose solutions are very powerful and everything, the integration point is just in my experience really painful. Um, so we've ultimately just accepted the tradeoff there. It's like we're go for the WordPress people who have got WordPress sites that don't really want to leave WordPress. How can we make something good enough for them? >> Uh, and I've got one other question that **[42:06]** came in from LinkedIn as well. Um any plans to integrate with CDP platforms? >> Uh yeah so CDP CDP platform customer data platform which is generally uh your big business and you use terms like data lake and data warehouses [laughter] and like all of your customer data just goes into this you know kind of black box. Um how could you integrate with something like that for the website? That's kind of I think what what the question is is getting at here. Um so yeah we we **[42:37]** definitely do have there are ways that you can already do that at a code level right I'm kind of mentioned we have like developer APIs that would look something like you know when the um browser is gathering the information that it has on the current user right it knows the time of day based off of you know the date in the browser right you could ultimately pull information from a CDP and feed that into the same pipeline so then I can go and create personalized content based off of attributes on the user maybe in my CDP, you know, that that's **[43:07]** the general flow. Um, so we don't have any like plugandplay adapters right now for specific CDPs, but but the um the the lower level is there and we're still looking to ultimately work on a kind of case by case of like uh let's let's do a specific integration when one arises that there's something tangible to do with because quite quite what happen often happens with customer data is um it's very like high level, move the **[43:39]** data, put the data there, connect the data. Yeah, great. Sharing my data or whatever. But like what is the actual user journey and what specific data would you use and when could you use it? Because if I just open my iPhone now and go to your website for the first time ever, though I might be in your CDP, it doesn't mean that there is a way to meaningfully link me right now. So there's all kinds of practical challenges to do with you know good things around data privacy and third party cookies and why it's difficult to do all those things. So so um there **[44:09]** definitely can be a tendency to look a little too high level in terms of connecting data and targeting users and things like that. Right? If I go watch something on Netflix and then I go on on my phone on Netflix when I've never visited before I'm not logged in. Well, I'm not getting any personalization. Right? There are a lot of limitations around what you can do uh with with customer data. So I would say the devil is in the details when it comes to any kind of CDP or CRM integration is you kind of do need to be able to drop a step lower. We usually have to talk to clients you know okay what are you **[44:39]** specifically looking to do where is that data how do you identify users to understand how that could be achieved because you know yeah there's there's one thing kind of having the idea there's another thing being out of building into the product you know >> right yeah for sure yeah and focusing on the outcome that you're actually going for particularly with uh personalization is probably you know the most important thing because personalization is hard enough as it is I mean that's the thing that I know that you all have been looking at for a long time. Pantheon's been looking at it for a long time. And **[45:11]** the problem with personalization is is like what you said, like there's a lot of work involved. So like if you don't want to spend a ton of work on on on something uh without knowing that it's actually valuable work, >> right? Right. Right. Exactly. It's it's kind of a tricky one because uh it can be that like you know the marketer's dream is just to know everything about everybody, right? And then like uh you know sell as much stuff to them, right? And then the kind of like uh users uh dream is often just like I want to stay anonymous and don't don't want to have **[45:41]** uh kind of anything specific uhly targeted to towards me. So, you know, uh we we're definitely um trying to play as much as we can on the on the privacy side of this, right? like we're not um uh doing anything uh untoward of trying to like circumvent the the the the user in in terms of the the the data that that uh might be held on them that that kind of thing. Um but yeah, I I think uh there's there is always a bit of a **[46:12]** tension there ultimately between uh more data is better ultimately from um a uh a marketer's point of view and less data is is is better from the user. You have you definitely have to strike the balance. Um and there are certainly uh yeah like ways that you can overstep that line and definitely have to be careful. Um it's definitely something that is important to us like I mentioned on the documentation right integration we've had with the WP consent API from day one because that is just a key thing **[46:42]** I mean not only for like regulation and stuff in Europe but ultimately um we we want to be playing nice and respecting the privacy tools that are in place and you know choices of users. >> Yeah. Yep. Well and and anyone who's watching this you can go find uh the accelerate plugin either on accelerateplugin.com which we talked about earlier or just in the WordPress.org or repository. Uh, where can folks find you if they want to find you, Joe Hoy, specifically? >> Yeah. Yeah, you can go to my website with Accelerate on with about five **[47:14]** people visiting a day, which is jo.co.uk, though that's kind of changed into a website about woodworking. Um, and but I'm on I'm on uh I'm I I'm sorry to say I am still on Twitter um as Joe_HoY. That probably is the best way to to contact me. >> Well, awesome. I'm definitely going to go uh play around some more with Accelerate on my personal website. Uh I hope all of you watching either live or in the future uh check it out on on your website. Uh thanks Joe for coming on to **[47:46]** the live stream and for everyone else uh thank you for joining and we'll see you on the internet. >> All right. Thanks very much much for having us Chris. >> Yeah, no worries.