Jump to a popular page, or start typing.
    Talk to our team

    CONNECTIONS / Close / Close to Meta Conversion Leads

    Close smart-view opportunities into Meta, built for Meta Conversion Leads bidding.

    Signals reads your Close smart-view opportunities through scoped OAuth access to Close, reading only your Close smart-view opportunities, then reports lead-stage progress so Meta bids toward qualified pipeline so Meta sees lead conversions without an export.

    Talk to our team Explore the setup

    close -> meta-capi-crm :: live

    1. ● close → meta.leads :: live
    2. > read lead_pipeline rows=42,245
    3. hash sha256(email,phone) consent=filtered
    4. route meta deliver
    5. ✓ delivered · 36,753 matched

    WHAT THIS ENABLES

    Close to Meta CAPI for CRM

    Close to Meta CAPI for CRM: your Close smart-view opportunities, hashed and consent-checked, feed Meta as Signals reports lead-stage progress so Meta bids toward qualified pipeline as records change.

    • Signals reports lead-stage progress so Meta bids toward qualified pipeline, reading your Close smart-view opportunities as records change.
    • Bids weighted to revenue-grade lead stages, with no export step out of your Close smart-view opportunities.

    WHAT FLOWS WHERE

    Close to CAPI for CRM, mapped.

    Each sync hands the qualified-lead and pipeline signals from your Close smart-view opportunities to Signals, which hashes and filters every record, then Meta's Conversion Leads API logs the lead conversions for lead-stage selection.

    Each sync hands the qualified-lead and pipeline signals from your Close smart-view opportunities to Signals, which hashes and filters every record, then Meta's Conversion Leads API logs the lead conversions for lead-stage selection.

    WHO THIS IS FOR

    Built for the teams that own the number.

    Meta lead-gen advertisers whose lead quality swings more than volume, working out of Close leads, calls, and smart-view opportunities.

    Inside-sales teams running Close who need Meta bidding tuned to the lead stages that become revenue out of Close smart-view opportunities.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      Scoped OAuth access to Close, reading only your Close smart-view opportunities, mapped to Meta's Conversion Leads API and tuned for lead-stage selection.

    2. Map

      Columns from your Close smart-view opportunities align to Meta's Conversion Leads API in the visual mapper, hashed as the sync runs and checked for lead-stage selection.

    3. Deliver

      As records change, Signals reads your Close smart-view opportunities and reports lead-stage progress so Meta bids toward qualified pipeline, sends only the records that changed, with lead-stage selection watched in the debugger.

    WHAT YOU GET

    What ships with this use case.

    Meta bidding tuned to the lead stages that become revenue from your Close smart-view opportunities, delivered as records change.

    Bids weighted to revenue-grade lead stages out of your Close smart-view opportunities, delivered as records change without API call volume climbing.

    Match feedback on lead-stage selection from Meta's Conversion Leads API each run, tied back to your Close smart-view opportunities.

    ON THE WIRE

    What CAPI for CRM actually receives.

    signals :: close.meta-capi-crm :: wire

    1. ● signals :: event payload
    2. > POST /conversion_leads source=close.lead_pipeline
    3. event_name "Purchase" · value 4249 AED
    4. em sha256 "6f2a91…" · ph sha256 "d40c7e…"
    5. lead_id "lsh_92716" · action_source "system_generated"
    6. ✓ accepted pii=hashed-at-ingestion
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Close

    Close to Google EC for Leads

    Close to Google EC for Leads: your Close smart-view opportunities, hashed and…

    Learn more

    from Close

    Close to TikTok CRM

    Close to TikTok CRM Integration: your Close smart-view opportunities, hashed and…

    Learn more

    same use case

    ActiveCampaign to Meta Conversion Leads

    ActiveCampaign to Meta CAPI for CRM: Signals reads your ActiveCampaign contacts and deal…

    Learn more

    generic

    Meta CAPI for CRM

    Datahash ingests lead status from your CRM and sends Meta the qualified events it needs to…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the Close Meta Conversion Leads sync run?

    The pace follows your Close smart-view opportunities: Signals sends changes from Close to Meta as records change. Because it sends only the records that changed, Meta bidding tuned to the lead stages that become revenue stays current while inside-sales teams running Close keep lead-stage selection in view. Delivery needs no export and no manual upload.

    What match rate should a Close-sourced Meta Conversion Leads batch expect?

    In Close, match rate tracks the email and phone quality your Close smart-view opportunities carry. Clean identifiers land for Meta; blank ones never will. The first Conversion Leads API report shows inside-sales teams running Close where lead-stage selection needs work, a data-quality task handled in Close.

    NEXT STEP

    Close to Meta Conversion Leads, in production this week.

    Talk to our team All Close use cases