[{"data":1,"prerenderedAt":208},["ShallowReactive",2],{"marketing-blog-blog\u002Fconsent-and-the-post-event-email":3,"marketing-blog-related-blog\u002Fconsent-and-the-post-event-email":188},{"id":4,"title":5,"author":6,"body":7,"category":167,"date":168,"description":169,"draft":170,"extension":171,"image":172,"imageAlt":173,"imageCredit":174,"imageCreditUrl":175,"meta":176,"navigation":177,"path":178,"readTime":179,"seo":180,"stem":181,"tags":182,"__hash__":187},"blog\u002Fblog\u002Fconsent-and-the-post-event-email.md","Consent and the post-event email","The CheckInHub team",{"type":8,"value":9,"toc":156},"minimark",[10,14,17,22,25,28,31,37,41,44,47,56,60,63,127,130,134,137,145,150,153],[11,12,13],"p",{},"The most valuable thing your event produces is not the room full of people.\nIt is the list of people who came, and your ability to email them\nafterwards. That is also the easiest place to quietly break the rules,\nbecause the line between a reasonable follow-up and an unwanted marketing\nblast is narrower than most organisers realise, and crossing it costs you\ntrust you spent the whole event building.",[11,15,16],{},"A guest gave you their email address to register for one event. What you\nare allowed to do with it next depends entirely on what you told them, what\nthey agreed to, and how you treat the agreement afterwards. None of this is\ncomplicated, but it does need to be decided before the email goes out, not\nafter someone complains.",[18,19,21],"h2",{"id":20},"two-different-reasons-to-email","Two different reasons to email",[11,23,24],{},"It helps to separate the post-event email into two kinds, because they have\ndifferent rules and conflating them is where organisers get into trouble.",[11,26,27],{},"The first is the email about the thing that just happened — the thank-you,\nthe slides, the photos, the practical follow-up to the event the guest\nactually attended. This is generally on solid ground, because it is the\nreasonable completion of the transaction the guest entered into. They came\nto your event; an email closing the loop on that event is what they expect.",[11,29,30],{},"The second is the email about your next thing — the invitation to the\nfollowing event, the newsletter sign-up, the offer. This is marketing, and\nmarketing needs its own basis. You cannot assume that because someone came\nto one event, they have agreed to hear about everything you do next.",[32,33,34],"blockquote",{},[11,35,36],{},"A guest who registered for one event has consented to that event, not to\na relationship. The relationship is something you ask for, clearly, not\nsomething you assume.",[18,38,40],{"id":39},"ask-at-the-right-moment-in-plain-words","Ask at the right moment, in plain words",[11,42,43],{},"The clean way to handle the second kind of email is to ask for it at\nregistration, separately from the registration itself. A clear, unticked\nbox — \"I'd like to hear about future events\" — sitting apart from the\nrequired fields, in plain language, with no pre-selection. The guest who\nticks it has told you something real. The guest who does not has told you\nsomething too, and you respect both.",[11,45,46],{},"This matters more than it looks. A pre-ticked box or a buried clause might\ntechnically gather a long list, but it gathers a list that does not want to\nhear from you, and a list that does not want to hear from you is worse than\na short one that does. It hurts your deliverability, your reputation and\neventually your inbox placement. Consent gathered honestly is consent worth\nhaving.",[11,48,49,50,55],{},"We have written about the wider picture of handling guest data in\n",[51,52,54],"a",{"href":53},"\u002Fblog\u002Fgdpr-for-events-without-the-panic","gdpr for events without the panic",",\nand the post-event email is where the principles there meet the keyboard.",[18,57,59],{"id":58},"keep-the-two-lists-separate","Keep the two lists separate",[11,61,62],{},"The practical discipline is to keep the attended-this-event list separate\nfrom the wants-to-hear-more list, and to send each kind of email only to\nthe list that matches it.",[64,65,66,82],"table",{},[67,68,69],"thead",{},[70,71,72,76,79],"tr",{},[73,74,75],"th",{},"Email",[73,77,78],{},"Send to",[73,80,81],{},"Basis",[83,84,85,97,107,118],"tbody",{},[70,86,87,91,94],{},[88,89,90],"td",{},"Thank-you and event follow-up",[88,92,93],{},"Everyone who attended",[88,95,96],{},"Completing the event they came to",[70,98,99,102,104],{},[88,100,101],{},"Slides, photos, practical info",[88,103,93],{},[88,105,106],{},"Same",[70,108,109,112,115],{},[88,110,111],{},"Invitation to the next event",[88,113,114],{},"Only those who opted in",[88,116,117],{},"Marketing consent given freely",[70,119,120,123,125],{},[88,121,122],{},"Newsletter or general updates",[88,124,114],{},[88,126,106],{},[11,128,129],{},"The line down the middle of that table is the whole of it. Mix the lists —\nsend the next-event invitation to everyone who merely attended — and you\nhave used a registration address for a purpose the guest never agreed to.\nKeep them apart and every email you send is one the recipient expects.",[18,131,133],{"id":132},"make-leaving-as-easy-as-joining","Make leaving as easy as joining",[11,135,136],{},"Consent is not a one-time capture. It is something a guest can withdraw, and\nthe ease of withdrawing it is part of whether you are handling data\nhonestly. Every marketing email needs a working, obvious unsubscribe, and a\nguest who clicks it should be off that list immediately and permanently — no\nre-adding them at the next event because they registered again.",[11,138,139,140,144],{},"This is where the right tooling quietly does the work for you. CheckInHub\nkeeps the follow-up tied to the event and the guest, so the email comes\nfrom you, lands cleanly, and respects the choices the guest made at\nregistration. The point is not to send more email. It is to send the right\nemail to the right list with a basis you could explain to the guest without\nflinching. Our note on\n",[51,141,143],{"href":142},"\u002Fblog\u002Fwriting-a-follow-up-email-people-open","writing a follow-up email people open","\ncovers the craft side once the consent side is sound.",[146,147,149],"h3",{"id":148},"when-in-doubt-send-less","When in doubt, send less",[11,151,152],{},"If you are ever unsure whether a particular email is the close-the-loop kind\nor the marketing kind, treat it as marketing and send it only to the\nopted-in list. The cost of under-sending is a slightly smaller reach. The\ncost of over-sending is a complaint, a damaged sender reputation, and a\nguest who now distrusts the next email you send — including the legitimate\none.",[11,154,155],{},"The follow-up is where an event keeps paying back long after the room\nempties. Handle the consent behind it with the same care you put into the\ndoor, and the list you built stays an asset rather than becoming a\nliability. Ask clearly, keep the lists apart, make leaving easy, and send\nless when unsure. The guests who stay on your list will be the ones who\nactually want to be there next time.",{"title":157,"searchDepth":158,"depth":158,"links":159},"",2,[160,161,162,163],{"id":20,"depth":158,"text":21},{"id":39,"depth":158,"text":40},{"id":58,"depth":158,"text":59},{"id":132,"depth":158,"text":133,"children":164},[165],{"id":148,"depth":166,"text":149},3,"Security & data","2024-01-12","The follow-up email is the most valuable thing an event produces and the easiest place to break the rules. Here is how to send it cleanly.",false,"md","https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1561841505-3ff34c3c431f?ixlib=rb-4.1.0&w=1600&q=80&auto=format&fit=crop","People queueing on a pavement","Lumi W","https:\u002F\u002Funsplash.com\u002F@lumiwh?utm_source=checkinhub&utm_medium=referral",{},true,"\u002Fblog\u002Fconsent-and-the-post-event-email",5,{"title":5,"description":169},"blog\u002Fconsent-and-the-post-event-email",[183,184,185,186],"security","data","privacy","gdpr","_JymP9vPMh9UtIomAOP-up8it4WC6wOP9D3pZGLp3io",[189,196,202],{"to":190,"title":191,"description":192,"date":193,"category":167,"image":194,"readTime":195},"\u002Fblog\u002Fworking-with-the-venues-security-team","Working with the venue's security team at your front door","Your check-in desk and the venue's security team are running the same door with different lists. How to brief them, where the handover goes wrong, and the one number both sides need to agree on.","2026-07-26","https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1762474293029-6a7f3698312c?ixlib=rb-4.1.0&w=1600&q=80&auto=format&fit=crop",6,{"to":197,"title":198,"description":199,"date":200,"category":167,"image":201,"readTime":195},"\u002Fblog\u002Fmartyns-law-and-the-front-door","Martyn's Law and the front door: knowing who is in the building","The Terrorism (Protection of Premises) Act 2025 turns on how many people are present at once. What the standard and enhanced tiers ask for, and why an honest, live headcount is the quiet foundation under the procedures.","2026-06-30","https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1633358050629-bb6a292616ff?ixlib=rb-4.1.0&w=1600&q=80&auto=format&fit=crop",{"to":203,"title":204,"description":205,"date":206,"category":167,"image":207,"readTime":195},"\u002Fblog\u002Fcounting-people-out-not-just-in","Counting people out, not just in","Most front-of-house effort goes into getting people through the door. Far fewer teams can say, at the end of the night, that the building is actually empty. Here is how to make departures as reliable as arrivals, and why it is about to matter more.","2026-06-25","https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1540039155733-5bb30b53aa14?ixlib=rb-4.1.0&w=1600&q=80&auto=format&fit=crop",1787334033609]