> For the complete documentation index, see [llms.txt](https://docs.edgetag.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.edgetag.io/channels/meta/conversion-lift.md).

# Conversion Lift

We support the Conversion Lift study for the Meta channel. This allows you to send custom events to Meta, including details about the origin of each purchase. To enable this feature, please reach out to our support team at <support@blotout.io>.&#x20;

Read more about the study on Facebook help pages:

{% embed url="<https://www.facebook.com/business/help/221353413010930?id=547299432790676>" %}

{% embed url="<https://developers.facebook.com/docs/marketing-api/guides/lift-studies/>" %}

### Events

Below is a table of all custom events we send as part of this study:

| Event                     | Description                                                                    |
| ------------------------- | ------------------------------------------------------------------------------ |
| Purchase\_Paid\_Facebook  | An in-session purchase made with a Facebook click ID                           |
| Purchase\_Paid\_Google    | An in-session purchase made with a Google click ID                             |
| Purchase\_Paid\_Bing      | An in-session purchase made with a Bing click ID                               |
| Purchase\_Paid\_TikTok    | An in-session purchase made with a TikTok click ID                             |
| Purchase\_Paid\_Snap      | An in-session purchase made with a Snapchat click ID                           |
| Purchase\_Paid\_Twitter   | An in-session purchase made with a Twitter click ID                            |
| Purchase\_Paid\_Other     | An in-session purchase made with a UTM parameter from a campaign               |
| Purchase\_Direct          | An in-session purchase made with directly on-site without a referrer           |
| Purchase\_Other\_Referral | An in-session purchase made with a referrer without a UTM parameter            |
| Purchase\_Organic\_Google | An in-session purchase made from a Google search                               |
| Purchase\_Organic\_Bing   | An in-session purchase made from a Bing search                                 |
| Purchase\_Search\_Other   | An in-session purchase made from other well-known search providers             |
| Purchase\_Other           | This event triggers if a purchase is made that does not match the above rules  |
| Purchase\_AppLovin        | An in-session purchase made when referred to by a site using an AppLovin pixel |
| Purchase\_Retail          | Triggered on retail offline purchases                                          |
| Purchase\_Offline         | Triggered on all other offline purchases                                       |
| Paid\_Social\_NonFB       | Triggered when a TikTok or AppLovin event is generated                         |
| Purchase\_Google          | Triggered when a Google or Bing event is generated                             |
| Purchase\_Organic         | Triggered when a Google or Bing search event is generated                      |
| Purchase\_Custom\_Other   | Triggered when other purchase events occur                                     |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.edgetag.io/channels/meta/conversion-lift.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.