Skip to content

Meta Ads Actions and Conversions

Meta Ads tracks user actions after they interact with an ad. These actions fall into standard events, custom conversions, and Facebook Pixel events.

Standard Actions (actions)

Actions are returned via the actions field in the Insights API. Each action contains:

FieldTypeDescription
action_typestringType of action
valuenumberNumber of actions of this type
1d_clicknumberActions within 1 day after a click
7d_clicknumberActions within 7 days after a click
1d_viewnumberActions within 1 day after a view
7d_viewnumberActions within 7 days after a view

Main Action Types

Action TypeDescription
purchasePurchase on the website
add_to_cartItem added to cart
initiate_checkoutCheckout started
add_payment_infoPayment information added
leadLead form submitted
complete_registrationRegistration completed
view_contentContent viewed
searchSite search performed
contactContacted the business
customize_productProduct customized
donateDonation made
find_locationLocation search performed
scheduleAppointment scheduled
start_trialTrial started
submit_applicationApplication submitted
subscribeSubscription started

Cost of Actions (cost_per_action_type)

The cost_per_action_type field returns the cost of each action type:

json
{
  "cost_per_action_type": [
    {
      "action_type": "purchase",
      "value": "15.50"
    },
    {
      "action_type": "lead",
      "value": "3.20"
    }
  ]
}

Conversion Value (action_values)

The action_values field contains the total value of actions (used to track revenue):

json
{
  "action_values": [
    {
      "action_type": "purchase",
      "value": "1250.00"
    }
  ]
}

Facebook Pixel and Conversions API

Action data comes from two sources:

Facebook Pixel

JavaScript code on the website that tracks user actions in the browser. Data is transmitted automatically when the page loads.

Pixel limitations:

  • Doesn't work with ad blockers enabled
  • Browser restrictions (Intelligent Tracking Prevention in Safari)
  • Data loss on slow internet connections

Conversions API (CAPI)

A server-side method of sending events directly from server to Meta's server. More reliable and not dependent on the browser.

CAPI advantages:

  • Works even when trackers are blocked
  • More accurate attribution
  • Offline conversions can be sent

LightLead displays data from both Pixel and CAPI, aggregating and deduplicating it.

Offsite Conversions

The purchases, purchase_value, and purchase_roas metrics use offsite conversion data — actions taken on your website after interacting with the ad.

Attribution Windows for Conversions

Standard attribution windows:

  • 1d_click: conversion within 1 day after a click
  • 7d_click: conversion within 7 days after a click
  • 1d_view: conversion within 1 day after a view
  • 7d_view: conversion within 7 days after a view

For more details, see Attribution Windows.

Maintained by the LightLead Documentation Team · Last verified: 2026-07-25