Google Analytics setup
Connect SendBeam to Google Analytics: what you need, the steps, and the code.
Via automation
Google Analytics tells you what people did on your site; it cannot tell you which email sent them unless the link says so. Switch link tagging on and SendBeam adds the utm parameters Analytics reads, so every campaign and every automated email appears under Acquisition with its own name.
Before you start
- A Google Analytics property on the site your links point at
- A SendBeam workspace admin seat
Set it up
- Turn tagging on. Settings → General → Sending, then Tag links for analytics. The example under the fields shows exactly what a link will look like.
- Choose what the tags say.
utm_sourceis usually your brand ornewsletter;utm_mediumstaysemail.utm_campaigncan be the campaign’s name, that name as a slug, or its id — the slug is the easiest to read in a report. - Send something and look. In Analytics, open Reports → Acquisition → Traffic acquisition and set the dimension to Session source / medium. Your value appears as
<source> / email, and Session campaign splits it by campaign.
A link that already carries its own utm_source is left exactly as it was, so a partner or affiliate link keeps its own tagging. The unsubscribe link, the web version and the click-tracking redirect are never tagged.
What each parameter carries
| Parameter | What SendBeam puts in it |
|---|---|
utm_source |
Your value, the same on every email from the workspace |
utm_medium |
Your value, normally email |
utm_campaign |
The campaign’s name, its slug or its id — your choice. An automated email uses the automation’s name |
utm_content |
link-1, link-2… in the order the links appear, so two links to the same page can be told apart |
utm_term |
Only when you set one |
One campaign at a time
A single campaign can override the workspace: on the campaign’s Details step, Link tags offers as this workspace does, no tags on this campaign’s links, or its own utm_source and utm_medium. The Preview shows the tagged links before you send, and the API takes the same settings as utm on a campaign.
Over the API
The workspace default is link_tagging on POST /api/v1/workspaces/sending, which a workspace
admin sets while signed in — sending defaults are not key-authenticated. A single campaign’s
override is utm on POST /api/v1/campaigns and PATCH /api/v1/campaigns/<id>, which do take an
API key with campaigns:write in the usual x-api-key header: the same fields as above, null to
follow the workspace again, or enabled: false to send that campaign’s links untagged. Both are in
the API reference.
Stuck, or found a gap? Ask in the community — questions, tips and every release note, with this page as the source of truth.