> ## Documentation Index > Fetch the complete documentation index at: https://docs.extole.com/llms.txt > Use this file to discover all available pages before exploring further. # Send Event From Site or App > Sends this trigger event from a consumer's browser or app, through the program domain, so the campaigns that listen for it run for that consumer. A page that loads core.js does not need this call and needs no zone tag: when the page has loaded, core.js requests the zone that Zone Name sets, and that request sends this event. It does this on each page whose URL matches URL Filter, or on every page when URL Filter is empty, and shows the CTA in the Anchor Element ID element, or at the top of the page. Call this operation to send the event without core.js, for example to test a campaign. The call always answers 200. To find out if the event failed, read the X-Extole-Error-Message response header. ## OpenAPI ````yaml /feature-specific-apis/trigger-event-tagless-cta.json post /events openapi: 3.1.0 info: title: Trigger Event Tagless Cta version: 1.0.0 description: >- Operations published by Extole Trigger Event Tagless Cta components. Generated from the component contracts on my.extole.com. servers: - description: Production - your program domain url: https://{brand}.extole.io variables: brand: default: yourcompany description: >- Your Extole client subdomain (e.g. 'mycompany' for mycompany.extole.io) security: [] paths: /events: post: summary: Send Event From Site or App description: >- Sends this trigger event from a consumer's browser or app, through the program domain, so the campaigns that listen for it run for that consumer. A page that loads core.js does not need this call and needs no zone tag: when the page has loaded, core.js requests the zone that Zone Name sets, and that request sends this event. It does this on each page whose URL matches URL Filter, or on every page when URL Filter is empty, and shows the CTA in the Anchor Element ID element, or at the top of the page. Call this operation to send the event without core.js, for example to test a campaign. The call always answers 200. To find out if the event failed, read the X-Extole-Error-Message response header. requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/SendEventFromSiteOrAppRequest' responses: '200': description: Success content: application/json: schema: type: object properties: id: type: string description: >- Identifier of the event. It is absent when the event failed. token: type: string description: >- Access token of the consumer. Send it on the next call to keep the same consumer. It is absent when the event failed. '400': description: Bad Request content: application/json: schema: $ref: '#/components/schemas/RestExceptionResponse' examples: binding_error: $ref: '#/components/examples/binding_error' invalid_json: $ref: '#/components/examples/invalid_json' invalid_parameter: $ref: '#/components/examples/invalid_parameter' missing_request_body: $ref: '#/components/examples/missing_request_body' '403': description: Forbidden content: application/json: schema: $ref: '#/components/schemas/RestExceptionResponse' examples: access_denied: $ref: '#/components/examples/access_denied' expired_access_token: $ref: '#/components/examples/expired_access_token' invalid_access_token: $ref: '#/components/examples/invalid_access_token' jwt_authentication_error: $ref: '#/components/examples/jwt_authentication_error' method_unauthorized: $ref: '#/components/examples/method_unauthorized' missing_access_token: $ref: '#/components/examples/missing_access_token' security: - CONSUMER_AUTH_HEADER: [] - CONSUMER_AUTH_QUERY_PARAM: [] - CONSUMER_AUTH_COOKIE: [] servers: - description: Production - your program domain url: https://{brand}.extole.io variables: brand: default: yourcompany description: >- Your Extole client subdomain (e.g. 'mycompany' for mycompany.extole.io) components: schemas: SendEventFromSiteOrAppRequest: type: object required: - event_name properties: data: type: object properties: container: description: >- Container the event goes to, for example test to keep it out of analytics. Without it, the event goes to production. type: string email: description: >- The email of the consumer. It is the identity key of the client. Without it, the access token or cookie names the consumer. type: string event_name: description: The event this trigger event listens for. type: string enum: - tagless_cta RestExceptionResponse: type: object description: Represents the API error response properties: code: type: string description: Specific error code for this error type, documented per endpoint http_status_code: type: integer description: >- HTTP status code that was returned with this error, useful if client get response code message: type: string description: User readable English description of the error parameters: type: object description: >- Attributes related to the error, varies be error code, documented per endpoint additionalProperties: type: object description: >- Attributes related to the error, varies be error code, documented per endpoint unique_id: type: string description: >- Unique id associated with this error, useful for discussions with Extole required: - code - http_status_code - message - parameters - unique_id examples: binding_error: summary: binding_error value: unique_id: 00000000-0000-0000-0000-000000000000 http_status_code: 400 code: binding_error message: Argument is not of the expected type parameters: {} invalid_json: summary: invalid_json value: unique_id: 00000000-0000-0000-0000-000000000000 http_status_code: 400 code: invalid_json message: JSON is invalid parameters: {} invalid_parameter: summary: invalid_parameter value: unique_id: 00000000-0000-0000-0000-000000000000 http_status_code: 400 code: invalid_parameter message: Parameter is invalid. parameters: {} missing_request_body: summary: missing_request_body value: unique_id: 00000000-0000-0000-0000-000000000000 http_status_code: 400 code: missing_request_body message: Missing request body parameters: {} access_denied: summary: access_denied value: unique_id: 00000000-0000-0000-0000-000000000000 http_status_code: 403 code: access_denied message: >- The access_token provided is not permitted to access the specified resource. parameters: {} expired_access_token: summary: expired_access_token value: unique_id: 00000000-0000-0000-0000-000000000000 http_status_code: 403 code: expired_access_token message: The access_token provided with this request has expired. parameters: {} invalid_access_token: summary: invalid_access_token value: unique_id: 00000000-0000-0000-0000-000000000000 http_status_code: 403 code: invalid_access_token message: The access_token provided with this request is invalid. parameters: {} jwt_authentication_error: summary: jwt_authentication_error value: unique_id: 00000000-0000-0000-0000-000000000000 http_status_code: 403 code: jwt_authentication_error message: The jwt authentication failed. parameters: {} method_unauthorized: summary: method_unauthorized value: unique_id: 00000000-0000-0000-0000-000000000000 http_status_code: 403 code: method_unauthorized message: Access forbidden to this endpoint parameters: {} missing_access_token: summary: missing_access_token value: unique_id: 00000000-0000-0000-0000-000000000000 http_status_code: 403 code: missing_access_token message: No access_token was provided with this request. parameters: {} securitySchemes: CONSUMER_AUTH_HEADER: type: apiKey in: header name: Authorization description: >- A consumer access token, issued to a single person in the browser or app. Not a client access token - never send a client token from a consumer device. x-bearer-format: bearer CONSUMER_AUTH_QUERY_PARAM: type: apiKey in: query name: access_token description: >- A consumer access token, issued to a single person in the browser or app. Not a client access token - never send a client token from a consumer device. CONSUMER_AUTH_COOKIE: type: apiKey in: cookie name: extole_token description: >- A consumer access token, issued to a single person in the browser or app. Not a client access token - never send a client token from a consumer device. ```` ## Related topics - [Send Event From Site or App](https://docs.extole.com/api-reference/feature-specific/zone-event/send-event-from-site-or-app.md) - [How to Set Up Triggered By](https://docs.extole.com/guides/flow-campaigns/how-to-set-up-triggered-by.md) - [Javascript SDK and Mobile SDK Extensions](https://docs.extole.com/technical/platform-integrations/extensions/javascript-sdk-and-mobile-sdk-extensions.md) - [Send Events from the Partner Platform](https://docs.extole.com/technical/building-partner-integrations/integration-types/partner-events-send-from-platform.md) - [Send Event](https://docs.extole.com/api-reference/feature-specific/api-event/send-event.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.