` tag is not required; it is shown for demonstration.
## Insert code
There is a function for inserting HTML code into DCE. It may seem redundant since you can just write HTML in the editor, but this function gives you conditional control and the `onlypos` argument for flow control.
```
<% insert_code code="
Hello World"
[onlypos="first,middle,last"]
[notempty=String]
[empty=String]
%>
```
`onlypos` is not covered further here. `empty` and `notempty` are conditional arguments. They insert the code only if the string in the argument is empty or not empty.
## Flow control
DCE has functions for flowing content into the resulting document. Flowing means you do not explicitly insert a block using `insert_block`. When the container is rendered and its child is not rendered, the block renders all its unrendered children after its own content.
In eMarketeer, open the settings on a container block and mark it as a flow block so the children flow automatically. This also makes the UI drag-and-drop aware in that block, so you can reorder the children.
You can change where the flow happens. By default it is after the block's own content, but you can move it. In the example below, the flow occurs in the `after-this` div.
```
<% insert_block flow="true" %>
```
A child is aware of its position in the flow and can change its content based on that. A child knows whether it is inserted first, middle, or last in the flow. Think of this as a flow from top to bottom.
| Number of Blocks | | | |
|---|
| 1 Block | Only block, considers itself first and last | | |
| 2 Blocks | Top block considers itself first | Bottom block considers itself last | |
| 3 Blocks or more | Top block considers itself first | All blocks but top and bottom considers themselves middle | Bottom block considers itself last |
The `insert_block` and `insert_code` functions take the `onlypos` argument, which inserts code only if the position in the flow matches. If you use `onlypos`, rendering is off by default until a match is found. The positions in the `onlypos` argument are a comma-separated list of `first`, `middle`, or `last`. They are parsed from left to right, and a block renders if a block that considers itself first encounters a `first` in the argument. To suppress rendering, use `!` before the position. Consider this code:
```
<% insert_code code="
" onlypos="middle,last,!first" %>
```
The table below explains what happens to blocks when they encounter this specific code.
| Number of Blocks | | | |
|---|
| 1 Block | Only block, although "last" matches and would render, "!first" also matches and turns rendering off. | | |
| 2 Blocks | First block matches on "first" and will turn off rendering. | Last block matches on "last" and will render the code. | |
| 3 Blocks or more | First block matches on "!first" and will never render the code. | All blocks but top and bottom matches on "middle" and will render the code. | Last block matches on "last" and will render the code. |
It can be hard to see why you would need such a system. The code above can be inserted first in a block to draw a divider between blocks. The divider only renders before a block that has a sibling block directly before it. It never renders on the first block, and it never renders if there is only one block.
You can also reset the flow. After a reset, whatever block comes next is treated as first again. This is useful when you do not want a divider between specific blocks. For example, if an image block does not need a divider after it, put this code last in the image block:
```
<% flow command="reset" %>
```
With the `insert_code` above, the block that follows does not render a divider, because it is now first in the flow again.
## Case converting
DCL has three functions for converting the case of strings: uppercase, lowercase, and "title". Title means the first letter of the string becomes uppercase and the rest lowercase.
Convert the first name on the contact card to uppercase:
```
<% upper string=<% contact field="firstname" %> %>
```
Convert the first name on the contact card to lowercase:
```
<% lower string=<% contact field="firstname" %> %>
```
Convert the first name on the contact card to title case:
```
<% title string=<% contact field="firstname" %> %>
```
# Emarketeer specific functions
DCL functions unique to eMarketeer that fetch data from the contact card, your user account, and other product-specific sources.
## Link
To track a link in eMarketeer, use the `link` function. A normal `
Link` still renders, but it is not tracked. The `link` command looks like this:
```
<% link url="url-to-link" caption="Label to link" [attrib="htmlattributes"] [html="true"] %>
```
* `url`: the URL to link to. It must be URL-encoded; eMarketeer does not encode it for you.
* `caption`: the label of the link, as plain text or HTML. If it is HTML, pass `html="true"`.
* `attrib`: attributes added to the resulting `
` tag in the rendered HTML.
## Contact
The `contact` function fetches or prints values from the contact card the form is attached to.
```
<% contact field="fieldname" %>
```
`fieldname` is one of these:
| Fieldname | Explaination |
|---|
| firstname | Firstname of contact |
| lastname | Lastname of contact |
| salutation | How to salute this contact. For example "Mr", "Mrs" |
| company | This contacts work company |
| email | Email address of contact |
| title | Work title |
| telephone | Contacts telephone number |
| fax | Contacts fax number |
| mobile | Contact mobile telephone number |
| address1 | First line in contacts address |
| address2 | Second line in contacts address |
| city | City of contact |
| state | State of contact |
| zip | Zip or postal code of contact |
| country | Country of contact |
| external_id | Id in users CMS |
| note | Your note of this contact |
Custom contact fields use this syntax:
```
<% contact field="fieldname" type="custom" %>
```
If you are unsure of the right field code, open an email and use the built-in personalization button in any text. It surfaces the proper code for each field.
## User
The `user` function fetches or prints information about your user account.
| Fieldname | Explaination |
|---|
| logo | The url to your companys logo in emarketeer takes a second argument "version" which can be "light" or "dark". The light background logo is the default |
| company | Company name |
| address1 | First address line of company |
| address2 | Second address line of company |
| city | City of company |
| zip | Zip or postal code of company |
| state | State of company |
| country | Country of company |
| webpage | Homepage of company, optional argument "protocol" may be set to true to include protocol in adress (Normaly https://) |
| url | Url this user uses to access emarkeeter. |
| telephone | Tehephone number of company |
## Scramble
The scramble code is a unique identifier generated when sending an email. eMarketeer uses it internally to identify which contact is clicking a link in the email.
## Block
The `block` function fetches specific data from a block in eMarketeer. Different block types expose different fields. The function returns the literal string typed into the block, not evaluated code.
```
<% block name="text1" field="text" %>
```
The `name` argument is a relative path to the block you want, starting at the current node in the tree. Nodes are separated by `.`. The keyword `parent` is reserved and moves up one level. For example:
```
<% block name="parent.block1.text2" field="text" %>
```
This path goes from the current node up to the parent container block, then into `block1`, then into the `text2` text block.
If the `name` argument starts with `.`, the lookup begins at the root. For example:
```
<% block name=".block1.text2" field="text" %>
```
This path always resolves from the root, regardless of where you start.
**Text Block**
| Fieldname | Explaination |
|---|
| text | The text entered into the text block |
**Image Block**
| Fieldname | Explaination |
|---|
| url | the url of the image |
**Link Block**
| Fieldname | Explaination |
|---|
| url | the url of the link |
| caption | the link caption |
**Container Block**
| Fieldname | Explaination |
|---|
| text | Returns the HTML source code of the block |
**Option Block**
| Fieldname | Explaination |
|---|
| value | Current value of the option block |
# Conditionals
DCL supports a simple if-elseif-else-endif conditional for testing whether one string equals another.
Conditional functions follow normal function syntax and always return an empty string. They cannot be used as arguments to other functions. You can test for equality or inequality. There is no concept of boolean operators, but you can simulate AND by nesting conditionals.
Check if "foo" is equal to "foo" (true):
```
<% if compare="foo" equal="foo" %>
```
Check if "foo" is equal to "bar" (false):
```
<% if compare="foo" equal="bar" %>
```
Check if "foo" is not equal to "foo" (false):
```
<% if compare="foo" notequal="foo" %>
```
Check if "foo" is not equal to "bar" (true):
```
<% if compare="foo" notequal="bar" %>
```
Full example of a conditional block:
```
<% if compare=<% contact field="firstname" %> equal="Bart" %>
You're Homer's son!
<% elseif compare=<% contact field="firstname" %> equal="Lisa" %>
You're Homer's elder daughter!
<% elseif compare=<% contact field="firstname" %> equal="Maggie" %>
You're Homer's younger daughter!
<% else %>
Doh!
<% endif %>
```
Below we use the boolean `or` in an expression. To use an `and`, just replace `or` with `and`. Internally, the `if` function checks its `and` or `or` argument for `true`.
```
<% if compare=<% contact field="firstname" %> equal="Bart" or=<% if compare=<% contact field="firstname" %> equal="Lisa" %> %>
You're Homer's child
<% endif %>
```
# Why eMarketeer doesn't support SRI for embed scripts
eMarketeer does not support Subresource Integrity (SRI) on its embed scripts. This article explains why.
SRI can add trust for external assets, but it also brings trade-offs — especially for a platform that delivers scripts to many customers. This article covers the reasoning and what it means for you.
## What is SRI?
Subresource Integrity (SRI) lets browsers verify that a fetched resource, such as a JavaScript file, matches an expected cryptographic hash. If the content has been altered or corrupted, the browser refuses to execute it.
## Our reasoning
After careful evaluation, here are the primary reasons we currently do not support SRI for our embed scripts:
1. Frequent updates and version agility. We continuously release improvements, security patches, optimisations, and feature enhancements. Locking each customer to a specific hash would force a manual integration update for every release, no matter how small. That approach is unsustainable at scale.
2. Lock-in risk and customer burden. SRI essentially locks the script to a fixed version. Customers must track and update the integrity value with every release, which adds maintenance burden and increases the risk of integration breakage when clients lag behind.
3. Script blocking and functional risk. If a client's integrity hash does not match — even due to minor version drift — the browser blocks the script entirely. This could disable essential features like tracking or analytics, leading to significant disruption and support overhead.
4. SRI only guards against certain threats. SRI helps protect against tampering in transit or via a compromised CDN, but it does not defend against threats earlier in the supply chain, such as a compromised build or deployment pipeline. It is not a catch-all defence.
5. Robust alternative security measures already in place. We rely on multiple layers of security to ensure safe distribution of our scripts:
* HTTPS/TLS for secure transport.
* Secure and audited build and deployment workflows.
* Code reviews, access control, and internal security policies.
* Content Security Policy (CSP) support.
* Monitoring, auditing, and alerting on unusual activity.
Given these layers, we currently view SRI as a maintenance burden with limited added benefit in our architecture.
6. Industry precedent. Most established platforms make explicit statements that they do not support SRI for their scripts. Their documentation notes that many services (for example Facebook, Stripe, PayPal) have similarly avoided fixed versions or SRI for their public scripts.
## What this means for you
* You can continue using our scripts without managing or rotating integrity hashes.
* We can deploy updates freely, so you receive fixes, performance improvements, and new features in a timely manner.
* We maintain strict security throughout our development and distribution processes, so the scripts delivered to you are as safe as possible.
# Changing the mobile app navigation icons
How to change the icons in a mobile app component's navigation menu by editing the app's HTML in Developer Mode.
This guide explains how to change the icons used in a mobile app component's navigation menu.
The navigation menu uses icons from [Elusive Icons](https://elusiveicons.com/icons/). You can swap them for any of the 300+ available icons by editing the app's HTML. You need Developer permissions on your user account to make these changes.
{% stepper %}
{% step %}
### Choose which icons to use
Browse the icon list at [elusiveicons.com](https://elusiveicons.com/icons/) and pick the icons you want.
[](https://downloads.intercomcdn.com/i/o/467403408/8cf83dfe3a6ecf908c2b9a64/app-elusiveicons-list.png)
The Elusive Icons list page
{% endstep %}
{% step %}
### Look up the icon tag
Click the icon you want to use. Look for its el-tag — the icon name starting with "el-". For example, the calendar icon has the tag `el-calendar`. Note the tag — you will paste it into the HTML in a later step.
[](https://downloads.intercomcdn.com/i/o/467404444/50ba922f497aa71733a15555/app-elusiveicons-iconcode.png)
Elusive Icons page for the calendar icon
{% endstep %}
{% step %}
### Check which navigation menu style is in use
In eMarketeer, check which navigation menu style your app uses. The setting is called **Navigation Menu** and lives at the top of the Settings tab for the Content block.
Navigation Menu setting location on the Content Settings tab
There are three navigation menu styles: Icons, Icon List, and List. Note which one you use — you only need to change icons for that style.
The three navigation menu style options
{% endstep %}
{% step %}
### Open the HTML tab
On the mobile app component's editing page, click **Enable Developer Mode** in the left-side Tools menu, open **Colors, Fonts & Head**, and switch to the **HTML** tab in the right-side menu.
If you do not see the Developer Mode link, ask an account administrator to grant Developer permissions to your user account.
[](https://downloads.intercomcdn.com/i/o/467405809/2a5e2703535471d490640f41/app-html-tab.png)
Navigating to the HTML tab in Developer Mode
{% endstep %}
{% step %}
### Find the icon in the HTML
The HTML tab has two places where icons are defined. One controls the **Icon List** navigation style, the other controls the **Icons** style.
The top-level part of the HTML labels each section as `iconlist` or `icons`. Each navigation icon has its own sub-section. Inside, look for the el-tag of the icon currently in use, such as `el-time` or `el-bookmark`.
#### Iconlist HTML
[](https://downloads.intercomcdn.com/i/o/467437532/3f94673815295cdcc491f545/app-iconlist.png)
Location of the iconlist icon code in the HTML (usually close to line 113)
#### Icons HTML
[](https://downloads.intercomcdn.com/i/o/467437560/786013c0d589590cb65d0126/app-icons.png)
Location of the icons icon code in the HTML (usually close to line 237)
{% endstep %}
{% step %}
### Replace the icon tag and save
Change the current el-tag to the new one for your chosen icon, then save the HTML. For example, to change "Company News" from a bookmark icon to a calendar icon, replace `el-bookmark` with `el-calendar`. Leave the surrounding tags alone — `el`, `el-inverse`, and `el-fw` are the same for all icons in the app component.
{% endstep %}
{% endstepper %}
# Barcodes
What barcodes are, where they are used, and how you can use them in eMarketeer.
## What is a barcode?
A barcode scanner reading a barcode
A barcode is essentially a font that computers can read visually. To read one, a computer needs a barcode reader — its "eyes." Like any font, you can encode whatever you want: numbers, text, full sentences. What you encode only matters if it means something to someone, or something, on the other end.
For example, this phone number in a regular font: `004651410050`
Your eyes read the digits and know what to do with them.
The same number as a barcode looks like this:
## Where are barcodes used?
The most familiar place is your local store. The "beep" at checkout is a barcode reader scanning each product into the register. You also see barcodes on tickets, coupons, parcels, ID cards, and more.
## How can I use barcodes with eMarketeer?
You need two systems: one to generate the codes and one to scan them. eMarketeer transports the code from one to the other.
For example, you want to send coupons to your customers. You already have article numbers for the items and a cash register that scans barcodes. eMarketeer takes that information and sends a ready-to-print email with the offers and barcodes included. Customers print the email, bring it to the store, and the register scans the barcode to apply the discount.
## Barcode standards
eMarketeer supports the following barcode standards. The default in eMarketeer blocks is **Code 128**. To change the standard, edit the barcode in Developer Mode.
* Code 128
* Codabar
* Code 11
* Code 39
* Code 39 Extended
* Code 93
* EAN-8
* EAN-13
* ISBN-10 / ISBN-13
* Interleaved 2 of 5
* Standard 2 of 5
* MSI Plessey
* UPC-A
* UPC-E
* UPC Extension 2
* UPC Extension 5
* PostNet
# Platform
Reference documentation for eMarketeer's platform features: email, SMS, web tracking, and user accounts.
{% columns %}
{% column %}
{% content-ref url="/pages/krjQWGjanR5rBjTjLp6X" %}
[Email](/references/references/email)
{% endcontent-ref %}
{% content-ref url="/pages/mL2CVPvyYsxuUfMyp2XI" %}
[Forms](/references/references/forms)
{% endcontent-ref %}
{% content-ref url="/pages/Ab8CEBIcPu4iKIK8rRl1" %}
[SMS](/references/references/sms)
{% endcontent-ref %}
{% content-ref url="/pages/eNDpP8hSthVojszye9SB" %}
[Web Tracker](/references/references/web-tracker)
{% endcontent-ref %}
{% content-ref url="/pages/771Uq5SEX6IwY9VdVcLb" %}
[User accounts & auth](/references/references/accounts-auth)
{% endcontent-ref %}
{% content-ref url="/pages/HFwXYxIDr2hmBP7jk9bU" %}
[Credit card payments (Administrator)](/references/references/credit-card-payments)
{% endcontent-ref %}
{% content-ref url="/pages/w402hrS8MwBFwJP9dY0M" %}
[What happens when I reach my contact limit?](/references/references/what-happens-when-i-reach-my-contact-limit)
{% endcontent-ref %}
{% endcolumn %}
{% column %}
{% content-ref url="/pages/yN08YPGvHPL9ZPL9GmOq" %}
[Default score rules in eMarketeer](/references/references/default-score-rules-in-emarketeer)
{% endcontent-ref %}
{% content-ref url="/pages/HFYw5c9eyif9IK7DxoPO" %}
[Understanding eMarketeer URLs](/references/references/understanding-em-urls)
{% endcontent-ref %}
{% content-ref url="/pages/WTXW8NSdzb0XoH7naqZs" %}
[Where is eMarketeer data stored geographically?](/references/references/where-is-emarketeer-data-stored-geographically)
{% endcontent-ref %}
{% content-ref url="/pages/urobSHDtAHEBIqdqhtaa" %}
[GDPR & consent](/references/references/emarketeer-gdpr-overview)
{% endcontent-ref %}
{% endcolumn %}
{% endcolumns %}
# Email
Reference material for eMarketeer's email sending: platform behaviour, deliverability, and how email is measured.
{% columns %}
{% column %}
{% content-ref url="/pages/SOOQIPQ3DZhlGc0WYJPV" %}
[Deliverability](/references/references/email/deliverability)
{% endcontent-ref %}
{% content-ref url="/pages/hLlcy4hhdQCVRJgS7dF1" %}
[Automatic send pause](/references/references/email/automatic-send-pause)
{% endcontent-ref %}
{% content-ref url="/pages/v5AvutjraJOeo8R6GkaS" %}
[Exclude inactive recipients](/references/references/email/exclude-inactive-recipients)
{% endcontent-ref %}
{% content-ref url="/pages/7IoAV57ZKxjoVCb3cnsQ" %}
[Transactional sendouts](/references/references/email/transactional-sendouts)
{% endcontent-ref %}
{% content-ref url="/pages/459ZbO619ijBbNhhKabl" %}
[When is an email registered as opened?](/references/references/email/email-open)
{% endcontent-ref %}
{% endcolumn %}
{% column %}
{% content-ref url="/pages/kcJORJYE4LmuGSeQUcBb" %}
[eMarketeer sender policy](/references/references/email/emarketeer-sender-policy)
{% endcontent-ref %}
{% content-ref url="/pages/qqTv6hZJoeRmIkLQmvSK" %}
[Read on web](/references/references/email/read-on-web)
{% endcontent-ref %}
{% content-ref url="/pages/zZTuOectCtosunn3QXkS" %}
[Why you shouldn't use a URL as link text](/references/references/email/url-as-link-caption)
{% endcontent-ref %}
{% content-ref url="/pages/oZ2fL1f6you7plmWBbFJ" %}
[Understanding the Email Checklist](/references/references/email/checklist-explained)
{% endcontent-ref %}
{% content-ref url="/pages/1zhKsTeFi8MHkv5JmW7s" %}
[Email report explained](/references/references/email/email-report-explained)
{% endcontent-ref %}
{% content-ref url="/pages/7EMIXuiPwYD6wSCWylek" %}
[Maximizing Email Marketing Success: 10 Best Practices and Pitfalls to Avoid](/references/references/email/maximizing-email-marketing-success-best-practices-and-pitfalls-to-avoid)
{% endcontent-ref %}
{% endcolumn %}
{% endcolumns %}
---
[Next Page](/llms-full.txt/1)