Overview
This guide walks you through setting up and using the Salestrekker V2 integration. The system is designed to support both Salestrekker V1 and V2 simultaneously, ensuring existing leads are not disrupted while new leads take advantage of the updated V2 platform.
Before You Begin — Pre-Setup Checklist
Complete the following steps before switching to Salestrekker V2. Skipping these may result in data not loading correctly after the switch.
Step 1 — Save API and URL Settings in Aggregator Settings
Go to Broker Settings → Aggregator Settings and either add new entries or re-save the existing API Key and URL fields.
⚠️ Important: Even if these fields already appear to be filled in, re-saving them ensures the values are properly stored in the system. If this step is skipped, some data may fail to load after switching to V2.
Step 2 — Verify Stage Mappings
Review the Stage Mappings to confirm all pipeline stages are correctly mapped. If any mappings are missing, add them before proceeding.
Stage mappings define how deal progress in your system corresponds to stages in Salestrekker. Incomplete mappings can result in leads not appearing in the correct stage on the Salestrekker dashboard.
Setting Up Salestrekker V2
Once the pre-setup checklist above is complete, follow the steps below to activate and configure Salestrekker V2.
Step 1 — Switch the Aggregator to Salestrekker V2
In the Broker Profile, update the aggregator selection from Salestrekker to Salestrekker V2.
Step 2 — Add the API Key
Go to Broker Settings → Aggregator Settings and enter the API Key provided for Salestrekker V2.
Step 3 — Select the Owner
This ensures that any leads synced through V2 appear correctly on the broker's Salestrekker V2 dashboard. Without this, synced leads may not be visible to the right broker.
Step 4 — Configure Stage Mappings
Set up or review the Stage Mappings for V2 to ensure lead stages are correctly aligned between the two platforms.
Step 5 — (Optional) Update Salestrekker V1 Settings
If the broker also needs to maintain or update their Salestrekker V1 configuration, click the "Edit Salestrekker V1 Configurations" button. A popup will appear where V1 settings can be added or updated without affecting the V2 setup.
This allows both V1 and V2 to remain active and configured simultaneously.
Syncing Leads
The system automatically determines which version of Salestrekker to use when syncing a lead, based on its history.
How to Sync a Lead
From the lead record, click the "Sync / Add to Salestrekker" action button — the same as in V1.
How the System Decides Which Version to Use
Scenario | What Happens |
|---|---|
The lead was previously synced via V1 | The lead will continue to sync using V1 logic, ensuring no disruption to existing records. |
The lead has never been synced before | The lead will sync using the new V2 integration and will appear on the broker's Salestrekker V2 dashboard under the Owner ID configured in the settings. |
This behaviour ensures a smooth transition — existing leads are not migrated or affected, while all new leads benefit from the V2 integration automatically.
Summary
Phase | Key Actions |
|---|---|
Pre-Setup | Select aggregator, re-save API/URL settings, verify stage mappings |
V2 Setup | Switch to V2, add API Key, enter Owner ID, configure stage mappings |
Optional | Update V1 configurations via the Edit button |
Lead Sync | Use the same sync button — system handles V1 vs V2 automatically |
For technical support or configuration issues, please contact your system administrator or effi support at support@effi.com.au.
Key Features
One-time configuration saving before migration
Automatic retention of tracking URLs
Seamless transition from V1 to V2
Modal-based settings interface
Centralised configuration management
API-based tracking support
Important Notes
Original values must be saved before switching to V2.
URL tracking relies on aggregator configurations.
Changing aggregators may update URLs automatically.
Switching back to V1 may be restricted in future releases.
Some mapping improvements are still in progress.
Comments
0 comments
Please sign in to leave a comment.