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

# FAQ

### Why do I only see a subset of events in Cordial after setting up my channel?

Events that are generated by users with no associated email cannot be sent to Cordial since it requires associating events with emails.

### I don't see any events coming into my Cordial account after setting up my channel

Check that the API URL matches your account's domain. If the channel is not configured to use the correct endpoint, none of the events will be sent to your account until this is remedied.

If the API URL matches your account's domain, you can try rotating the API key and updating it in the channel form under **Access Token**. Please refer to Cordial's documentation on how to create a new API key:

{% embed url="<https://support.cordial.com/hc/en-us/articles/115005365087-API-keys>" %}


---

# 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/cordial/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.