Use case
Credit every lead and sale to the post or ad that earned it
- Clicked a campaign linkspring-webinar from YouTubeOct 14 · 7:02 PM
- Registered for the webinarRegistration form · contact createdOct 14 · 7:03 PM
- Attended liveSpring webinar · attendance recordedOct 16 · 8:00 PM
- Bought Foundations6 payments plan · first payment$165.00Oct 16 · 9:12 PM
- Purchase sent to MetaMatched to the same visitOct 16 · 9:12 PM
The problem
What gets in the way
Ad platforms see clicks, the CRM sees leads, and the payment app sees revenue. Without a shared record, the budget goes to whatever looks cheapest.
What you get
What changes in your workspace
Campaign links with views, visitors, leads, customers and revenue
Channels report for first-touch visitors and revenue
A Meta event per form, sent from browser and server once
Purchases sent to Meta, with a log you can retry and export
Product flow
How it fits together
Each step happens in the same workspace, on the same contact record.
- Step 01
Mint a campaign link for each post, ad or partner.
- Step 02
A visitor converts on a form, and first touch is saved on the contact.
- Step 03
Their purchase is credited back to the link and channel.
- Step 04
With tracking on, Meta receives the form event and the purchase.
In the product
See it in Planeward

What you use
The modules behind it
- See which post, ad or partner brought each lead and each sale.
- Publish sites, landing pages and funnels on your own domain, with your forms built in.
- Turn every form submit into a contact, a deal and a tracked lead.
- Sell one-time, recurring and payment-plan offers on your own domain.
Questions
Straight answers
Still unsure? Create your workspace and look around.
Business and Agency, as part of Sites.
Yes. Record the purchase through the API or MCP, and it can be sent to Meta. Repeating it with the same reference is safe.
Run the whole business from one workspace.
Projects, CRM, checkout, community, sites, email and workflows in one workspace, with AI built in.
