Setting Up for Website Ads




Prerequisites are in place. Your Dataset ID is ready. Your telecrm account is set up. Now it's time to bring it all together.

In this video, we'll go through the complete configuration of the Meta Conversions API for Website Ads— step by step.

We'll cover two phases —

Phase 1 — Setting up your Dataset on Meta and generating your Access Token and Endpoint URL.

Phase 2 — Connecting it all inside telecrm by creating the API Template, mapping your Facebook Lead ID, adding the payload, and testing the integration end-to-end.

By the end of this video, your telecrm and Meta will be talking to each other. 


Now let's get into the steps:

PHASE 1: Set Up Your Dataset on Meta


STEP 1 — Log In to Meta Business Manager

1. Open a new browser tab and go to business.facebook.com. Sign in to your account.

2. From the left-hand menu — navigate to Events Manager and click on Connect Data.


STEP 2 — Create or Select a Dataset

3. A window will appear asking you to connect a new data source. Select CRM from the list and click Next.

If you already have a dataset, select it from the dropdown list.

If you don't have one yet, click Create New Dataset and give it a name.


STEP 3 — Choose Manual Connection

4. On the next screen, click on Connect Manually.

5. Select "Do the code manually yourself" — this is the recommended option as it gives you full control over the connection.

6. Click Next.


STEP 4 — Generate Your Access Token and Endpoint URL

7. You will land on a new page. Scroll down to the Create Endpoint section and click on Generate Access Token.

8. Once generated, you will see your unique Endpoint URL.


⚠️ Critical — Copy and store both your Endpoint URL and Access Token immediately and securely. Meta will NOT display the Access Token again once you leave this page.

Now open telecrm web application, go to Automations. Click on API Templates and then click on Create New.

Give a template name. 


STEP 4 — Add the Payload


15. Click on the Body tab and paste the JSON payload template based on your lead generation type.

Endpoint URL —

https://graph.facebook.com/v23.0/{{Instant_Form_Dataset_ID}}/events?access_token={{Dataset_Access_Token}}

Payload —

json

{
  "data": [
    {
      "action_source": "website",
      "custom_data": {
        "event_source": "crm",
        "lead_event_source": "telecrm",
        "fbclid": "{{map your facebook click id}}"
      },
      "event_name": "{{status}}",
      "event_time": "{{$date({{now,seconds}})}}",
      "user_data": {
        "em": ["{{$hash({{Email}})}}"],
        "ph": ["{{$hash({{Phone}})}}"],
        "ct": ["{{$hash({{City}})}}"],
        "country": ["{{$hash({{country}})}}"]
      }
    }
  ]
}


This payload is for leads coming from Website Ads — where the lead clicked your Facebook Ad and filled a form on your website before landing in telecrm. 

The action_source is set to "website," identifying that the conversion originated from a website visit

Instead of a lead_id, you are passing the fbclid (Facebook Click ID) — this is the unique identifier automatically appended to your website URL when a lead clicks your Facebook Ad. Make sure this is being captured and stored in telecrm as a lead field so it can be mapped here correctly.

All other user_data fields — hashed email, phone, city, and country — remain the same as the Instant Form payload


STEP 6 — Test Your Setup


Before going live, always test the integration first.

17. Before going live, always test the integration first. Fill in the test variables below —

Facebook Click ID (fbclid) — The unique Click ID that is automatically appended to your website URL when a lead clicks your Facebook Ad. This must be captured and stored in telecrm as a lead field before testing.

Status — The event name you are sending, for example, Lead or AppointmentBooked

Now, seconds — The current Unix epoch time. You can get this from epochconverter.com

Email — The test lead's email address

Phone — The test lead's phone number

City — The test lead's city

Country — The test lead's country

18. Click Test Template.

19. Navigate to the Response Mapper and add the following two JSON paths —

events_received

fbtrace_id

20. Click Save Mapping.

If the test is successful — you will see a confirmation response from Meta confirming the Website conversion event has been received. Your Website Ads CAPI integration is now live.


And that's the complete Meta Conversions API setup for Website Ads. Meta is no longer flying blind. It now has real, accurate, CRM-level conversion data to work with.

This was a one-time setup. But the impact it creates runs forever.