Zaius will tie a user's behavioral data to that user's customer record and to his or her email address in order to target the user with email campaigns. The best way to ensure email behavior is tracked is by sending campaigns via Zaius. However, during a transition period it is beneficial to include tracking information in your existing ESP's emails in order to link a user's pageview data to an existing email campaign.

This involves sending a unique ID in the URL used to send the user to a site, which is then used to tie the user's email address back to Zaius's cookie. Otherwise, Zaius's browsing information about a user may not be tied back to the corresponding user until the user identifies him or herself by logging in, providing an email, or making a purchase.

Email Forwarding can be dangerous

If email recipients forward many emails, this can result in clicks being attributed to the wrong user. A handful of forwards aren't likely to impact the customer base meaningfully, but if this is a common occurrence in the customer base, please discuss implementation of this type of strategy with Zaius before adjusting third party campaigns.

SilverPop and ExactTarget

If your ESP (such as SilverPop or ExactTarget) provides a base64 encoding function, base64 encode the user's email and append it to the URL using a parameter called "zm64_id".


In links back to the website, Mailchimp users should specify a URL parameter called "zaius_alias_mailchimp_id" and set it to "*|UNIQID|*"

 or if you have multiple parameters*|UNIQID|*

Constant Contact

Constant Contact allows custom fields to be uploaded for individual users. Upload an MD5 hash of each user's email address (call it email_md5), and then pass that value in the links by like so: zaius_alias_email_md5=$Subscriber.Custom.email_md5

With this approach, we can take the Zaius customer list and generate the required hashes on our side, so the only requirements for you are to add that ID to Constant Contact and make sure links include the new parameter.

Linking Emails Sent via Zaius

The overall strategy here is to pass a URL parameter named zm64_id, which contains a base64 encoded string corresponding to the user's email address. This will then provide the email address to Zaius.

In order to do so, configure your campaign with the following liquid script in the script block of the first section of your template.

{% assign zm64_id = | base64_encode %} 
{% assign new_utm_params = 'utm_campaign=%s&utm_content=%s&utm_source=%s&utm_medium=%s&zm64_id=%s' | format: utm_campaign, utm_content, utm_source, utm_medium, zm64_id %}
{% assign _new_utm_params = new_utm_params | escape_once %}
{% assign utm_params_unescaped = _new_utm_params | unescape %}

If you are not using the Zaius auto UTM parameters, this allows you to enter a parameter of zm64_id with a value of #{{zm64_id}} for all URLs.

Other ESPs

Users of other ESPs should consult their ESP's documentation. A field must start with "zaius_alias_" and be provided in both the URL the user visits and in the data imported to Zaius from the ESP.

Did this answer your question?