Why this integration matters
- Prevents manual URL mistakes during content scheduling.
- Keeps campaign tracking consistent across every post and channel.
- Makes reporting cleaner because naming and UTM structure are standardized.
How it works
- Your scheduler workflow sends destination URL + metadata to LeadPulse.
- LeadPulse returns a short link for that campaign context.
- The scheduler publishes the short link in the post caption or bio link slot.
- Clicks are tracked in LeadPulse with source/referrer/device context.
Prerequisites
- A working LeadPulse workspace and at least one verified domain (recommended).
- A LeadPulse API key with link creation permissions.
- A scheduler that supports API calls, webhooks, or automation connectors.
Step-by-step setup
- Generate and securely store your LeadPulse API key.
- In your scheduler, create a pre-publish automation step that requests a LeadPulse short link.
- Map post fields to campaign metadata (source, medium, campaign, content).
- Insert the returned short URL into the final post payload.
- Publish one controlled test post per channel.
Validation checklist
- Scheduled post contains the LeadPulse short URL (not the original long URL).
- Click event appears in LeadPulse with expected campaign tags.
- Referrer and device data are visible for test clicks.
Common failure points
- API key missing scopes or expired.
- Inconsistent UTM mapping across different social profiles.
- Fallback to long URLs when automation fails silently.