> 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/gcp-pub-sub.md).

# GCP Pub/Sub

GCP Pub/Sub allows seamless streaming of events from your site to Google Cloud with a simple credential setup. Just enter your GCP Pub/Sub **Topic** and **Service Account JSON** to enable automatic server-side event routing to your Google Cloud.

### Details

Channel Name: gcpPubSub

### Event Flow

Events are captured from your site and delivered to Google Cloud Topic via server-side API.

### What is **Google Pub/Sub**?

**Google Cloud Pub/Sub** (short for **Publish/Subscribe**) is a **messaging service** on Google Cloud. It’s designed to enable different parts of your system to **communicate asynchronously** by sending and receiving messages at scale.

Think of it like a **postal system** for your apps:

* One system (the **publisher**) writes a message (like mailing a letter).
* Pub/Sub delivers the message into a topic (akin to a mailbox).
* Another system (the **subscriber**) reads the message when it’s ready.

This way, your applications don’t need to talk to each other directly—they drop off and pick up messages.

Edgetag will write events from your website to a topic using **Service Account JSON.**


---

# 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/gcp-pub-sub.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.