Skip to main content

Journey Builder vs. Targeted Content

They’re separate systems. Targeted Content shows featurettes, which are self-contained pages of content, at trigger points in a client’s app. Journey Builder draws messages, tours, and callouts directly on top of the client’s own screens. They have separate admin areas, separate SDKs, and separate rules.

”Trigger point” means different things

In Targeted Content, a trigger point is a named moment in the app that featurettes are attached to. Journey Builder uses the word trigger for the moment its own content can appear. Older Journey Builder content also has a legacy “trigger point” field, which mobile apps still use. When someone says “trigger point”, check which system they mean.

Callout vs. highlight

They’re the same thing. Callout is the name authors see. Highlight is the older name, still used inside the code and the API.

”Journey” usually means a tour

The product is called Journey Builder, but buttons such as Launch Journey and Get Started start a tour. In everyday use, “a journey” usually means a tour.

Switched on vs. published

A piece of content can be switched on without being deployed to an environment. Websites only receive content that is both, which is why a Web message published from the admin editor can still show Draft on Home. Mobile apps currently receive anything switched on, in every environment.

Mobile-sized web is not mobile

A website viewed in a narrow browser window counts as “mobile” for Web screen-size settings, even on a desktop computer. Those settings are about how wide the window is, not what device the user has. Mobile apps are a separate platform altogether.

The mobile app and the website can look different

Websites take their look from admin themes. Mobile apps currently take theirs from the app’s own code.