> 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/emotive-sms/faq.md).

# FAQ

### How are events handled?

#### 1. AddToCart

* Event Name: Converts to `blotout.cart.added`
* Data Sent: Product details (ID, variant ID, name, image, URL, price, currency)
* Requirement: Must have `data.contents` with product data

#### 2. ViewContent

* Event Name: Converts to `blotout.product.viewed`
* Data Sent: Product details (ID, variant ID, name, image, URL, price, currency)
* Requirement: Must have `data.contents` with product data

#### 3. Other Events

* Event Name: Never sent to Emotive 
* Data Sent: Nothing (event is skipped)

### Key Limitations:

* Only 2 events get converted names (AddToCart, ViewContent)
* Only AddToCart and ViewContent can be sent (if they have product content)
* All other event types are completely skipped regardless of data content

### Summary:

Emotive SMS only handles AddToCart and ViewContent events that have product content data. All other event types are completely skipped and never sent to Emotive, regardless of whether they have product content or not.


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.edgetag.io/channels/emotive-sms/faq.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.