Bhavin Suthar
Currently, merge tags are embedded directly inside the exported HTML content. For our email processing and analytics pipeline, we need to scan the entire HTML to identify merge tags before sending emails, which adds extra processing overhead and complexity.
Requested Enhancement:
Provide an option to export all merge tags separately along with the HTML export.
Example Response:
{
"html": "<html>...{{first_name}}...{{company_name}}...</html>",
"mergeTags": [
"{{first_name}}",
"{{company_name}}",
"{{unsubscribe_link}}"
]
}
Or, if possible, provide detailed metadata:
{
"html": "<html>...</html>",
"mergeTags": [
{
"tag": "{{first_name}}",
"name": "first_name"
},
{
"tag": "{{company_name}}",
"name": "company_name"
}
]
}
Why this is needed
Eliminates the need to scan and parse the entire HTML for merge tags.
Improves performance for analytics and email processing pipelines.
Makes merge tag validation and replacement easier.
Enables pre-processing and analytics before sending emails.
Reduces implementation complexity and potential parsing errors.
Use Case
Our platform exports email templates from Stripo and processes them further for analytics and email delivery. Having merge tags available separately would significantly simplify our pipeline and improve performance.