> 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/x/faq.md).
# FAQ
### Do I need to create new events on Twitter?
Not necessarily, if you want to use existing events in Twitter (defined with code, not with URL rules), you can use those, but make sure the previous source that is sending data to those events is turned off, else you will see duplicate data for those events.
### I am unable to view Twitter events within the EdgeTag dashboard when attempting to map the events.
This could be the case if the Twitter events created are URL events; EdgeTag only works with events created with code. In the following image, the Blotout Purchase Twitter event is created as a code-based event; we can map this event. But the URL event shown in the image below is not code-based, so it won't be shown in the EdgeTag dashboard for mapping.
### How to create events on Twitter?
Like we mentioned earlier, EdgeTag only works with events defined with code. Let's try to create a code-based event.
In the Events Manager, click the "Add events" button to create an event.
In the Event Details tab, add a descriptive name for the event and select the correct event type. Please adjust the attribution windows to your preference. You can also enable the Website activity audience if you want to build audiences for remarketing purposes, etc. Once done, click the Next button at the bottom right.
By default setup method selected would be Define event with code, if not please change it to that. Click on the Next button at the bottom right.
You don't need any values from the Event installation tab. Please click 'Save' at the bottom right, which will save the event and take you to the Events Manager overview page.
In the events overview, if you see the ID next to the event that was created. Then the event is successfully created.
---
# 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/x/faq.md?ask=&goal=
```
`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.