Upcoming Feature: UTM Tracking Parameters

We know that sending an email is only half the story. The real magic happens when a customer clicks a link, makes a purchase, or books a table. Soon, we’ll be making it easier than ever to track that journey from start to finish.

What’s New?

While TalkBox has always tracked link clicks internally, that data was previously stuck inside our app. We are introducing Custom Tracking Parameters, including the industry-standard UTM set.

This means your TalkBox data can now “talk” to the other platforms you rely on, such as Google Analytics, Point of Sale (POS) systems, and online ordering platforms.

Why This Matters

• Unified Reporting: By using UTM parameters, your TalkBox email traffic will appear alongside your social media and search ads in Google Analytics for a complete view of your marketing performance.
  
• Close the Loop: Our additional TalkBox IDs allow data partners to correlate a specific email recipient with a specific transaction or booking.
  
• Data-Driven Decisions: Stop wondering if your “Birthday Promotion” worked. Now, you can prove it by seeing exactly which communications drove the most revenue.

Parameter	What it tracks	Why use it?
UTM Set	Source, Medium, Campaign, Content, and Term.	Standardizes your data for Google Analytics and other web reporting tools.
TalkBox IDs	Contact, Recipient, and Promotion IDs.	Allows TalkBox and its partners to link consumer actions directly to your contacts and communications.

You’re in Control

You can manage these settings to fit your specific workflow:

1. Set Global Defaults: Visit the new tab in Communication Settings to set your “always-on” defaults (like setting your utm_source to talkbox).
2. Fine-Tune Individual Links: Need a specific tag for a single button? You can edit individual parameters directly within the email editor whenever you add a link.

Implementation

1. Standard UTM Parameters (GA4 Auto-Mapping)

These parameters are industry-standard and will automatically map to the Session source/medium/campaign dimensions in GA4.

Parameter	Type	Default Value	Marketing Ops Use Case
utm_source	String (text)	talkbox	Identifies the specific platform driving the traffic.
utm_medium	String (text)	email	Categorizes traffic within the “Email” default channel group.
utm_campaign	String (text)	TalkBox Communication Name	Groups all traffic associated with a specific marketing communication.
utm_content	String (text)	Link text/Button label	Used for testing different CTAs or link placements within the same email.
utm_term	String (text)	User-defined	Can be used to track specific offer codes or segment-specific keywords.

2. TalkBox Relevant IDs

These parameters are unique to TalkBox and provide a persistent ID that links a web session back to a specific entity in your database. Note that these are Encrypted IDs, ensuring security while maintaining data integrity across platforms.

• tb_contact_id: An encrypted unique identifier for the specific contact. In GA4, this can be mapped as a User Property to track long-term user behaviour across multiple sessions.
  
• tb_recipient_id: An encrypted identifier for the specific instance of the communication sent. This is useful for troubleshooting and highly granular attribution (e.g., identifying exactly which channel, eg Email or SMS for a given Contact, triggered a purchase).
  
• tb_promotion_id: An encrypted identifier for the TalkBox communication. This allows you to join GA4 data with TalkBox internal reports via API or data warehouse exports.

Integration Recommendations

To get the most out of these parameters in Google Analytics:

• Register Custom Dimensions: For the tb_ parameters to be searchable in GA4, you must register them as Custom Dimensions within the GA4 Admin interface.
  
• Global vs. Local Overrides: Use the Communication Settings tab to set global defaults for utm_source and utm_medium to ensure data cleanliness. Use the individual link editor to override or append to utm_content for specific button-level tracking.
  
• Data Partner Sync: If you use a third-party POS or booking system, ensure they are configured to “capture” these URL parameters upon landing. This “closes the loop” by passing the tb_contact_id directly into your transaction records.