Headless commerce platform that helps businesses deliver world-class buying experiences
E-commerce is capturing an ever-increasing market share of shoppers. In addition to the requirements of managing a physical store (like tracking inventory), e-commerce stores have additional challenges, which include getting the product to the customer, using a payment processor, and building relationships with customers. All of these tasks require specialized infrastructure, which in turn interact with your database. A lot of your store’s efficiency and effectiveness rests on the decisions you make about structuring and storing data. In this article, we’ll explore the pros and cons of a NoSQL database for your e-commerce application and use the most popular document store option, MongoDB, in our examples. Note: This data modeling exercise is a response to the  Hacker News comments  about a  previous post  we published about building a scalable e-commerce data model. NoSQL Databases and MongoDB
MongoDB supports  ACID  (atomicity, consistency, isolation, and durability) transactions, and its cloud offering is  PCI DSS  (Payment Card Industry Data Security Standard) compliant. It's one of the best NoSQL options for e-commerce. MongoDB also saves documents in a JSON-like format, which means it's very simple to convert queries and results into a format your frontend code understands. This removes the need to write object-relation mappers (ORMs). Further, MongoDB scales extremely well; it's  designed  to be distributed across multiple machines. NoSQL databases don't come with enforced schemas. Introducing new fields is fast because the database doesn't need to be told you're going to change the format or even the existence of a field. It simply saves what you tell it, no fuss. While this is great for growing businesses where products and checkout workflows evolve rapidly, it does require lots of care to ensure you don't create data that will confuse future developers and application versions. Before starting to model your system, be aware that MongoDB doesn't start with access control. Don't let this default catch you by surprise. Enable access control  before you write real data! PCI compliance requires that some cardholder information is encrypted at rest and in motion. You can enable Transport Layer Security/Secure Sockets Layer (TLS/SSL) encryption to secure network traffic. We'll cover at-rest encryption later in the article, but before going live with any site using MongoDB, go over the  security checklist  to make sure you're up to date on best practices. Data Modeling a Digital Storefront with NoSQL
There’s an almost endless array of features you can build out for an online store, but for the purposes of this article, I’ll focus on modeling just a few: your product catalog, user information, payments, and orders. Product Catalog
In order to sell things, you need to record what you have so clients can browse before committing to a purchase. The bare essentials for a product document are the 
price
sku
. It's also common to include a description, the quantity you have available, and an image file. All examples are run from in the  Mongo shell  and should be adopted to a driver for your application. db.inventory.insertOne( { item: "journal", price: 9.99, qty: 25, size: { h: 14, l: 21, w: 1 }, features: "Beautiful, handmade journal. ", categories: ["writing", "bestseller"], image: "items/journal.jpg"} )
This will return a verification message like this:
{ "acknowledged" : true, "insertedId" : ObjectId("600e814359ba901629a14e13")}
_id
ObjectId
_id
 field is a unique, immutable, indexed identifier. To make your example more lifelike and show the flexibility of MongoDB, use the 
updateOne
 to accommodate two related products with slightly different features, and throw in a promotional offer. db.inventory.updateOne(    { _id: ObjectId("600e814359ba901629a14e13") },    {        $unset: {image: 1, size: 1, qty: 1, price: 1},        $set : { item: "journal", features: ["Inner pocket", "Durable cover"], skus: [ { sku: "154A", price: { base: NumberDecimal(9.99), currency: "USD" }, quantity: 20, options: { size: { h: 14, l: 21, w: 1 }, features: ["72 sheets of premium lined paper"], colors: ["brown", "red"], ruling: "wide", image: "images/journal1.jpg" }            }, { sku: "154B", price: { base: NumberDecimal(14.99), currency: "USD", discount: NumberDecimal(4.00)                }, quantity: 15, options: { size: { h: 18, l: 22, w: 2 }, features: ["140 sheets of premium paper"], colors: ["brown"], ruling: "unlined", image: "images/journals.jpg" }            } ]        }    })
Notice that we changed the structure of the 
features
 field from a string to an array. This highlights the powerful (and dangerous) flexibility of NoSQL databases—you can radically change how data is formatted without a peep from the database. In that regard, command-line SQL is scary, but command-line MongoDB is terrifying. We also settled on a format for  monetary data . Choose one and stick to it throughout your application. You can get a head start on product modeling by scouting the data required by major providers like  Google Marketplace  and  Amazon Marketplace . You can also check out Fabric's  product information management (PIM) system  to learn how an e-commerce platform like Fabric handles product modeling. Query Design Practices
The goal with MongoDB is to structure your schema so your application returns all the data it needs in a single read query. Adding complexity in MongoDB often involves adding  embeddable documents  to a record. Indexing  is important for efficiently scanning for information. Without an index, MongoDB must perform a collection scan, examining every document in a collection before returning the result. Index the fields you'll use to regularly search for products. Users
Once you have an idea of what products you want to offer, think about how to model your users. You want to store information that will allow you to build an ongoing relationship with a customer, such as being able to display items relevant to them. If you’re selling physical products, every customer must have contact information. Here's a simple user profile for a store that needs to ship a physical product. Because you want to enforce unique email addresses for users and use that field to look them up, you'll index that field and make it unique. You could accomplish this with a command like the following:
db.customers.createIndex(  { email: 1 },  { unique: true })
But this example will use the built in 
_id
_id 
field is indexed, unique, and immutable. If a user changes their email, you’ll want to revalidate it. In this case, immutability is an asset; if a user wants to update their email address, MongoDB will demand a new collection entry, and you can be sure that your 
emailVerified
 field gets reset to false. db.customers.insertOne( { _id: "journalfanatic@e/mail.com", fname: "Journal", lname: "Fanatic", hashedAndSaltedPassword: "$1$O3JMY.Tw$AdLnLjQ/5jXF9.MTp3gHv/", emailVerified: false, address: { country: "United States", street1: "99 Main Street", street2: "Apt #3", city: "Boston", state: "MA", zip: "74586" }} )
Customer profiles are a tricky part of e-commerce because they represent people. Unlike products, people are out of your control and constantly changing. They change addresses, want packages delivered to work, and forget their passwords. This is when you have to start thinking about protecting personally identifiable information (PII) and start working toward  Payment Card Industry (PCI) compliance . Becoming PCI compliant is a big undertaking and often one of the compelling cases for using a third-party provider that is already compliant. Let's update our simple example to start handling these issues. First, you'll update the zip code, then add a new delivery address and a date modified field. db.customers.updateOne(    { _id: "journalfanatic@e/mail.com" },    { $set: { "address.zip": "60601", shippingAddress: { street1: "50 Work Street", street2: "Floor 16", city: "Chicago", state: "IL", zip: "60601" } },     $setOnInsert: { dateModified: new Date() }    })
Next, help your model accommodate a password reset request that has an expiration for thirty minutes from now (and update the 
dateModified
field). For performance reasons, you need to be sure that embedded documents don't infinitely expand over time. If a user resets their password a hundred times, and each time it's added to the 
customer
document, pulling information about that customer for a simple action (like a login) will be very resource-intensive. It's better to separate out events that can be repeated many times, like orders, site visits, and password resets into their own collection, and use  document references  to link other collections. To make a reset collection:
db.reset.insertOne({ customerId: "journalfanatic@e/mail.com",    token: "493654",    status: "requested",    expiration: new Date(ISODate().getTime() + (1000 * 60 * 30)),    requestTime: new Date()} )
These tables can get much more complicated very quickly, especially once you start tracking user sessions, presenting customized content, or selling products to teams of users and want to track utilization and distribution of resources. Validation
Validation might not be necessary for your product models, but it's absolutely a requirement for customer-related fields. Addresses, phone numbers, emails, and credit card numbers have to be validated to ensure you're not opening your site to malicious users and to prevent mistakes that stop customers from obtaining your products. MongoDB offers tools for  validating schema  at the collection level. You'll also want to implement application-level validation. Validating uniqueness in MongoDB is only possible by creating an index and requiring it to be unique. A 
customers
 collection already exists in our example, so use runCommand  to add some validation. db.runCommand( { collMod: "customers",   validator: { $jsonSchema: {      bsonType: "object",      required: [ "hashedAndSaltedPassword", "address" ],      properties: {         _id: {            bsonType: "string",            pattern: '.+\@.+\..+',            description: "must match the email pattern" }, hashedAndSaltedPassword: { bsonType: "string",            minLength: 10,            description: "must be a string ten characters long, and is required" }, address: { bsonType: "object",            required: [ "street1", "zip" ],            properties: {                zip: {                    pattern: "^[0-9]{5}(? :-[0-9]{4})?$",                    description: "must match pattern and is required" }, street1: { bsonType: "string",                    description: "must be a string and is required" }, street2: { bsonType: "string",                    description: "must be a string" }            }, description: "must be an object, and is required"         }      }   } },} )
As you can see, writing validation in MongoDB is cumbersome. We only validated six fields, and the code took twice as many lines as creating the record. Libraries like  Mongoose  can make validation easier, while headless commerce APIs from third parties like Fabric] will handle data validation for you. No matter how you decide to implement validation, it's vital for the long-term health of your application that you audit your data and create solid schema and application-level validation for any user-entered fields. Payments
Modeling your payments is where the  security of your application  is most important. It's also the first place where you really need to reference another table. It can be tempting to include payments in the customer table by adding a nested document, but it's not wise. Payment information has specific and extremely important security concerns; it's simpler to audit your PCI compliance practices if payments are not mixed in with a lot of other data. Let's start with a naive (and dangerous!) implementation, then discuss some of the security implications that can improve the model. db.payments.insertOne( { customerId: "journalfanatic@e/mail.com", status: "verified", gateway: "stripe", type: "credit", amount: NumberDecimal(1.00), card: { brand: "Visa", pan: "4242424242424242", expirationMonth: 1, expirationYear: 2090, cvv: 123 }} )
This is a starting point, but e-commerce experts will panic seeing this schema. All the information necessary to use this card is in your database in plaintext, which might be convenient but creates huge legal liabilities for your business. The  PCI DSS  is very clear, don't store cardholder data unless it's necessary, and never store authentication data like the verification code. Encryption
MongoDB offers enterprise clients the ability to  encrypt data files  and perform  automatic client-side encryption . Any user is able to use manual client-side encryption  to encrypt individual fields, then set  schema validations to enforce the encryption. Encrypted fields are stored as binary data ( subtype 6 ). With manual encryption, the  driver for your chosen language  handles applying an appropriate encryption key, as well as the encryption and decryption operations. Following the  PCI DSS  guidelines, you don’t have to encrypt your database fields if you're only storing the last four digits of the card. But be aware that any time you're bundling the Primary Account Number (PAN) with other personally identifiable information, whether at rest or in motion, all that data must be encrypted. Let's try again. db.payments.remove( { } )db.payments.insertOne( { customerId: "journalfanatic@e/mail.com", status: "verified", gateway: "stripe", type: "credit", amount: NumberDecimal(1.00), card: { brand: "Visa", panLastFour: "4242", expirationMonth: 1, expirationYear: 2090, cvvVerified: true    }} )
Now you've removed the authentication data and replaced it with a Boolean, truncated the card number so you're not required to encrypt other information like the expiration date. In this example, you've handled one type of payment option (credit cards), but there are many others, each with its own security requirements and data models. Research what you'll need, and the best practices for handling and storing that information. Tokenization
A great way to remove some of the complexity of PCI compliance is to check if your payment processor (like  Stripe ) offers a tokenization service. Tokenization ) replaces all the information used in payment processing with a token string that your systems can use to track payments. Tokenization is great as it offloads PCI compliance requirements to your payment processor, reducing your liability and simplifying your code. Here's an example of a tokenized model:
db.payments.insertOne( { customerId: "journalfanatic@e/mail.com", status: "awaitingVerification", gateway: "stripe", type: "token", token: "card_1IDHBZFdjJUqVVV2gPlbz8BC"} )
Orders
Orders are where the rubber meets the road. Your customer has a profile that enables you to send them something, and you have products to send them and the ability to accept payments. The order tracks your product through the process of leaving your possession and entering the customer's hands. Orders are another data model for tracking human behavior, so they can get messy. Customers can abandon and modify orders and request refunds. This step in the example brings together all the moving parts of your model: products are purchased by customers with payments. Our model will include things that exist in other collections, like shipping addresses and discounts. In a SQL database, this information would exist as references to existing tables, but remember that in MongoDB you want all the relevant data to be returned in a single read command. It's often more efficient to make a copy of relevant information and store it in the 
orders
 collection. That way, when a user checks on an order, you don't have to read through multiple collections to display the information you want. db.orders.insertOne( { customerId: "journalfanatic@e/mail.com", paymentId: "600e6f37aa2232f59e273082", paymentStatus: "paid", status: "shippedAwaitingDelivery", currency: "USD", totalCost: NumberDecimal(39.85) items: [        { sku: "154B", quantity: "2", price: NumberDecimal(14.99), discount: NumberDecimal(1.00), preTaxTotal: NumberDecimal(27.98), tax: NumberDecimal(1.00), total: NumberDecimal(28.98),  }, { sku: "154A", quantity: "1", price: NumberDecimal(9.99), preTaxTotal: NumberDecimal(9.99), tax: NumberDecimal(.87), total: NumberDecimal(10.86)        }    ], shipping:  { address:{ street1: "50 Work Street", street2: "Floor 16", city: "Chicago", state: "IL", country: "USA", zip: "60601" }, origin: { street1: "1 Penn Ave", street2: "", city: "New York", state: "NY", country: "USA", zipCode: "46281" }, carrier: "USPS", tracking: "123412341234" }} )
Modeling the Whole
Here are all the parts of your NoSQL e-commerce data model so far:
It's an excellent start, but as I stated at the beginning of this guide, there are many facets of an e-commerce store, and we’ve barely brushed the surface. Other valid activities to the model could include adding  product distribution channels , handling image optimization, internationalization, additional  data validation , product categorization, customer customization, subscriptions, recurring payments, taxes, and returns. When modeling your data for e-commerce, mistakes can be costly, and customers will rarely appreciate the amount of effort that goes into creating a finely tuned database. With that in mind, you can consider offloading the management of your e-commerce database to a service. You can make use of low-overhead API requests to store your data and let someone else keep up with industry best practices while you focus on improving your product. Previously published at https://resources.fabric.inc/blog/nosql-ecommerce-data-model

Building a MongoDB NoSQL E-Commerce Data Model

MPs and peers have urged minister Steve Brine (pictured) to immunise boys as well as girls against the HPV virus
The Minister in charge of vaccine policy has been urged by MPs and peers to start immunising boys as well as girls against the cancer-causing Human Papilloma Virus (HPV). In a boost to The Mail on Sunday’s End The Vaccine Apartheid campaign, members of the All-Party Parliamentary Group on Cancer have written to minister Steve Brine calling for an end to the current imbalance. In a separate move Mr Brine’s Labour shadow, Sharon Hodgson, said she welcomed the Government’s recent decision to vaccinate gay and bisexual men. But she added the extension must go further to include all adolescent boys. RELATED ARTICLES
Share
As The Mail on Sunday has revealed, HPV, spread by sexual contact and kissing, causes thousands of devastating cancers every year, many in the head and neck – which in men is the fourth most common type. But although girls aged 12 and 13 have been vaccinated on the NHS since 2008, vaccinating boys is not considered ‘cost-effective’. The letter to Mr Brine is signed by group chairman John Baron, a Conservative MP, and vice chairmen Baroness Morgan of Drefelin and Baroness Masham of Ilton, who are both crossbench peers. Girls aged 12 and 13 have been vaccinated against HPV on the NHS since 2008, but boys haven't and are considered to not be 'cost effective'
It says the NHS computer model used to determine whether gender-neutral vaccination is cost-effective works from ‘very low estimates’ of the proportion of cancers caused by HPV, and ignores projections of their future increase – set to more than double by the 2020s. It adds: ‘Vaccinating only girls is discriminatory against boys – and indeed girls themselves, because it implies they alone are responsible for transmitting HPV, and must bear the burden of the immunisation process.’
The Health Department said it was currently reviewing whether to extend the HPV vaccination to boys.

HPV vaccine should be extended to boys, say MPs and peers

2.55
Rate Article:
Follow >
Click here to remove the Arif Qawi alert
,
Click here to remove the Damian Hinds alert
,
Click here to remove the Facebook alert
Disable alert for Facebook
Click here to remove the Imam Yunus Dudhwala alert
,
Click here to remove the London alert
Disable alert for London
Click here to remove the Neena Lall alert
,
Click here to remove the SHUTTERSTOCK alert
Disable alert for SHUTTERSTOCK
Click here to remove the Sunday Times alert
,
Click here to remove the The Sunday Times alert
Police in the UK have opened an investigation into online abuse targeting the head teacher of an East London primary school where girls younger than the age of eight were banned from wearing the hijab. Neena Lall, the head teacher at St. Stephen’s primary school, along with Arif Qawi, the former chairman of governors, received emails, Facebook posts and other social media messages leading to a complaint being filed with police, according to The Sunday Times. Qawi said he received abusive online messages the day after a report broke about St. Stephen’s last month which mentioned the decision to ban the hijab being worn by young girls. Local Imam Yunus Dudhwala shared Qawi’s Facebook post of The Sunday Times article and invited people to comment online. According to reports, some of the messages that followed were abusive. One described Qawi as a “coconut,” while another comment claimed he was Islamophobic; a third comment called him an “imbecile.”
 
The school has since reversed its hijab ban, with Qawi claiming that the campaign of messages, some abusive, had forced the school to change tack. Qawi has since resigned his position, stating that he left as he did not agree with reversing the hijab ban and to protect the head teacher. “She was told that if I left, the campaign would stop,” he told The Sunday Times. St. Stephen’s school also reportedly forbade Muslim pupils from fasting on school days during Ramadan. Qawi refuted the claim, telling The Sunday Times: “We did not ban fasting altogether but we encouraged (children) to fast in holidays, at weekends and not on the school campus. “Here we are responsible for their health and safety if they pass out on campus ... it is not fair to us.”
 
School inspectors are expected to publish a report praising the school’s leaders and governors this week. Ofsted is expected to criticize the pressures that have fallen on Lall and her management team. The education secretary, Damian Hinds, has defended the school in an interview, saying: “No head teacher or governing body should be subject to the sorts of abuse we have heard reported in these recent incidents.”

UK Teachers Get Hate Mail After Hijab Ban at Primary School, Police Investigate

February 19, 2018 - Written By Dominik Bosnjak
Facebook will start verifying the identities of some ad buyers via traditional mail, primarily in order to avoid another situation in which its social media network is abused for the purposes of spreading politically motivated misinformation, a company official said this weekend. While speaking at a recent conference organized by the National Association of Secretaries of State, Facebook’s global policy programs chief Katie Harbath said the company is planning to start using postcards to authenticate individuals seeking to purchase election-related advertising in the United States. The verification method will only be used in the United States and won’t be employed for political ads that are issue-based, Ms. Harbath said. The postcards Facebook is planning to send via U.S. mail will contain a unique code advertisers will have to input into the social network’s marketing platform after they attempt to purchase ads that promote any individual candidate running for federal office. State-level elections initially won’t require the same authentication method, the executive implied. Ms. Harbath admitted the mechanism won’t be able to solve every related issue but should at the very least prevent the vast majority of foreign agents posing as someone else from purchasing political ads in the United States. Foreign donations meant to contribute to one’s run for any government office are illegal in the U.S. The newly announced solution will be put in place before this year’s congressional mid-terms scheduled to take place in November. The move comes shortly after U.S. Special Counsel Robert Mueller publicized a previously sealed indictment seeking action against three Russian companies and thirteen Russian nationals over espionage and a criminal conspiracy to interfere with the 2016 presidential election with the goal of assisting then-candidate Donald Trump win the run for the highest office in the country. The issue of the so-called “ fake news ” has been widely reported about following the outcome of the election, with the likes of Facebook, Google, and Twitter facing significant pressure from Washington to police their platforms more aggressively and prevent foreign powers from easily meddling in U.S. affairs going forward. Facebook has recently been expanding its content review teams meant to help fight the spread of misinformation on the social network but its efforts are still yielding limited success , according to its own statements.

Facebook To Start Verifying IDs Of Some Ad Buyers Via Mail

Компании собираются поддерживать как молодые команды, так и сформировавшиеся компании. Поделиться
В избранном
Игровое инвестиционное подразделение Games Ventures холдинга Mail.Ru Group договорилось о партнёрстве с компанией Epic Games, которая занимается разработкой и выпуском игр, а также поддержкой движка Unreal Engine. Партнёры собираются вместе поддерживать игровые студии. Epic Games будет искать лучших игровых разработчиков, которым предложат сотрудничать с MRGV, все заявки будет оценивать инвестиционный комитет холдинга. Компаниям предложат финансовую и информационную поддержку. Mail.Ru Group обещает предоставить экспертную поддержку, доступ к аналитическим и маркетинговым инструментам, технологиям в области информационной безопасности, а также различным игровым сервисам и маркетплейсам. Epic Games поможет в разработке игр, в том числе, при использовании движка Unreal Engine. «Объем финансирования для каждого проекта будет определяться каждый раз индивидуально. Инвестиции могут составить как и несколько сотен тысяч, так и несколько миллионов долларов», — сказал vc.ru директор Mail.Ru Games Ventures Илья Карпинский. 27 декабря 2017
{ "author_name": "Andrey Frolov", "author_type": "self", "tags": ["\u043d\u043e\u0432\u043e\u0441\u0442\u0438","\u0438\u043d\u0432\u0435\u0441\u0442\u0438\u0446\u0438\u0438","gamedev"], "comments": 0, "likes": 12, "favorites": 1, "is_advertisement": false, "section_name": "default", "id": "33561", "is_wide": "1" }
Вакансии
голосом Пастернака и смотреть в окно на осень
Подписаться на push-уведомления
Включите уведомления
поддержка
[    {        "id": 1,        "label": "100%×150_Branding_desktop",        "provider": "adfox",        "adaptive": [            "desktop",            "tablet"        ],        "auto_reload": true,        "adfox": {            "ownerId": 228129, "params": {                "pp": "g",                "ps": "bugf",                "p2": "ezfl"            }        }    },    {        "id": 2,        "label": "1200х400",        "provider": "adfox",        "adaptive": [            "phone"        ],        "auto_reload": true,        "adfox": {            "ownerId": 228129,            "params": {                "pp": "g",                "ps": "bugf",                "p2": "ezfn"            }        }    },    {        "id": 3,        "label": "240х200 _ТГБ_desktop",        "provider": "adfox",        "adaptive": [            "desktop"        ],        "adfox": {            "ownerId": 228129,            "params": {                "pp": "g",                "ps": "bugf",                "p2": "fizc"            }        }    },    {        "id": 4,        "label": "240х200_mobile",        "provider": "adfox",        "adaptive": [            "phone"        ],        "adfox": {            "ownerId": 228129,            "params": {                "pp": "g",                "ps": "bugf",                "p2": "flbq"            }        }    },    {        "id": 5,        "label": "300x500_desktop",        "provider": "adfox",        "adaptive": [            "desktop"        ],        "adfox": {            "ownerId": 228129,            "params": {                "pp": "g",                "ps": "bugf",                "p2": "ezfk"            }        }    },    {        "id": 6,        "label": "1180х250_Interpool_баннер над комментариями_Desktop",        "provider": "adfox",        "adaptive": [            "desktop",            "tablet"        ],        "adfox": {            "ownerId": 228129,            "params": {                "pp": "h",                "ps": "bugf",                "p2": "ffyh"            }        }    },    {        "id": 7,        "label": "Article Footer 100%_desktop_mobile",        "provider": "adfox",        "adaptive": [            "desktop",            "tablet",            "phone"        ],        "adfox": {            "ownerId": 228129,            "params": {                "pp": "g",                "ps": "bugf",                "p2": "fjxb"            }        }    },    {        "id": 8,        "label": "Fullscreen Desktop",        "provider": "adfox",        "adaptive": [            "desktop",            "tablet"        ],        "auto_reload": true,        "adfox": {            "ownerId": 228129,            "params": {                "pp": "g",                "ps": "bugf",                "p2": "fjoh"            }        }    },    {        "id": 9,        "label": "Fullscreen Mobile",        "provider": "adfox",        "adaptive": [            "phone"        ],        "auto_reload": true,        "adfox": {            "ownerId": 228129,            "params": {                "pp": "g",                "ps": "bugf",                "p2": "fjog"            }        }    },    {        "id": 10,        "disable": true,        "label": "Native Partner Desktop",        "provider": "adfox",        "adaptive": [            "desktop",            "tablet"        ],        "adfox": {            "ownerId": 228129,            "params": {                "pp": "g",                "ps": "clmf",                "p2": "fmyb"            }        }    },    {        "id": 11,        "disable": true,        "label": "Native Partner Mobile",        "provider": "adfox",        "adaptive": [            "phone"        ],        "adfox": {            "ownerId": 228129,            "params": {                "pp": "g",                "ps": "clmf",                "p2": "fmyc"            }        }    },    {        "id": 12,        "label": "Кнопка в шапке",        "provider": "adfox",        "adaptive": [            "desktop"        ],        "adfox": {            "ownerId": 228129,            "params": {                "p1": "bscsh",                "p2": "fdhx"            }        }    },    {        "id": 13,        "label": "DM InPage Video PartnerCode",        "provider": "adfox",        "adaptive": [            "desktop",            "tablet",            "phone"        ],        "adfox_method": "create",        "adfox": {            "ownerId": 228129,            "params": {                "pp": "h",                "ps": "bugf",                "p2": "flvn"            }        }    },    {        "id": 14,        "label": "Yandex context video banner",        "provider": "yandex",        "yandex": {            "block_id": "VI-223676-0",            "render_to": "inpage_VI-223676-0-158433683",            "adfox_url": "//ads.adfox.ru/228129/getCode?p1=bxbwd&p2=fpjw&puid1=&puid2=&puid3=&puid4=&puid8=&puid9=&puid21=&puid22=&puid31=&fmt=1&pr="        }    },    {        "id": 15,        "label": "Плашка на главной",        "provider": "adfox",        "adaptive": [            "desktop",            "tablet",            "phone"        ],        "adfox": {            "ownerId": 228129,            "params": {                "p1": "byudx",                "p2": "ftjf"            }        }    },    {        "id": 16,        "label": "Кнопка в шапке мобайл",        "provider": "adfox",        "adaptive": [            "tablet",            "phone"        ],        "adfox": {            "ownerId": 228129,            "params": {                "p1": "byzqf",                "p2": "ftwx"            }        }    }]

Mail.Ru Group и Epic Games займутся инвестициями в игровые студии

Post Office is a retail network and financial services chain.

Post Office

The South African Post Office has signed an agreement with Mail that it says will give online traders better access into all of Southern Africa , including rural areas .

Post Office in e-commerce deal with Mail Americas

Wibbitz is an AI-powered platform supporting custom branded, short-form video creation and distribution for publishers, enabling them to increase audience engagement and ad revenues across desktop, mobile, and social. On November 10th, 2021, Wibbitz was acquired by Vimeo. Terms of the transaction were not disclosed.

Wibbitz

DLJMB

252 of the biggest, costliest startup failures of all time

Acquired

Mail.com personalized free web-based email. Mail.com aims to provide consumers with web-based e-mail services, which are accessible from any computer connected to the Internet, anywhere in the world. nnTo signup for a mail.com e-mail account click here.

Date	9/22/2010
Round	Acquired
Amount
Investors	United Internet
Valuation
Revenue	0 FY undefined
Sources	1

First funding	9/22/2010
Last Funding	9/22/2010
Investor	United Internet
Rounds	1 Acquired
Board Seats
Type	Corporation
Location	Germany

Date	6/24/2009
Investment Stage
Companies	DeadlineHollywoodDaily.com
Valuation	$99M
Total Funding
Note	Acquired
Sources	1

Wells Fargo Success Story

Professional Services

Platform Overview

Mail.com

Investors Count

Funding, Valuation & Revenue

This profile has not been claimed.

Mail.com Investors

Mail.com Acquisitions

1 Acquisition

Discover the right solution for your team