{"id":1611,"date":"2026-03-26T10:43:38","date_gmt":"2026-03-26T10:43:38","guid":{"rendered":"https:\/\/apte.ai\/news\/?p=1611"},"modified":"2026-03-26T10:43:38","modified_gmt":"2026-03-26T10:43:38","slug":"server-side-tracking-meta-ads-conversions-api","status":"publish","type":"post","link":"https:\/\/apte.ai\/news\/2026\/03\/26\/server-side-tracking-meta-ads-conversions-api\/","title":{"rendered":"Server Side Tracking for Meta Ads Using Conversions API Setup Guide"},"content":{"rendered":"

Why server side tracking matters for Meta ads<\/h2>\n

Client side pixel code can be blocked by browsers, ad blockers or privacy settings, which leads to missing conversion data. Server side tracking sends events directly from your backend to Meta, bypassing the user\u2019s browser and ensuring that every purchase, lead or sign\u2011up is recorded even when the pixel cannot fire.<\/p>\n

When the data arrives through a trusted server connection, Meta can apply more accurate matching, improve attribution and give you a clearer view of return on ad spend.<\/p>\n

Core components of a Conversions API integration<\/h2>\n

Three pieces work together to move event data from your system to Meta:<\/p>\n

1. Event source<\/h3>\n

This is the part of your stack that knows when a conversion happens \u2013 for example an e\u2011commerce order service, a CRM webhook or a subscription platform.<\/p>\n

2. Data connector<\/h3>\n

The connector formats the event data to match Meta\u2019s schema and makes an HTTPS request to the Conversions API endpoint. Connectors can be built in\u2011house, deployed as a cloud function or provided by a partner platform such as Shopify, Segment or Zapier.<\/p>\n

3. Access token and Business ID<\/h3>\n

Meta authenticates each request with a system user access token that is linked to your Business Manager ID. The token is generated in the Meta Events Manager and should be stored securely on your server.<\/p>\n

Preparing your Meta Business Manager<\/h2>\n

Before any code is written you need to create the assets that will receive the data.<\/p>\n

    \n
  1. Open Events Manager and click Add<\/strong> then Connect Data Sources<\/strong>.<\/li>\n
  2. Select Conversions API<\/strong> and choose the ad account you want to associate the events with.<\/li>\n
  3. Give the data source a descriptive name, for example Server side e\u2011commerce<\/em>.<\/li>\n
  4. Copy the Business ID and the generated access token. Keep the token in a secret manager; do not embed it in client side scripts.<\/li>\n<\/ol>\n

    At this point Meta has provisioned an endpoint URL that looks like https:\/\/graph.facebook.com\/v16.0\/\/events<\/code>. All future requests will target this URL.<\/p>\n

    Mapping event fields to Meta specifications<\/h2>\n

    Meta expects a JSON payload that contains an array of events. Each event must include at least the event name, event time and a user identifier such as email<\/code> or phone_number<\/code>. Optional fields like currency<\/code>, value<\/code> and custom_data<\/code> improve matching quality.<\/p>\n

    Below is a minimal representation of a purchase event:<\/p>\n

    {\n  \"data\": [{\n    \"event_name\": \"Purchase\",\n    \"event_time\": 1701234567,\n    \"user_data\": {\n      \"em\": \"hashedemail@example.com\"\n    },\n    \"custom_data\": {\n      \"currency\": \"USD\",\n      \"value\": 129.99,\n      \"contents\": [{\n        \"id\": \"SKU123\",\n        \"quantity\": 2,\n        \"item_price\": 64.99\n      }]\n    }\n  }]\n}<\/pre>\n
    All user data fields must be SHA\u2011256 hashed before they are sent. Meta provides a helper library for many languages that handles hashing and payload creation.<\/p>\n
    Implementing the server side request<\/h2>\n
    The implementation steps are the same regardless of the programming language you use.<\/p>\n
      \n
    1. Collect the conversion data at the point of sale \u2013 order ID, amount, currency, product SKUs and the user\u2019s email or phone.<\/li>\n
    2. Hash every piece of user data with SHA\u2011256. Do not store the raw values in logs that could be exposed.<\/li>\n
    3. Create the JSON payload following the schema shown earlier. Include event_id<\/code> if you want to deduplicate events that might also be sent by the pixel.<\/li>\n
    4. Issue an HTTPS POST request to the Conversions API endpoint. Set the Content-Type<\/code> header to application\/json<\/code> and add the access token as a query parameter access_token=YOUR_TOKEN<\/code>.<\/li>\n
    5. Check the HTTP response. A 200 status means Meta accepted the event; a non\u2011200 response contains an error object that you should log and retry.<\/li>\n<\/ol>\n
      Below is a concise example in Python using the requests<\/code> library:<\/p>\n
      import hashlib, json, time, requests\n\ndef hash_data(value):\n    return hashlib.sha256(value.strip().lower().encode()).hexdigest()\n\ndef send_purchase(order):\n    payload = {\n        \"data\": [{\n            \"event_name\": \"Purchase\",\n            \"event_time\": int(time.time()),\n            \"user_data\": {\"em\": hash_data(order[\"email\"])},\n            \"custom_data\": {\n                \"currency\": order[\"currency\"],\n                \"value\": order[\"total\"],\n                \"contents\": [{\n                    \"id\": item[\"sku\"],\n                    \"quantity\": item[\"qty\"],\n                    \"item_price\": item[\"price\"]\n                } for item in order[\"items\"]]\n            }\n        }]\n    }\n    url = f\"https:\/\/graph.facebook.com\/v16.0\/{BUSINESS_ID}\/events?access_token={ACCESS_TOKEN}\"\n    response = requests.post(url, json=payload)\n    response.raise_for_status()\n    return response.json()\n<\/pre>\n
      Replace BUSINESS_ID<\/code> and ACCESS_TOKEN<\/code> with the values you saved earlier.<\/p>\n
      Testing and validation<\/h2>\n
      Meta supplies a Test Events tool inside Events Manager. When you send a request with the test_event_code<\/code> parameter, the event appears only in the test view and does not affect real reporting.<\/p>\n
      Run a few test orders and verify that the following details are correct:<\/p>\n