Key Points
Sourcing email data for both content personalisation and send-time personalisation requires a Database Providers standing brief that specifies four fields not always included in standard sourcing briefs: role title for content routing, seniority level for content depth routing, company primary location for time zone adjustment, and SMTP verification at the 60-day standard for engagement event association accuracy
Including all four fields in the standing brief at sourcing is significantly more efficient than sourcing without them and retroactively enriching — the enrichment process can add missing fields but adds time, cost, and the risk that some fields cannot be populated for all contacts
Database Providers provides all four personalisation-enabling fields as part of the standard firmographic export when specified in the brief — making the personalisation data requirement a brief specification decision rather than a separate enrichment exercise
The most important data sourcing discipline for programmes implementing both personalisation types is specifying SMTP verification at the 60-day standard rather than the default 90-day — because both personalisation types depend on accurate email address matching for their personalisation signals to work correctly
Analyze this article with
Sourcing email data for both content personalisation and send-time personalisation requires specifying the data fields that both approaches depend on at the brief stage — not attempting to add them retrospectively after the segment has been delivered. Most programmes that attempt to retrofit personalisation data after sourcing discover that the retrospective enrichment process adds cost, time, and incomplete coverage — some contacts cannot be enriched because the matching key (company name or email domain) is ambiguous.
The most efficient approach: specify all personalisation-enabling fields in the standing brief before the first delivery, ensuring that every contact in every subsequent refresh arrives with the complete personalisation data set from the moment of import.
The Four Personalisation-Enabling Fields
Field One — Role Title (for Content Personalisation Routing)
Role title is the primary routing field for content personalisation — the decision rule references this field to assign each contact to the appropriate role-specific content variant. It must be populated for all contacts and accurate at the 97 percent standard.
Brief specification: "Role title required field — classify by primary functional role (Finance, Operations, Technology, Legal, HR, Compliance). Accuracy standard: minimum 97 percent role classification precision."
Field Two — Seniority Level (for Content Depth Routing)
Seniority level enables the routing rules that differentiate senior executive content (C-Suite, VP) from mid-level manager content (Director, Manager) — the most impactful secondary content routing dimension after role category.
Brief specification: "Seniority level required field — five-level hierarchy: C-Suite, VP, Director, Manager, Individual Contributor. Applied by Database Providers using title, company size, and organisational structure context."
Field Three — Company Primary Location (for Send-Time Time Zone Adjustment)
Company primary location at the city level enables the sending platform to infer the contact's time zone and deliver each email at the local optimal send time rather than the sender's standard time.
Brief specification: "Company primary location required field — city and country. Used for time zone inference in sending platform scheduling. All contacts should have primary office city populated."
Field Four — SMTP Verification at 60-Day Standard (for Engagement Event Association Accuracy)
The 60-day SMTP verification standard ensures that the email address in the CRM is current — enabling both personalisation types to function accurately by maintaining the email address matching key that associates engagement events (for engagement-based content personalisation) and behavioural events (for send-time behaviour tracking) with the correct CRM contact record.
Brief specification: "SMTP verification standard: 60-day freshness window for all contacts in the segment. Priority verification for contacts within eight weeks of the previous delivery."
How to Write the Personalisation-Enabled Standing Brief
The personalisation-enabled standing brief has all standard firmographic specification elements plus the four personalisation-enabling field requirements. Standard elements: role function category (Finance, Operations, Technology, etc.), company industry, company size range, geography, additional firmographic filters relevant to the specific audience.
Personalisation-enabling additions: role title accuracy standard (97 percent), seniority level classification requirement, company primary location city level, and SMTP verification standard (60-day explicitly stated).
The brief should explicitly note that the segment is for use in an automated email personalisation programme — this context triggers Database Providers to apply the personalisation-appropriate quality standards to the delivery rather than the standard cold outreach quality standards, which may use a 90-day verification window.
The email marketing guide from Database Providers covers the personalisation-enabled brief specification in detail. For the personalisation-enabled contact data with all four required fields populated, Database Providers provides purchase email list by zip code contacts and best email database provider verified segments with the role classification, seniority level, location data, and 60-day SMTP verification that both personalisation types require from a single brief.
Maintaining Personalisation Data Quality Through Refresh Cycles
The personalisation-enabled standing brief should apply to every monthly refresh, not just the initial delivery. Specify in the brief that each refresh delivery should maintain the same four personalisation-enabling fields at the same quality standards — ensuring that new contacts entering the programme through the monthly refresh arrive with complete personalisation data.
Additionally, the quarterly enrichment should update all four personalisation-enabling fields for contacts already in the programme — confirming role currency (which changes at the 22 to 30 percent annual rate), seniority level currency (which may change when contacts are promoted), and SMTP address currency (which must remain within the 60-day window for the engagement event association to function).
FAQ's
Role title and seniority level classification, company primary location, and 60-day SMTP verification are all standard capabilities of the Database Providers sourcing process — they do not increase cost or lead time when specified in the brief. The cost and lead time remain the same as a standard brief delivery; the brief specification simply ensures these fields are explicitly included and quality-checked.
The delivery will include role title as standard (it is always part of the firmographic export) but may not explicitly classify seniority level, may not include company primary location at the city level, and will default to the 90-day SMTP verification standard rather than the 60-day personalisation-appropriate standard. Retroactively adding the missing fields requires a supplementary enrichment brief.
Separate briefs are recommended — the cold outreach brief uses the standard 90-day verification standard (appropriate for lower-frequency sending), while the nurturing sequence brief requires the 60-day standard. A shared brief defaults to the less stringent standard, which is insufficient for the nurturing sequence's engagement event association requirements.
Specify the geography as a brief filter (contacts in the UK, Germany, and Netherlands, for example) and request that company primary location be provided at the city level for all contacts in the segment. Database Providers includes the primary office city in the export, enabling the sending platform to assign the correct time zone for each contact regardless of their country.
The personalisation data quality check at import: confirm role title is populated for above 98 percent of contacts (any missing role titles are flagged for enrichment before import). Confirm seniority level is populated for above 90 percent of contacts (the remaining 10 percent fall to the catch-all routing). Confirm company primary location is populated for above 85 percent of contacts (the remaining 15 percent use the sender's standard time as the delivery time). Confirm verification date is within 60 days of import date.
