We use cookies to measure how the site is used and to measure our ads. You can accept all or reject the non-essential ones. Privacy policy
Your client opens Ads Manager and sees one number. Their shop or CRM shows another. You lose the call explaining the gap. GetAttrib records the first ad that brought each visitor, then matches the lead or payment to that visit, so your report says which campaign, ad set and ad earned the result.
Meta can count a sale when someone only saw an ad. The client counts what actually arrived in Stripe, their store or their forms. The two lists argue, and you are in the middle.
Pulling spend from one place, leads from another and sales from a third into a sheet is slow, and it is wrong the moment someone edits a cell.
If the pixel counts form fills that never turn into customers, Meta finds more people like them. It cannot learn from sales it never hears about.
Each client gets its own tracking script, numbers and settings, so one client never sees another's data. Free covers 1 website, Starter up to 5, Pro unlimited.
Every lead is listed under the Meta ad set that brought it, next to spend, cost per lead, sales and revenue. It updates as leads and payments arrive.
See which ad sets bring people who buy, and how long they take, so you know how long to wait before judging an ad.
On paid plans, confirmed sales go back to the client's Meta pixel through the Conversions API, so the algorithm learns from real buyers.
A visitor clicks the client's Meta ad (campaign: Spring Offer, ad set: Homeowners 35+). GetAttrib records the first visit.
The same visitor returns from a Google search and submits a form. The lead is stored with the Day 1 ad as its source.
A $1,800 payment arrives in Stripe. GetAttrib matches it to the visitor and credits the Day 1 ad set.
Example only. The names and amounts are made up to show how a journey reads.
Free to start. Paste one script on your site and connect your tools.