Solution Launchpad is available through our certified partner program. Click here to learn how you can become a certified partner.
This document outlines what is included when a campaign is installed from one app to another, using Solution Launchpad.
Table of Contents
What’s included?
The following data is included when installing an advanced automation:
- Campaign name
- Campaign category
- All canvas elements and sequence structure
- Data/selections within configuration screens
- Canvas notes
- Campaign Merge Fields
- Campaign Links
Supported dependencies
When configuring an advanced automation, it’s possible to reference or embed other items, which will also be included in your install. Supported dependencies listed by automation element:
- Goals
- Appointment Goal
- Pipeline Stage Moved Goal
- Tag applied Goal
- Checkout Form Goal
- Form Submitted Goal
- Web Form Submitted Goal
- Web Form (legacy)
-
Internal Form Submitted Goal
- Internal Form (legacy)
- Landing Page Goal
- Landing Page Submitted Goal
- Legacy Landing Page (legacy)
- Product Purchased Goal
- Product Category
- Failed Purchase
- Product Category
- Sequence Items
- Create a Deal
- Pipeline (Solution Launchpad only)
- Field Timer
- Email message
- Email Template (including Subject Line and Preview Text)
- Email message (legacy)
- Legacy (BARD) email
- Apply/Remove Tags
- Apply Note
- Create Task
- Set Field Value
- Add to Sequence
- Advanced Automation (if sequence is in a different automation)
- Create a Deal
Non-supported dependencies
When configuring an advanced automation, it’s possible to reference or embed other items. The following items will not be included with your install:
- Goals
- Product Purchased Goal
- Products
- Failed Purchase Goal
- Products
- Opportunity Stage Moved
- Opportunity settings/defaults
- Product Purchased Goal
- Sequence Items
- Create Order
- Products
- Create Opportunity
- Opportunity settings/defaults
- Cancel Subscription
- Subscription
- Apply Action Set
- Action Sets
- Move Opportunity
- Opportunity settings/defaults
- Create Order
Behavior notes
When an automation contains a create task process, and the task has a task outcome selected, and that automation is exported/imported into another app via solution launchpad, the task outcome will be created in the destination app automatically. Task outcomes are especially useful tools to streamline business processes. Here are a couple of use cases:
Use Case 1
Sales Call Results
This is a very common use case. When a sales rep finishes a call, the next step depends entirely on the conversation.
Outcome: "Left Voicemail" - Triggers an automated email: "Sorry I missed you! Just left a voicemail..." and schedules a follow-up task for 2 days later.
Outcome: "Interested / Send Quote" - Triggers an automation that sends a pre-formatted quote and a nurture sequence about your services.
Outcome: "Not Interested" - Applies a "Lost Lead" tag, stops all sales emails, and perhaps adds them to a long-term monthly newsletter.
Use Case 2
Failed Payment Recovery
When a payment fails and automated emails don't work, a staff member might try to call the client.
Outcome: "Payment Processed Over Phone" - Stops the "Billing Failure" automation and sends a receipt.
Outcome: "Subscription Cancelled" - Triggers the "Offboarding" automation and removes access to the product.
Outcome: "Requested Extension" - Pauses the billing automation for 7 days.
Comments
0 comments