What a source is
A source represents where your events originate before they flow through Echo. Today that means a JavaScript source, used for client-side tracking and data collection from your website. Each source carries a friendly name, a description, a type, a version, and an enabled state, and it can optionally route silent-pipeline alerts to a notification group.
Sources are scoped to your company. Once a source exists, you link it to destinations through connections, which decide which events from the source reach which advertising platform. The source itself is the upstream half of that picture: it defines the origin, while destinations and connections handle where events go.
Opening the Sources list
Navigate to Echo > Sources. The list shows each source's Title, Description, Type, Version, Created By, and Last Modified, with an Options column on the right for editing or cloning. Disabled sources appear with their title struck through so you can see at a glance which ones are paused.
Click Add Source in the top right to create a new one, or click an existing source in the Options column to edit it. Both open the same edit page.
Naming the source
On the edit page, the Title field is required. Use it to identify where the events come from, for example the name of the site or app sending them. The Description field below it is optional but worth filling in. Use it to describe the purpose and configuration of the source so teammates understand its role later.
Keep titles distinct. When you later wire up connections, you pick sources by name, so a clear, specific title saves confusion when a company runs more than one.
Choosing a type and version
The Type field is required. JavaScript is the available type today, covering client-side JavaScript tracking and data collection. Additional source types are planned for future releases, so the dropdown is built to grow.
The Version field is also required. The available versions are 1.0, 1.1, 2.0, and 2.1. Version 1.0 was the initial release, 1.1 added bug fixes and minor improvements, 2.0 was a major update with enhanced features, and 2.1 is the latest with performance improvements. Pick the version that matches the SDK build deployed on your site.
Setting up pipeline alerts
The Notification Group dropdown is optional and defaults to None (no pipeline alerts). Choose a group to have its recipients emailed if this source's event volume drops to zero while a baseline of prior traffic existed. That is the silent-pipeline alert, and it is how you find out that a working source has gone quiet before the gap shows up in your reporting.
If you have not created a notification group yet, use the Manage notification groups link next to the label. It opens the notification groups page in a new tab so you can set up recipients without losing your place on the source form.
The alert only fires when volume falls to zero after a baseline existed, so it signals a real outage rather than normal quiet periods. Assign a notification group to any source whose data you depend on.
Enabling and saving
The Enabled checkbox controls whether the source is active. Leave it ticked for a source that should be collecting events. Untick it to pause the source without deleting its configuration, in which case it shows struck through in the Sources list.
Click Submit to save. A new source is created under your current company, and an existing source is updated in place so its system-managed fields are preserved. You are returned to the Sources list with a confirmation message. To duplicate a source, use the clone option in the list, which opens a pre-filled copy with - Copy appended to the title.
Tips
- Title, Type, and Version are required. The form will not save until all three are set.
- Clone an existing source to reuse its settings. The copy opens pre-filled with " - Copy" added to the title.
- Assign a notification group to important sources so you get an email if the pipeline goes silent.
- Disable rather than delete when pausing collection. Disabled sources stay in the list struck through, so configuration is preserved.
Troubleshooting
The form will not save
The Title, Type, and Version fields are all required. If submission fails with a message to fill out the form completely, check that none of these three are blank. The form validates them before saving.
A source stopped collecting and I was not told
Silent-pipeline alerts only go out when a notification group is assigned to the source. If a source went quiet without an email, confirm it has a notification group set on its edit page, and that the group has recipients. The alert also requires a prior baseline of traffic, so a source that never received events will not trigger it.
I cannot find the source when creating a connection
Connections pick sources by title, so a vague or duplicated name makes the right one hard to spot. Give each source a distinct, descriptive title. If the source is disabled, re-enable it on the edit page if it should be active.