Email generation and display methods, apparatus, equipment and storage media

CN116846858BActive Publication Date: 2026-08-11HANGZHOU ALIBABA INT INTERNET IND CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2023-06-06
Publication Date
2026-08-11

AI Technical Summary

Technical Problem

然而,现有的基于AMP技术开发的动态交互邮件通常是以页面维度为单位进行开发,不同的邮件页面还需要开发人员进行单独开发,这就使得基于AMP技术生成的邮件的生成效率较低

Benefits of technology

[0012]在本申请实施例中,能够预先在邮件组件库中加入同时适用于普通邮件版本和动态交互邮件版本的邮件组件,这样在有邮件创建需求时,便可直接从与邮件搭建平台关联的邮件组件库中选择符合邮件创建需求的邮件组件,组装得到目标邮件,由于目标邮件中的各邮件组件均支持普通邮件版本和动态交互邮件版本,因此该组装得到的目标邮件也可同时兼容普通邮件版本和动态交互邮件版本,避免动态交互邮件不适用于不支持动态交互邮件版本的客户端显示的问题,而且邮件组件库中的邮件组件可被多个邮件重复利用,也能有效提高了动态交互邮件的生成效率。

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN116846858B_ABST
    Figure CN116846858B_ABST
Patent Text Reader

Abstract

This application provides an email generation and display method, apparatus, device, and storage medium. In this application embodiment, the method includes: responding to an email creation request, creating a blank email template on an email building platform, the email template including a common content area and a content area to be configured, the common content area containing common email components; obtaining a target email component configured by the user for the content area to be configured from an email component library associated with the email building platform, thus obtaining an initial email; obtaining configuration data of the user for the target email component and the common email component; and generating a target email compatible with both ordinary email versions and dynamic interactive email versions, based on the configuration data of the target email component and the common email component and the initial email, according to the formats of ordinary email versions and dynamic interactive email versions.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of Internet information processing technology, and in particular to a method, apparatus, device and storage medium for generating and displaying emails. Background Technology

[0002] Email marketing (EDM, Email Direct Marketing) is a form of online marketing that delivers valuable information to target users via email, typically with the user's prior permission. Regular emails usually only support static content display, often redirecting users to the corresponding marketing product's web page by clicking on images or links displayed in the email. When using this method, users are unlikely to click on the product links shown in the email, leading to customer churn and fewer users ultimately reaching the marketing product's web page, thus significantly impacting the conversion rate of EDM emails.

[0003] In response to this, emails based on Accelerated Mobile Pages (AMP) technology are gaining increasing popularity in email marketing because they support dynamic interactive operations such as direct form operations within the email, asynchronous retrieval of the latest data, and rich interactivity, all without requiring redirection to a landing page. This effectively improves page click-through rates and thus increases the conversion rate of EDM emails. However, existing dynamic interactive emails developed based on AMP technology are typically developed on a page-by-page basis, requiring separate development for different email pages, resulting in low generation efficiency. Furthermore, some clients do not support the display format of emails generated using AMP technology, leading to the problem of these emails being unviewable by users. Summary of the Invention

[0004] This application provides a method, apparatus, device, and storage medium for generating and displaying emails, in order to improve the generation efficiency of emails generated based on AMP technology and address the issue that some clients do not support the display of emails generated based on AMP technology.

[0005] This application embodiment also provides an email generation method, comprising: responding to an email creation request, creating a blank email template on an email building platform, the email template including a public content area and a content area to be configured, the public content area containing a public email component; obtaining a target email component configured by the user for the content area to be configured from an email component library associated with the email building platform, thereby obtaining an initial email, wherein each email component stored in the email component library is applicable to both ordinary email versions and dynamic interactive email versions; obtaining configuration data of the user for the target email component and the public email component; and generating a target email compatible with both ordinary email versions and dynamic interactive email versions based on the configuration data of the target email component and the public email component and the initial email, according to the formats of ordinary email versions and dynamic interactive email versions.

[0006] This application embodiment also provides an email display method, including: receiving a target email, the target email being generated based on an email generation method; determining the email display environment of the client; and when the email display environment of the client supports a dynamic interactive email version, displaying the target email in the format of a dynamic interactive email version.

[0007] This application embodiment also provides an email generation device, including: a template creation module, used to create a blank email template on an email building platform in response to an email creation request, the email template including a common content area and a content area to be configured, the common content area containing common email components; a component acquisition module, used to acquire a target email component configured by the user for the content area to be configured from an email component library associated with the email building platform, to obtain an initial email, wherein each email component stored in the email component library is applicable to both ordinary email versions and dynamic interactive email versions; a data acquisition module, used to acquire configuration data of the user for the target email component and the common email component; and an email generation module, used to generate a target email compatible with both ordinary email versions and dynamic interactive email versions based on the configuration data of the target email component and the common email component and the initial email, according to the formats of ordinary email versions and dynamic interactive email versions.

[0008] This application embodiment also provides a client, including: an email receiving module for receiving a target email, the target email being generated based on an email generation method; an environment determination module for determining the email display environment of the client; and an email display module for displaying the target email in the format of a dynamic interactive email version when the email display environment of the client supports a dynamic interactive email version.

[0009] This application embodiment also provides an electronic device, including: a memory and a processor; the memory is used to store a computer program; the processor, coupled to the memory, is used to execute the computer program for: responding to an email creation request, creating a blank email template on an email building platform, the email template including a common content area and a content area to be configured, the common content area containing common email components; obtaining a target email component configured by the user for the content area to be configured from an email component library associated with the email building platform, obtaining an initial email, wherein each email component stored in the email component library is applicable to both ordinary email versions and dynamic interactive email versions; obtaining configuration data of the user for the target email component and the common email component; and generating a target email compatible with both ordinary email versions and dynamic interactive email versions based on the configuration data of the target email component and the common email component and the initial email, according to the formats of ordinary email versions and dynamic interactive email versions.

[0010] This application embodiment also provides an electronic device, including: a memory and a processor; the memory is used to store a computer program; the processor is coupled to the memory and is used to execute the computer program for: receiving a target email, the target email being generated based on an email generation method; determining the email display environment of the client; and when the email display environment of the client supports a dynamic interactive email version, displaying the target email in the format of a dynamic interactive email version.

[0011] This application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, causes the processor to implement the steps in the email generation method or email display method provided in this application.

[0012] In this embodiment, email components applicable to both regular email and dynamic interactive email versions can be pre-added to the email component library. When there is a need to create an email, the appropriate email component can be directly selected from the email component library associated with the email building platform to assemble the target email. Since each email component in the target email supports both regular and dynamic interactive email versions, the assembled target email is also compatible with both versions, avoiding the problem that dynamic interactive emails are not suitable for display on clients that do not support dynamic interactive email versions. Furthermore, the email components in the email component library can be reused for multiple emails, which also effectively improves the generation efficiency of dynamic interactive emails. Attached Figure Description

[0013] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0014] Figure 1 A schematic diagram illustrating the process of generating electronic marketing emails based on AMP technology, provided for existing technologies;

[0015] Figure 2 A schematic diagram illustrating a scenario of an email generation method provided in one embodiment of this application;

[0016] Figure 3 A flowchart illustrating the application of an email generation method provided in one embodiment of this application;

[0017] Figure 4 A flowchart illustrating an exemplary embodiment of this application for generating an email;

[0018] Figure 5 A schematic diagram illustrating the functions of the email building platform in the email generation method provided as an exemplary embodiment of this application;

[0019] Figure 6 A schematic diagram illustrating the addition of functionality to the email component in the email building platform within the email generation method provided in an exemplary embodiment of this application;

[0020] Figure 7 A schematic diagram illustrating the configuration data of the variables to be configured for the email component in the email building platform of the email generation method provided in an exemplary embodiment of this application;

[0021] Figure 8 A schematic diagram of an email preview mode in an email building platform provided in an exemplary embodiment of this application;

[0022] Figure 9 A schematic diagram of another email preview mode in the email building platform of the email generation method provided in an exemplary embodiment of this application;

[0023] Figure 10 A schematic diagram of an actual process for applying the email generation method provided in the embodiments of this application;

[0024] Figure 11 A schematic diagram illustrating the implementation process of the email display method provided in this application embodiment;

[0025] Figure 12 A schematic diagram of the structure of an email generation apparatus provided as an exemplary embodiment of this application;

[0026] Figure 13A schematic diagram of the structure of a client provided for an exemplary embodiment of this application;

[0027] Figure 14 A schematic diagram of the structure of an electronic device provided as an exemplary embodiment of this application;

[0028] Figure 15 A schematic diagram of the structure of another electronic device provided as an exemplary embodiment of this application. Detailed Implementation

[0029] Many specific details are set forth in the following description to provide a full understanding of this application. However, this application can be implemented in many other ways different from those described herein, and those skilled in the art can make similar extensions without departing from the spirit of this application; therefore, this application is not limited to the specific embodiments disclosed below.

[0030] The terminology used in one or more embodiments of this application is for the purpose of describing particular embodiments only and is not intended to limit the scope of one or more embodiments of this application. The singular forms “a,” “the,” and “the” used in one or more embodiments of this application and in the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” used in one or more embodiments of this application refers to and includes any or all possible combinations of one or more associated listed items.

[0031] It should be understood that although the terms first, second, etc., may be used to describe various information in one or more embodiments of this application, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, first may also be referred to as second without departing from the scope of one or more embodiments of this application, and similarly, second may also be referred to as first. Depending on the context, the word "if" as used herein may be interpreted as "when," "when," or "in response to a determination."

[0032] First, the terms and concepts involved in one or more embodiments of this application will be explained.

[0033] EDM: This stands for Email Direct Marketing, a direct marketing method that uses email to communicate with customers and is widely used in the field of online marketing.

[0034] AMP: Accelerated Mobile Pages is a web component framework that easily enables high-performance, highly interactive, and user-centric web pages, advertisements, EDM, and other web experiences. AMP can be used to send interactive, dynamic emails (hereinafter referred to as dynamic interactive emails).

[0035] Conversion rate: The conversion rate is calculated as follows: (A) Number of users who clicked on the marketing email / (B) Total number of users who opened the marketing email.

[0036] As described in the background section, when using regular email for email marketing (EDM), users need to perform additional clicks to be redirected to the marketing product's web page. This process can easily lead to user churn, resulting in low EDM conversion rates. To address this, Google developed AMP technology, short for Accelerated Mobile Pages, a web component framework that easily creates user-centric web experiences. AMP's biggest advantages lie in search engine optimization and improved page experience. AMP email is a subset of AMP, primarily relying on Google's Gmail client. Defined as next-generation email, its key feature is dynamic interactivity. While regular email does not allow custom scripts, AMP email, using officially provided components, can achieve dynamic interactive effects that are impossible in regular email.

[0037] Figure 1 A schematic diagram of the existing process for generating electronic marketing emails based on AMP technology, such as Figure 1 As shown, the process may include: s11, developers write email code suitable for the regular email version and email code suitable for the AMP format based on email development requirements; s12, developers combine the developed email code suitable for the regular email version and the email code suitable for the AMP format to generate a complete email code for the email to be sent; s13, the email code suitable for the AMP format in the email code for the email to be sent is validated; s14, after the email code suitable for the AMP format in the email code for the email to be sent passes validation, the email code for the email to be sent is sent to the email sending platform, which then sends the email corresponding to the email code to the corresponding client user; s15, the client user views and operates the received email.

[0038] During the development phase, due to some clients' incompatibility with AMP email display, developers typically need to write two sets of email code: one for the AMP format and one for a regular email version. These two sets of code must then be manually merged, and the AMP-compatible code must be copied from the official AMP website. The validity of the AMP-compatible code must be manually verified before it is sent to the client. Even emails developed using the same template require repeating this process. Clearly, the current process for generating marketing emails based on AMP technology is cumbersome, resulting in low efficiency in AMP email generation.

[0039] To address the numerous shortcomings of current AMP-based email marketing generation methods, the method provided in this application pre-adds email components to an email component library that are compatible with both standard and dynamic interactive email versions. When an email creation requirement arises, a suitable email component can be directly selected from the email component library associated with the email building platform and assembled into the target email. Since each email component in the target email supports both standard and dynamic interactive email versions, the assembled target email is also compatible with both versions, avoiding the problem of AMP-based email marketing generation being unsuitable for clients that do not support dynamic interactive email versions. Furthermore, the email components in the email component library can be reused across multiple emails, effectively improving the generation efficiency of dynamic interactive emails. Specifically, this application provides an email generation method, which also relates to email generation apparatus, electronic devices, and computer-readable storage media, each of which will be described in detail in the following embodiments.

[0040] See Figure 2 and Figure 3 , Figure 2 The illustration shows a scenario diagram of an email generation method according to an embodiment of this application. Figure 3 A flowchart illustrating an email generation method according to an embodiment of this application is shown. In one embodiment of this application, to improve the development efficiency of emails generated based on AMP technology, the development module can pre-develop the various email components that make up the dynamic interactive email according to the operational needs of the dynamic interactive email, and register each email component on the email building platform, thereby establishing an association between each email component and the email building platform. Specifically, each email component can be added to... Figure 2 Save the email component library as shown, and establish the email component library with... Figure 2The diagram illustrates the relationships between email platform architectures. Furthermore, to avoid email version compatibility issues, when developing various email components for dynamic interactive emails, consider using the same codebase to develop both email components adapted for the standard email version and those adapted for the dynamic interactive email version (i.e., AMP email). Specifically, a single code directory can be used to create two subdirectories, one for storing code for the standard email version and the other for the dynamic interactive email version.

[0041] Specifically, such as Figure 3 As shown, the method provided in the embodiments of this specification is applied to... Figure 2 The email building platform shown is used to create dynamic interactive emails (i.e., target emails). When a user needs to create such emails, they can create a blank email template through the platform. The user can then select email components from the component library that meet their operational needs using the platform's component selection module. They can configure the reserved variables in the email components (including common and user-selected components) within the template to obtain the component configuration data. Finally, the concatenation module combines the email template, email components, and configuration data. Figure 2 The preview browser renders the email template, email component description, and configuration data that make up the target email based on the code for both the regular email version and the dynamic interactive email version (i.e., AMP email) corresponding to each email component. This allows for the rendering of target emails compatible with both dynamic interactive and regular email versions. The preview module simulates and displays these two versions of email, and the browser allows switching between these versions. Finally, the sending module sends this target email, compatible with both dynamic interactive and regular email versions, to the client user. Figure 2 As shown, this determines which version of the target email to display based on whether the client supports the AMP format. Clearly, in this process, the same email component can be reused during the development of dynamically interactive email versions, and emails generated using this method are compatible with both regular and dynamically interactive versions.

[0042] As can be seen, in the above application scenarios, email components are pre-developed by developers and registered in the email building platform to establish a relationship with the platform. When there is a need to create an email, the appropriate email component can be selected directly from the email component library associated with the platform to assemble the target email. Since each email component in the target email supports both plain email and dynamic interactive email versions, the assembled target email is also compatible with both versions, avoiding the problem that dynamic interactive emails are not suitable for display on clients that do not support them. Furthermore, the email components in the email component library can be reused for multiple emails, which also effectively improves the generation efficiency of dynamic interactive emails.

[0043] It should be noted that the above application scenarios are only used to illustrate the methods provided in the embodiments of this specification, and do not constitute a limitation on the methods provided in the embodiments of this specification. The methods provided in the embodiments of this specification can create dynamic interactive emails through various AMP-based technologies.

[0044] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use and processing of the relevant data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and corresponding operation portals are provided for users to choose to authorize or refuse.

[0045] Figure 4 This is a flowchart illustrating an exemplary embodiment of the present application for generating an email. Figure 4 As shown, the method includes:

[0046] Step 410: In response to the email creation request, create a blank email template on the email building platform. The email template includes a public content area and a content area to be configured. The public content area contains public email components.

[0047] To facilitate users' email creation process and allow them to promptly obtain the results of email creation, this email creation platform provides a visual creation function for the entire process. This means that users can see the results of each step of email creation from the very beginning. Figure 5 This is a functional diagram of the email building platform in the email generation method provided as an exemplary embodiment of this application. Figure 5This email platform provides users with an email component selection and sorting area, an email preview area, a preview mode switching area, and a data configuration area. The email component selection and sorting area allows users to drag and drop desired email components from the component library into a blank email template and customize their order. The email preview area generates an email based on the selected components and displays a simulated version. The preview mode switching area allows users to switch the displayed version and client. The data configuration area allows users to configure variables within the email components of the email template.

[0048] A blank email template can be obtained from multiple emails generated within a historical time period. The common areas of these emails are extracted as the common content area, and the unique personalized content area of ​​each email is extracted as the content area to be configured.

[0049] To improve email creation efficiency, this public content area can also include public email components. To avoid email version compatibility issues, the code for each public email component can include both regular email and dynamic interactive email versions. Furthermore, to adapt to email display on different clients, the code for the regular email version of each public email component can include both mobile and desktop code, and the code for the dynamic interactive email version can also include both mobile and desktop code. The configurable content area can be a blank area in the email template. This configurable content area can be customized by the user by selecting email components from the email component library and determining the display position of the email components, or it can be displayed according to the pre-set positions of each email component within the email.

[0050] In some exemplary embodiments, to improve email generation efficiency, the necessary email components can be determined in advance based on the operational needs of the email (i.e., email generation needs), and the development of each email component can be completed. The developed email components are then added to an email component library to achieve reuse of each component. In other words, an email component is only developed and added to the email component library when it is first requested. Subsequent times when the component is needed, it can be directly selected from the library without repeated development, thus effectively improving email generation efficiency. Specifically, before creating a blank email template on the email platform in response to an email creation request, the method provided in this application embodiment further includes:

[0051] Obtain the generation requirements for the target email;

[0052] Based on the generation requirements of the target email, the code corresponding to multiple email components in the target email is constructed. The code corresponding to an email component includes the code for a regular email version and the code for a dynamic interactive email version.

[0053] Add the code corresponding to the multiple email components in the target email to the email component library;

[0054] Associate the email component library with the email building platform.

[0055] Because some email clients support displaying dynamically interactive email versions while others only display the standard version, and because some clients are installed on mobile devices (e.g., phones) while others are installed on desktop computers, their email size requirements also differ. Therefore, to meet the display needs of different client versions and provide email users with a better email viewing experience, subdirectories for the standard email version and the dynamically interactive email version can be added to the code development directory of each email component. Furthermore, subdirectories for the mobile and desktop versions can be added within the standard email version code subdirectory, and further subdirectories for the dynamically interactive email version code subdirectory. This allows the client to determine which part of the email code to render and display based on the client's specific needs after receiving the email.

[0056] As an optional implementation, developers can initialize the code for each email component using a scaffolding method. The scaffolding automatically generates two directories: one for the dynamic interactive email (AMP email) version and the other for the regular email version. Each directory can be further divided into mobile and desktop code directories. In the dynamic interactive email version's code directory, code conforming to the AMP specification can be written; in the regular email version's code directory, code conforming to the regular email specification can be written. The entry points for these directories can be provided to the email platform, which can then select the appropriate entry point during email preview to render and preview different versions and formats of emails.

[0057] Furthermore, during the email component development process, some configurable variables can be reserved for email builders (i.e., operations personnel) to configure later. After each email component is developed, its corresponding code can be packaged and published to the cloud, and its calling entry point can be added to the email component library, allowing the email building platform to select and add each email component from the library. It should be understood that while developing each email component, a copy of the email's HTML structure also needs to be configured, namely the blank email template mentioned above. This template describes the common content area and the content to be configured. The common content area includes common component packages and common styles, among other things.

[0058] Step 420: Obtain the target email component configured by the user for the content area to be configured from the email component library associated with the email building platform, and obtain the initial email. The email components stored in the email component library are applicable to both the regular email version and the dynamic interactive email version.

[0059] Figure 6 This diagram illustrates the function of adding email components to an email building platform in the email generation method provided in an exemplary embodiment of this application. Users can select the "Add Email Component" button on this interface to trigger the display of a list of email components in the email component library. Users can then drag and drop any required email components from the displayed list to the configurable content area in the email template according to operational needs. Specifically, the initial email is obtained by retrieving the target email component configured by the user for the configurable content area from the email component library associated with the email building platform, including:

[0060] Retrieve the target email component selected by the user from the email component library associated with the email building platform for the configurable content area;

[0061] Get the display position configured by the user for the target email component in the configurable content area, and generate the initial email based on the display position configured by the user for the target email component in the configurable content area.

[0062] The display position of the target email component configured by the user in the configurable content area can be determined based on the destination area where the user drags the target email component, or it can be determined based on the order in which the user drags it. Specifically, multiple areas in the configurable content area that can hold email components can be pre-sorted. For example, the multiple areas in the configurable content area that can hold email components can include areas 1 to N. The email component 1 dragged by the user for the first time can be placed in area 1, the email component 2 dragged by the user for the second time can be placed in area 2, and so on, until areas 1 to N are filled with email components. After the user has finished dragging and dropping email components in areas 1 to N, the order of these email components can be adjusted as needed. For example, if email component 2 in area 2 is dragged to area 1, then email component 1 in area 1 will automatically be displayed in area 2.

[0063] Step 430: Obtain the user's configuration data for the target email component and the public email component.

[0064] The target email component and the public email component can reserve some configurable variables during email component development, such as user salutation, content description, header banner image, text background color, font color, and font style. These configurable variables can be displayed to the user when selecting configuration data in the email building platform, allowing the user to perform data configuration operations. Specifically, the target email component and the public email component also reserve configurable variables to obtain the user's configuration data for the target email component and the public email component, including:

[0065] In response to user requests for data configuration for the email platform, display the configurable areas in the target email component and the public email component;

[0066] Retrieves the configuration data of the user for the variables to be configured in the target email component and the public email component in the configurable areas of the target email component and the public email component.

[0067] The configuration data for the target email component includes target marketing content, which supports interactive operations. This target marketing content can include product images, product surveys, and other marketing materials. Because the target email component supports dynamic interactive operations, when the configuration data in the target email component is target marketing content, it also supports dynamic interactive operations. When a user in the email client interacts with the target marketing content, the dynamic interactive results of that target marketing content will be displayed in its display area. For example, when the target marketing content is a product image, when a user in the email client clicks on the product image, a purchase entry point for the product can be directly displayed in the display area of ​​the target marketing content.

[0068] Figure 7This diagram illustrates the configuration data for the variables to be configured in the email component within the email building platform of the email generation method provided in an exemplary embodiment of this application. Users can select... Figure 5 The "Configure Data" button shown triggers a data configuration request for the email platform and displays the configuration. Figure 7 The configurable areas in the target email component and the public email component are shown. These configurable areas include variables to be configured such as email subject, email subtitle, AMP form question 1, AMP form question 2, AMP form submission address, and email background color. Users can configure these variables according to their operational needs.

[0069] Step 440: Based on the configuration data of the target email component and the public email component, as well as the initial email, generate a target email compatible with both the regular email version and the dynamic interactive email version, according to the formats of the regular email version and the dynamic interactive email version.

[0070] Obviously, by using the email generation method provided in this application embodiment, each email component only needs to be developed once. After the email component is added to the email component library, the email component library is associated with the email building platform, so that email operators can complete operations such as selecting, editing and generating email components in the email building platform. Moreover, it supports the simulated display of the format of ordinary email version and dynamic interactive email version, which can help operators find problems in the generated email in a timely manner and effectively improve email generation efficiency.

[0071] In some exemplary embodiments, based on the configuration data of the target email component and the public email component, and the initial email, a target email compatible with both the regular email version and the dynamic interactive email version is generated, according to the formats of the regular email version and the dynamic interactive email version, including:

[0072] From the initial email, obtain the email component description of the target email. The email component description of the target email includes the location of each email component in the target email, the version number of each email component, and the address of each email component.

[0073] Based on the description of the email components in the target email and the configuration data of the target email components and the common email components, each email component in the target email is rendered according to the format of the ordinary email version and the dynamic interactive email version, respectively, to obtain the HTML code of the ordinary email version and the dynamic interactive email version corresponding to each email component.

[0074] The HTML code of the target email is obtained by concatenating the HTML code of the regular email version and the HTML code of the dynamic interactive email version corresponding to each email component in the target email into a blank email template.

[0075] Based on the HTML code of the target email, generate a target email compatible with both regular email versions and dynamically interactive email versions.

[0076] The description of the email components in the target email may also include information such as the number of email components in the target email, the dependencies between email components, and the version of each email component.

[0077] The information required to render an email includes an email template, email component descriptions, and configuration data. The email template is the structural description of the email, including HTML standards, meta tags, and header and footer descriptions. The email component description, as mentioned above, is a set of code descriptions generated during email generation based on the email components selected by the user. It includes information such as the order (i.e., the position) of each email component, its version, address, dependencies, and number. Configuration data consists of the configuration data for the user-editable variables within each email component, including email title, subtitle, and other configuration variables.

[0078] Optionally, based on the email component description of the target email and the configuration data of the target email component and the common email component, each email component in the target email is rendered according to the format of a regular email version and a dynamic interactive email version. This can be performed using a rendering SDK, a JavaScript package that can obtain the email template, email component description, and configuration data. Combined with the React common package, it renders each email component according to the format of a regular email version and a dynamic interactive email version (i.e., renders the code for the regular email version and the code for the dynamic interactive email version corresponding to each email component), obtaining the HTML code for the regular email version and the dynamic interactive email version corresponding to each email component. Then, according to the position of each email component, the HTML code of each email component is combined and concatenated into the email structure to generate the HTML code for the regular email version and the dynamic interactive email version of the target email, conforming to email sending specifications. Finally, the HTML code for the regular email version and the dynamic interactive email version of the target email are concatenated to generate the HTML code for the target email.

[0079] In some exemplary embodiments, to facilitate operators in promptly viewing the generation effect of the target email and identifying potential problems, this application embodiment can also simulate the display of both a plain email version and a dynamically interactive email version of the target email during the target email generation process. Specifically, based on the HTML code of the target email, generating a target email compatible with both the plain email version and the dynamically interactive email version includes:

[0080] Send the HTML code of the target email to the preview browser. The preview browser includes a normal email version preview mode and a dynamic interactive email version preview mode.

[0081] By using a preview browser set to plain email version preview mode, the plain email version code of each email component in the HTML code of the target email is rendered to simulate the display of the target email in the format of plain email.

[0082] In addition, by using a preview browser set to dynamic interactive email version preview mode, the code of each email component in the HTML code of the target email is rendered to simulate the display of the target email in the format of dynamic interactive email version, generating a target email that is compatible with both ordinary email version and dynamic interactive email version.

[0083] The preview browser is a browser with an embedded iframe page. This preview browser can be built into the email platform as a container to simulate the presentation effect of the target email being opened in the client.

[0084] Figure 8 This diagram illustrates an email preview mode within an email platform provided as an exemplary embodiment of this application. Users can choose between a dynamic interactive email version preview mode or a standard email version preview mode to simulate the display of the target email, providing operators with a WYSIWYG (What You See Is What You Get) presentation. Figure 8 This is a preview image showing the preview effect when selecting the normal email version preview mode.

[0085] The URL parameters for the preview mode of the regular email version correspond to those for the regular email version, while the URL parameters for the preview mode of the dynamic interactive email version correspond to those for the dynamic interactive email version. Based on the URL parameters of the preview mode, the code of the corresponding email component is called from the code directory of each email component to perform the rendering operation.

[0086] In some exemplary embodiments, to adapt to the display of different clients and provide better email display effects for client users, the preview browser also includes a mobile preview mode and a desktop preview mode. The code for a regular email version corresponding to an email component includes both mobile and desktop code, and the code for a dynamic interactive email version corresponding to an email component includes both mobile and desktop code. By using a preview browser set to dynamic interactive email version preview mode, the dynamic interactive email version code of each email component in the HTML code of the target email is rendered to simulate the display of the target email according to the format of the dynamic interactive email version, including:

[0087] By using a preview browser set to mobile preview mode in dynamic interactive email version preview mode, the mobile code corresponding to the dynamic interactive email version of each email component in the target email's HTML code is rendered to simulate the display of the target email in dynamic interactive email version according to the mobile display format.

[0088] By using a preview browser set to desktop preview mode in dynamic interactive email version preview mode, the desktop code corresponding to the dynamic interactive email version of each email component in the target email's HTML code is rendered to simulate the display of the target email in the desktop display format.

[0089] The URL parameters for the mobile preview mode correspond to the URL parameters for the mobile email display format, while the URL parameters for the desktop preview mode correspond to the URL parameters for the desktop email display format.

[0090] Figure 9 This is a schematic diagram illustrating another email preview mode in the email building platform of the email generation method provided in an exemplary embodiment of this application. Figure 9 In the dynamic interactive email version preview mode, users can choose between desktop and mobile preview modes. Alternatively, in the standard email version preview mode, users can choose between desktop and mobile preview modes to simulate the display of the target email. Figure 9 This is a screenshot showing the preview effect in the mobile preview mode of the regular email version preview mode.

[0091] In some exemplary embodiments, after the target email is generated, an email sending interface can be called to send the HTML code of the target email to the target email client user. After the HTML code of the target email is sent to the target email client user, the version and display format of the target email can be determined based on whether the client supports the display of dynamic interactive emails and whether the client is a mobile or PC client.

[0092] In some exemplary embodiments, after a user previews the target email, they can modify it according to their needs. For example, they can modify the category of the target email and the configuration data of the variables to be configured in the email components within the target email. For details, please click [link to documentation]. Figure 8 and Figure 9 The "Data Configuration" function triggers a modification request for the target email. Specifically, in response to a user's modification operation on the simulated target email, it can obtain the user's modification information for the simulated target email. The modification information includes the category of the email component in the target email and the configuration data of the variables to be configured for the email component in the target email.

[0093] Based on the modified information, modify the target email displayed in the simulation.

[0094] In some exemplary embodiments, since AMP emails have separate validation rules, the code of the dynamic interactive email versions of each email component in the target email can be validated before the email is sent to determine whether the target email conforms to the AMP email specification. Specifically, a preview browser set to dynamic interactive email version preview mode renders the code of the dynamic interactive email versions of each email component in the HTML code of the target email to simulate the display of the target email according to the format of the dynamic interactive email version, including:

[0095] By using a preview browser set to dynamic interactive email version preview mode, the code for dynamic interactive email versions of each email component in the HTML code of the target email is verified.

[0096] When the dynamic interactive email version code of each email component in the HTML code of the target email passes the validation, the dynamic interactive email version code of each email component in the HTML code of the target email is rendered to simulate the display of the target email in the format of the dynamic interactive email version.

[0097] To further improve the accuracy of the verification, a more granular verification can be performed on the dynamic interactive email versions of each email component in the target email's HTML code before calling the email sending interface and sending the target email's HTML code to the target email's client user.

[0098] Figure 10 This is a schematic diagram illustrating an actual process of applying the email generation method provided in the embodiments of this application. Figure 10 In, it may include:

[0099] S101, build email components based on operational needs.

[0100] The code for an email component includes code for a regular email version and code for a dynamically interactive email version. The code for a regular email version of an email component includes code for both mobile and desktop versions. The code for a dynamically interactive email version of an email component includes code for both mobile and desktop versions.

[0101] S102, Add the email component to the email component library.

[0102] Specifically, the entry points for calling the code of the regular email version and the dynamic interactive email version of the email component, as well as the entry points for calling the code of the mobile and desktop versions under each version, can be packaged and added to the email component library.

[0103] S103, Establish the association between the email component library and the email building platform.

[0104] S104, Select an email component from the email component library.

[0105] At the same time, obtain the email component description for each email component, which includes the location, version number, and address of each email component.

[0106] S105, Configure the data for the variables to be configured in the email component.

[0107] S106, Generate the HTML code for the target email.

[0108] Specifically, based on the description of the email components in the target email and the configuration data of the target email components and common email components, the rendering SDK can be used to render each email component in the target email according to the format of a regular email version and a dynamic interactive email version, respectively, to obtain the HTML code of the regular email version and the dynamic interactive email version corresponding to each email component. The HTML code of the regular email version and the dynamic interactive email version corresponding to each email component in the target email can be concatenated into a blank email template to obtain the HTML code of the target email.

[0109] S107, based on the HTML code of the target email, simulates the display of the target email as a regular email version / dynamic interactive email version.

[0110] S108, call the sending interface to send the target email to the client user.

[0111] Each version of the email preview also allows you to choose between mobile or desktop preview modes.

[0112] The email generation method provided in this application allows for the pre-addition of email components suitable for both regular and dynamic interactive email versions to the email component library. When an email creation requirement arises, a suitable email component can be directly selected from the email component library associated with the email building platform and assembled into the target email. Since each email component in the target email supports both regular and dynamic interactive email versions, the assembled target email is also compatible with both versions, avoiding the problem of dynamic interactive emails being unsuitable for clients that do not support them. Furthermore, the email components in the email component library can be reused across multiple emails, effectively improving the generation efficiency of dynamic interactive emails.

[0113] Figure 11 This is a flowchart illustrating an email display method applied to a client, as provided in an exemplary embodiment of this application. Figure 11 As shown, the method includes:

[0114] Step 1110: Receive the target email, which is generated based on the email generation method.

[0115] Among them, the target email can be categorized as follows: Figures 2-9 The email was generated using the method shown.

[0116] Step 1120: Determine the email display environment for the client.

[0117] This includes determining the email display environment of the client, which may specifically include determining whether the client is installed on a mobile device or a computer, and whether the client supports the display of dynamic interactive email versions.

[0118] Step 1130: When the client's email display environment supports dynamic interactive email versions, display the target email in the format of a dynamic interactive email version.

[0119] Specifically, when the client's email display environment supports dynamic interactive email versions, the client can render the dynamic interactive email version code of each email component in the target email's HTML code, thereby displaying the target email in the format of a dynamic interactive email version. When the client's email display environment does not support dynamic interactive email versions, the client can render the plain email version code of each email component in the target email's HTML code, thereby displaying the target email in the format of a plain email version.

[0120] It should be understood that due to differences in aspect ratios and other dimensions between mobile and desktop devices, to provide users with a better email display experience, the mobile client and desktop client can be displayed differently. Specifically, when the client's email display environment supports dynamic interactive email versions, the target email will be displayed according to the format of the dynamic interactive email version, including:

[0121] When the client is determined to be a mobile client, the client renders the mobile code corresponding to the dynamic interactive email version of each email component in the HTML code of the target email, so as to display the target email in the mobile display format according to the mobile display format.

[0122] When the client is determined to be a desktop client, the client renders the desktop code corresponding to the dynamic interactive email version of each email component in the HTML code of the target email, so as to display the target email in the desktop display format.

[0123] When the client's email display environment does not support dynamic interactive email versions, the target email will be displayed in the format of a regular email, including:

[0124] When the client is determined to be a mobile client, the client renders the mobile version of the regular email version of each email component in the HTML code of the target email so that the regular email version of the target email is displayed in the mobile display format.

[0125] When the client is determined to be a desktop client, the client renders the desktop version of the regular email version of each email component in the HTML code of the target email, so as to display the regular email version of the target email in the desktop display format.

[0126] Optionally, since the dynamic interactive version of the email supports interactive operations within the email display interface and can directly display the interaction results to the user without requiring the user to click on a redirect link to view the marketing content, it can effectively improve the conversion rate of the marketing content. Specifically, after displaying the target email in the format of the dynamic interactive email version, the method further includes:

[0127] Acquire user interactions with targeted marketing content;

[0128] Display the response results of interactive actions in the display area of ​​the targeted marketing content.

[0129] The email display method provided in this application can detect the email display environment of target emails that are compatible with both regular and dynamic interactive versions. When the client's email display environment supports the dynamic interactive version, the target email is prioritized for display in the format of the dynamic interactive version, effectively increasing the probability of user interaction with the target email and thus improving the click-through rate of the marketing content displayed within the target email. Furthermore, since the generated target email is compatible with both dynamic interactive and regular email versions, the problem of dynamic interactive emails being unsuitable for display on clients that do not support dynamic interactive versions is avoided.

[0130] It should be noted that the execution subject of each step of the method provided in the above embodiments can be the same device, or the method can be executed by different devices. For example, the execution subject of steps 410 to 440 can be device A; or the execution subject of steps 410 to 420 can be device A, and the execution subject of steps 430 to 440 can be device B; and so on.

[0131] Furthermore, some processes described in the above embodiments and accompanying drawings include multiple operations that appear in a specific order. However, it should be clearly understood that these operations may not be executed in the order they appear herein, or they may be executed in parallel. The operation numbers, such as 410, 420, etc., are merely used to distinguish different operations and do not represent any execution order. In addition, these processes may include more or fewer operations, and these operations may be executed sequentially or in parallel.

[0132] Figure 12 This is a schematic diagram of the structure of an email generation device provided for an exemplary embodiment of this application. Figure 12 As shown, the device 1200 includes: a template creation module 1210, a component acquisition module 1220, a data acquisition module 1230, and an email generation module 1240, wherein:

[0133] The template creation module 1210 is used to create a blank email template in the email building platform in response to an email creation request. The email template includes a public content area and a content area to be configured. The public content area contains public email components.

[0134] The component acquisition module 1220 is used to acquire the target email component configured by the user for the content area to be configured from the email component library associated with the email building platform, and obtain the initial email. The email components stored in the email component library are applicable to both ordinary email versions and dynamic interactive email versions.

[0135] The data acquisition module 1230 is used to acquire the user's configuration data for the target email component and the public email component;

[0136] The email generation module 1240 is used to generate a target email compatible with both the ordinary email version and the dynamic interactive email version, based on the configuration data of the target email component and the public email component and the initial email, and in accordance with the formats of the ordinary email version and the dynamic interactive email version.

[0137] The email generation apparatus provided in this application embodiment can pre-add email components that are applicable to both regular email versions and dynamic interactive email versions to the email component library. In this way, when there is a need to create an email, the email component that meets the email creation requirements can be directly selected from the email component library associated with the email building platform and assembled to obtain the target email. Since each email component in the target email supports both regular email versions and dynamic interactive email versions, the assembled target email can also be compatible with both regular email versions and dynamic interactive email versions. This avoids the problem that dynamic interactive emails are not suitable for display on clients that do not support dynamic interactive email versions. Moreover, the email components in the email component library can be reused for multiple emails, which can also effectively improve the generation efficiency of dynamic interactive emails.

[0138] Email generation devices can achieve Figures 2 to 10 For details of the method implementation examples, please refer to [link / reference]. Figures 2 to 10 The email generation method shown in the embodiment will not be described in detail again.

[0139] Optionally, before the template creation module 1210 creates a blank email template on the email building platform in response to the email creation request, the device further includes a component association module for:

[0140] Obtain the generation requirements for the target email;

[0141] Based on the generation requirements of the target email, code corresponding to multiple email components in the target email is constructed. The code corresponding to one email component includes code for a regular email version and code for a dynamic interactive email version.

[0142] Add the code corresponding to the multiple email components in the target email to the email component library;

[0143] Associate the email component library with the email building platform.

[0144] Optionally, when the component acquisition module 1220 acquires the target email component configured by the user for the configurable content area from the email component library associated with the email building platform to obtain the initial email, it is specifically used for:

[0145] Obtain the target email component selected by the user from the email component library associated with the email building platform for the configurable content area;

[0146] The system obtains the display position configured by the user for the target email component in the configurable content area, and generates the initial email based on the display position configured by the user for the target email component in the configurable content area.

[0147] Optionally, the target email component and the public email component also reserve variables to be configured. When the data acquisition module 1230 acquires the user's configuration data for the target email component and the public email component, it is specifically used for:

[0148] In response to a user's data configuration request for the email platform, the configurable areas in the target email component and the public email component are displayed.

[0149] Obtain the configuration data of the variables to be configured for the target email component and the public email component in the configurable areas of the target email component and the public email component.

[0150] Optionally, when the email generation module 1240 generates a target email compatible with both the ordinary email version and the dynamic interactive email version based on the configuration data of the target email component and the public email component, and the initial email, according to the formats of the ordinary email version and the dynamic interactive email version, it is specifically used for:

[0151] From the initial email, obtain the email component description of the target email, which includes the location of each email component in the target email, the version number of each email component, and the address of each email component.

[0152] Based on the description of the email components of the target email and the configuration data of the target email components and the common email components, each email component in the target email is rendered according to the format of the ordinary email version and the dynamic interactive email version, respectively, to obtain the HTML code of the ordinary email version and the dynamic interactive email version corresponding to each email component.

[0153] The HTML code of the target email is obtained by concatenating the HTML code of the regular email version and the HTML code of the dynamic interactive email version corresponding to each email component in the target email into the blank email template.

[0154] Based on the HTML code of the target email, generate a target email compatible with both regular email and dynamic interactive email versions.

[0155] Optionally, when the email generation module 1240 generates a target email compatible with both regular and dynamically interactive versions based on the HTML code of the target email, it is specifically used for:

[0156] The HTML code of the target email is sent to a preview browser, which includes a normal email version preview mode and a dynamic interactive email version preview mode.

[0157] By using a preview browser set to the normal email version preview mode, the code of each email component in the HTML code of the target email is rendered to simulate the display of the target email in the format of the normal email version.

[0158] And by using a preview browser set to the dynamic interactive email version preview mode, the code of each email component in the HTML code of the target email is rendered to simulate the display of the target email in the format of the dynamic interactive email version, thereby generating a target email compatible with both the ordinary email version and the dynamic interactive email version.

[0159] Optionally, the preview browser further includes a mobile preview mode and a desktop preview mode. The code for a regular email version corresponding to one of the email components includes both mobile and desktop code. The code for a dynamic interactive email version corresponding to one of the email components includes both mobile and desktop code. The email generation module 1240, through a preview browser set to the dynamic interactive email version preview mode, renders the dynamic interactive email version code of each email component in the HTML code of the target email. Specifically, when simulating the display of the target email according to the dynamic interactive email version format, it is used for:

[0160] By using a preview browser set to the mobile preview mode of the dynamic interactive email version preview mode, the mobile code corresponding to the dynamic interactive email version of each email component in the HTML code of the target email is rendered to simulate the display of the target email of the dynamic interactive email version according to the mobile display format.

[0161] By using a preview browser set to the computer preview mode in the dynamic interactive email version preview mode, the computer code corresponding to the dynamic interactive email version of each email component in the HTML code of the target email is rendered, so as to simulate the display of the target email in the dynamic interactive email version according to the computer display format.

[0162] Optionally, the device further includes an email editing module for:

[0163] In response to a user's modification operation on the simulated target email, the modification information of the simulated target email is obtained, including the category of the email component in the target email and the configuration data of the variable to be configured of the email component in the target email.

[0164] Based on the modified information, the target email displayed in the simulation is modified.

[0165] Optionally, the email generation module 1240 renders the dynamic interactive email version code of each email component in the HTML code of the target email using a preview browser set to the dynamic interactive email version preview mode, specifically for simulating the display of the target email according to the format of the dynamic interactive email version when:

[0166] The code of the dynamic interactive email version of each email component in the HTML code of the target email is verified by using a preview browser set to the dynamic interactive email version preview mode.

[0167] When the dynamic interactive email version code of each email component in the HTML code of the target email passes the verification, the dynamic interactive email version code of each email component in the HTML code of the target email is rendered to simulate the display of the target email in the format of the dynamic interactive email version.

[0168] Optionally, the configuration data of the target email component includes target marketing content, which supports interactive operations.

[0169] Figure 13 This is a schematic diagram of the structure of a client 1300 provided for an exemplary embodiment of this application. For example... Figure 13 As shown, the client 1300 includes: an email receiving module 1310, an environment determination module 1320, and an email display module 1330, wherein:

[0170] Email receiving module 1310 is used to receive target emails, which are generated based on email generation methods;

[0171] The environment determination module 1320 is used to determine the email display environment of the client.

[0172] The email display module 1330 is used to display the target email in the format of a dynamic interactive email version when the email display environment of the client supports a dynamic interactive email version.

[0173] Optionally, the target email contains targeted marketing content, and after displaying the target email in a dynamic interactive email format, the client further includes:

[0174] The operation acquisition module is used to acquire user interaction operations in response to the target marketing content;

[0175] The results display module is used to display the response results of the interactive operation in the display area of ​​the target marketing content.

[0176] Email display devices can achieve Figure 11For details of the method implementation examples, please refer to [link / reference]. Figure 11 The email display method shown in the embodiment will not be described in detail again.

[0177] Figure 14 This is a schematic diagram of the structure of an electronic device provided as an exemplary embodiment of this application. For example... Figure 14 As shown, the device includes a first memory 141 and a first processor 142.

[0178] The first memory 141 is used to store computer programs and can be configured to store various other data to support operation on the computing device. Examples of this data include instructions for any application or method operating on the computing device, contact data, phone book data, messages, pictures, videos, etc.

[0179] A first processor 142, coupled to a first memory 141, is configured to execute a computer program stored in the first memory 141 for: responding to an email creation request, creating a blank email template on an email building platform, the email template including a common content area and a content area to be configured, the common content area containing common email components; obtaining a target email component configured by the user for the content area to be configured from an email component library associated with the email building platform, obtaining an initial email, wherein each email component stored in the email component library is applicable to both ordinary email versions and dynamic interactive email versions; obtaining configuration data of the user for the target email component and the common email component; and generating a target email compatible with both ordinary email versions and dynamic interactive email versions based on the configuration data of the target email component and the common email component and the initial email, according to the formats of ordinary email versions and dynamic interactive email versions.

[0180] Furthermore, such as Figure 14 As shown, the electronic device also includes other components such as a first communication component 143, a first display 144, a first power supply component 145, and a first audio component 146. Figure 14 The diagram only shows some components and does not mean that the electronic device includes only these components. Figure 14 The components shown. Additionally, depending on the implementation of the traffic playback device, Figure 14 The components within the dashed box are optional, not mandatory. For example, when an electronic device is implemented as a terminal device such as a smartphone, tablet, or desktop computer, it may include... Figure 14 The components within the dashed box; when the electronic device is implemented as a server-side device such as a conventional server, cloud server, data center, or server array, it may be excluded. Figure 14 The component within the dashed box.

[0181] Accordingly, embodiments of this application also provide a computer-readable storage medium storing a computer program, which, when executed by a processor, enables the processor to implement the steps in the above-described email generation method embodiments.

[0182] The above Figure 14 The first communication component is configured to facilitate wired or wireless communication between the device containing the communication component and other devices. The device containing the communication component can access wireless networks based on communication standards, such as WiFi, 2G, or 3G, or combinations thereof. In one exemplary embodiment, the communication component receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, the first communication component may further include a near-field communication (NFC) module, radio frequency identification (RFID) technology, Infrared Data Association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, etc.

[0183] The above Figure 14 The first memory in the memory can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk or optical disk.

[0184] The above Figure 14 The first display includes a screen, which may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen can be implemented as a touchscreen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors can sense not only the boundaries of the touch or swipe action but also the duration and pressure associated with the touch or swipe operation.

[0185] The above Figure 14 The first power supply component provides power to various components of the device in which the first power supply component is located. The first power supply component may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to the device in which the power supply component is located.

[0186] The above Figure 14The first audio component can be configured to output and / or input audio signals. For example, the first audio component includes a microphone (MIC) configured to receive external audio signals when the device containing the first audio component is in an operating mode, such as call mode, recording mode, or voice recognition mode. The received audio signals can be further stored in memory or transmitted via a communication component. In some embodiments, the first audio component also includes a speaker for outputting audio signals.

[0187] Figure 15 This is a schematic diagram of the structure of an electronic device provided as an exemplary embodiment of this application. For example... Figure 15 As shown, the device includes: a second memory 151 and a second processor 152.

[0188] The second memory 151 is used to store computer programs and can be configured to store various other data to support operation on the computing device. Examples of this data include instructions for any application or method operating on the computing device, contact data, phone book data, messages, pictures, videos, etc.

[0189] The second processor 152, coupled to the second memory 151, is used to execute a computer program in the second memory 151 for: receiving a target email, the target email being generated based on an email generation method; determining the email display environment of the client; and, when the email display environment of the client supports a dynamic interactive email version, displaying the target email in the format of a dynamic interactive email version.

[0190] Furthermore, such as Figure 15 As shown, the electronic device also includes other components such as a second communication component 153, a second display 154, a second power supply component 155, and a second audio component 156. Figure 15 The diagram only shows some components and does not mean that the electronic device includes only these components. Figure 15 The components shown. Additionally, depending on the implementation of the traffic playback device, Figure 15 The components within the dashed box are optional, not mandatory. For example, when an electronic device is implemented as a terminal device such as a smartphone, tablet, or desktop computer, it may include... Figure 15 The components within the dashed box; when the electronic device is implemented as a server-side device such as a conventional server, cloud server, data center, or server array, it may be excluded. Figure 15 The component within the dashed box.

[0191] Accordingly, embodiments of this application also provide a computer-readable storage medium storing a computer program, which, when executed by a processor, enables the processor to implement the steps in the above-described email display method embodiments.

[0192] The above Figure 15 The second communication component is configured to facilitate wired or wireless communication between the device containing the communication component and other devices. The device containing the communication component can access wireless networks based on communication standards, such as WiFi, 2G, or 3G, or combinations thereof. In one exemplary embodiment, the communication component receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, the second communication component may further include a near-field communication (NFC) module, radio frequency identification (RFID) technology, Infrared Data Association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, etc.

[0193] The above Figure 15 The second memory in the memory can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk or optical disk.

[0194] The above Figure 15 The second display includes a screen, which may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen can be implemented as a touchscreen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors can sense not only the boundaries of the touch or swipe action but also the duration and pressure associated with the touch or swipe operation.

[0195] The above Figure 15 The second power supply component provides power to various components of the device in which the second power supply component is located. The second power supply component may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to the device in which the power supply component is located.

[0196] The above Figure 15 The second audio component can be configured to output and / or input audio signals. For example, the second audio component includes a microphone (MIC) configured to receive external audio signals when the device containing the second audio component is in an operating mode, such as call mode, recording mode, or voice recognition mode. The received audio signals can be further stored in memory or transmitted via a communication component. In some embodiments, the second audio component also includes a speaker for outputting audio signals.

[0197] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0198] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0199] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0200] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0201] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0202] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0203] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0204] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0205] The above description is merely an embodiment of this application and is not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. A method for generating emails, characterized in that, include: In response to an email creation request, a blank email template is created on the email building platform. The email template includes a common content area and a content area to be configured. The common content area contains common email components. The system retrieves the target email component configured by the user for the content area to be configured from the email component library associated with the email building platform, and obtains the initial email. The email component stored in the email component library is applicable to both the regular email version and the dynamic interactive email version. Obtain the user's configuration data for the target email component and the public email component; Based on the configuration data of the target email component and the public email component, as well as the initial email, a target email compatible with both the ordinary email version and the dynamic interactive email version is generated, according to the formats of the ordinary email version and the dynamic interactive email version. The ordinary email version corresponds to an email that does not support dynamic interactivity, while the dynamic interactive email version corresponds to an email that supports dynamic interactivity.

2. The method as described in claim 1, characterized in that, Before creating a blank email template on the email creation platform in response to the email creation request, the method further includes: Obtain the generation requirements for the target email; Based on the generation requirements of the target email, code corresponding to multiple email components in the target email is constructed. The code corresponding to one email component includes code for a regular email version and code for a dynamic interactive email version. Add the code corresponding to the multiple email components in the target email to the email component library; Associate the email component library with the email building platform.

3. The method as described in claim 1 or 2, characterized in that, The step of obtaining the initial email by acquiring the target email component configured by the user for the configurable content area from the email component library associated with the email building platform includes: Obtain the target email component selected by the user from the email component library associated with the email building platform for the configurable content area; The system obtains the display position configured by the user for the target email component in the configurable content area, and generates the initial email based on the display position configured by the user for the target email component in the configurable content area.

4. The method as described in claim 1, characterized in that, The target email component and the public email component also reserve variables to be configured. Obtaining the user's configuration data for the target email component and the public email component includes: In response to a user's data configuration request for the email platform, the configurable areas in the target email component and the public email component are displayed. Obtain the configuration data of the variables to be configured for the target email component and the public email component in the configurable areas of the target email component and the public email component.

5. The method as described in claim 2, characterized in that, The process of generating a target email compatible with both the standard email version and the dynamic interactive email version, based on the configuration data of the target email component and the public email component, and the initial email, according to the formats of the standard email version and the dynamic interactive email version, includes: From the initial email, obtain the email component description of the target email, which includes the location of each email component in the target email, the version number of each email component, and the address of each email component. Based on the description of the email components of the target email and the configuration data of the target email components and the common email components, each email component in the target email is rendered according to the format of the ordinary email version and the dynamic interactive email version, respectively, to obtain the HTML code of the ordinary email version and the dynamic interactive email version corresponding to each email component. The HTML code of the target email is obtained by concatenating the HTML code of the regular email version and the HTML code of the dynamic interactive email version corresponding to each email component in the target email into the blank email template. Based on the HTML code of the target email, generate a target email compatible with both regular email and dynamic interactive email versions.

6. The method as described in claim 5, characterized in that, The process of generating a target email compatible with both regular and dynamically interactive versions based on the HTML code of the target email includes: The HTML code of the target email is sent to a preview browser, which includes a normal email version preview mode and a dynamic interactive email version preview mode. By using a preview browser set to the normal email version preview mode, the code of each email component in the HTML code of the target email is rendered to simulate the display of the target email in the format of the normal email version. And by using a preview browser set to the dynamic interactive email version preview mode, the code of each email component in the HTML code of the target email is rendered to simulate the display of the target email in the format of the dynamic interactive email version, thereby generating a target email compatible with both the ordinary email version and the dynamic interactive email version.

7. The method as described in claim 6, characterized in that, The code for a regular email version corresponding to one of the email components includes code for mobile devices and code for desktop computers. The code for a dynamic interactive email version corresponding to one of the email components also includes code for mobile devices and code for desktop computers. The preview browser further includes a mobile preview mode and a desktop preview mode. The step of rendering the dynamic interactive email version code of each email component in the HTML code of the target email using a preview browser set to the dynamic interactive email version preview mode, to simulate displaying the target email according to the format of the dynamic interactive email version, includes: By using a preview browser set to the mobile preview mode of the dynamic interactive email version preview mode, the mobile code corresponding to the dynamic interactive email version of each email component in the HTML code of the target email is rendered to simulate the display of the target email of the dynamic interactive email version according to the mobile display format. By using a preview browser set to the computer preview mode in the dynamic interactive email version preview mode, the computer code corresponding to the dynamic interactive email version of each email component in the HTML code of the target email is rendered, so as to simulate the display of the target email in the dynamic interactive email version according to the computer display format.

8. The method as described in claim 6 or 7, characterized in that, The method further includes: In response to a user's modification operation on the simulated target email, the modification information of the simulated target email is obtained, including the category of the email component in the target email and the configuration data of the variable to be configured of the email component in the target email. Based on the modified information, the target email displayed in the simulation is modified.

9. The method as described in claim 7, characterized in that, The step of rendering the dynamic interactive email version code of each email component in the HTML code of the target email using a preview browser set to the dynamic interactive email version preview mode, so as to simulate the display of the target email according to the format of the dynamic interactive email version, includes: The code of the dynamic interactive email version of each email component in the HTML code of the target email is verified by using a preview browser set to the dynamic interactive email version preview mode. When the dynamic interactive email version code of each email component in the HTML code of the target email passes the verification, the dynamic interactive email version code of each email component in the HTML code of the target email is rendered to simulate the display of the target email in the format of the dynamic interactive email version.

10. The method as described in claim 1, characterized in that, The configuration data for the target email component includes target marketing content, which supports interactive operations.

11. A method for displaying emails, characterized in that, The method is applied to a client, and the method includes: Receive a target email, wherein the target email is generated based on the email generation method described in any one of claims 1 to 10; Determine the email display environment of the client; When the client's email display environment supports dynamic interactive email versions, the target email will be displayed in the format of a dynamic interactive email version.

12. The method as described in claim 11, characterized in that, The target email contains targeted marketing content. After displaying the target email in a dynamic interactive email format, the method further includes: Obtain user interactions with the target marketing content; The response results of the interactive operation are displayed in the display area of ​​the target marketing content.

13. An email generation device, characterized in that, include: The template creation module is used to create a blank email template in response to an email creation request on the email building platform. The email template includes a common content area and a content area to be configured. The common content area contains common email components. The component acquisition module is used to acquire the target email component configured by the user for the content area to be configured from the email component library associated with the email building platform, and obtain the initial email. The email components stored in the email component library are applicable to both ordinary email versions and dynamic interactive email versions. The ordinary email version corresponds to ordinary emails that do not support dynamic interactivity, while the dynamic interactive email version corresponds to dynamic interactive emails that support dynamic interactivity. The data acquisition module is used to acquire the user's configuration data for the target email component and the public email component; The email generation module is used to generate a target email compatible with both the standard email version and the dynamic interactive email version, based on the configuration data of the target email component and the public email component, as well as the initial email, and in accordance with the formats of the standard email version and the dynamic interactive email version.

14. A client, characterized in that, include: An email receiving module is used to receive a target email, wherein the target email is generated based on the email generation method described in any one of claims 1 to 10; The environment determination module is used to determine the email display environment of the client. The email display module is used to display the target email in the format of a dynamic interactive email version when the email display environment of the client supports dynamic interactive email versions.

15. An electronic device, characterized in that, include: Memory and processor; The memory is used to store computer programs; The processor, coupled to the memory, is configured to execute the computer program for: In response to an email creation request, a blank email template is created on the email building platform. The email template includes a common content area and a content area to be configured. The common content area contains common email components. The system retrieves the target email component configured by the user for the content area to be configured from the email component library associated with the email building platform, and obtains the initial email. The email components stored in the email component library are applicable to both ordinary email versions and dynamic interactive email versions. The ordinary email version corresponds to ordinary emails that do not support dynamic interactivity, while the dynamic interactive email version corresponds to dynamic interactive emails that support dynamic interactivity. Obtain the user's configuration data for the target email component and the public email component; Based on the configuration data of the target email component and the public email component, as well as the initial email, a target email compatible with both the regular email version and the dynamic interactive email version is generated, according to the formats of the regular email version and the dynamic interactive email version.

16. An electronic device, characterized in that, include: Memory and processor; The memory is used to store computer programs; The processor, coupled to the memory, is configured to execute the computer program for: Receive a target email, wherein the target email is generated based on the email generation method described in any one of claims 1 to 10; Determine the email display environment on the client side; When the client's email display environment supports dynamic interactive email versions, the target email will be displayed in the format of a dynamic interactive email version.

17. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by the processor, it causes the processor to perform the steps of the email generation method according to any one of claims 1 to 10 or the email display method according to any one of claims 11 to 12.

Citation Information

Patent Citations

  • Method for converting file formats and conversion tool

    CN102609400A

  • Method and system for monitoring automatic transmission of mails, computer device and storage medium

    CN109245988A