> For the complete documentation index, see [llms.txt](https://support.emarketeer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.emarketeer.com/guides/journeys/journeys-triggering-events.md). # Journeys Triggering Events A journey's starting point is not evaluated continuously. It is only evaluated when a specific event occurs for a contact. This page lists every event that triggers evaluation. ## Triggering events When any of the events below occurs for a contact, eMarketeer checks whether that contact matches a journey's starting point and should enter the journey. ### Engagement * Email engagement * Form engagement * SMS engagement * Landing page engagement * Web monitor engagement * SuperOffice engagement * Facebook engagement * LinkedIn engagement * Custom signals engagement ### Contact card * Contact card update * Legal basis update * Added to a contact list ### Lead Board * Lead state change ## How evaluation works eMarketeer evaluates starting points only when a triggering event fires — not on a schedule, and not when a journey is first activated. A contact that already matches the starting point condition when you activate the journey will not enter it until a triggering event occurs for them. ## Example: contact list starting point If your starting point filters on a contact list, contacts already in that list when you activate the journey will not enter immediately. eMarketeer waits for a triggering event to fire for each contact individually. It does not have to be "Added to contact list" — any of the events listed above will do. To get contacts into the journey as soon as possible, populate the list after you activate the journey rather than before. --- # 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://support.emarketeer.com/guides/journeys/journeys-triggering-events.md?ask= ``` 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.