Meta Ads
Spend, delivery, and Meta reported conversions show the Meta Ads side of the question.
How to connect Meta AdsMeta Ads + Salesforce
Are Meta leads becoming qualified Salesforce pipeline?
Connect Meta Ads and Salesforce to Hendrik. Check whether Meta Ads lead reporting is reflected in Salesforce qualified opportunity movement.
See Hendrik at work
Meta Ads + Salesforce review
Previous: 1–28 January. Current: 29 January–25 February. Both periods contain 28 days. Monetary values use USD and all timestamps use UTC. The example compares acquisition measures with CRM deal progression. A submitted lead and a qualified deal are different events, with different reporting dates.
| Metric | Previous | Current |
|---|---|---|
| Meta AdsReported lead conversions · selected Lead form submitted action (count, 28 days) | 210 | 260 |
| Salesforcequalified opportunities created (count, 28 days) | 28 | 24 |
| Meta Adsspend (USD, consecutive 28-day periods) | 21,000 USD | 26,000 USD |
What Hendrik checks
Attribution and delivery mix
Check Meta attribution setting, conversion event, placements, audiences, and creative delivery before interpreting reported outcomes.
Opportunity and campaign definition
Check Salesforce record type, stage history, campaign membership, and identity coverage before using opportunity movement.
Explain the divergence
Meta Ads: Reported lead conversions · selected Lead form submitted action (count, 28 days) changed from 210 to 260. Salesforce: qualified opportunities created (count, 28 days) changed from 28 to 24. Compare the timing and definitions before attributing one change to the other.
About this example Synthetic data · Illustrative analysis · Changes require your approval.
How Hendrik handles your dataWant Hendrik to answer this with your data?
One analysis, different integrations
What each integration adds
Salesforce
Leads, opportunities, stages, and campaign membership show whether paid leads become qualified opportunities.
How to connect SalesforceConnect your stack
Set up each integration in one workspace.
- Create your Hendrik account. Choose a workspace for your business.
- Connect your data. Use each integration’s setup instructions above. Availability and permissions are shown in your workspace.
- Ask your first question. Hendrik uses the available data and tells you when a comparison needs more history or more data.
Requirements and data limits
What you need
- Use one explicit 28-day comparison window, time zone, market, and legal-entity scope before comparing values.
- Connected Meta Ads account with delivery and conversion reporting for the stated window.
- Connected Salesforce org with agreed lead, opportunity, and stage definitions.
- Keep provider-specific definitions visible and use an identity or product mapping only where it is established for this workspace.
Keep these differences in mind
- Meta attribution remains separate from store, payment, or CRM outcomes; do not sum it with another platform’s conversion value.
- CRM campaign and opportunity records require an established identity relationship before attribution claims.
- Meta leads and Salesforce opportunities are separate records unless a relationship is established.
Your data. Your next step.
Put Hendrik to work on your stack.
Create your account, choose your workspace and connect your data.
See plans and pricing