api - Mandrill - The difference between global_merge_vars and normal merge_vars -

i've looked @ mandrill knowledgebase article on , on , cannot see obvious explanation of difference between global merge vars , merge vars, , when should use global vs normal.

both global_merge_vars , merge_vars declared within 'message' object (as shown here in the mandrill api), it's not you're declaring global_merge_vars outside message object , including multiple merge_vars.

also - there difference between how these declared in template or use *|merge_var_name|* format?

the global_merge_vars parameter allows pass global values particular merge tag, applied recipients in api call default, while merge_vars allows specify per-recipient values based on recipient email address (this why rcpt declared merge_vars). content in email or template doesn't vary - these api parameters distinct since apply differently.

the template_content parameter editable regions in template. more details here. originally, mandrill didn't support merge tags, , supported editable regions in templates. backwards-compatibility, template_content still required when calling template. helps ensure if template region isn't replaced, that's done explicitly passing blank array.

the mandrill kb has quite bit of info on various topics, , can submit support request there if have questions specific account, or in general!