Step 1: Implement Conversion Leads Integration

1. You should be redirected to a Zapier template for your selected CRM. If your CRM does not have a template, create a new Zap from scratch.


2. We'll assume Zap creation from scratch to cover all steps.
   Choose your CRM app as the first app (trigger). Choose the Facebook Conversions app and Send Funnel Event action as the second app (action).


3. You will need to create Zap(s) for when:
   1. New leads are added to your CRM from Meta.
   2. Leads status change and progress further into your sales process.
4. In this example, we will send a funnel event from Hubspot to Meta whenever a contact's status changes. This Zap will send event updates when the lead status changes. Later, you will need to create a second Zap to send events when new leads are added to your CRM.
   


5. First, let's set up the trigger app (HubSpot, in this case). During the setup steps, ensure you select the appropriate CRM and trigger events, and connect your CRM account to Zapier. In this example, we choose the New Contact Property Change event to send an event when the property changes.
   


6. Then, click Continue, select the property that will trigger Zapier to send an event when the property changes. In our Hubspot example, Zapier will send an event when the Lifecycle Stage property changes in Hubspot.
   
   Zapier will only integrate a select number of properties by default for some CRMs. You may add additional properties to integrate if the default selection does not include all relevant properties.
   
   In our example, since we have stored the Facebook lead ID in our manually added properties in Hubspot, we can retrieve it through additional properties.
   


7. In the action app, ensure that the Facebook Conversion app and Send Funnel Event action event are chosen, and connect your Facebook account.
   


8. Click Continue, connect your Facebook account and choose your CRM pixel (datasource).


9. Fill in all fields in the Set up action section of the action app.
   1. Time of customer event — A Unix timestamp that represents when this event has been updated in your CRM. If you cannot find an applicable field in your CRM, you can leave this parameter empty and Zapier will use the upload time.
   
   
   2. Stage in Sales Process — Refers to a lead moving through the sales funnel in your CRM. Make sure to send all stages as they are updated, including the initial raw lead stage. We will use Hubspot's Lifecycle Stage property to represent this.
      
      For example, your funnel could look like this:
      1. Raw Lead from Meta
      2. Marketing Qualified Lead
      3. Sales Opportunity
      4. Customer
      If a lead reaches the final Customer stage, then the previous 3 stages should have been sent as they occurred.
   
   
   3. CRM you use — The name of your CRM. This could be a static text like "Hubspot".
   
   
   4. Customer information parameter — The field containing the customer information parameter for your downloaded leads. Please send as many parameters as you can for better ad performance.
   
   
   5. Facebook Lead ID — We recommend sending the Facebook lead ID for best performance. Note that in the case of Hubspot, there is no Facebook lead ID field by default. However, since we retrieved the additional property of lead ID in step 6, we can map it to the Facebook lead ID field. Please refer to the How to Find the Meta Lead ID documentation.
      


10. Review the Zap to verify the correct data is pulled into the parameters. If everything appears correct, send a test event to Meta by clicking the test button.
    
    Publish the Zap to begin sending events if the test is successful.
    


11. Repeat from Step 3 above if you need to create additional Zaps for when:
    • New leads are added to your CRM from Meta.
    • Leads status change and progress further into your sales process.
12. If you receive the Sample error 1 below, you either can choose to connect Zapier using the Meta Events Manager onboarding flow (see this Business Help Center article⁠ for more). Or, if you prefer, you can can connect from the Zapier side by opening the datasource permission:
    
    Datasource -> Setting -> Conversions API -> Choose a partner -> Zapier -> Turn on permission
    
    Sample Error 1
    
    Steps to follow to resolve error:
    
    
    

Sample error 2

Error - No customer information parameter, or a combination of customer information parameters that is too broad.

Please make sure there’s at least one customer information parameter chosen on the mapping sessions.

Also, if you choose to use the field mapping features, make sure the field has actual data attached to pass the test action. Screenshots below show error field mapping versus correct field mapping.