🔍 What is a Template-Based Email in SFMC?

Posted on by admin

A Template-Based Email is an email created using a pre-designed layout (template) in Email Studio. These templates help you maintain brand consistency and streamline email creation using reusable content blocks.

Your screenshots show an email named “Email1” that was created using the Blank Page Template, under the Admin folder/location. This type of email is typically used in day-to-day marketing campaigns, newsletters, and automated journeys.

🧾 Explanation of Template-Based Email Details (from first screenshot)

Let’s break down each element:

FieldDescriptionUsage
Email NameThe name of the email in the UI.Used for reference in the platform.
Asset IDInternal unique ID for the email asset.Referenced in APIs or tracking exports.
Customer KeyUnique GUID for the asset (also called EmailKey).Used in REST API calls, AMPscript (ContentBlockByKey()), and Journey Builder.
LocationFolder where the email is stored (e.g., Admin).Helps in organizing and managing emails in folders.
OwnerThe user who created/modified the email.Useful for audit logs or team collaboration.
Created/Modified TimestampsTrack changes to the email.Useful for version control and reporting.
Email IDNumeric ID assigned to this email (used in sends and logs).Used in SQL queries (e.g., _Job, _Sent views), SSJS, and REST API.
LanguageEncoding format, typically UTF-8.Ensures multilingual content rendering properly.
Attributes (Parameters)UTM tracking parameters (utm_source, utm_medium, etc.).Used in tracking, AMPscript, and personalization for campaign attribution.

🛠️ What is the Properties Section in Template-Based Email (Second Screenshot)?

This section allows you to define or edit the core settings of your email:

  • Name: Editable name of the email.
  • Description: Optional field to describe the purpose or content of the email.
  • Location: Folder where the email is saved.
  • Campaign: You can associate the email with a Campaign object in SFMC for performance attribution.
  • Target Language: Specifies character encoding (Unicode UTF-8 by default).
  • UTM Parameters: Custom tracking tags that can be used in links to monitor source, medium, campaign, content, and term.

These properties enhance organization, tracking, and campaign attribution.

🔧 Where These Email Details Are Used

Let’s explore how you can use the above details in different SFMC technologies:

🔹 1. AMPscript

Use Case: Personalize a CTA using the Email Name and Customer Key.

%%[
SET @emailName = AttributeValue("_emailname")
SET @emailKey = AttributeValue("_emailkey")
]%%

<a href="https://example.com?utm_source=%%=v(@emailName)=%%">Click Here</a>

✅ AMPscript can retrieve:

  • EmailName, CustomerKey
  • UTM attributes defined in the email

🔹 2. SQL Query Activities

Use Case: Extract performance data by Email ID from _Sent or _Job data views.

SELECT
  s.EmailID,
  j.EmailName,
  s.SubscriberKey,
  s.EventDate
FROM _Sent s
JOIN _Job j
  ON s.JobID = j.JobID
WHERE j.EmailID = 124834

✅ SQL can reference:

  • Email ID
  • Send Job ID from tracking tables

🔹 3. HTML Content in Email

Use Case: Append UTM parameters to a CTA for tracking.

<a href="https://example.com/?utm_source=%%=AttributeValue('utm_source')=%%&utm_medium=%%=AttributeValue('utm_medium')=%%">Learn More</a>

✅ HTML uses:

  • Attributes from the properties panel for tracking and analytics

🔹 4. SSJS (Server-Side JavaScript)

Use Case: Log Email properties to a Data Extension during a triggered send.

javascriptCopyEditvar emailID = Platform.Variable.GetValue("@emailID");
var subKey = Platform.Variable.GetValue("@subscriberKey");

// Perform a write to a DE or log it

✅ SSJS can access:

  • Send context variables like Email ID, Subscriber Key

🔹 5. REST API

Use Case: Retrieve Email Asset Details via EmailKey (CustomerKey)

GET /asset/v1/content/assets?assetType=email&customerKey=f99b1e85-bf32-4bec-8fe2-712151fc6ef8

✅ REST API can:

  • Use CustomerKey to fetch, clone, or update email assets
  • Track email performance by Email ID or Asset ID

🧠 Real-World Use Cases

Use CaseToolExample
Link-level tracking with UTM parametersAMPscript/HTMLAppend parameters from Email Properties
Analyze bounce rate per EmailSQLQuery _Bounce using EmailID
Automate sends with REST APIAPIUse CustomerKey to trigger send
Audit email ownership and last modified dateUI/APIUse Created/Modified fields
Retrieve Email in JourneyJourney Builder or APIUse CustomerKey (EmailKey)

✅ Conclusion

Understanding the Template-Based Email Details and Properties Section in SFMC allows marketers and developers to fully optimize their emails for personalization, analytics, automation, and API integrations. Whether you’re adding UTM tracking, querying sends via SQL, or referencing the CustomerKey in AMPscript or REST API, these properties form the foundation of your email operations.

Related Posts