> For the complete documentation index, see [llms.txt](https://help.thinkpickle.com.au/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.thinkpickle.com.au/flows/actions/send-analytics-event.md).

# Send Analytics Event

This action allows you to send custom analytics events to [Segment](https://segment.com/). You can then setup Segment to forward this event to any of your other analytics providers such as Google Analytics, Facebook,  Mixpanel, Heap etc. The full list can be found [here](https://segment.com/catalog#integrati).

### Configuration

| **Property**     | **Description**                               |
| ---------------- | --------------------------------------------- |
| Event Name       | The segment event name                        |
| Event Properties | Custom segment properties                     |
| Source ID        | Segment Source ID (get this from segment.com) |
| Write Key        | Segment Write Key (get this from segment.com) |

### Finding your Source ID and Write Key

1. Login to segment.com
2. Navigate to **Settings > API Keys** your Source ID and Write Key should be listed here.

![](/files/-LFptapQ4osNl9bUhY4Q)

  3\. Paste these settings into the node configuration panel.

![](/files/-LFpu43yU2O_K35PZcH4)

### Event Name and Properties

You will also need to configure an **Event Name** and optional **Event Properties**. These will be used to send a segment [track request](https://segment.com/docs/spec/track/). This will be of the form:

```
{
  "type": "track",
  "event": your-event-name-here,
  "properties": your-custom-event-properties
}
```

### Use Cases

#### Send a 'phone-call' analytics event

![](/files/-LFpwlhHLsIWDadxFOUc)

#### Send a 'voicemail' analytics event when it outside of operating hours

![](/files/-LFpy-BYRX8bpd52BbPe)


---

# 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://help.thinkpickle.com.au/flows/actions/send-analytics-event.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.