- Knowledge Base
- Unific Integrations
- How Unific Works
-
Unific Integrations
-
Unific's Ecommerce Properties, Workflows and Lists for HubSpot
-
Unific FAQ's
-
Quotific
-
Revenue Conduit & ActiveCampaign
-
Revenue Conduit & HubSpot
- HubSpot FAQs
- HubSpot Marketing System: Smart Lists - Key Segments
- Hubspot Marketing System- RFM Smartlists/Saved Filters
- Hubspot Marketing System: Smartlist - ROI Workflows
- HubSpot Marketing System: Workflows
- HubSpot Platform Connections
- Revenue Conduit Data Sync: HubSpot Properties
- Revenue Conduit: Features & Settings
-
Revenue Conduit & Infusionsoft
-
Revenue Conduit Account Management
-
Revenue Conduit Frequently Asked Questions
-
Revenue Conduit Shopping Carts
Staging / Test / Dev Environments
Best Practices for Testing Unific with your lower environments
When testing Unific on your lower test or cloned production environments we recommend that you use a separate Unific account from what you plan on using for Production and connect a test Hubspot portal.
The reasoning behind this is that there's a high possibility of overlapping contact and deal ids between your test and production stores causing conflicts in data when you are syncing production data later on. Using a test Hubspot portal prevents any of these conflicts from affecting you in the future.