1. Can I run campaigns for multiple customers using a single Smartlead account?
Yes, but it comes with limitations. When multiple campaigns share the same lead lists or use overlapping custom variables, data may be overwritten, resulting in inaccurate messaging for some leads.
2. How do custom variables work across campaigns?
In Smartlead, custom variables are attached globally to leads.
đ¨ This means that if two campaigns use the same variable names, the data from one campaign can overwrite the data from another, even if the campaigns are for different customers.
3. Does the âClient Access/Agency Viewâ add-on isolate campaigns per customer?
No. Although Smartlead recommends this add-on to separate client data, testing has shown that it does not isolate custom variables. Leads can still share variables across campaigns, making this approach unreliable for multi-customer setups.
4. How can I avoid overlapping data issues?
Ensure lead lists are deduplicated before importing or exporting.
Use unique custom variable names for each campaign.
Consider running separate Smartlead accounts or workspaces per customer if campaigns are highly overlapping.
5. Can Twain help manage multi-customer campaigns safely?
Twain can export campaign data, but the same caution applies: overlapping leads with shared variable names can cause data to mix. Proper deduplication and variable management are essential.
6. Are there any workarounds if I need to use one Smartlead account for multiple customers?
Currently, thereâs no fully safe workaround within Smartlead. Agencies should take care to:
Deduplicate leads before exporting
Avoid reusing custom variable names across campaigns
Monitor exported data for inconsistencies
7. Will Smartlead fix this limitation?
Smartlead is aware of the limitation, but no timeline has been provided for a solution. Agencies should plan campaigns assuming custom variables are global to all leads.
What is the key takeaway for agencies?
Multi-customer campaigns in Smartlead require careful planning: isolate campaigns, manage variables carefully, and deduplicate leads to avoid message errors.