Not everyone on a wedding day needs the full timeline. Your couple wants everything, but the wedding party usually only needs to know where to be and when, and a vendor might only care about the two or three blocks that involve them. Audiences build those smaller views for you, without you assembling a second timeline by hand.
What an audience is
An audience is a custom view of the wedding you build once and keep alongside the main timeline. Where the couple's share link always reflects every couple-visible block, an audience shows only the blocks you've chosen for it: a short list for the wedding party, a handful of drop-off and pickup times for the florist, whatever the recipient actually needs. A single wedding can have up to 10 audiences, each named and configured independently.
Two views always exist without any setup: the couple-facing timeline the couple sees, and, whenever a block is hidden from the couple or carries an internal note, a distinct internal team view of everything. Audiences sit alongside those as views you build yourself, one per group of people you need to brief separately.
Creating one and picking its blocks
- Open the wedding's Share page.
- In the Timeline group of the rail, click New audience.
- Name it. "Wedding Party" or "Florist" tells you at a glance who it's for. The name also shows on the audience's link preview, so pick one you're happy for the recipient to see. Daymarked creates the audience with an empty block list.
- Check the blocks this audience should see. Every block on the wedding is listed with its title and time. Nothing is included by default, so an audience starts as an empty document until you build it out.
On a phone, the Share page shows your views as a list. Tap New audience, type a name, and tap Create; the audience opens as its own page, with its blocks at the top and Document options underneath. Use Rename at the top of the page to change its name.
The list stays live: if you delete a block later, it drops out of any audience that had it checked, rather than leaving a stale reference behind.
Below the block list, each audience also carries its own document options, the same section toggles and cover-page choices covered in exporting PDFs, set independently of the main couple-facing document. A vendor's audience might skip the welcome note and family-photo list entirely; that's a per-audience choice, not a global one.
Internal notes never appear on an audience, no matter which blocks you've included or how the block's own visibility is set. Audiences are built from the same couple-facing data as the couple's timeline, filtered down to the blocks you picked, so there's no route from a block's internal notes to any audience's share link or PDF.
Sharing it
Each audience has its own share link and its own PDF, generated independently of the couple's and of every other audience. The first click mints the link; after that, the same button hands back the same URL, so you can send it once and keep it current as you edit. Revoking one audience's link doesn't touch any other: the couple's link, the internal view, and every other audience's link keep working.
When you text or email an audience's link, the preview carries your studio branding and the couple's names, the same as the couple's own link, with the audience's name just above the names.
Creating or updating an audience doesn't email or alert anyone. You send the link or PDF to whoever needs it, the same as you would the couple's timeline. An audience is also a view of one wedding's timeline, not a saved template: building one for this couple's wedding party doesn't carry over to the next wedding, so you'd set up a fresh one there.