TagPipes + webhooks
Receive events from any system that can send a webhook, and send events to any endpoint you control.
Echo: receive events by webhook
A server-to-server source gives you a webhook URL. Anything that can post to it, such as a CRM, a booking system or your own backend, sends events into Echo. They flow to Lens and to your Echo destinations like browser events do.
How you set it up
- In Echo, open Sources and add a Server to Server source.
- TagPipes issues a unique URL and a signing secret. Paste the URL into the sending system.
- Rotate or revoke the URL whenever you need to (a revoked URL returns 410 Gone). The secret rotates separately.
| What it accepts | JSON or form posts up to 5 MB. Every field is kept as an event parameter, and the raw payload is stored. |
|---|---|
| Limits | There is no browser behind these events, so they have no visitor IP, location, session or client ID, and session-based reports leave them out. |
| Plan | Included with every Echo plan. |
Echo: send events to your own endpoint
A custom destination sends Echo events to any HTTPS endpoint you control: a CRM, a warehouse loader or your own API.
How you set it up
- In Echo, open Destinations, click Add Destination and choose Custom.
- Enter the endpoint URL, method, headers, an optional auth token, and a batch size from 1 to 500.
| What it sends | The Echo event as JSON. Any 2xx response counts as delivered; anything else is retried, then held and replayed. |
|---|---|
| Limits | Your endpoint has to accept Echo's event shape. A custom mapping is the only transformation. |
| Plan | Included with every Echo plan. Counts as one destination. |
Documentation: Echo destinations · Custom mapping
What every Echo destination does
- A per-destination event filter decides which events are sent.
- You choose the consent categories an event needs before it is sent. Global Privacy Control signals and bot traffic are handled per destination.
- Failed sends are retried, then held and replayed automatically.
- There is no "send a test event" button yet, and Echo does not yet compare what it sent with what the platform recorded.
More on the module: Echo product page.
How your data is handled
- Credentials you add are stored in Settings > Security & Access, and you can remove them there at any time.
- Each company sees only the data from the accounts and sources it connected.
Read the Privacy Policy and the Terms of Service.
TagPipes monitors, configures and reports. It does not determine legal compliance and does not provide legal advice. Output is informational and reflects observed state at the time of observation. Rawsoft's expertise is technology, not law; please confirm any regulatory interpretation with your own counsel.
Get every system's events into one place.
Sign up and add a webhook source in Echo, or ask us for a walkthrough first.
Already have an account? Log in.