BlueConic Lifecycles help you orchestrate customer journeys using marketing touchpoints. Here are some tips to prevent or fix problems when you're setting up or running BlueConic Lifecycles.
Things to remember
- Not all connections support Lifecycles.
- Touchpoints are required in order to complete and Lifecycle, and there is no maximum amount of touchpoints allowed within a Lifecycle.
- Profiles can go through multiple Lifecycles at a time.
- Lifecycles are broken into stages which can be defined by sets of profile property criteria, behavioral scores, segments, objectives, and groups.
- Lifecycles can have a maximum of 10 stages.
- Lifecycles can be sequential, but profiles can skip stages.
- A profile can only belong to one stage within a given Lifecycle.
-
Thresholds are used to limit the number of touchpoints a customer receives across channels in a given time period while part of a specific lifecycle stage.
-
Note: You cannot set the order of touchpoints while using thresholds.
-
Best practices for using Dialogues in Lifecycles
-
The Lifecycle priority will override Dialogue priority while the Lifecycle is on.
-
When a Dialogue is a part of a stage, it will only be served to profiles present in that stage.
- A best practice for using Dialogues in Lifecycles is not to reuse an existing Dialogue -- instead, you should create a new version of the Dialogue for use inside the Lifecycle.
Strategy for adding dialogue variants to a Lifecycle stage
Dialogue variants cannot be added directly to a Lifecycle stage. You cannot add dialogue variants to different lifecycle stages because dialogues placed in a lifecycle stage are shown to profiles that meet the lifecycle criteria, the lifecycle stage criteria, AND all the criteria listed on the dialogue's Who tab. Because Who rules are dialogue-specific and not variant-specific, you cannot assign variants within the same dialogue to different lifecycle stages because this would cause conflicts. For this use case we recommend creating a separate dialogue for each variant instead.
Impact of user role permissions on working with Lifecycles
BlueConic uses role-based permissions. So in order to edit Lifecycles, your user role needs to have the Lifecycle permission. If you have the correct Lifecycles permission and want to add connection goals or dialogues as marketing touchpoints in your lifecycles, your user role will also need permissions for connections or dialogues.
So, for example, if you have permissions to create lifecycles, but do not have dialogue permissions, you will not be able to edit or update a lifecycle that contains dialogue touchpoints.
Contacting Support
For information on contacting our Support Team with questions, see Contacting BlueConic Support.