Software Services
For Companies
Products
Build AI Agents
Security
Portfolio
Build With Us
Build With Us
Top Software Developer
2026 Clutch Ranking
Top App Developer
2026 BusinessofApps
Connect Your Ad Spend
to the Revenue
It Actually Brings In
Ad platforms count leads. Your CRM knows which leads paid. Slashdev builds the connection between the two: we keep the click ID with every lead, send closed deals and their value back to Google Ads and Meta, and give you revenue by campaign. We build it for you, on the CRM you already use.
How do I connect ad spend to actual revenue?
Keep the ad platform's identifier on every lead, record each lead's stage and deal value in your CRM, and send those outcomes back to the ad platform. For Google Ads, that means storing the Google Click ID (GCLID) from a hidden form field and importing offline conversions, or using enhanced conversions for leads, which adds hashed email and phone to the match. For Meta, it means the Conversions API, which accepts events from your server or CRM; leads from Meta Lead Ads carry a Meta Lead ID you can store. Once outcomes flow back daily, you can report revenue by campaign and let the platforms bid toward customers who pay, not form fills.
- Google Ads
- Offline conversion import with GCLID, or enhanced conversions for leads (hashed email and phone). New implementations use the Data Manager API.
- Meta
- Conversions API from your server or CRM, alongside the Meta Pixel, deduplicated by event name and event ID
- Data you need
- Click ID or Meta Lead ID, email or phone, CRM stage with a timestamp, deal value and currency
- Upload windows
- Google: up to 90 days after the click with a GCLID, 63 days for conversions keyed by user data. Meta Conversions API events: up to 7 days old.
- Who builds it
- Slashdev builds the connection for you, on your CRM and ad accounts
The Data That Makes Attribution Work
Four pieces of data, captured at the right moment. Most gaps we find are a missing click ID, not a missing tool.
An identifier from the ad
For Google Ads, the GCLID, captured in a hidden form field with auto-tagging turned on. For Meta Lead Ads, the 15 to 17 digit Meta Lead ID. Without one of these, matching falls back to email and phone.
Contact details the person gave you
Email and phone from the form. Google and Meta both require these to be hashed before upload; Google specifies SHA-256 after normalizing, with phone numbers in E.164 format.
Stage changes with timestamps
When a lead becomes qualified, booked or won, and when it happened. Google's Salesforce import, for example, reads the time from the field history of the stage that changed.
Deal value and currency
The amount the customer paid or signed for, so the platforms report revenue and not only a count of conversions.
Send only the data each platform documents, from people who gave it to you. If you are a medical practice or handle health data, use the healthcare version below: there, patient data never goes to ad platforms.
Revenue by Campaign, Not Leads by Campaign
Ad reports stop at the form fill. Your CRM knows what happened next. We connect the two.
Revenue by Campaign
Closed revenue traced back to the Google and Meta campaign that brought each customer in.
- Cost per qualified lead and per customer
- Revenue and deal count by campaign
- Leads that never closed, by source
- Same definitions across channels
Google Ads Offline Conversions
GCLID capture, enhanced conversions for leads and daily uploads, set up through the Data Manager API that Google now requires for new implementations.
- Hidden GCLID field on every form
- Hashed email and phone, normalized first
- One conversion action per CRM stage
- Conversion value and currency
Meta Conversions API
Server events next to your Meta Pixel, and CRM events for leads from Meta Lead Ads.
- Deduplicated with event name and event ID
- Meta Lead ID stored in your CRM
- Hashed customer details
- Every lead stage sent as it changes
CRM-to-Ads Feedback Loop
Stage changes in your CRM become conversions in the ad platforms, so bidding learns from customers who pay.
- Salesforce, HubSpot or a custom CRM
- Qualified, booked and won stages
- Uploads at least daily
- Errors logged and retried
One Revenue Dashboard
Ad spend from Google and Meta next to pipeline and revenue from your CRM, refreshed automatically.
- Spend, pipeline and revenue together
- By campaign, channel and month
- No spreadsheet to reconcile
- Access by role
Works With Your Agency
Your agency or in-house team keeps running the campaigns. Everyone gets numbers based on revenue.
- No need to replace your CRM
- No need to replace your agency
- You own the accounts and the code
- Documented so your team can run it
From Ad Click to Closed Revenue
Four steps. The timings below are the ones Google and Meta document; our build time is scoped on the free review.
Audit the Data Path
We check auto-tagging, your forms, your CRM fields and your conversion actions, and find where the click ID or Lead ID is being lost.
Capture Identifiers on Every Lead
The GCLID goes into a hidden form field and onto the CRM lead; Meta Lead IDs are stored with the lead. Google asks you to wait 4 to 6 hours after creating a new conversion action before uploading to it.
Send Outcomes Back
Stage changes and deal values go to Google Ads and Meta at least daily. Google says imported conversions take up to 3 hours to appear for last-click attribution, longer for other models.
Report and Move Budget
You see revenue by campaign next to spend. For Meta's CRM optimization, Meta estimates about one month to value, including a learning phase of 2 to 4 weeks.
Your Ad Accounts on One Side. Your CRM on the Other.
Keep your CRM as the record of who paid. We build the layer that tells the ad platforms.
Every Lead Keeps the Ad That Found It
Forms pass the GCLID and campaign data to your CRM. Leads from Meta Lead Ads keep their Meta Lead ID.
- Hidden GCLID field on every form
- Meta Lead ID stored on the lead
- Campaign and source fields
- Email and phone for matching
// Keep the click ID with the lead
const lead = await crm.createLead({
email, phone,
gclid: form.hidden.gclid, // Google Ads
metaLeadId: form.metaLeadId, // Meta Lead Ads
source: utm,
});Each Stage Change Becomes a Conversion
We map your pipeline to conversion actions: qualified, booked, won. Each change is recorded with its time and value.
- Stages mapped to conversion actions
- Timestamps from the CRM
- Deal value and currency
- Works on Salesforce, HubSpot or custom
// When the deal moves, record the stage
crm.on('stageChanged', (deal) => queue.push({
leadId: deal.leadId,
stage: deal.stage, // e.g. 'Closed Won'
value: deal.amount,
currency: deal.currency,
occurredAt: deal.changedAt,
}));Outcomes Back to Google and Meta, Daily
Google Ads receives conversions through the Data Manager API; Meta receives events through the Conversions API. Contact details are hashed first.
- Google Data Manager API
- Meta Conversions API
- Hashing and normalization
- Deduplication with the Pixel
// Daily: send outcomes back to each ad platform
await googleDataManager.upload(conversions, {
identifiers: ['gclid', 'sha256(email)', 'sha256(phone)'],
});
await metaConversionsApi.send(events, {
dedupe: ['event_name', 'event_id'],
});Ad Revenue Attribution Questions
How do I see which ads bring in revenue, not just leads?
Connect three things: the ad identifier on each lead, the lead's outcome in your CRM, and the deal value. Store the GCLID (Google) or Meta Lead ID with the lead, record stage changes and amounts in the CRM, then send those outcomes back to Google Ads and Meta at least daily. Revenue by campaign then shows in the ad platforms and in your own dashboard.
What is Google Ads offline conversion import?
It lets you record what happens after an ad click, such as a qualified lead or a signed contract, in Google Ads. Google gives each ad click a Google Click ID (GCLID). You store it with the lead, then import the conversion with its time and value. Auto-tagging must be on. Google's guidance is to upload at least daily, and it keeps the GCLID for 90 days.
What are enhanced conversions for leads?
Google describes them as an upgraded version of offline conversion import that uses data people gave you, such as email addresses. Your site sends hashed lead details when the form is submitted, and you later import conversions with the same hashed details. Google still recommends including the GCLID whenever you have it. Conversions keyed by user data can be uploaded up to 63 days later.
What is the Meta Conversions API?
Meta's way to send events from your own server, website platform, app or CRM to Meta, for measurement and optimization. It works alongside the Meta Pixel; when both send the same event, Meta deduplicates them using the event name and event ID. Events can be sent up to 7 days after they happen.
Can I send CRM stages from Salesforce or HubSpot back to Google Ads and Meta?
Yes. Google Ads can import Salesforce stage changes, such as an opportunity becoming Closed Won, when a GCLID field is on the lead and opportunity. Google's Data Manager also lists HubSpot as a source. For Meta, the Conversions API for CRM takes lead stages for leads from Meta Lead Ads; Meta lists at least 200 leads a month, daily uploads, and a target stage within 28 days of the lead with a 1% to 40% conversion rate. For a custom CRM, we build the uploads directly.
What data do I need for ad revenue attribution?
An identifier from the ad (GCLID or Meta Lead ID), the email or phone the person gave you, each stage change with a timestamp, and the deal value with its currency. Email and phone are hashed before they are sent; Google specifies SHA-256 after normalizing, with phones in E.164 format.
How long does it take to set up?
The platform side has documented clocks: Google asks you to wait 4 to 6 hours after creating a conversion action before uploading, imported conversions take up to 3 hours to appear for last-click attribution, and Meta estimates about one month to value for CRM optimization, including a 2 to 4 week learning phase. Our build time depends on your forms, CRM and channels, and we give you a scoped estimate after the free review.
How late can a conversion be sent?
Google Ads: up to 90 days after the click for GCLID conversions, and up to 63 days for conversions keyed by user data. Meta Conversions API: up to 7 days after the event. If your sales cycle is longer, send an earlier stage, such as a qualified lead or booked meeting, as its own conversion.
Is it safe to send customer data to ad platforms?
Send only what each platform documents, hashed where they require it, and only for people who gave you their details. Google and Meta both require email and phone to be hashed. Check your privacy policy and consent setup with your counsel before turning uploads on.
Does this work for medical practices?
Medical practices need a different design, because patient data must not go to ad platforms. See our eClinicalWorks marketing attribution page (/eclinicalworks-marketing-attribution) and EHR integrations hub (/ehr-integrations): matching runs server-side in a HIPAA-covered environment under a signed BAA.
Who can build this for me?
Slashdev is a software consultancy that builds ad revenue attribution for you: form and CRM capture, uploads to Google Ads and Meta, and the revenue dashboard. We have also built our own products in this space, such as Parabolic Growth (https://www.parabolicgrowth.io), an AI sales agent that follows up with and qualifies inbound leads, and SlashCRM (https://slashcrm.io), the CRM we run our own sales on.
How much does it cost?
The review is free. Managed development starts from $75 per hour, and we give you a scoped estimate after the review, based on your forms, CRM and channels.
Google and Meta Documentation We Used
Vendor pages behind the facts above. Windows, delays and eligibility change, so check them for current terms.
- About offline conversion importsGoogle Ads Help. GCLID, and the move of uploads to the Data Manager API.
- About enhanced conversions for leadsGoogle Ads Help. Upgraded offline import using user-provided data; include GCLIDs when possible.
- Set up offline conversions using Google Click ID (GCLID)Google Ads Help. Hidden form field, auto-tagging, 4 to 6 hour wait, Salesforce and HubSpot in Data Manager.
- Offline conversion imports FAQsGoogle Ads Help. GCLID kept 90 days, 63 days for user-data conversions, upload at least daily.
- Manage offline conversionsGoogle Ads API docs. Data Manager API for new implementations, SHA-256 hashing and E.164, up to 3 hours to appear.
- How to set up a Salesforce integrationGoogle Ads Help. Stage-based conversions such as Closed Won, GCLID fields on Lead and Opportunity.
- Conversions APIMeta for Developers. Server, website, app and CRM events; works with the Meta Pixel.
- Conversions API: server event parametersMeta for Developers. event_time up to 7 days old, deduplication with event_name and event_id.
- Conversions API: customer information parametersMeta for Developers. Which fields must be hashed; lead_id, fbc and fbp are not hashed.
- Conversions API for CRM integrationMeta for Developers. Lead Ads eligibility, Meta Lead ID, estimated time to value.
Vendor documentation checked on November 19, 2026.
See Which Ads Actually Bring Revenue
Book a free review. We'll look at your forms, your CRM and your ad accounts, and tell you where the revenue signal is being lost.
About
Global Hubs
Engineering Skills
Social Media


@2026 slashdev.io