Campaign Settings
Configure shared campaign access, customer authentication, link behavior, domains, and post-payment destinations.
How this fits into Lead360Explore the white label platformDeliver branded customer experiences and campaign destinations for client businesses.- 01
How Lead360 helps
- 02
Choose the access method
- 03
Configure the customer entry flow
- 04
Set destinations carefully
How Lead360 helps
Campaign Settings defines shared defaults and controls that shape how campaigns appear, run, and connect with the customer app. Central settings help teams keep identity, timing, destinations, and measurement consistent across multiple campaign records.
When to use this area
Use Campaign Settings before launching campaigns at scale or when a shared campaign behavior must change for the sub-account.
Before you begin
- Document the current behavior and the intended new default.
- Identify active campaigns and customer destinations that could be affected.
- Confirm timezone, branding, tracking, and integration dependencies.
Choose the access method
- Use Customer App login when campaigns should reuse the shared signed-in app session.
- Use public access only for content intended for anyone with the link.
- Use a form gate when contact capture is required before entry.
- Use Campaign OTP login for verified campaign access, or secure invite when each recipient needs a controlled invitation.
Configure the customer entry flow
- Review signup, sign-in, verification, and welcome copy for clarity and brand consistency.
- Confirm which customer details are required, where verification is delivered, and what an expired or invalid link should show.
- Use a verified domain and keep a working fallback until DNS and HTTPS checks succeed.
Set destinations carefully
- Choose the default or full post-payment redirect URL only after the checkout destination is ready.
- Confirm campaign links, check-in links, service-menu destinations, login state, and mobile behavior.
- Because these settings can affect several campaigns, test existing customer paths before and after saving.
Use Ask360 here
Ask360 can explain the current campaign settings and prepare one reviewed setting change when supported. It waits for Accept and never publishes campaign content, sends an invite or OTP, processes payment, handles credentials, or claims a customer flow passed before a controlled test.
Confirm the result
A completed Campaign Settings workflow should be visible in the product area that owns the final record. Use these checks before relying on the result or moving to the next customer-facing step.
- Test the change with a draft or controlled campaign.
- Preview customer-facing output and internal reporting.
- Review active campaigns to make sure a shared default did not alter an existing commitment.
Troubleshooting
A campaign ignored the new setting
Check whether the campaign has its own override, was already published, or uses a different customer destination.
A shared change affected active content
Restore the prior value if appropriate, then review each dependent campaign before republishing.
Frequently asked questions
What should I confirm before using Campaign Settings?
Document the current behavior and the intended new default. Identify active campaigns and customer destinations that could be affected. Confirm timezone, branding, tracking, and integration dependencies. Start with a small, reviewable change whenever the workflow can affect customers, money, published content, or shared records.
How does Lead360 help with Campaign Settings?
Campaign Settings defines shared defaults and controls that shape how campaigns appear, run, and connect with the customer app. Central settings help teams keep identity, timing, destinations, and measurement consistent across multiple campaign records.
Continue with Lead360
Use this workflow in Lead360
Put this guide into practice with a 14-day free trial of Lead360 Pro early access, or continue learning through the related collection.
Support