Meta Ads CRM Sync

Sync Meta Ads company visit data directly into your CRM. Fibbler creates custom properties on company and account records showing how many times they've visited your website from your Facebook and Instagram ads, so your sales team can see engagement data without leaving the CRM.

Supported CRMs

  • HubSpot: syncs to company records
  • Salesforce: syncs to account records
  • Attio: syncs to company records
  • Pipedrive: syncs to organization records

Global sync

Global sync creates CRM properties that track website visits across all your Meta campaigns. You can enable three rolling windows:

  • 7-day: Website visits in the last 7 days
  • 30-day: Website visits in the last 30 days
  • 90-day: Website visits in the last 90 days

Toggle each window on or off depending on your needs. Fibbler will automatically create the corresponding CRM properties when you enable a window.

Global sync properties are named:

  • HubSpot: fibbler_meta_ads_visits_7_days, fibbler_meta_ads_visits_30_days, fibbler_meta_ads_visits_90_days
  • Salesforce: fibbler_meta_visits_7_days, fibbler_meta_visits_30_days, fibbler_meta_visits_90_days
Salesforce uses the shorter meta stem because Salesforce custom field API names are capped at 40 characters. Attio and Pipedrive get equivalent fields, created for you when you enable a window.

Campaign-specific sync

For more granular data, create campaign-specific sync groups. Each group:

  1. Has a custom name (e.g., "Retargeting" or "Prospecting")
  2. Includes one or more Meta campaigns
  3. Syncs visit counts for the intervals you choose (7d, 30d, 90d)

Campaign-specific sync properties are named:

  • HubSpot: fibbler_meta_ads_7d_vis_abc123 with a display name like "Meta Ads Visits (7 days) - Retargeting"
  • Salesforce: fibbler_meta_7d_vis_abc123__c
Campaign-specific sync depends on the utm_id parameter on your Meta ads, which is what tells Fibbler which campaign a visit belongs to. Without it a visit still counts toward the global windows, but cannot be attributed to a campaign group. See Add the required URL parameters.

Use cases

  • CRM reporting: Build reports showing how Meta Ads influences pipeline and revenue over time
  • Account scoring: Use the visit count properties as signals in your account scoring model
  • Outbound workflows: Trigger outbound sequences when a company visits from Meta Ads
  • Sales context: Give your sales team visibility into Meta Ads engagement before they reach out