# Campaign strategy ## The thinking behind all three Banking Transformation Summit runs a two-sided model. **Banks attend free. Sponsors pay to meet them.** That makes a *qualified, attending* bank delegate the product sponsors are buying. Email therefore has three jobs, and each campaign does one: | Campaign | Job | Revenue line it protects | |---|---|---| | 1. Executive invitation | Grow and qualify the bank audience | Delegate quality, which sets sponsor value | | 2. Sponsor outreach | Turn vendor relevance into sponsorship pipeline | Sponsorship revenue | | 3. Insights newsletter | Keep both sides engaged between events, and learn what each contact cares about | Next year's registrations, renewals and enquiries | Two principles run through all of them: 1. **Qualify inside the email.** Every send tells the reader who it's for and routes everyone else (vendors to the paid delegate pass, wrong edition to the right one). Fewer, better clicks beat more clicks. 2. **Every click should teach us something.** Topic chips, edition switches and segment-tagged UTMs mean the database gets more valuable with each send, not just bigger. --- ## Campaign 1: Banking executive invitation **Audience.** People employed by banks and building societies in the UK and Europe who are responsible for deciding or delivering change: C-suite, SVP/Director, VP/Senior Manager in technology, transformation, data and AI, digital, operations, payments, risk and cyber. **Segmentation.** - *Relationship stage (send order):* (1) the 2027 ticket waitlist, 48 hours before anyone else. (2) 2026 and earlier attendees who attended. (3) Applied-but-didn't-attend and speakers. (4) Engaged newsletter subscribers flagged `banking_executive`. (5) Report downloaders from bank domains. - *Eligibility:* company domain matched to a maintained list of bank and building society domains. Contacts at unmatched domains get the newsletter, not this email. - *Seniority and function:* job titles normalised into seniority bands and the 11 programme topics. These drive the content variant tests (below) and suppress juniors where the brief calls for decision-makers. - *Engagement:* anyone with no click in 12 months is excluded from the launch send and gets a separate re-permission email. **Hypothesis.** Senior bankers don't respond to "event" messaging. They respond to *who else will be there* and *whether they'll learn something they can't get from vendors*. Leading with peer presence ("The people changing banking. In one room."), named 2026 practitioners and small-format sessions should lift qualified applications compared with a features-and-agenda email. **Conversion journey.** 1. **Click →** an application page that repeats the email's promise: same headline, same photo, same three peer stats. 2. **Short form, pre-filled.** HubSpot recognises known contacts, so they confirm rather than retype. Progressive fields ask only for what's missing (job function, topics of interest). 3. **Eligibility check at submission.** A bank domain gets instant "application received". A non-bank domain is routed to the delegate pass page with a polite explanation. Edge cases go to manual review. 4. **Confirmation page and email.** Add to calendar, pick topics (feeds newsletter personalisation), invite a colleague (referral link). 5. **Approval email**, then a pre-event nurture: agenda by chosen topics, app launch, meeting booking ("search the attendee list"), and logistics. A final "can't make it? release your place" email protects show rate. > **Timing note:** on 18 November 2026 bank applications are not yet open (the tickets page offers a waitlist, "Applications open early 2027"). This email is the *applications open* send. Until then, the same design runs with the CTA "Join the priority waitlist" and the eyebrow "Applications open early 2027". **A/B tests.** 1. **Sender identity:** a named person ("Mark at Banking Transformation Summit") vs the brand ("Banking Transformation Summit Europe"). *Measures:* application rate per delivered and approval rate. Senior readers tend to answer people, not brands. 2. **Proof type:** peer proof (named 2026 speakers and "20 of Europe's 25 largest banks") vs format proof (Boardrooms, The Exchange Theatre, meet-ups up front). *Measures:* qualified applications per 1,000 delivered, split by seniority band. This tells us what senior bankers value, which feeds the landing page and next year's copy. *Test design:* hold out 20% of the list for each test cell and send the winner to the remainder. Decide on qualified applications, not clicks. Run tests on the wider list, never on the waitlist. **KPIs.** - **North star:** approved applications from target seniority (VP and above) per 1,000 delivered. - Supporting: click-through rate, click-to-application rate, approval rate (share of applications that are eligible), and **show rate** (approved who attend). - Guardrails: unsubscribe rate below 0.3%, spam complaints below 0.1%, and vendor applications to the free route trending down. --- ## Campaign 2: Sponsor acquisition outreach *(Full copy, follow-ups and personalisation map are in `emails/02-sponsor-outreach.md`.)* **Audience.** Commercial, marketing, partnerships and events leaders at fintechs, enterprise technology vendors and consultancies that sell to banks. **Segmentation.** By product category (mapped to the 11 programme topics), target bank segment (tier 1, tier 2/regional, building societies, specialist lenders), and relationship stage: never engaged, intent signals (sponsor-page visits, report downloads, 2026 delegate pass), or lapsed sponsor. Current and 2026 sponsors are excluded and handled by account management. **Hypothesis.** Vendors don't buy "packages". They buy access to a specific buyer. An email that names *their* target customer and shows a matching audience stat and a relevant 2026 session will earn more positive replies than a generic sponsorship pitch, even though the email is shorter. **Conversion journey.** Reply → discovery call (agree goals, target accounts, budget timing) → tailored audience breakdown for their segment → proposal with recommended formats → contract. Positive replies that "aren't ready yet" go into the technology-partners newsletter with a sales task set for the right quarter. **A/B tests.** 1. **Opener:** trigger-based personalised opener vs category-level opener. *Measures:* positive reply rate and meetings per 100 contacts. Shows whether SDR research time pays for itself. 2. **Ask:** meeting ask ("Worth a quick conversation?") vs a lower-friction resource ask ("Want the audience breakdown for `{{target_customer}}`?"). *Measures:* meetings booked and pipeline £ within 30 days, because a softer ask can raise replies without raising revenue. **KPIs.** Positive reply rate, meetings booked, proposals sent, **sponsorship pipeline £ per 100 contacts**, and win rate and average deal value by category. Guardrails: bounce rate below 2%, spam complaint rate, and opt-out rate per mailbox. --- ## Campaign 3: Personalised banking insights newsletter **Audience.** Everyone opted in to Banking Transformation Summit updates, split by `bts_audience_segment`: - `banking_executive` (Variation A): bank and building society employees - `technology_provider` (Variation B): fintechs, vendors, consultancies - Unknown contacts get A by default, plus a prominent "switch edition" link, so they classify themselves. **Segmentation.** - *Segment:* domain classification, then form self-identification, then the edition switch click (the latest signal wins). - *Interests:* the multi-select `bts_topic_interests`, filled from topic chip clicks, forms and session attendance. Once a contact has 2+ interests, the session module reorders to lead with them. - *Engagement tiers:* active (clicked in 90 days), cooling (90–180 days, lower frequency), dormant (180+ days, sunset flow, then suppression). - *Event cycle:* the CTA panel switches by date: waitlist → apply → final places → post-event content. **Hypothesis.** One generic monthly newsletter teaches subscribers to ignore it. Showing bankers peer learning and showing vendors buyer insight, on the same template, keeps both engaged year-round. The topic picker gives us the data to keep getting more specific. **Conversion journey.** - *A:* content click → report or programme page → "apply" or "join waitlist" as a soft secondary CTA on every content page → application journey as in Campaign 1. - *B:* content click → insight page with a sponsor case/proof panel → brochure download (gated) → lead scoring → sales follow-up within one working day. Direct "enquire" clicks notify the commercial team in real time. **A/B tests.** 1. **Topic picker present vs absent.** *Measures:* share of recipients who state an interest, and the click-through rate of the *following* issue for those who did. This proves whether zero-party data improves engagement. 2. **CTA hierarchy by distance to event:** content-first vs event-first primary CTA at 6 months, 3 months and 6 weeks out. *Measures:* applications (A) and enquiries (B) per 1,000 delivered, and unsubscribe rate. Finds the point where pushing the event stops costing goodwill. **KPIs.** Engaged audience size (clicked in 90 days), the share of the list with a known segment and 1+ interest, click-through rate by module and topic, newsletter-influenced applications and sponsor enquiries (HubSpot attribution), and list health (unsubscribes, complaints, sunset volume). --- ## Automation map | Flow | Trigger | Steps | |---|---|---| | Waitlist → applicant | Applications open | Early-access invite (Email 1) → reminder to non-clickers after 4 days, with the alternative proof variant → "final places" only if true | | Application nurture | Application submitted | Received → approved / redirected → topic picker → agenda by topic → app and meetings → logistics → release-your-place | | Post-event | Attended / no-show | Thank you + report → session takeaways by topic → "save the date" for next year. No-shows: what they missed + re-apply | | Newsletter | Monthly | Segment edition + interest-ordered modules | | Vendor intent | Sponsor page visit, brochure download or 2026 delegate pass, with a vendor domain | Lead score → task to commercial team → Campaign 2 Tier A sequence | | Sunset | No engagement in 180 days | Re-permission email → suppress if no click | ## Deliverability, consent, data quality and suppression **Authentication and infrastructure.** SPF, DKIM and DMARC aligned on the marketing subdomain, with DMARC moving from `p=none` to `quarantine`. One-click unsubscribe (`List-Unsubscribe` + `List-Unsubscribe-Post`) to meet Gmail and Yahoo bulk-sender rules. Keep the spam complaint rate well under 0.3%. Marketing, transactional (approvals, logistics) and one-to-one sales email go out on separate subdomains, so a problem on one doesn't spread. **Consent.** Marketing emails go to opted-in contacts and, under PECR's soft opt-in, to past attendees for similar events. Cold outbound to vendors is one-to-one and covered by a documented legitimate-interest assessment (see Campaign 2 for country exceptions). Every email states why the recipient is getting it and offers both preference management and a full unsubscribe. **Data quality.** Normalise job titles into seniority and function bands. Classify company domains as bank, building society, vendor, consultancy or other. Deduplicate contacts by email and by company. Validate emails at capture. Re-verify contacts older than 12 months before a launch send. Keep a hard rule that segment is never inferred from a guess: unknown stays unknown until the contact tells us. **Suppression lists.** Global unsubscribes. Hard bounces. Spam complainers. Role addresses on cold sends. Current sponsors from sponsor prospecting. Registered applicants from "apply" sends (they get the nurture instead). Competitors. Dormant contacts after sunset. ## Measurement framework | Level | Executive invitation | Sponsor outreach | Newsletter | |---|---|---|---| | Delivery health | Delivered %, complaints, unsubscribes | Bounce %, opt-outs | Delivered %, complaints, sunset volume | | Engagement | Click-through rate, click-to-application rate | Reply and positive reply rate | Click-through rate by module and topic, topic-picker rate | | Conversion | Approved applications, VP+ share | Meetings, proposals | Influenced applications and enquiries | | Business outcome | **Show rate and attendee seniority** | **Pipeline £ and closed revenue** | **Engaged, profiled audience size** | Opens are reported but never used to judge results, because Apple Mail Privacy Protection inflates them. Every link carries `utm_campaign`, `utm_content` (module) and `utm_term` (segment), so performance can be read by module and audience in GA4 as well as HubSpot.