Tagging customer information is optional, but enables Nosto’s email features. Tagging can be applied to different page types where a customer opts-in for emails.

<!-- Tag your customer's contact information, replace static example values to equivalent database/ecom engine variables -->
         <div class="nosto_customer" style="display:none">
           <span class="email">john.doe@example.com</span>
           <span class="first_name">John</span>
           <span class="last_name">Doe</span>
           <span class="marketing_permission">true</span>

           <!-- Optional properties -->
           <span class="customer_reference">e18daf14-d715-4d77-82f2-93eceb4ae1ef</span>              

General Guidelines

Email-addresses and name details are tagged and mapped to Nosto only to enable Nosto’s email features. Nosto never approaches your customers directly. Therefore, if strict company policy doesn’t allow using Nosto as an email service you can skip this part and move to tagging order content, but be aware that you can’t leverage any of Nosto’s email features.

The customer tagging is placed in the log-in area if a site has one. The tagging needs to be present just once, preferably immediately after a customer has logged in. The tagging can also be implemented in use cases when a customer leaves an email address for other purposes, for example when a customer subscribes for a newsletter. Simply load the same tagging on the page where customer is directed after signing up!

Nosto only uses the email address and typically just first name for email personalisation, meaning that you can leave last name and DOB out.

Once ready, enable debugger, verify by logging in, and if all looks good jump to learn how to tag order content!

Note: If a customer reference is in use in the customer information tagging, make sure the identifier is secure enough. Nosto recommend to use a UUID or the following if a UUID can’t be supported:

– SHA-1
– {customer_id}_{UUID}
– {customer_id}_{merchant_specific_secret}_{customer_specific_data}_{timestamp}_{random}
– {customer_id}_{merchant_specific_secret}_{customer_specific_data}_{timestamp}
– {customer_id}_{merchant_specific_secret}_{timestamp}

Did this answer your question?