LogoLogo
MerchantsHelpSign in
  • Overview
    • Countries & Currencies
    • Glopal Solutions Portfolio
  • Getting started
    • Shopify
      • Glopal Duty & Tax for Shopify
      • Shopify Collaborator Access
    • BigCommerce
    • Magento (Adobe Commerce)
      • Magento 1
      • Magento 2
        • Magento Activation
        • Magento Configuration
        • Magento Database Model
    • Visualsoft
    • PrestaShop
  • Marketing Solutions
    • Acquisition channels
      • Integrate Google Ads
      • Integrate Facebook Ads
    • Feed localization
      • Read domestic items
      • Localize the items
      • Upload the localized items
    • Features / Customization
      • Google Shopping countries coverage
      • Filters
      • Free listings
      • Comparison Shopping Services (CSS)
    • Google Ads
      • Conversion tracking
      • Standard accounts structure
      • Launching and monitoring Google Ads campaigns
    • Facebook
      • Facebook & Instagram Shops
      • Catalog Based Campaigns
      • Conversion and Brand awareness campaigns
      • Facebook conversion tracking
    • Email marketing
  • Localization
    • Site localization
      • Content localization
      • Price localization
      • Site search
      • Checkout
      • User account
    • Site discovery
      • Domains and Routing
      • Search engine optimization
      • Geo-localization
      • Country selector
    • Content distribution
      • Site security
      • Domains (DNS)
      • Traffic Splitting
        • Akamai
        • Cloudflare
        • Nginx
        • Microsoft IIS
        • AWS CloudFront
        • Magento Cloud
      • Third-party CDN
        • Cloudflare
      • Site speed
    • Integrations
      • CSS customizations
      • JavaScript customizations
      • Server-side customizations
      • Exclude from localization
      • Integration examples
        • Hiding Products
        • Newsletter Signup
        • Custom Price Logic
  • Checkout
    • Localized checkout
      • Overview
      • Styling
      • Integration
        • Callback Functions
        • Confirmation Page
        • Checkout Analytics
        • Allowlisting Glopal IPs
      • Price localization
    • Order processing
      • Order creation
        • Plug & Play integration
        • Order API
        • Event webhook
        • Custom Integration
      • Cancellation & refund
      • Returns
      • Buyer's communication
      • Customer account
    • Financials
      • EU VAT
  • DUTY & TAXES
    • Product Classification
    • Duty & Tax Calculation
      • Product Pricing
      • Supported Countries
    • Compliance Checks
      • Prohibited Goods
      • Denied Party Screening
  • SHIPPING
    • Order Creation
    • Label Generation
    • Manifest
    • Tracking
  • Translations
    • Translation Editor
  • MERCHANT ACCOUNT
    • Dashboards
      • SEO dashboard
  • What's New
    • Release Notes
Powered by GitBook
On this page
  1. Marketing Solutions

Email marketing

PreviousFacebook conversion trackingNextSite localization

Last updated 2 days ago

Email localization

Glopal Email Localization is a unique feature enabling the localization of emails sent from your eCommerce platform or another third-party marketing tool to international buyers who completed the purchase in the Glopal Checkout.

By tailoring email content for the international buyer you can see an increase in email performance (open rate, click-through, direct conversion on localized sites).

Glopal Email Localization solution is built as an Email Proxy. This makes the email localization solution usable from any eCommerce platform, CRM, or email marketing tool. For every recipient, Glopal can generate a unique email alias address. When emails are sent to this email alias, Glopal can localize the email subject, headers, and email body content, re-mailing the localized email to the buyer's original email address.

Email localization is using the same technology that is powering our real-time , ensuring that localized email content is correctly targeting the corresponding localized site.

Alias Address

When the international buyer makes a purchase in the Glopal Checkout, if the Email Localization feature is enabled, Glopal creates the email alias for the buyer and can automatically replace the true buyer's email with this created email alias when inserting the order back to your eCommerce backend. This ensures that generated email alias will be used for all communication with the buyer.

Email Alias API

It is also possible to create Email Alias outside of the order flow, for example on customers signup, or to use inside CRM tool, by calling Glopal API. Please contact your account manager to receive the server endpoint and your API key.

Email Content

Email localization solution is localizing HTML email content.

If your emails have both text and HTML parts, Glopal will localize the HTML part and discard the text part to avoid having a significant mismatch between HTML and text parts that could increase spam score. Attachments will not be localized and are forwarded as-is.

The maximum size of the email message that can be processed via alias address is 6 MB, including all headers and attachments. Larger email messages will be silently discarded.

Email Tracking

Email localization is done on the fly, rewriting email subject and HTML content. Glopal is localizing email content by processing email content without actually loading, interpreting, or opening emails. If your email includes a special code/pixel to track the email open rate, localization will not register as "opening".

It is common for links in emails to use click tracking analytics services. When emails are sent from your email marketing tool, links may be rewritten automatically into unique links for each recipient to provide click tracking functionality. Glopal works seamlessly to preserve click tracking, while also rewriting links to target localized sites when clicked. In some cases, Geo-Location reported by click tracking analytics may appear less granular (showing the nearest major city in major countries) than when not using Glopal Email localization.

In addition, UTM and all other query parameters are preserved.

Sender Identity

By default, Glopal Email Localization sends emails using Glopal's sender identity. If the original email is sent From: "{Name}" <{Address}>, Glopal will resend a localized version of the email as From: "{Name}" <{StoreName}@glopalmail.com>.

Preserving the original display name, buyers will still recognize the sender in their inbox. The original sender's email will appear in the Reply-To header allowing buyers to reply directly to the original sender by clicking the reply button.

As emails will be remailed using Glopal's sender identity with DMARC alignment, in the default configuration, there is no need to adjust DKIM / SPF options in the DNS settings of your sender domain.

Alternatively, merchants can choose to use their own sender identity. To enable this, please provide SMTP credentials authorized to send from the sender domain to your Glopal account manager. Using your own SMTP server to send emails allows to track email deliverability as in your existing email flow.

Merchants integrating with can retrieve both true email and email alias and decide which email address to pass to different systems. For example, you can choose to associate the buyer's purchase with the true email address, but pass the alias email address into your CRM for sending marketing emails.

Merchants using receive the true email in the additional order note field, while the alias email address is used as the identity of the customer.

Glopal Order API
plug and play integration
site localization
Email Localization with Glopal Email Proxy
Email using Glopal Sender Identity
  • Email localization
  • Alias Address
  • POSTCreate Email Alias
  • Email Content
  • Email Tracking
  • Sender Identity

Create Email Alias

post
Authorizations
Path parameters
store_idstringRequired

Store Identifier

Body
addressstring ยท emailRequired
country_codestringRequired

ISO 3166-1 alpha-2 country code

Example: FRPattern: ^[A-Z]{2}$
currency_codestringRequired

ISO 4217 currency code

Example: EURPattern: ^[A-Z]{3}$
language_codestringRequiredExample: fr-FRPattern: ^(?<Language>[a-z]{2})(-(?<Script>[A-Z][a-z]{3}))?(-(?<Country>[A-Z]{2}))?$
Responses
200
Successful response
application/json
400
Invalid request
401
Invalid authentication
404
Store not found, or not authorized
post
POST /v2/email/{store_id}/alias HTTP/1.1
Host: 
Authorization: Bearer token
Content-Type: application/json
Accept: */*
Content-Length: 94

{
  "address": "name@gmail.com",
  "country_code": "FR",
  "currency_code": "EUR",
  "language_code": "fr-FR"
}
{
  "status": "ok",
  "aliased_address": "text"
}