On-site hold
Keep on-site and in-app content serving only while the customer still matches a condition, when a journey sends to a web or app channel.
A Send node on an on-site channel (Web banner, Web personalization or Mobile in-app) does not deliver anything to an address. It holds the content for the customer, and your website or app shows it the next time the customer visits. The hold condition decides whether it keeps showing: the content is served only while the customer still matches the condition, checked again on every visit. It appears on the send node only when its channel is one of these three.
Who uses it
Campaign creators who combine journeys with on-site content. Changing the node needs campaign_editor, or another role your administrator has given access to this area — see Licences and roles. On-site channels belong to the Digital package, and journeys to the Campaign package.
Fields
| Field | Meaning | Valid values | Default |
|---|---|---|---|
| Hold condition | When the held content may still be served. | Always serve, Segment, Custom conditions | Always serve |
| Segment | For Segment: the segment the customer must still be in. | A segment | None |
| Hold condition (conditions) | For Custom conditions: conditions built in the same filter builder segments use. | Filter rules | None |
Always serve means no condition: the content serves until it is used up or expires. With Segment or Custom conditions, the content serves only while the profile still matches, evaluated live on every visit.
Every group of conditions needs its AND or OR choice and at least one condition. A journey with an unfinished group is refused when you save it.
The condition is pinned when the send fires. Editing the segment later does not change content that was already sent; only content sent afterwards uses the new definition.
Other fields on an on-site send behave a little differently:
- Extra data is frozen into the delivery when it is sent and is available to the content as
.Data.key, merged with the offer's payload. If both set the same key, the offer wins. - Silent hours are not offered, because on-site content is pulled by the visitor, not pushed.
- On fatigue still applies.
- Consent is checked again when the content is served, not only when it was sent.
Actions
- Choose a Hold condition option to switch. Switching to Always serve removes the condition.
- On the campaign page, On-site deliveries lists what the campaign has written, with each delivery's State (Active, Delivered, Clicked, Dismissed, Expired), impressions, profile and expiry, and a Filter by state control.
- In Pre-flight, a message proof for an on-site send shows the content handed to the website and the frozen data. Create entitlement writes one real, proof-marked delivery for a profile so you can load your site and see it in place.
Examples
An offer banner for people who have not bought. The journey sends a Web banner. Hold condition: Custom conditions requiring that the customer has no purchases. If the customer buys before they next visit, the banner is no longer served.
A members-only notice. Hold condition: Segment Loyalty members. A customer who leaves the segment stops seeing the notice.
A one-shot welcome. Leave Always serve. The welcome shows until it has been shown as many times as the content allows, or it expires.
Common problems
- The Hold condition is not on my send node. It appears only for Web banner, Web personalization and Mobile in-app.
- A customer never saw the content. They have not visited since the send, they no longer match the hold condition, or they have not granted the consent purpose when the content is served. The On-site deliveries card shows the state.
- No Send a proof button for my on-site send. On-site channels have no destination address. Use the render proof and Create entitlement in Pre-flight.
- The segment changed but old deliveries behave the same. The condition is fixed at the moment of the send.