Marketing messaging and copy
Messaging is the set of words that carries a product's positioningPositioningGo-To-MarketProduct positioning statementView reference → to a specific audience through a specific channel. A headline, a body, a call to action, in a chosen tone. One positioning produces many messages, because the landing page, the cold email, the launch tweet, and the in-product nudge each meet a different reader at a different moment. The craft is keeping all of them true to one underlying claim while letting each one fit its surface.
Messaging as a discipline grows out of mid-twentieth-century advertising craft. David Ogilvy's *Confessions of an Advertising Man* (1963) codified the idea that the headline does most of the work and that copy should sell a specific benefit to a specific reader, backed by evidenceEvidenceValidationData supporting or refuting a hypothesisView reference →. The "message" was the promise, distinct from the medium that carried it.
The structured, testable version arrived with the lean and growth eras. Teams stopped treating copy as a one-shot creative act and started running headline and call-to-action variantsVariantGrowthA variant in an A/B testView reference → as experimentsExperimentValidationA test designed to validate a hypothesisView reference →, reading conversion by message rather than by hunch. Practitioners such as Joanna Wiebe formalised conversion copywriting, the practice of building copy from the customer's own language, harvested from reviews and interviews, and validating it against behaviour rather than taste.
The settled view separates two layers cleanly. A message house, or messaging framework, holds the durable claims that flow directly from positioning. The channel variants are the surface expressions, tuned per channel and per funnelFunnelGrowthA conversion funnel tracking user progressionView reference → stage, that all trace back to that house. A landing-page hero and a sales pitch can read very differently and still be the same message, provided both ladder up to the same positioning. Drift between channels is the failure mode the framework exists to catch.
A team has positioning fixed: a meeting-intelligence tool for consultants that saves billable hours. The single claim spawns variants by channel and funnel stage.
The landing-page hero, an awareness-stage message, reads "Stop losing billable hours to meeting notes" with a "See it on your next call" call to action, in a confident, peer tone. The conversion-stage email to a trialist who has recorded three calls but never opened a summary reads "Your three calls are sitting unsummarised, here is the first one" with a "Open my summary" call to action, in a helpful, direct tone. Same positioning, different reader, different moment, different words. When the team A/B tests the hero against "Turn every call into a client-ready doc", the billable-hours framing wins by 18 percent, because it names the cost the consultant already feels.
In the Unified Product Graph, messaging is a leaf in the Go-To-Market domain within the Business, GTM and Growth region, fourth in the canonical sequence right after PositioningGo-To-MarketProduct positioning statementView reference →. It receives its claim through positioningPositioningcommunicated viaMessaginghierarchy and is shaped by the audience via positioning_communicated_via_messagingIdeal Customer ProfileshapesMessagingcausal and ideal_customer_profile_shapes_messagingMessagingtargetsPersonacross-domain. It stays on-brand through messaging_targets_personaMessagingaligns withBrand Voicecross-domain and is consumed downstream by messaging_aligns_with_brand_voiceMessagingused inLaunchcross-domain and messaging_used_in_launchAd CreativereferencesMessagingcross-domain. The typed ad_creative_references_messagingchannel and funnel_stage properties are what enforce the region's anti-pattern guard: messaging without channel variants is incomplete, because each channel needsNeedUserA user need, pain, desire, or constraintView reference → its own variant tracing back to the one positioning.
Type-specific fields on BaseNode
channelstringChannel this messaging variant is crafted for
funnel_stagestringMarketing funnel stage this variant targets
headlinestringPrimary headline or hook
bodystringFull message body copy
call_to_actionstringCall-to-action text
tonestringVoice and tone for this variant (e.g. "conversational", "authoritative", "playful")
idstringrequiredUnique identifier (UUID)
typeNodeTyperequiredDiscriminator for the entity type
titlestringrequiredDisplay name
descriptionstringOptional detailed description
statusstringLifecycle status
tagsstring[]Freeform tags for filtering
4 phases — initial: draft · template: PUBLISHING
8 edge types connected to this entity.
positioning_communicated_via_messagingmessaging_targets_personaad_creative_references_messagingcontent_piece_supports_messagingmessaging_aligns_with_brand_voiceideal_customer_profile_shapes_messagingmessaging_used_in_launchmessaging_enables_sales_motion